ARIN-prop-255: NRPM Cleanup [Archived]

Date: 10 April 2018

Proposal Originator: Leif Sawyer

Problem Statement:

Current NRPM has many inconsistent title and organizational issues.

Policy Statement:

A number of small, editorial changes are provided in order to help clean up the NRPM, by standardizing the section titles, and collapsing the retired sections from multiple lines into single lines.

The official text of the actual changes are provided as a separate document in order not to clutter this proposal template.

The changes listed below take place in both the table of contents as well as at the head of each section within the NRPM. Due to the number of changes, they have been collapsed into the following two areas.

These sections have been retired and removed from the NRPM.

Where appropriate, multiple levels of retired sections have been collapsed.

Any remaining section text has been changed to [Retired]

2.3.
2.8. - 2.9.
4.1.1. - 4.1.4.
4.1.7.
4.1.9.
4.2.4.4.
4.2.5. - 4.2.6.
4.6. - 4.9.
5.1
6.2.
6.4.3.
6.5.6.
6.5.9.3.
6.6. - 6.9.
7.

Case, Spelling, or Punctuation changes:

The following sections have been normalized to maintain consistent capitalization, punctuation, spelling, or number representation.

2.10. End Site
3.4.1. Acceptable Use Policy
3.5.2.1. Description of Data
3.5.2.2. Bulk Publication of Data
3.5.2.3. Other Formats
4.1.5. Resource Request Size
4.1.8.1. Waiting List
4.1.8.2. Fulfilling Unmet Needs
4.2.1.3. Utilization Rate
4.2.1.4. Slow Start
4.2.1.5. Minimum Allocation
4.2.1.6. Immediate Need
4.2.2. Initial Allocation to ISPs
4.2.3.1. Efficient Utilization
4.2.3.3. Contiguous Blocks
4.2.3.4. Downstream Customer Adherence
4.2.3.5. ARIN Pre-approval of Reassignments/Reallocations
4.2.3.5.3. Required Documentation for Pre-approval Requests
4.2.3.6. Reassignments to Multihomed Downstream Customers
4.2.3.7.2. Assignments Visible Within Seven Days
4.2.4.1. Utilization Percentage (80%)
4.2.4.2. Return Address Space as Agreed
4.2.4.3. Request Size
4.3.4. Additional Considerations
4.10. Dedicated IPv4 Block to Facilitate IPv6 Deployment
6.3. Goals of IPv6 Address Space Management
6.3.7. Minimized Overhead
6.3.8. Conflict of Goals
6.4.1. Address Space Not to be Considered to be Property
6.4.2. Routability not Guaranteed
6.5. Policies for Allocations and Assignments
6.5.4.1. Assignment to Operator’s Infrastructure
6.5.5.1. Reassignment Information
6.5.5.2. Assignments Visible Within Seven Days
6.5.5.4 Registration Requested by Recipient. 6.5.7. Existing IPv6 Address Space Holders
6.5.8. Direct Assignments from ARIN to End-user Organizations
6.5.8.2. Initial Assignment Size
6.5.8.2.1. Standard Sites
6.5.8.2.2. Extra Large Sites
6.5.8.3. Subsequent Assignments
6.5.8.4. Consolidation and Return of Separate Assignments
8.3. Transfers Between Specified Recipients Within the ARIN Region
8.5.3. Minimum Transfer Size
8.5.4. Initial Block
8.5.5. Block Size
8.5.6. Efficient Utilization of Previous Blocks
8.5.7. Alternative Additional IPv4 Address Block Criteria
11.1. Documentation of Recognized Experimental Activity
11.3. Coordination over Resource Use