I’m fine with the wordsmithing, but I don’t see a reason for the extended timeline from 7 to 14 days. In a world where everything continues to accelerate, including transit use of addresses by criminals, a longer timeline for registration visibility strikes me as counter productive.
The rest of the text changes are “meh”. I don’t see them doing anything meaningful, but I have no objection to them, either. Owen > On Jul 18, 2025, at 09:59, ARIN <[email protected]> wrote: > > The following Draft Policy has been revised: > > *ARIN-2024-10: Registration Requirements and Timing of Requirements With > Retirement of Section 4.2.3.7.2 > > Revised text is below and can be found at: > > https://www.arin.net/participate/policy/drafts/2024_10/ > > 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: > > * Enabling Fair and Impartial Number Resource Administration > * Technically Sound > * Supported by the Community > > > The PDP can be found at: > > https://www.arin.net/participate/policy/pdp/ > > > Draft Policies and Proposals under discussion can be found at: > > https://www.arin.net/participate/policy/drafts/ > > > Regards, > > Eddie Diego > Policy Analyst > American Registry for Internet Numbers (ARIN) > > > Draft Policy ARIN-2024-10: Registration Requirements and Timing of > Requirements With Retirement of Section 4.2.3.7.2 > > Problem Statement: > > 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. > > 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. > > Policy Statement: > > REPLACE: Section 4.2.3.7.1 > > Original Text: > > “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.” > > New Text: > > “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.” > > RETIRE: Section 4.2.3.7.2 - Reassignments and Reallocations Visible Within > Seven Days > > RENAME: 6.5.5.1 from “Reassignment Information” to “Reassignment and > Reallocation Information”. > > REPLACE: 6.5.5.1 > > Original Text: > ”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.” > > New Text: > ”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.” > > RENAME: 6.5.5.2 from “Reassignments and Reallocations Visible Within Seven > Days” to “Reassignments and Reallocations Visible Within Fourteen Days” > > REPLACE: Section 6.5.5.2 > > Original Text: > > “All reassignments and reallocations shall be made visible as required in > section 6.5.5.1 within seven calendar days of reassignment or reallocation.” > > New Text: > > “All reassignments and reallocations shall be made visible as required in > section 6.5.5.1 within fourteen calendar days of reassignment or reallocation. > > Timetable for implementation: Immediate > > > > > > _______________________________________________ > ARIN-PPML > You are receiving this message because you are subscribed to > the ARIN Public Policy Mailing List ([email protected]). > Unsubscribe or manage your mailing list subscription at: > https://lists.arin.net/mailman/listinfo/arin-ppml > Please contact [email protected] if you experience any issues. _______________________________________________ ARIN-PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List ([email protected]). Unsubscribe or manage your mailing list subscription at: https://lists.arin.net/mailman/listinfo/arin-ppml Please contact [email protected] if you experience any issues.
