[arin-announce] Policy Proposal 116: Permitted Uses of space reserved under NRPM 4.10

[Member Services]

The following is a new policy proposal that has been posted to the ARIN
Public Policy Mailing List for discussion on that list.

Reminder: RSS feeds of all posts to the Public Policy Mailing List
(PPML) and just postings by ARIN to PPML are available at:
https://www.arin.net/participate/mailing_lists/rss.html

Regards,

Member Services
American Registry for Internet Numbers (ARIN)

Member Services wrote:
> ARIN received the following policy proposal and is posting it to the
> Public Policy Mailing List (PPML) in accordance with the Policy
> Development Process.
>
> This proposal is in the first stage of the Policy Development Process.
> ARIN staff will perform the Clarity and Understanding step to make sure
> that they understand the proposal and believe the community will as
> well. Staff will report their results to the ARIN Advisory Council (AC)
> within 10 days.
>
> The AC will review the proposal at their next regularly scheduled
> meeting (if the period before the next regularly scheduled meeting is
> less than 10 days, then the period may be extended to the subsequent
> regularly scheduled meeting). The AC will decide how to utilize the
> proposal and announce the decision to the PPML.
>
> In the meantime, the AC invites everyone to comment on the proposal on
> the PPML, particularly their support or non-support and the reasoning
> behind their opinion. Such participation contributes to a thorough
> vetting and provides important guidance to the AC in their deliberations.
>
> Draft Policies and Proposals under discussion can be found at:
> https://www.arin.net/policy/proposals/index.html
>
> The ARIN Policy Development Process can be found at:
> https://www.arin.net/policy/pdp.html
>
> Mailing list subscription information can be found
> at: https://www.arin.net/mailing_lists/
>
> Regards,
>
> Member Services
> American Registry for Internet Numbers (ARIN)
>
>
> ## * ##
>
>
> Policy Proposal 116: Permitted Uses of space reserved under NRPM 4.10
>
> Proposal Originator: Owen DeLong
>
> Proposal Version: 1
>
> Date: 18 June 2010
>
> Proposal type: modify
>
> Policy term: permanent
>
> Policy statement:
>
> Add the following to section 4.10 of the NRPM
>
> 6. No organization may receive more than 16 /24 equivalents under this
> section.
>
> Add the following to section 4 of the NRPM
>
> 4.11 Required utilization for subsequent allocation under section 4.10
>
> No organization shall receive more than one allocation or assignment
> under section 4.10 unless all prior space issued under 4.10 meets the
> utilization requirements of this section.
>
> 1. The most recent 4.10 allocation/assignment must be at least 80% 
> utilized.
> 2. All utilization must be permitted under section 4.12
> 3. All prior 4.10 allocation/assignments must be at least 90% utilized.
>
> 4.12 Permitted uses of allocations or assignments under section 4.10
>
> No organization shall use space received under section 4.10 for any
> purpose other than as specified in this section
>
> 1. To provide the required public IPv4 address(es) for transitional
> technologies operated by the recipient organization.
> a. Large scale or "Carrier Grade" NAT
> b. NAT-PT
> c. DS-LITE/AFTeR
> d. DNS64 or other transitional DNS enablers
> e. etc.
>
> 2. For other transitional technologies not envisioned at the time of
> this proposal, but, in no case for general IPv4 addressing provided to
> customers.
>
> Rationale:
>
> The current terminology in section 4.10 is vague and could allow a
> variety of interpretations which could lead to allocations or
> assignments being made to ISPs intending to misuse the space for general
> deployment by using IPv6 overlay technologies as a "IPv6 deployments"
> requiring IPv4 space for transition. For example, the current policy
> could be interpreted to enable an ISP to require IPv4 addresses for all
> IPv6 customers to roll IPv6 out as 6rd to customers who would be
> otherwise unable to get IPv4 space. This is clearly outside of the
> original intent of the proposal which created 4.10 (6rd was not yet
> envisioned at the time that was written). This proposal seeks to clarify
> that intent and tighten up the requirements for organizations seeking to
> get space from this limited final resource so that it truly is available
> to facilitate transitional technologies.
>
> Timetable for implementation: immediate
>
> For reference, here is the current text of 4.10
>
> 4.10 Dedicated IPv4 block to facilitate IPv6 Deployment
>
> When ARIN receives its last /8 IPv4 allocation from IANA, a contiguous
> /10 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 size allocation of /28 and a
> 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;
> 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 meet the
> utilization requirements of end user assignments;
> 4. the applicant must demonstrate that no other allocations or
> assignments will meet this need;
> 5. on subsequent allocation under this policy, ARIN staff may require
> applicants to renumber out of previously allocated / assigned space
> under this policy in order to minimize non-contiguous allocations.
>
>
>
>
>
>
>
>
>