<div dir="auto">While I’m willing to be convinced otherwise, I see no compelling reason to change from 7 to 14 days. I’m not strongly opposed to 14 days. But if no one is willing to make a first-person argument supporting the change to 14 days, then why make the change?</div><div dir="auto"><br></div><div dir="auto">Thanks.</div><div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Sun, Jul 20, 2025 at 18:12 Martin Hannigan <<a href="mailto:hannigan@gmail.com">hannigan@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><br></div><div dir="auto">There is seemingly no pre revenue, capex or opex backlog implied by comments related to this requirement. There is no RIR issue to fix that I can read. This is a business problem that at face value isn't superior to speed of public registration.</div><div dir="auto"><br></div><div dir="auto">+1 harmonize to 7 days. </div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto">On Sun, Jul 20, 2025 at 18:51 Owen DeLong via ARIN-PPML <<a href="mailto:arin-ppml@arin.net" target="_blank">arin-ppml@arin.net</a>> wrote:<br></div><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div dir="ltr"></div><div dir="ltr">While I appreciate the explanation, I don’t have a lot of sympathy. They have 7 days to register it AFTER giving it to the customer. If they need more time, then they can delay the customer receipt of the addresses to facilitate that. </div><div dir="ltr"><br></div><div dir="ltr">Owen</div><div dir="ltr"><br></div><div dir="ltr"><br><blockquote type="cite">On Jul 19, 2025, at 09:21, Kat Hunter <<a href="mailto:takokat81@gmail.com" target="_blank">takokat81@gmail.com</a>> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"></div></blockquote></div><div dir="auto"><blockquote type="cite"><div dir="ltr"><div dir="ltr">Staff had reached out to the WG stating larger organizations needed a little more time to get their registrations in as they had a larger number of customers and could sometimes get backlogged. Since I'm from a large organization, I want to clarify that we were not one of the requesters of this, however, I do know it was an issue of others who were trying to stay compliant with ARIN but potentially had some sort of system/network issue and got backed up. The 14 days was to give them a little extra time to get their registrations in. <div><br></div><div>-Kat Hunter</div><div>Comcast/ARIN AC Chair</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Jul 19, 2025 at 7:23 AM Matthew Cowen via ARIN-PPML <<a href="mailto:arin-ppml@arin.net" target="_blank">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>
I have no particular issue with the draft proposal.
<div><br>
</div>
<div>However, is there an explanation of the rationale behind the 14 days. I understand the harmonisation between v4 and v6, but why move up to 14 days rather than moving both to 7?<br id="m_-7212786962079464951m_7358885161438902715m_-7001843299732929792lineBreakAtBeginningOfMessage">
<div>
<div dir="auto" style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<div dir="auto" style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<div dir="auto" style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<br>
—<br>
My best/Cordialement,<br>
<br>
Matthew Cowen<br>
</div>
</div>
</div>
</div>
<div><br>
<blockquote type="cite">
<div>On 18 Jul 2025, at 12:59, ARIN <<a href="mailto:info@arin.net" target="_blank">info@arin.net</a>> wrote:</div>
<br>
<div>
<div>The following Draft Policy has been revised:<br>
<br>
*ARIN-2024-10: Registration Requirements and Timing of Requirements With Retirement of Section 4.2.3.7.2<br>
<br>
Revised text is below and can be found at:<br>
<br>
<a href="https://www.arin.net/participate/policy/drafts/2024_10/" target="_blank">https://www.arin.net/participate/policy/drafts/2024_10/</a><br>
<br>
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:<br>
<br>
* Enabling Fair and Impartial Number Resource Administration<br>
* Technically Sound<br>
* Supported by the Community<br>
<br>
<br>
The PDP can be found at:<br>
<br>
<a href="https://www.arin.net/participate/policy/pdp/" target="_blank">https://www.arin.net/participate/policy/pdp/</a> <br>
<br>
<br>
Draft Policies and Proposals under discussion can be found at:<br>
<br>
<a href="https://www.arin.net/participate/policy/drafts/" target="_blank">https://www.arin.net/participate/policy/drafts/</a><br>
<br>
<br>
Regards,<br>
<br>
Eddie Diego<br>
Policy Analyst<br>
American Registry for Internet Numbers (ARIN)<br>
<br>
<br>
Draft Policy ARIN-2024-10: Registration Requirements and Timing of Requirements With Retirement of Section 4.2.3.7.2<br>
<br>
Problem Statement:<br>
<br>
Registration is central to the value provided by ARIN to the community. Registry quality depends greatly upon the timely registration of reassignments from ISPs to end users. The motivation for registration has waned since the depletion of the free pool. Registration
remains vital to a number of stakeholders, including law enforcement and network operators.<br>
<br>
This proposal aims to modernize the registration-related policies in Section 4 by introducing language that is meant to remind ISPs of the importance of registration when feasible for the benefit of the community.<br>
<br>
Policy Statement:<br>
<br>
REPLACE: Section 4.2.3.7.1<br>
<br>
Original Text:<br>
<br>
“Each IPv4 reassignment or reallocation containing a /29 or more addresses shall be registered via SWIP or a directory services system which meets the standards set forth in section 3.2.”<br>
<br>
New Text:<br>
<br>
“Each IPv4 reassignment or reallocation containing a /29 or more addresses shall be registered via an approved directory services system which meets the standards set forth in section 3.2, within fourteen calendar days.”<br>
<br>
RETIRE: Section 4.2.3.7.2 - Reassignments and Reallocations Visible Within Seven Days<br>
<br>
RENAME: 6.5.5.1 from “Reassignment Information” to “Reassignment and Reallocation Information”.<br>
<br>
REPLACE: 6.5.5.1<br>
<br>
Original Text:<br>
”Each static IPv6 reassignment or reallocation containing a /47 or more addresses, or subdelegation of any size that will be individually announced, shall be registered in the WHOIS directory via SWIP or a distributed service which meets the standards set forth
in section 3.2. Reassignment and reallocation registrations shall include each client’s organizational information, except where specifically exempted by this policy.”<br>
<br>
New Text:<br>
”Each static IPv6 reassignment or reallocation containing a /47 or more addresses, or subdelegation of any size that will be individually announced, shall be registered via an approved directory services system which meets the standards set forth in section
3.2. Reassignment and reallocation registrations shall include each client’s organizational information, except where specifically exempted by this policy.”<br>
<br>
RENAME: 6.5.5.2 from “Reassignments and Reallocations Visible Within Seven Days” to “Reassignments and Reallocations Visible Within Fourteen Days”<br>
<br>
REPLACE: Section 6.5.5.2<br>
<br>
Original Text:<br>
<br>
“All reassignments and reallocations shall be made visible as required in section 6.5.5.1 within seven calendar days of reassignment or reallocation.”<br>
<br>
New Text: <br>
<br>
“All reassignments and reallocations shall be made visible as required in section 6.5.5.1 within fourteen calendar days of reassignment or reallocation.<br>
<br>
Timetable for implementation: Immediate<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<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" 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>
</div>
</div>
</blockquote>
</div>
<br>
</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>
<span>_______________________________________________</span><br><span>ARIN-PPML</span><br><span>You are receiving this message because you are subscribed to</span><br><span>the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).</span><br><span>Unsubscribe or manage your mailing list subscription at:</span><br><span><a href="https://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a></span><br><span>Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.</span><br></div></blockquote></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>
_______________________________________________<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>