<div dir="ltr">+1 on David's point. Unless "a timely manner" is defined somewhere within the NRPM and a limit is provided, it's open to interpretation as the interpreting party sees fit.<div><br></div><div>In addition to this, I'm personally not a fan of adding the "to the extent permitted and manner provided by applicable law" wording, because again: which legislation is being applied here, from which jurisdiction and by which party? This is also up to interpretation which without being defined may not result in the intended actions or meaning.</div><div><br></div><div>Regards,<div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Peter Potvin | Executive Director</div><div>------------------------------------------------------------------------------</div><b>Accuris Technologies Ltd.</b><br><div><br></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jul 26, 2023 at 9:37 PM David Farmer via ARIN-PPML <<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">I think the change from 7 days to timely, is unacceptable. Timely is simply too vague and indefinite, it could mean virtually any timeframe, even up to 90 days or 180 days.</div><div dir="auto"><br></div><div dir="auto">I’d be fine extending the timeframe to 14 days, or 10 business days, to allow some flexibility for holidays. I’d even accept 21 days, but it needs to be a definite timeframe.</div><div dir="auto"><br></div><div dir="auto">Thanks </div><div dir="auto"><br><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Tue, Jul 25, 2023 at 11:11 ARIN <<a href="mailto:info@arin.net" target="_blank">info@arin.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang="EN-US"><div><p class="MsoNormal">On 20 July 2023, the ARIN Advisory Council (AC) accepted “ARIN-prop-322: Modernization of Registration Requirements” as a Draft Policy.<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">Draft Policy ARIN-2023-4 is below and can be found at:<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal"><a href="https://www.arin.net/participate/policy/drafts/2023_4/" title="https://www.arin.net/participate/policy/drafts/2023_4/" target="_blank">https://www.arin.net/participate/policy/drafts/2023_4/</a><u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></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:<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">* Enabling Fair and Impartial Number Resource Administration<u></u><u></u></p><p class="MsoNormal">* Technically Sound<u></u><u></u></p><p class="MsoNormal">* Supported by the Community<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">The PDP can be found at:<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal"><a href="https://www.arin.net/participate/policy/pdp/" title="https://www.arin.net/participate/policy/pdp/" target="_blank">https://www.arin.net/participate/policy/pdp/</a><u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">Draft Policies and Proposals under discussion can be found at:<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal"><a href="https://www.arin.net/participate/policy/drafts/" title="https://www.arin.net/participate/policy/drafts/" target="_blank">https://www.arin.net/participate/policy/drafts/</a><u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">Regards,<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">Eddie Diego<u></u><u></u></p><p class="MsoNormal">Policy Analyst<u></u><u></u></p><p class="MsoNormal">American Registry for Internet Numbers (ARIN)<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">Draft Policy ARIN-2023-4: Modernization of Registration Requirements<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">Problem Statement:<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">Registration is central to the value provided by ARIN to the<u></u><u></u></p><p class="MsoNormal">community. Registry quality depends greatly upon the timely<u></u><u></u></p><p class="MsoNormal">registration of reassignments from ISPs to end users. The motivation<u></u><u></u></p><p class="MsoNormal">for registration has waned since the depletion of the free pool. At<u></u><u></u></p><p class="MsoNormal">the same time, privacy laws have been introduced in many jurisdictions<u></u><u></u></p><p class="MsoNormal">across ARIN’s service region which constrain registration in certain<u></u><u></u></p><p class="MsoNormal">cases. This combination of forces has generally discouraged many ISPs<u></u><u></u></p><p class="MsoNormal">from registering reassignments. Registration remains vital to a number<u></u><u></u></p><p class="MsoNormal">of stakeholders, including law enforcement and network operators.<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">This proposal aims to modernize the registration-related policies in<u></u><u></u></p><p class="MsoNormal">Section 4 by introducing language that is meant to make registration<u></u><u></u></p><p class="MsoNormal">requirements more adaptable to changing privacy laws, while reminding<u></u><u></u></p><p class="MsoNormal">ISPs of the importance of registration when feasible for the benefit<u></u><u></u></p><p class="MsoNormal">of the community.<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">Policy Statement:<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">In section 4.2.3.7.1,<u></u><u></u></p><p class="MsoNormal">Replace<u></u><u></u></p><p class="MsoNormal">"Each IPv4 reassignment or reallocation containing a /29 or more<u></u><u></u></p><p class="MsoNormal">addresses shall be registered via SWIP or a directory services system<u></u><u></u></p><p class="MsoNormal">which meets the standards set forth in section 3.2."<u></u><u></u></p><p class="MsoNormal">With<u></u><u></u></p><p class="MsoNormal">"Each IPv4 reassignment or reallocation containing a /29 or more<u></u><u></u></p><p class="MsoNormal">addresses shall be registered in the WHOIS directory via SWIP or a<u></u><u></u></p><p class="MsoNormal">directory services system which meets the standards set forth in<u></u><u></u></p><p class="MsoNormal">section 3.2, in a timely manner, to the extent permitted and manner<u></u><u></u></p><p class="MsoNormal">provided by applicable law."<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">Retire section 4.2.3.7.2 Reassignments and Reallocations Visible<u></u><u></u></p><p class="MsoNormal">Within Seven Days<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">Rename 6.5.5.1<u></u><u></u></p><p class="MsoNormal">From<u></u><u></u></p><p class="MsoNormal">"Reassignment Information"<u></u><u></u></p><p class="MsoNormal">To<u></u><u></u></p><p class="MsoNormal">"Reassignment and Reallocation Information"<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">In section 6.5.5.1,<u></u><u></u></p><p class="MsoNormal">Replace<u></u><u></u></p><p class="MsoNormal">"Each static IPv6 reassignment or reallocation containing a /47 or<u></u><u></u></p><p class="MsoNormal">more addresses, or subdelegation of any size that will be individually<u></u><u></u></p><p class="MsoNormal">announced, shall be registered in the WHOIS directory via SWIP or a<u></u><u></u></p><p class="MsoNormal">distributed service which meets the standards set forth in section<u></u><u></u></p><p class="MsoNormal">3.2. Reassignment and reallocation registrations shall include each<u></u><u></u></p><p class="MsoNormal">client’s organizational information, except where specifically<u></u><u></u></p><p class="MsoNormal">exempted by this policy."<u></u><u></u></p><p class="MsoNormal">With<u></u><u></u></p><p class="MsoNormal">"Each static IPv6 reassignment or reallocation containing a /47 or<u></u><u></u></p><p class="MsoNormal">more addresses, or subdelegation of any size that will be individually<u></u><u></u></p><p class="MsoNormal">announced, shall be registered in the WHOIS directory via SWIP or a<u></u><u></u></p><p class="MsoNormal">distributed service which meets the standards set forth in section<u></u><u></u></p><p class="MsoNormal">3.2, in a timely manner, to the extent permitted and manner provided<u></u><u></u></p><p class="MsoNormal">by applicable law. Reassignment and reallocation registrations shall<u></u><u></u></p><p class="MsoNormal">include each client’s organizational information, except where<u></u><u></u></p><p class="MsoNormal">specifically exempted by this policy."<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">Retire section 6.5.5.2 Reassignments and Reallocations Visible Within Seven Days<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">Timetable for Implementation: Immediate<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><u></u> <u></u></p></div></div>
_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br>
</blockquote></div></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature">===============================================<br>David Farmer <a href="mailto:Email%3Afarmer@umn.edu" target="_blank">Email:farmer@umn.edu</a><br>Networking & Telecommunication Services<br>Office of Information Technology<br>University of Minnesota <br>2218 University Ave SE Phone: 612-626-0815<br>Minneapolis, MN 55414-3029 Cell: 612-812-9952<br>=============================================== </div>
_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br>
</blockquote></div>