<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 11 May 2018, at 03:02, Viktor Dukhovni <<a href="mailto:ietf-dane@dukhovni.org" class="">ietf-dane@dukhovni.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><br class="">The below have all been delegated for some time, and yet the name<br class="">collision sentinels are still in place:<br class=""><br class="">example.etisalat. A 127.0.53.53<br class="">example.arab. A 127.0.53.53<br class="">example.xn--mgbaakc7dvf. A 127.0.53.53<br class="">example.xn--mxtq1m. A 127.0.53.53<br class="">example.xn--ngbrx. A 127.0.53.53<br class="">example.politie. A 127.0.53.53<br class=""><br class="">Is that intentional, or neglected cleanup?</div></div></blockquote><br class=""></div><div>The later, usually. But they are only out of compliance if there are other names in zone besides nic.TLD. You can find at this link (<a href="https://community.icann.org/download/attachments/58735971/New gTLD Subsequent Procedures Request for Data (CI).pdf?version=1&modificationDate=1505866493000&api=v2" class="">https://community.icann.org/download/attachments/58735971/New%20gTLD%20Subsequent%20Procedures%20Request%20for%20Data%20%28CI%29.pdf?version=1&modificationDate=1505866493000&api=v2</a>) some statistics on how it happened with other gTLDs. </div><div><br class=""></div><div>This is one of the reasons that made the workgroup looking at this topic recommend ICANN to run controlled interruption before TLDs are delegated to registries. </div><div><br class=""></div><div><br class=""></div><div>Rubens</div><div><br class=""></div><div><br class=""></div></body></html>