<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">The version sent out a few minutes ago contained an edit which was misapplied.<div><br></div><div>4.10.6(a) should be limited to /14.</div><div>4.10.6(b) should be limited to /16.</div><div><br></div><div>The corrected text appears below:</div><div><br></div><div><div><font class="Apple-style-span" face="Monaco">Draft Policy 2010-13: Permitted Uses of Space Reserved under NRPM 4.10</font></div><div><font class="Apple-style-span" face="Monaco">Proposal Originator: Owen DeLong </font></div><div><font class="Apple-style-span" face="Monaco">Proposal Version: 1.9</font></div><div><font class="Apple-style-span" face="Monaco">Date: 18 June 2010</font></div><div><font class="Apple-style-span" face="Monaco">Proposal type: modify</font></div><div><font class="Apple-style-span" face="Monaco">Policy term: permanent</font></div><div><font class="Apple-style-span" face="Monaco">Policy statement:</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco">Rename section 4.10: "Dedicated IPv4 pool to facilitate IPv6 Deployment"</font></div><div><font class="Apple-style-span" face="Monaco">Amend section 4.10 replacing</font></div><div><font class="Apple-style-span" face="Monaco"> "When ARIN receives its last /8 IPv4 allocation from IANA, a</font></div><div><font class="Apple-style-span" face="Monaco"> contiguous /10 IPv4 block will be set aside and dedicated to</font></div><div><font class="Apple-style-span" face="Monaco"> facilitate IPv6 deployment."</font></div><div><font class="Apple-style-span" face="Monaco">with</font></div><div><font class="Apple-style-span" face="Monaco"> "When ARIN receives its last /8 IPv4 allocation from IANA, that</font></div><div><font class="Apple-style-span" face="Monaco"> /8 will form a dedicated pool to facilitate IPv6 Deployment."</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco">and replacing</font></div><div><font class="Apple-style-span" face="Monaco"> "...when possible within that /10 block."</font></div><div><font class="Apple-style-span" face="Monaco">with</font></div><div><font class="Apple-style-span" face="Monaco"> "...when possible within this pool, particularly within the last</font></div><div><font class="Apple-style-span" face="Monaco"> /8 block. Following IANA depletion, all IPv4 address space returned</font></div><div><font class="Apple-style-span" face="Monaco"> directly to ARIN except space to be reissued under an 8.3 directed</font></div><div><font class="Apple-style-span" face="Monaco"> transfer will be added to this pool." .</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco">and Strike</font></div><div><font class="Apple-style-span" face="Monaco"> "This block will be subject to a minimum size allocation of /28</font></div><div><font class="Apple-style-span" face="Monaco"> and a maximum size allocation of /24." from section 4.10.</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco">Amend 4.10.1 replacing</font></div><div><font class="Apple-style-span" face="Monaco"> "...under this policy in the preceding..."</font></div><div><font class="Apple-style-span" face="Monaco">with</font></div><div><font class="Apple-style-span" face="Monaco"> "...under each provision of this policy (as detailed in</font></div><div><font class="Apple-style-span" face="Monaco"> section 4.10.6) in the preceding..."</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco">Add the following to section 4.10 of the NRPM</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco">6. Specific types of transitional uses have specific requirements:</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco"> (a) An ISP/LIR may request a block no smaller than a /24 nor larger than</font></div><div><font class="Apple-style-span" face="Monaco"> a /18 to be used to provide single IPv4 /32s to their customers which</font></div><div><font class="Apple-style-span" face="Monaco"> could justify a /28 or more of IPv4 under ARIN policies in effect at</font></div><div><font class="Apple-style-span" face="Monaco"> the time of IANA depletion.</font></div><div><font class="Apple-style-span" face="Monaco"> 1. No customer may receive more than a single IPv4 /32 under this</font></div><div><font class="Apple-style-span" face="Monaco"> provision.</font></div><div><font class="Apple-style-span" face="Monaco"> 2. The customer must not have any other IPv4 allocations or assignments</font></div><div><font class="Apple-style-span" face="Monaco"> from the provider at the time of this assignment.</font></div><div><font class="Apple-style-span" face="Monaco"> 3. The customer must not have any direct assignments from ARIN at the</font></div><div><font class="Apple-style-span" face="Monaco"> time of this assignment.</font></div><div><font class="Apple-style-span" face="Monaco"> 4. The customer must not have more than a single IPv4 /32 from any</font></div><div><font class="Apple-style-span" face="Monaco"> other provider at the time of this assignment.</font></div><div><font class="Apple-style-span" face="Monaco"> 5. The customer must have IPv6 addresses with IPv6 connectivity to</font></div><div><font class="Apple-style-span" face="Monaco"> the ISP/LIR (must be dual-stacked).</font></div><div><font class="Apple-style-span" face="Monaco"> 6. The ISP/LIR must demonstrate that it already provides IPv6</font></div><div><font class="Apple-style-span" face="Monaco"> addressing and connectivity to at least one existing customer</font></div><div><font class="Apple-style-span" face="Monaco"> for each /32 requested, up to 90% of their total customer base.</font></div><div><font class="Apple-style-span" face="Monaco"> 7. No organization shall receive more than a total of a /14 or</font></div><div><font class="Apple-style-span" face="Monaco"> equivalent under this section.</font></div><div><font class="Apple-style-span" face="Monaco"> (b) An ISP/LIR or End user organization may request a block no</font></div><div><font class="Apple-style-span" face="Monaco"> smaller than a /28 and no larger than a /22 to provide single</font></div><div><font class="Apple-style-span" face="Monaco"> IPv4 /32s to each physical server used to provide Internet</font></div><div><font class="Apple-style-span" face="Monaco"> reachable content.</font></div><div><font class="Apple-style-span" face="Monaco"> 1. Space issued under this provision is an assignment, not an</font></div><div><font class="Apple-style-span" face="Monaco"> allocation. An LIR may not distribute this space to their customers.</font></div><div><font class="Apple-style-span" face="Monaco"> 2. No server may recieve more than a single IPv4 /32 under this</font></div><div><font class="Apple-style-span" face="Monaco"> provision.</font></div><div><font class="Apple-style-span" face="Monaco"> 3. The server must have IPv6 addresses with IPv6 connectivity (must</font></div><div><font class="Apple-style-span" face="Monaco"> be dual-stacked).</font></div><div><font class="Apple-style-span" face="Monaco"> 4. The recieving organization must demonstrate that it already</font></div><div><font class="Apple-style-span" face="Monaco"> provides IPv6 addressing and connectivity to at least one</font></div><div><font class="Apple-style-span" face="Monaco"> existing server in addition to the server for which each</font></div><div><font class="Apple-style-span" face="Monaco"> /32 is requested, up to 100% of their total server base.</font></div><div><font class="Apple-style-span" face="Monaco"> (organizations which can show 100% dual stack are exempt</font></div><div><font class="Apple-style-span" face="Monaco"> from this requirement).</font></div><div><font class="Apple-style-span" face="Monaco"> 5. The recieving organization must enable all of their content</font></div><div><font class="Apple-style-span" face="Monaco"> on the following schedule:</font></div><div><font class="Apple-style-span" face="Monaco"> 25% of content IPv6 reachable within six months of receiving</font></div><div><font class="Apple-style-span" face="Monaco"> their first addresses under this policy</font></div><div><font class="Apple-style-span" face="Monaco"> 50% of content IPv6 reachable within one year of receiving</font></div><div><font class="Apple-style-span" face="Monaco"> their first addresses under this policy</font></div><div><font class="Apple-style-span" face="Monaco"> 75% of content IPv6 reachable within 18 months of receiving</font></div><div><font class="Apple-style-span" face="Monaco"> their first addresses under this policy</font></div><div><font class="Apple-style-span" face="Monaco"> 90% of content IPv6 reachable within 24 months of receiving</font></div><div><font class="Apple-style-span" face="Monaco"> their first addresses under this policy</font></div><div><font class="Apple-style-span" face="Monaco"> 6. No organization shall receive more than a total of a /16 or</font></div><div><font class="Apple-style-span" face="Monaco"> equivalent under this section.</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco"> (c) An ISP/LIR or End user organization may request a block no smaller</font></div><div><font class="Apple-style-span" face="Monaco"> than a /28 and no larger than a /24 for purposes relevant to their</font></div><div><font class="Apple-style-span" face="Monaco"> ability to deploy IPv6 as specified in section 4.12.</font></div><div><font class="Apple-style-span" face="Monaco"> 1. Space issued under this provision is an assignment, not an</font></div><div><font class="Apple-style-span" face="Monaco"> allocation. An LIR may not distribute this space to their customers.</font></div><div><font class="Apple-style-span" face="Monaco"> 2. Space issued under this provision must be used to provide the</font></div><div><font class="Apple-style-span" face="Monaco"> required public IPv4 address(es) for transitional technologies</font></div><div><font class="Apple-style-span" face="Monaco"> operated by the recipient organization. Specific examples of</font></div><div><font class="Apple-style-span" face="Monaco"> permitted uses are:</font></div><div><font class="Apple-style-span" face="Monaco"> a. Large scale or "Carrier Grade" NAT</font></div><div><font class="Apple-style-span" face="Monaco"> b. NAT-PT</font></div><div><font class="Apple-style-span" face="Monaco"> c. DS-LITE/B4/AFTeR</font></div><div><font class="Apple-style-span" face="Monaco"> d. DNS64 or other transitional DNS enablers</font></div><div><font class="Apple-style-span" face="Monaco"> e. For other technologies of similar purpose and scope.</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco"> (d) An ISP/LIR or End user organization may request a block no smaller</font></div><div><font class="Apple-style-span" face="Monaco"> than a /28 and no larger than a /24 for other transitional</font></div><div><font class="Apple-style-span" face="Monaco"> technologies not envisioned at the time of this proposal, but,</font></div><div><font class="Apple-style-span" face="Monaco"> in no case for general IPv4 addressing provided to customers.</font></div><div><font class="Apple-style-span" face="Monaco"> (e) A /10 from the final /8 shall be reserved for issuance under</font></div><div><font class="Apple-style-span" face="Monaco"> 4.10.6(c) and 4.10.6(d). In no case shall any addresses from</font></div><div><font class="Apple-style-span" face="Monaco"> this /10 be issued under 4.10.6(a) and 4.10.6(b).</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco">Add the following to section 4 of the NRPM</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco">4.11 Required utilization for subsequent allocation under section 4.10</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco"> No organization shall receive more than one allocation or assignment</font></div><div><font class="Apple-style-span" face="Monaco"> under section 4.10 unless all prior space issued under 4.10 meets</font></div><div><font class="Apple-style-span" face="Monaco"> the utilization requirements of this section:</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco"> 1. The most recent 4.10 allocation/assignment must be at least</font></div><div><font class="Apple-style-span" face="Monaco"> 80% utilized.</font></div><div><font class="Apple-style-span" face="Monaco"> 2. All utilization must be permitted under section 4.10</font></div><div><font class="Apple-style-span" face="Monaco"> 3. All prior 4.10 allocation/assignments must be at least 90% utilized.</font></div><div><font class="Apple-style-span" face="Monaco"> 4. For purposes of this computation, space received under each</font></div><div><font class="Apple-style-span" face="Monaco"> provision shall be considered separately if an organization has</font></div><div><font class="Apple-style-span" face="Monaco"> received resources through multiple provisions.</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco">4.12 Quarterly Utilization Monitoring</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco"> Allocations and assignments under section 4.10 shall be subject</font></div><div><font class="Apple-style-span" face="Monaco"> to quarterly verification of utilization.</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco"> 1. An organization which is not meeting their utilization targets</font></div><div><font class="Apple-style-span" face="Monaco"> may have their allocation or assignment reduced accordingly</font></div><div><font class="Apple-style-span" face="Monaco"> with the reclaimed portions going back to ARIN for distribution</font></div><div><font class="Apple-style-span" face="Monaco"> to other organizations. Space reclaimed in this manner shall be</font></div><div><font class="Apple-style-span" face="Monaco"> exempt from any requirement to return space to the IANA.</font></div><div><font class="Apple-style-span" face="Monaco"> 2. An organization which is using space received under 4.10 in a</font></div><div><font class="Apple-style-span" face="Monaco"> manner contrary to 4.10 et seq. may have their allocation or</font></div><div><font class="Apple-style-span" face="Monaco"> assignment reduced or revoked with reclaimed portions going back</font></div><div><font class="Apple-style-span" face="Monaco"> to ARIN for distribution to other organizations. Space reclaimed</font></div><div><font class="Apple-style-span" face="Monaco"> in this manner shall be exempt from any requirement to return</font></div><div><font class="Apple-style-span" face="Monaco"> space to the IANA.</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco">Rationale:</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco">The current terminology in section 4.10 is vague and could allow a</font></div><div><font class="Apple-style-span" face="Monaco">variety of interpretations which could lead to allocations or assignments</font></div><div><font class="Apple-style-span" face="Monaco">being made to ISPs intending to misuse the space for general deployment by</font></div><div><font class="Apple-style-span" face="Monaco">using IPv6 overlay technologies as a "IPv6 deployments" requiring IPv4</font></div><div><font class="Apple-style-span" face="Monaco">space for transition. For example, the current policy could be interpreted</font></div><div><font class="Apple-style-span" face="Monaco">to enable an ISP to require IPv4 addresses for all IPv6 customers to roll</font></div><div><font class="Apple-style-span" face="Monaco">IPv6 out as 6rd to customers who would be otherwise unable to get IPv4 space.</font></div><div><font class="Apple-style-span" face="Monaco">This is clearly outside of the original intent of the proposal which</font></div><div><font class="Apple-style-span" face="Monaco">created 4.10 (6rd was not yet envisioned at the time that was written).</font></div><div><font class="Apple-style-span" face="Monaco">This proposal seeks to clarify that intent and tighten up the requirements</font></div><div><font class="Apple-style-span" face="Monaco">for organizations seeking to get space from this limited final resource</font></div><div><font class="Apple-style-span" face="Monaco">so that it truly is available to facilitate transitional technologies.</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco">It also expands the scope of 4.10 to include more address space to be</font></div><div><font class="Apple-style-span" face="Monaco">given out in manners that facilitate transition, but, are not directly</font></div><div><font class="Apple-style-span" face="Monaco">transitional technologies per se. These allocatios and assignments</font></div><div><font class="Apple-style-span" face="Monaco">require specific IPv6 deployment targets to be met and have much</font></div><div><font class="Apple-style-span" face="Monaco">stricter limitations on the utilization of IPv4 addresses issued</font></div><div><font class="Apple-style-span" face="Monaco">from this pool.</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco">Timetable for implementation: immediate</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco">For reference, here is the current text of 4.10</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco">4.10 Dedicated IPv4 block to facilitate IPv6 Deployment</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco">When ARIN receives its last /8 IPv4 allocation from IANA, a</font></div><div><font class="Apple-style-span" face="Monaco">contiguous /10 IPv4 block will be set aside and dedicated to</font></div><div><font class="Apple-style-span" face="Monaco">facilitate IPv6 deployment. Allocations and assignments from</font></div><div><font class="Apple-style-span" face="Monaco">this block must be justified by immediate IPv6 deployment</font></div><div><font class="Apple-style-span" face="Monaco">requirements.</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco">Examples of such needs include:</font></div><div><font class="Apple-style-span" face="Monaco"> IPv4 addresses for key dual stack DNS servers, and</font></div><div><font class="Apple-style-span" face="Monaco"> NAT-PT or NAT464 translators.</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco">ARIN staff will use their discretion when evaluating justifications.</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco">This block will be subject to a minimum size allocation</font></div><div><font class="Apple-style-span" face="Monaco">of /28 and a maximum size allocation of /24. ARIN</font></div><div><font class="Apple-style-span" face="Monaco">should use sparse allocation when possible within that /10 block.</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco">In order to receive an allocation or assignment under this policy:</font></div><div><font class="Apple-style-span" face="Monaco"> 1. the applicant may not have received resources under</font></div><div><font class="Apple-style-span" face="Monaco"> this policy in the preceding six months;</font></div><div><font class="Apple-style-span" face="Monaco"> 2. previous allocations/assignments under this policy must</font></div><div><font class="Apple-style-span" face="Monaco"> continue to meet the justification requirements of this policy;</font></div><div><font class="Apple-style-span" face="Monaco"> 3. previous allocations/assignments under this policy must</font></div><div><font class="Apple-style-span" face="Monaco"> meet the utilization requirements of end user assignments;</font></div><div><font class="Apple-style-span" face="Monaco"> 4. the applicant must demonstrate that no other allocations or</font></div><div><font class="Apple-style-span" face="Monaco"> assignments will meet this need;</font></div><div><font class="Apple-style-span" face="Monaco"> 5. on subsequent allocation under this policy, ARIN staff may</font></div><div><font class="Apple-style-span" face="Monaco"> require applicants to renumber out of previously</font></div><div><font class="Apple-style-span" face="Monaco"> allocated / assigned space under this policy in order to</font></div><div><font class="Apple-style-span" face="Monaco"> minimize non-contiguous allocations.</font></div></div><div><br></div></body></html>