<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><font class="Apple-style-span" face="Monaco" size="3"><span class="Apple-style-span" style="font-size: 12px;">TEMPLATE: ARIN-POLICY-PROPOSAL-TEMPLATE-2.0</span></font></div><div><font class="Apple-style-span" face="Monaco" size="3"><span class="Apple-style-span" style="font-size: 12px;"><br></span></font></div><div><font class="Apple-style-span" face="Monaco" size="3"><span class="Apple-style-span" style="font-size: 12px;">1. Policy Proposal Name: /24 End User Minimum Allocation Unit</span></font></div><div><font class="Apple-style-span" face="Monaco" size="3"><span class="Apple-style-span" style="font-size: 12px;">2. Proposal Originator</span></font></div><div><font class="Apple-style-span" face="Monaco" size="3"><span class="Apple-style-span" style="font-size: 12px;"> a. name: Owen DeLong</span></font></div><div><font class="Apple-style-span" face="Monaco" size="3"><span class="Apple-style-span" style="font-size: 12px;"> b. email: <a href="mailto:owen@delong.com">owen@delong.com</a></span></font></div><div><font class="Apple-style-span" face="Monaco" size="3"><span class="Apple-style-span" style="font-size: 12px;"> c. telephone: 408-890-7992</span></font></div><div><font class="Apple-style-span" face="Monaco" size="3"><span class="Apple-style-span" style="font-size: 12px;"> d. organization: Hurricane Electric</span></font></div><div><font class="Apple-style-span" face="Monaco" size="3"><span class="Apple-style-span" style="font-size: 12px;">3. Proposal Version: 0.9</span></font></div><div><font class="Apple-style-span" face="Monaco" size="3"><span class="Apple-style-span" style="font-size: 12px;">4. Date: 8/3/09</span></font></div><div><font class="Apple-style-span" face="Monaco" size="3"><span class="Apple-style-span" style="font-size: 12px;">5. Proposal type: new</span></font></div><div><span class="Apple-style-span" style="font-family: Monaco; font-size: 12px; ">6. Policy term: permanent</span></div><div><span class="Apple-style-span" style="font-family: Monaco; font-size: 12px; ">7. Policy statement:</span></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>Replace section 4.3.2.2 of the NRPM with the following:</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>4.3.2.2 Multihomed Connection</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>For end-users who demonstrate an intent to announce the requested space in a</font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>multihomed fashion to two or more distinct providers, the minimum block of IP</font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>address space assigned is a /24. If assignments smaller than a /24 are needed,</font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>multihomed end-users should contact their upstream providers. When prefixes are</font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>assigned which are longer than /20, they will be from a block reserved for that</font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>purpose so long as that is feasible. End-users may not receive a block smaller</font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>than /22 under this policy if they already have resources from ARIN, except as</font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>specified in section 4.3.6.2.</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>Renumber the existing paragraph under the 4.3.6 to </font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>4.3.6.1 Utilization requirements for additional Assignment</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>Add the following paragraph 4.3.6.2</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>4.3.6.2<span class="Apple-tab-span" style="white-space:pre"> </span>Replacement assignments for small multi-homers</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>Any end-user that possesses an assignment smaller than /22 under any part of</font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>section 4.3 shall not be able to get an additional assignment unless they agree</font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>to return all existing assignments within 12 months of receiving a new assignment.</font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>The new assignment shall be sized to accommodate their existing utilization in</font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>addition to their justified additional growth space under section 4.3.6.1.</font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>The common cases for this are expected to be a /24 returned after receipt of a /23,</font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>or a /23 returned after receipt of a /22.</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco" size="3"><span class="Apple-style-span" style="font-size: 12px;">8. Rationale:</span></font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>This policy attempts to incorporate the recent and historical discussions of</font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>policy for multi-home users on PPML. The intent is to provide as fair a process</font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>as possible for multi-homed organizations down to the smallest feasible size</font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>while still preserving some control over growth in the routing table.</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>It has been repeatedly noted that /24 multi-homers exist today with PA space</font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>and still occupy a routing table slot, so, it is unlikely that moving this</font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>boundary to /24 would significantly impact the routing table.</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>By requiring smaller assignments to renumber and return, rather than add more</font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>small blocks to their assignments, this policy seeks to further reduce the</font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>chances of unnecessary growth in the routing table and encourage good aggregation</font></div><div><font class="Apple-style-span" face="Monaco"><span class="Apple-tab-span" style="white-space:pre"> </span>where possible.</font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco" size="3"><span class="Apple-style-span" style="font-size: 12px;">9. Timetable for implementation: Immediate</span></font></div><div><font class="Apple-style-span" face="Monaco"><br></font></div><div><font class="Apple-style-span" face="Monaco" size="3"><span class="Apple-style-span" style="font-size: 12px;">END OF TEMPLATE</span></font></div><div><br></div></body></html>