[Gnso-newgtld-wg-wt4] ICANN Compliance x Name Collisions

Rubens Kuhl rubensk at nic.br
Wed Sep 13 00:07:21 UTC 2017

https://www.icann.org/en/system/files/files/compliance-update-jun17-en.pdf <https://www.icann.org/en/system/files/files/compliance-update-jun17-en.pdf>

At the end of page 3:
"This quarter, the ICANN Contractual Compliance team also processed referrals from ICANN Technical Services regarding controlled interruption wildcard record violations. Approximately 45 TLDs were found to have activated names (other than nic.tld) in the DNS, while controlled interruption wildcard records continued to exist in their zone file."

It seems a high number of TLDs are still having issues with the 2012-round Name Collision Framework, long after delegation. This specific data point suggests that one of the suggested modifications, having ICANN or an ICANN contractor run the process before the TLD is delegated to the approved applicant, would not only address the time-to-market problem seen by registries but also improve compliance with the framework as designed.

We should note though that this report doesn't mention distribution by registry service provider; all 45 TLDs could share a single back-end for all we know.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg-wt4/attachments/20170912/9afe0b62/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg-wt4/attachments/20170912/9afe0b62/signature.asc>

More information about the Gnso-newgtld-wg-wt4 mailing list