Your IP address could not be determined at this time.

ARIN-prop-255: NRPM Cleanup

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 three areas. 

1. 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.8. - 2.9.
          4.1.1. - 4.1.4.

          4.2.5. - 4.2.6.
          4.6. - 4.9.
          6.6. - 6.9.

2. Case, Spelling, or Punctuation changes: The following sections have been normalized to maintain consistent capitalization, punctuation, spelling, or number representation.

          2.10. End Site
          2.12. Organizational Information
    3.4.1. Acceptable Use Policy
    3.5. Autonomous System Originations 
    3.5.1. Collection
    3.5.2. Publication 
 Description of Data
 Bulk Publication of Data
 Other Formats
    3.6. Annual Validation of ARIN’s Public Whois Point of Contact Data 
    3.6.1. Annual POC Verification
    3.6.2. Specified Public Whois Points of Contact for Verification
    3.6.3. Organizations Covered by this Policy
    3.6.4. Procedure for Verification
          4.1.5. Resource Request Size
 Waiting List
 Fulfilling Unmet Needs
 Utilization Rate
 Slow Start
 Minimum Allocation
          4.2.2. Initial Allocation to ISPs
 Efficient Utilization
 Contiguous Blocks
 Downstream Customer Adherence
 Reassignments to Multihomed Downstream Customers
 Assignments Visible Within Seven Days
 Utilization Percentage (80%)
 Return Address Space as Agreed
 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
 Assignment to Operator's Infrastructure
 Reassignment Information
 Assignments Visible Within Seven Days
 Registration Requested by Recipient. 6.5.7. Existing IPv6 Address Space Holders
          6.5.7. Existing IPv6 Address Space Holders
    6.5.8. Direct Assignments from ARIN to End-user Organizations
 Initial Assignment Size
 Standard Sites
 Extra Large Sites
 Subsequent Assignments
 Consolidation and Return of Separate Assignments Qualification Criteria Allocation Size Reassignments by Community Networks
    6.10.1. Micro-allocations for Critical Infrastructure
    6.10.2. Micro-allocations for Internal Infrastructure
          8.3. Transfers Between Specified Recipients Within the ARIN Region
    8.5. Specified Transfer Recipient Requirements
    8.5.1. Registration Services Agreement
    8.5.2. Operational Use
    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
    10.3. IANA Policy for Allocation of ASN Blocks to RIRs
          11.1. Documentation of Recognized Experimental Activity
          11.3. Coordination over Resource Use

3. Grammatical Cleanup: One small change is proposed to Section 6.4.1.

Current Text: 6.4.1. Address Space Not to be Considered to be Property

Proposed Text: 6.4.1. Address Space Not to be Considered Property

Search Related Content

full site search.