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

[ARIN]

On 15 November 2018 the ARIN Advisory Council (AC) accepted 
"ARIN-prop-258: Clarify Reassignment Requirements in 4.2.3.7.1" as a 
Draft Policy.

Draft Policy ARIN-2018-6 is below and can be found at:
https://www.arin.net/policy/proposals/2018_6.html

You are encouraged to discuss all Draft Policies on PPML. The AC will 
evaluate the discussion in order 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/policy/pdp.html

Draft Policies and Proposals under discussion can be found at:
https://www.arin.net/policy/proposals/index.html

Regards,

Sean Hopkins
Policy Analyst
American Registry for Internet Numbers (ARIN)



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

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