ARIN-prop-354: Relax 4.10 Usage Restrictions

Relax 4.10 Usage Restrictions

Problem Statement

4.10 space is restricted to IPv6 transition mechanisms such as 464XLAT. For small operators, deploying NAT64 is more costly than operating a dual-stack network, driving them towards the waitlist. Over 10 years post-runout, dual stack is still the standard network deployment for most operators, so we should support limited dual stack deployments with 4.10 space.

In addition, we ought to remove the reference to the historic NAT-PT protocol, and more clearly allow for future translation and transition mechanisms.

Policy Statement

Amend 4.10, paragraph 1, sentence 4 from “Examples of such needs include: IPv4 addresses for key dual stack DNS servers, and NAT-PT or NAT464 translators.”

to “Examples of such needs include, but are not limited to: IPv4 addresses for key dual stack DNS servers and deployment of NAT64 as in 464XLAT. Organizations with less than a /22 in aggregate IPv4 allocations may request an allocation under this section to deploy dual stack to customer or end-user devices.”

Comments

4.10 gives ARIN a fair amount of discretion in determining justifications. This change explicitly allows dual-stack deployments, which may open the space up to increased levels of abuse. I’ve elected to not include specific metrics for measuring IPv6 deployment under this revised policy, however that may be warranted in a future policy proposal. Also note that organizations who request space under the proposed dual-stack policy may be required to return it or re-deploy it for transition mechanisms once they cross the /22 threshold.