ARIN-prop-258: Clarify Reassignment Requirements in 4.2.3.7.1 [Archived]
OUT OF DATE?
Here in the Vault, information is published in its final form and then not changed or updated. As a result, some content, specifically links to other pages and other references, may be out-of-date or no longer available.
Date: 8 October 2018
Proposal Originator: Andrew Dul
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 in an approved directory services system which meets the standards set forth in section 3.2.
Reassignment registrations shall include each customer’s name, except where specifically exempted by this policy. Except where otherwise exempted by policy, reassignment registration 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 shall contain the customer’s name and appropriate point of contact (POC) information.
Timetable for Implementation:
Immediate
OUT OF DATE?
Here in the Vault, information is published in its final form and then not changed or updated. As a result, some content, specifically links to other pages and other references, may be out-of-date or no longer available.