[council] FW: FW: Revised Resolution regarding Verisign Registry Site Finder Service

Cade,Marilyn S - LGCRP mcade at att.com
Thu Sep 25 14:00:41 UTC 2003

> Whereas, on September 15, 2003, VeriSign Registry introduced a wild 
> card registry service into .com and .net zones that creates a 
> registry-synthesized address record in response to look ups of domain 
> names that are not present in the zone. This registry service changes 
> the routing of traffic by directing traffic that would have otherwise 
> resulted in a 'no domain' notification to the "sender" to a VeriSign 
> operated web site with search results and links to paid > advertisements.

Whereas the IAB commentary published its architectural Concerns on the 
> use of DNS wildcards on 19 September 2003.

>Whereas VeriSign Registry on 21 September 2003, responded to Paul 
> Twomey, President and CEO, ICANN, acknowledging ICANN's advisory and 
> declining to suspend the service until they (VeriSign) has an 
> opportunity to collect and review available data.
Whereas the Security and Stability Advisory Committee, 22 September 
> 2003,has published its recommendations regarding VeriSign's Introduction of Wild Card Response to Uninstantiated Domains within COM and NET on the ICANN web site at www.icann.org
> Therefore, the gNSO Council:
> Supports ICANN's actions to
> 1) monitor community reaction and experiences with the new registry 
> service
> 2) request advice from the Security and Stability Advisory Committee 
> and from the IAB on the impact of change introduced by the registry 
> service of VeriSign
> 3) encourages broad participation by the community in the upcoming 
> meeting hosted by the Security and Stability Advisory Committee
> Pledges to
> 1) work cooperatively to ensure full opportunity to fully understand 
> the service, its implications for the DNS, and any implications for the need for
Policy development within the scope of the gNSO.

More information about the council mailing list