Draft Policy ARIN-2024-10

Registration Requirements and Timing of Requirements With Retirement of Section 4.2.3.7.2

Status: Under Discussion
Shepherds: Alicia Trotman, Daniel Schatte

Current Text (21 November 2024)

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 a 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 a 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.

Comments: This is an iteration of abandoned policy ARIN-2023-4. Due to substantial changes in the problem statement, it was preferred to abandon that policy and resubmit, as opposed to modifying the policy during its PDP cycle.

Staff and Legal Review (30 September 2024)

Staff Understanding: Staff understands that this policy will eliminate the outdated term of SWIP in section 4, and simplify the language to use directory services, which includes SWIP and RWhois. This draft policy will combine sections of 4.2.3.7.1 and 4.2.3.7.2 into a single section, further simplifying the policy text. It also extends the time to publicly report IPv4 reassignments and reallocations from seven days to 14 days. This draft policy is not clear on the timing being calendar days. If this policy is adopted, staff would implement it as 14 calendar days to maintain consistency with the previous policy and current practice.

This draft policy also changes the title of section 6.5.5.1 to include IPv6 Reallocations, aligning it with current staff practices. Staff suggests updating additional text in section 6 to remain consistent with the proposed changes to section 4.

Section 6.5.5.2 outlines that reassignments and reallocations are to be reported within seven calendar days. This introduces differences in reassignment and reallocation requirements for holders of IPv4 (14 days) and IPv6 (7 days), which could lead to confusion for customers holding both IPv4 and IPv6. Staff recommends updating section 6.5.5.2 to 14 calendar days, being consistent with the proposed change in section 4.2.3.7.1.

Also of note, section 6.5.5.1 uses the terms SWIP and distributed service while the proposed revision to 4.2.3.7.1 uses directory services system. Staff recommends using directory services system to be consistent with revised section 4.2.3.7.1.

Implementable as Written?: Yes

Impact on ARIN Registry Operations and Services: None

Legal Review: No material legal issue

Implementation Timeframe Estimate: 3 Months

Implementation Requirements:

• Staff Training
• Updates to public documentation
• Updates to internal procedures and guidelines

Proposal/Draft Policy Text Assessed: 13 September 2024

History and Earlier Versions

Related Meetings