<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><br class=""></div><div class=""><a href="https://www.icann.org/en/system/files/files/compliance-update-jun17-en.pdf" class="">https://www.icann.org/en/system/files/files/compliance-update-jun17-en.pdf</a></div><div class=""><br class=""></div><div class="">At the end of page 3:</div><div class="">"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."</div><div class=""><br class=""></div><div class="">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. </div><div class=""><br class=""></div><div class="">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. </div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Rubens</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div></body></html>