[arin-ppml] Draft Policy ARIN-2019-3: Update 4.10 – IPv6 Deployment Block

hostmaster at uneedus.com hostmaster at uneedus.com
Sat Mar 2 12:39:32 EST 2019

+1 on this

Since anything smaller than a /24 is unrouteable, this is a positive 

Albert Erdmann
Network Administrator
Paradise On Line Inc.

On Tue, 26 Feb 2019, ARIN wrote:

> On 21 February 2019, the ARIN Advisory Council (AC) accepted 
> "ARIN-prop-262:Update 4.10 – IPv6 Deployment Block" as a Draft Policy.
> Draft Policy ARIN-2019-3 is below and can be found at:
> https://www.arin.net/policy/proposals/2019_3.html
> You are encouraged to discuss all Draft Policies on PPML. The AC will 
> evaluate the discussion in order to assess the conformance of this draft 
> policy with ARIN's Principles of Internet number resource policy as stated in 
> the Policy Development Process (PDP). Specifically, these principles are:
> * Enabling Fair and Impartial Number Resource Administration
> * Technically Sound
> * Supported by the Community
> The PDP can be found at:
> https://www.arin.net/policy/pdp.html
> Draft Policies and Proposals under discussion can be found at:
> https://www.arin.net/policy/proposals/index.html
> Regards,
> Sean Hopkins
> Policy Analyst
> American Registry for Internet Numbers (ARIN)
> Draft Policy ARIN-2019-3: Update 4.10 – IPv6 Deployment Block
> Problem Statement:
> ARIN staff has noted that the current 4.10 policy is causing problems in its 
> implementation.
> The current policy specifies a /28 minimum. However, ARIN can only allocated 
> a /24 as its minimum size. ARIN's current tools only support a minimum of /24 
> for reverse DNS.
> The current RPKI landscape is also an impediment to using smaller block 
> sizes. Furthermore, a /28 practically is unroutable, so an organization if 
> they were to receive a /28 would be unable to functionally interoperate with 
> most IPv4 end points, for applications which were noted examples in the 
> original policy. (At the time of writing the original policy, it was hoped 
> that by creating a policy with a smaller block size other RIRs and network 
> operators would embrace the routing of blocks smaller than a /24.)
> Updating ARINs tools to allow smaller than a /24 for reverse DNS (such as 
> RFC2317) would likely be a large cost compared value received by the 
> community. This value is further diminished because the purpose of an IPv4 
> block to facilitate IPv6 deployment is that it be routable to the rest of the 
> IPv4 Internet.
> This policy attempts to address these issues, by raising the minimum size to 
> a /24 and limits total amount an organization can receive to a /21. It also 
> removes the requirement for return and renumber, since that was primarily 
> added to allow organizations to obtain larger blocks if that was necessary. 
> The policy also clarifies the utilization requirements by placing them 
> directly in this section rather than a reference to the utilization 
> requirements of end users.
> Policy Statement:
> Replace current 4.10 with the following updated section
> 4.10 Dedicated IPv4 block to facilitate IPv6 Deployment
> ARIN shall allocate a contiguous /10 from its last /8 IPv4 allocation from 
> IANA. This IPv4 block will be set aside and dedicated to facilitate IPv6 
> deployment. Allocations and assignments from this block must be justified by 
> immediate IPv6 deployment requirements. Examples of such needs include: IPv4 
> addresses for key dual stack DNS servers, and NAT-PT or NAT464 translators. 
> ARIN staff will use their discretion when evaluating justifications.
> This block will be subject to a minimum and maximum size allocation of /24. 
> ARIN should use sparse allocation when possible within that /10 block.
> In order to receive an allocation or assignment under this policy:
> 1. the applicant may not have received resources under this policy in the 
> preceding six months and cannot receive more than a /21 under this policy 
> section;
> 2. previous allocations/assignments under this policy must continue to meet 
> the justification requirements of this policy;
> 3. previous allocations/assignments under this policy must be utilized to at 
> least 80% to obtain an additional allocation or assignment;
> 4. the applicant must demonstrate that no other allocations or assignments 
> will meet this need.
> Timetable for Implementation: Immediate
> _______________________________________________
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> https://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net if you experience any issues.

More information about the ARIN-PPML mailing list