[arin-ppml] Recommended Draft Policy ARIN-2018-6: Clarify Reassignment Requirements in 4.2.3.7.1

[ARIN]

On 18 July 2019 the ARIN Advisory Council (AC) advanced the following 
Draft Policy to Recommended Draft Policy status:

Recommended Draft Policy ARIN-2018-6: Clarify Reassignment Requirements 
in 4.2.3.7.1

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

https://www.arin.net/participate/policy/drafts/2018_6/

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,

Sean Hopkins
Policy Analyst
American Registry for Internet Numbers



Recommended Draft Policy ARIN-2018-6: Clarify Reassignment Requirements 
in 4.2.3.7.1

AC assessment of conformance with the Principles of Internet Number 
Resource Policy:

This proposal is technically sound and enables fair and impartial number 
policy by making it clear when reassignments are required to have 
customer Point of Contact (POC) information (reassign detail and 
reallocations) and when they do not (reassign simple).

Problem Statement:

Current NRMP section “Reassignment and Reallocation Information” is 
being interpreted by some organizations to require a “detailed 
reassignment” for all customers. Under the current reassignment schema, 
only a “detailed reassignment or reallocation” contains fields for 
“organizational information”.

This policy intends to simplify the reassignment requirements by noting 
that only a customer’s name is required. Thus a “simple reassignment” 
can be used for most reassignments.

Policy statement:

Replace section 4.2.3.7.1 with the following:

4.2.3.7.1. Reassignment and Reallocation Information

Each IPv4 reassignment or reallocation containing a /29 or more 
addresses shall be registered via SWIP or a valid directory services 
system which meets the standards set forth in section 3.2.

Reassignment registrations must include each customer name, except where 
specifically exempted by this policy.  Reassignment registrations shall 
only include point of contact (POC) information if either: (1) requested 
by the customer; or (2) the reassigned block is intended to be routed 
and announced outside of the provider's network.

Reallocation registrations must contain the customer’s organization name 
and appropriate point of contact (POC) information.

Comments:

Timetable for implementation: Immediate