ARIN-prop-269: Clarify Interactions Between NRPM 4.5 IPv6 Transition Space Requests and NRPM 188.8.131.52 Unmet Needs Requests
Proposal Originator: Chris Woodfield
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 184.108.40.206, Unmet Needs. This proposal aims to remove this potential for duplicate requests under these sections.
Section 220.127.116.11, 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 will be considered fulfilled and removed from the waiting list. If a requestor with an outstanding waiting list request receives resources under Section 4.10, Dedicated IPv4 Block To Facilitate IPv6 Deployment, the size of the qualified block contained in their waiting list entry under this section will be reduced by the size of the allocation granted to the requestor under Section 4.10.
Timetable for Implementation: Immediate
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.