<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;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-ligatures:standardcontextual;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@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" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>The following Draft Policy has been revised:<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>* 2023-4: Modernization of Registration Requirements<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Revised text is below and can be found at:<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal><a href="https://www.arin.net/participate/policy/drafts/2023_4/">https://www.arin.net/participate/policy/drafts/2023_4/</a><o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>You are encouraged to discuss all Draft Policies on PPML. The AC will evaluate the discussion to assess the conformance of this Draft Policy with ARIN's Principles of Internet number resource policy as stated in the Policy Development Process (PDP). Specifically, these principles are:<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>* Enabling Fair and Impartial Number Resource Administration<o:p></o:p></p><p class=MsoNormal>* Technically Sound<o:p></o:p></p><p class=MsoNormal>* Supported by the Community<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>The PDP can be found at:<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal><a href="https://www.arin.net/participate/policy/pdp/">https://www.arin.net/participate/policy/pdp/</a><o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Draft Policies and Proposals under discussion can be found at:<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal><a href="https://www.arin.net/participate/policy/drafts/">https://www.arin.net/participate/policy/drafts/</a><o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Regards,<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Eddie Diego<o:p></o:p></p><p class=MsoNormal>Policy Analyst<o:p></o:p></p><p class=MsoNormal>American Registry for Internet Numbers (ARIN)<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Problem Statement:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Registration is central to the value provided by ARIN to the<o:p></o:p></p><p class=MsoNormal>community. Registry quality depends greatly upon the timely<o:p></o:p></p><p class=MsoNormal>registration of reassignments from ISPs to end users. The motivation<o:p></o:p></p><p class=MsoNormal>for registration has waned since the depletion of the free pool. At<o:p></o:p></p><p class=MsoNormal>the same time, privacy laws have been introduced in many jurisdictions<o:p></o:p></p><p class=MsoNormal>across ARIN’s service region which constrain registration in certain<o:p></o:p></p><p class=MsoNormal>cases. This combination of forces has generally discouraged many ISPs<o:p></o:p></p><p class=MsoNormal>from registering reassignments. Registration remains vital to a number<o:p></o:p></p><p class=MsoNormal>of stakeholders, including law enforcement and network operators.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>This proposal aims to modernize the registration-related policies in<o:p></o:p></p><p class=MsoNormal>Section 4 by introducing language that is meant to make registration<o:p></o:p></p><p class=MsoNormal>requirements more adaptable to changing privacy laws, while reminding<o:p></o:p></p><p class=MsoNormal>ISPs of the importance of registration when feasible for the benefit<o:p></o:p></p><p class=MsoNormal>of the community.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Policy Statement:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In section 4.2.3.7.1,<o:p></o:p></p><p class=MsoNormal>Replace<o:p></o:p></p><p class=MsoNormal>"Each IPv4 reassignment or reallocation containing a /29 or more<o:p></o:p></p><p class=MsoNormal>addresses shall be registered via SWIP or a directory services system<o:p></o:p></p><p class=MsoNormal>which meets the standards set forth in section 3.2."<o:p></o:p></p><p class=MsoNormal>With<o:p></o:p></p><p class=MsoNormal>"Each IPv4 reassignment or reallocation containing a /29 or more<o:p></o:p></p><p class=MsoNormal>addresses shall be registered in the WHOIS directory via SWIP, or a<o:p></o:p></p><p class=MsoNormal>directory services system which meets the standards set forth in<o:p></o:p></p><p class=MsoNormal>section 3.2, within 14 days."<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Retire section 4.2.3.7.2 Reassignments and Reallocations Visible<o:p></o:p></p><p class=MsoNormal>Within Seven Days<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Rename 6.5.5.1<o:p></o:p></p><p class=MsoNormal>From<o:p></o:p></p><p class=MsoNormal>"Reassignment Information"<o:p></o:p></p><p class=MsoNormal>To<o:p></o:p></p><p class=MsoNormal>"Reassignment and Reallocation Information"<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In section 6.5.5.1,<o:p></o:p></p><p class=MsoNormal>Replace<o:p></o:p></p><p class=MsoNormal>"Each static IPv6 reassignment or reallocation containing a /47 or<o:p></o:p></p><p class=MsoNormal>more addresses, or subdelegation of any size that will be individually<o:p></o:p></p><p class=MsoNormal>announced, shall be registered in the WHOIS directory via SWIP or a<o:p></o:p></p><p class=MsoNormal>distributed service which meets the standards set forth in section<o:p></o:p></p><p class=MsoNormal>3.2. Reassignment and reallocation registrations shall include each<o:p></o:p></p><p class=MsoNormal>client’s organizational information, except where specifically<o:p></o:p></p><p class=MsoNormal>exempted by this policy."<o:p></o:p></p><p class=MsoNormal>With<o:p></o:p></p><p class=MsoNormal>"Each static IPv6 reassignment or reallocation containing a /47 or<o:p></o:p></p><p class=MsoNormal>more addresses, or subdelegation of any size that will be individually<o:p></o:p></p><p class=MsoNormal>announced, shall be registered in the WHOIS directory via SWIP, or a<o:p></o:p></p><p class=MsoNormal>distributed service which meets the standards set forth in section<o:p></o:p></p><p class=MsoNormal>3.2, within 14 days. Reassignment and reallocation registrations shall<o:p></o:p></p><p class=MsoNormal>include each client’s organizational information, except where<o:p></o:p></p><p class=MsoNormal>specifically exempted by this policy."<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Retire section 6.5.5.2 Reassignments and Reallocations Visible Within Seven Days<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Timetable for Implementation: 90 days.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>