<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On 22/03/2010, at 9:43 AM, Alexander Mayrhofer wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><blockquote type="cite">There's not much chance of that. The DNS requirements in <br></blockquote><blockquote type="cite">ICANN's gTLD <br></blockquote><blockquote type="cite">contracts are rather low: a brush from a feather rather than a <br></blockquote><blockquote type="cite">pummelling.<br></blockquote><br>Have you looked at the new gTLD documents yet? Those are requiring 100%<br>uptime for the "service" (defined as at least 2 out of the set of<br>authoritative nameserver ip addresses have service), *plus* 99.9% of<br>uptime for each and every ip address per month (which is 43 minutes of<br>outage). <font class="Apple-style-span" color="#000000"><font class="Apple-style-span" color="#144FAE"><br></font></font></div></blockquote><br></div><div>So, for the sake of clarity, it is probably worth pointing out there are several different name server requirements under the auspices of ICANN:</div><div><br></div><div>1. Requirements on all TLDs</div><div><br></div><div>These are designed to be absolute minimum criteria, and are checked by IANA staff in implementing root zone change requests. They are listed at <a href="http://www.iana.org/procedures/nameserver-requirements.html">http://www.iana.org/procedures/nameserver-requirements.html</a>. These are clearly not designed to be best practice, rather a set of objective baseline criteria that can be checked to identify configuration problems or errors in intent.</div><div><br></div><div>2. Requirements on existing gTLDs</div><div><br></div><div>These are spelled out in the individual contracts that existing gTLD operators have with ICANN. See, for example, Section 7 of <a href="http://www.icann.org/en/tlds/agreements/tel/appendix-7-07apr06.htm">http://www.icann.org/en/tlds/agreements/tel/appendix-7-07apr06.htm</a></div><div><br></div><div>3. Proposed requirements for future gTLDs</div><div><br></div><div>These are those mentioned by Alexander, which are still in draft and subject to change (and of course, feedback is welcome on revising them, if they are not considered appropriate).</div><div><br></div><div>kim</div></body></html>