[arin-ppml] (Corrected copy) Recommended Draft Policy ARIN-2023-4: Modernization of Registration Requirements

[ARIN]

Corrected copy with Statement of Conformance Included.

* ARIN-2023-4: Modernization of Registration Requirements

The text of the Recommended Draft Policy is below, and may also be found at: 

https://www.arin.net/participate/policy/drafts/2023_4/ 

You are encouraged to discuss all Recommended Draft Policies on PPML prior to their presentation at the next ARIN Public Policy Consultation (PPC). PPML and PPC discussions are invaluable to the AC when determining community consensus. 

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)


Recommended Draft Policy ARIN-2023-4: Modernization of Registration Requirements

Current Text (21 September 2023)

AC Assessment of Conformance with the Principles of Internet Number Resource Policy:

Draft Policy ARIN-2023-4: Modernization of Registration Requirements, conforms to the principles of the ARIN Policy Development Process. This draft policy is found to be fair, impartial and technically sound. Based on community feedback and AC discussion we motion to move ARIN-2023-4: Modernization of Registration Requirements to Recommended Draft. If adopted this policy aims to modernize the registration related policies in Section 4.

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. At
the same time, privacy laws have been introduced in many jurisdictions
across ARIN’s service region which constrain registration in certain
cases. This combination of forces has generally discouraged many ISPs
from registering reassignments. 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 make registration
requirements more adaptable to changing privacy laws, while reminding
ISPs of the importance of registration when feasible for the benefit
of the community.

Policy Statement:

In section 4.2.3.7.1,
Replace
"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."
With
"Each IPv4 reassignment or reallocation containing a /29 or more
addresses shall be registered in the WHOIS directory via SWIP, or a
directory services system which meets the standards set forth in
section 3.2, within 14 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"

In section 6.5.5.1,
Replace
"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."
With
"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, within 14 days. Reassignment and reallocation registrations shall
include each client’s organizational information, except where
specifically exempted by this policy."

Retire section 6.5.5.2 Reassignments and Reallocations Visible Within Seven Days

Timetable for Implementation: 90 days.