[RFCI-Discuss] TLD wildcards

[Frank Ellermann]

Hi, 

I just stumbled over interesting articles about TLD wildcards:
<http://weblog.johnlevine.com/ICANN/morewild.writeback>

Here's a wildcard list generated by a quick and dirty script:

TLD ac     apparently uses a wildcard nameservices.net
TLD io     apparently uses a wildcard nameservices.net
TLD museum apparently uses a wildcard index.museum
TLD nu     apparently uses a wildcard webrouter0.telia.nic.nu
TLD sh     apparently uses a wildcard nameservices.net
TLD st     apparently uses a wildcard mailgw.nic.st
TLD tm     apparently uses a wildcard nameservices.net
TLD vg     apparently uses a wildcard IP 64.74.134.64
TLD ws     apparently uses a wildcard mailrelay.33.website.ws
TLD ph     apparently uses a wildcard unreg.emc.com.ph
TLD pw     apparently uses a wildcard pwregistry.pw
TLD tk     apparently uses a wildcard HOSTED-BY.DOT.TK
TLD cg     apparently uses a wildcard IP 64.22.91.27
TLD rw     apparently uses a wildcard IP 64.22.91.27
TLD cm     apparently uses a wildcard vcr-ha-cluster.agoga.com

In the sitefinder-verisign case ICANN and IAB found some 
formula why this practice is wrong.  Maybe it's up to the
communities in the ccTLDs to redelegate their ccTLD to a
trustworthy entity.  What could / should RFCI do about it ?

Frank