ARIN-prop-269: Clarify Interactions Between NRPM 4.5 IPv6 Transition Space Requests and NRPM 4.1.8.2 Unmet Needs Requests [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.

Proposal Originator: Chris Woodfield

Problem Statement:

It has been observed that an organization requesting IPv4 resources under NRPM Section 4.10, Dedicated IPv4 Block To Facilitate IPv6 Deployment, can also request similar or the same resources under Section 4.2.1.8, Unmet Needs. This proposal aims to remove this potential for duplicate requests under these sections.

Policy Statement:

Section 4.1.8.2, Unmet Needs:

Current language: Any requests met through a transfer will be considered fulfilled and removed from the waiting list.

Proposed language (New text in italics):

Any requests met through a transfer or an allocation request fulfilled under Section 4.10 will be considered fulfilled and removed from the waiting list.

Timetable for Implementation: Immediate

Anything Else:

Currently, organizations can receive no more than a /24 at a time under Section 4.10. However, Proposal ARIN-PROP-266, submitted by Chris Tacit and myself, could potentially allow an org to receive up to a /21 under that section, widening the potential for abuse by “double-dipping” waiting list and transition space requests. As such, this proposal should be considered in that context.

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.