[arin-ppml] Draft Policy ARIN-2016-1: Reserved Pool Transfer Policy

Seth Mattinen sethm at rollernet.us
Wed Apr 6 22:06:16 EDT 2016

On 3/22/16 09:55, ARIN wrote:
> Problem Statement:
> Section 8 of the current NRPM does not distinguish between the transfer
> of blocks from addresses that have been reserved for specific uses and
> other addresses that can be transferred. In sections 4.4 and 4.10 there
> are specific address blocks set aside, based on the need for critical
> infrastructure and IPv6 transitions. Two issues arise if transfers of
> reserved address space occur under the current language of section 8.
> First, if transfers of 4.4 or 4.10 space occur under the current policy
> requirements set forth in sections 8.3 and 8.4, the recipients will be
> able to acquire space that was originally reserved for a specific
> purpose without ever providing evidence that they will be using the
> space for either critical infrastructure or IPv6 transition. Second, if
> we allow an allocation or assignment from the block reserved in section
> 4.10 to be transferred out of the region, it would complicate the single
> aggregate from which providers are being asked to allow in block sizes
> smaller than a /24. This policy would limit the transfer of addresses
> from reserved pools.
> Policy statement:
> Add to Section 8.3 and Section 8.4 under the "Conditions on source of
> the transfer:"
> Address resources from a reserved pool (including those designated in
> Section 4.4 and 4.10) are not eligible for transfer.

I support this policy.


More information about the ARIN-PPML mailing list