<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt'>On 15 October 2020, the ARIN Advisory Council (AC) sent the following Recommended Draft Policy to Last Call:<br><br>* ARIN-2020-5: Clarify and Update Requirements for Allocations to Downstream Customers<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>This Recommended Draft Policy has been revised since the community discussion period at ARIN 46, removing “your” from the proposed text for NRPM Section 4.2.3.4.1.<br><br>Feedback is encouraged during the Last Call period. All comments should be provided to the Public Policy Mailing List. Last Call will expire on 3 November 2020.<br><br>The Recommended Draft Policy text is below and available at:<br><a href="https://www.arin.net/participate/policy/drafts/2020_5/">https://www.arin.net/participate/policy/drafts/2020_5/</a><br><br>The ARIN Policy Development Process is available at:<br><a href="https://www.arin.net/participate/policy/pdp/">https://www.arin.net/participate/policy/pdp/</a><br><br>Regards,<br><br>Sean Hopkins<br>Policy Analyst<br>American Registry for Internet Numbers (ARIN)<br><br><br><br>Recommended Draft Policy ARIN-2020-5: Clarify and Update Requirements for Allocations to Downstream Customers<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><br>AC Assessment of Conformance with the Principles of Internet Number Resource Policy:<br><br>This Draft Policy is fair, impartial, and technically sound. This draft policy replaces outdated RFC2050 references in Sections 4.2.3.4.1. and 4.2.3.6. with references to the end user assignment utilization requirements in Section 4.3.3.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><br>Problem Statement:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>A recent Policy Experience Report demonstrated the fact that the existing Section 4.2.3.6 references RFC2050, which is obsolete, and is not synchronized with utilization requirements carried in Section 4.3.3, specifically the utilization rate.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Policy Statement:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Given that RFC7020, which supercedes RFC2050, no longer carries specific utilization requirements for downstream customers of ISPs, its reference may be removed from Section 4.2.3.6, instead referencing 4.3.3 (currently, 50% utilization within 24 months) to harmonize the utilization requirements of both ISPs and their downstream customers.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Removing these references from Section 4.2.3.6 will simplify the language of that section.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Replace sections 4.2.3.4.1 and sections 4.2.3.6 with the following text:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>4.2.3.4.1. Utilization<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>A downstream customer requesting address space from an upstream ISP must document a plan to the allocating ISP for their utilization to conform to Section 4.3.3. Reassignment and reallocation information for prior allocations must show that each customer meets the 80% utilization criteria and must be available via SWIP / a distributed service which meets the standards set forth in section 3.2 prior to issuing them additional space.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>4.2.3.6. Reassignments to Multihomed Downstream Customers<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>If a downstream customer has a requirement to multihome, that requirement alone will serve as justification for a /24 allocation. Downstream customers must provide contact information for all of their upstream providers to the ISP from whom they are requesting a /24, and utilize a border routing protocol between the customer and the ISP. Customers may receive a /24 from only one of their upstream providers under this policy without providing additional justification. ISPs may demonstrate they have made an assignment to a downstream customer under this policy by supplying ARIN with the information they collected from the customer, as described above, or by identifying the AS number of the customer. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Timetable For Implementation: Immediate<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><br><br><o:p></o:p></span></p></div></body></html>