[arin-ppml] Recommended Draft Policy ARIN-2019-3: Update 4.10 – IPv6 Deployment Block
fhfrediani at gmail.com
Tue Aug 20 15:34:54 EDT 2019
I would like to support this proposal in full, but before just want to
clarify two points:
- If I understand correctly an organization may receive multiple /24's
(or a combination of other sizes) for this propose up to a maximum of a
/21 and not a /21 every six months.
- Any blocks received under this policy and later transferred or merged
to or by other organizations must be keep used and justified for its
original propose of IPv6 Deployment ? The proposal text is unclear about
transfers so wanted to clarify if in that scenario it remains the same.
On 20/08/2019 15:56, ARIN wrote:
> On 15 August 2019, the ARIN Advisory Council (AC) advanced the
> following Draft Policy to Recommended Draft Policy status:
> * ARIN-2019-3: Update 4.10 – IPv6 Deployment Block
> The text of the Recommended Draft Policy is below, and may also be
> found at:
> You are encouraged to discuss all Recommended Draft Policies on PPML
> prior to their presentation at the next ARIN Public Policy
> Consultation (PPC). PPML and PPC discussions are invaluable to the AC
> when determining community consensus.
> The PDP can be found at:
> Draft Policies and Proposals under discussion can be found at:
> Sean Hopkins
> Policy Analyst
> American Registry for Internet Numbers
> Recommended Draft Policy ARIN-2019-3: Update 4.10 – IPv6 Deployment Block
> AC Assessment of Conformance with the Principles of Internet Number
> Resource Policy:
> Because it will better enable fair number distribution, provide
> improved clarity and compatibility with existing systems, is
> technically sound, has received the support of the community, and
> there are no material legal issues related to implementation, the ARIN
> Advisory Council moved draft policy 2019-3 to recommended draft status.
> 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
> In order to receive an allocation or assignment under this policy:
> - 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;
> - previous allocations/assignments under this policy must continue to
> meet the justification requirements of this policy;
> - previous allocations/assignments under this policy must be utilized
> to at least 80% to obtain an additional allocation or assignment;
> - 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:
> Please contact info at arin.net if you experience any issues.
More information about the ARIN-PPML