<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><blockquote type="cite" class=""><div dir="ltr" class=""><div class="gmail_extra" style="font-size:12.8px"><div class="gmail_quote"><span class="im"><div class=""><span style="font-size: 12.8px;" class="">In the ARIN region, TLD Registry Operators can get a block under the Critical Infra definition. We can debate wether or not they are indeed "critical" I would tend to want to leave them out of this policy.</span></div></span></div></div></div></blockquote><div><br class=""></div>In the ARIN region, operators of gTLD name servers cannot use the reservation, but they can justify under critical infrastructure. Previous policy allowed the established gTLD operators to pull from the reserved pool.</div><div><br class=""></div><div>The operative language from the ARIN NRPM is:</div><div><br class=""></div><div><h4 style="margin: 1em 0px 0.5em; padding: 0px; border: 0px; font-family: 'Open Sans', arial, helvetica, sans-serif; line-height: 16px; font-size: 1.2em !important;" class="">4.4. Micro-allocation</h4><div style="margin: 0.5em 0px; padding: 0px; border: 0px; font-size: 1.2em; line-height: 1.5em; font-family: arial, helvetica, sans-serif;" class="">ARIN will make IPv4 micro-allocations to critical infrastructure providers of the Internet, including public exchange points, core DNS service providers (e.g. ICANN-sanctioned root and ccTLD operators) as well as the RIRs and IANA. These allocations will be no smaller than a /24. Multiple allocations may be granted in certain situations.</div><div style="margin: 0.5em 0px; padding: 0px; border: 0px; font-size: 1.2em; line-height: 1.5em; font-family: arial, helvetica, sans-serif;" class="">Exchange point allocations MUST be allocated from specific blocks reserved only for this purpose. All other micro-allocations WILL be allocated out of other blocks reserved for micro-allocation purposes. ARIN will make a list of these blocks publicly available.</div><div style="margin: 0.5em 0px; padding: 0px; border: 0px; font-size: 1.2em; line-height: 1.5em; font-family: arial, helvetica, sans-serif;" class="">Exchange point operators must provide justification for the allocation, including: connection policy, location, other participants (minimum of three total), ASN, and contact information. ISPs and other organizations receiving these micro-allocations will be charged under the ISP fee schedule, while end-users will be charged under the fee schedule for end-users. This policy does not preclude exchange point operators from requesting address space under other policies.</div><div style="margin: 0.5em 0px; padding: 0px; border: 0px; font-size: 1.2em; line-height: 1.5em; font-family: arial, helvetica, sans-serif;" class="">ARIN will place an equivalent of a /15 of IPv4 address space in a reserve for Critical Infrastructure, as defined in section 4.4.</div><div style="margin: 0.5em 0px; padding: 0px; border: 0px; font-size: 1.2em; line-height: 1.5em; font-family: arial, helvetica, sans-serif;" class="">ICANN-sanctioned gTLD operators may justify up to the equivalent of an IPv4 /23 block for each authorized new gTLD, allocated from the free pool or received via transfer, but not from the above reservation. This limit of a /23 equivalent per gTLD does not apply to gTLD allocations made under previous policy.</div><div class=""><br class=""></div></div><div><br class=""></div><div><br class=""><blockquote type="cite" class=""><div dir="ltr" class=""><div class="gmail_extra" style="font-size:12.8px"><div class="gmail_quote"><div class=""><span style="font-size: 12.8px;" class="">Most TLD registry operators employ a back-end Registry Operator (Verisign, afilias, Neustar, etc). Do we want these entities to be using AfriNIC IP space if they aren't using them in Africa?</span></div></div></div></div></blockquote><div><br class=""></div>The policy as written in the ARIN region is implemented strictly for support of the name servers for those domains, not for the various other systems involved in administering the other aspects of the TLD.</div><div><br class=""></div><div>Owen</div><div><br class=""></div><br class=""></body></html>