Draft Policy ARIN-2022-12

Skip to main text Jump to related content

Direct Assignment Language Update

Staff Understanding

This Draft Policy takes steps towards deprecating language around “Assignments” from the NRPM by updating text for clarity and alignment with current ARIN practices. In furtherance of those goals, we recommend terminology and descriptions be consistent and concise to avoid confusion and misinterpretations. Therefore, the following recommendations are made with those purposes in mind:

  • Section 2.5 Allocation – Generally, in context “Allocation” is a block of IP addresses throughout the NRPM. So, we recommend defining “Allocation” in that context instead of as a method. In addition, we recommend replacing the phrase “IP address resources” with “IP addresses.”
    • For example: “IP addresses issued directly from ARIN to an organization.”
  • Section 2.5 Assignment – We recommend a minor restructuring that limits the description of Assignment to its new definition, Allocation, followed by a bracketed explanation.
    • For example: Assignment – Allocation. [Note - The use of Assignment as a differentiating term has been deprecated. Assignment should instead be read as Allocation]
  • Section 2.8 – “Internet number resources” was recently defined in the NRPM, so we recommend using that term for “number resources.”
  • Section 4.2.2 – The new section now contains duplicative language, and we recommend a closer look to ensure alignment with current practice. There also appears to be a typo, “initiation” should be “initial.”
  • Sections 4.3.2, 8.5.4, and 8.5.6 – The phrase “IPv4 resources directly issued by ARIN” can be replaced with “an IPv4 Allocation(s).”
  • Section 4.3.2 - We recommend replacing all instances of “assignment” with “Allocation.”
  • Section 8.5.4 – “block” can be “Allocation.”

Implementable as Written? Yes

Impact on ARIN Registry Operations and Services: None

Legal Review

No material legal issue, however legal agrees with staff’s comment recommending further clarity.

Implementation Timeframe Estimate: Three months

Implementation Requirements:

  • Staff training
  • Updates to public documentation

Proposal/Draft Policy Text Assessed: 5 September 2023

Related