[arin-ppml] Draft Policy ARIN-2016-4: Transfers for new entrants

[Brett Frankenberger]

On Wed, Jul 20, 2016 at 12:38:51PM -0700, John Springer wrote:
> Dear PPML,
> 
> ARIN-2016-4 was accepted as a Draft Policy in June.
> 
> https://www.arin.net/policy/proposals/2016_4.html
> 
> Expressions of support or opposition to the DP are solicited to assist in
> evaluating what to do with it in the run up to the meeting in Dallas.
> 
> At the moment, it appears technically sound and fair to me, but expressions
> of support will be required to advance.

Support.

> On Tue, Jun 21, 2016 at 8:40 AM, ARIN <info at arin.net> wrote:
> 
> > On 16 June 2016 the ARIN Advisory Council (AC) advanced the following
> > Proposal to Draft Policy status:
> >
> > ARIN-prop-229: Transfers for new entrants
> >
> > This Draft Policy has been numbered and titled:
> >
> > Draft Policy ARIN-2016-4: Transfers for new entrants
> >
> > Draft Policy ARIN-2016-4 is below and can be found at:
> > https://www.arin.net/policy/proposals/2016_4.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,
> >
> > Communications and Member Services
> > American Registry for Internet Numbers (ARIN)
> >
> > ##########
> >
> > Draft Policy ARIN-2016-4: Transfers for new entrants
> >
> > Date: 21 June, 2016
> > Problem Statement:
> >
> > New organizations without existing IPv4 space may not always be able to
> > qualify for an initial allocation under NRPM 4.2, particularly if they are
> > categorized as ISPs and subject to 4.2.2.1.1. Use of /24. Now that ARIN's
> > free pool is exhausted, 4.2.1.6. Immediate need states that "These cases
> > are exceptional", but that is no longer correct. End user organizations
> > requiring less a /24 of address space may also be unable to acquire space
> > from their upstream ISP, and may instead need to receive a /24 from ARIN
> > via transfer.
> >
> > Policy statement:
> >
> > Replace Section 4.2.2 with:
> >
> > 4.2.2. Initial allocation to ISPs
> >
> > "All ISP organizations without direct assignments or allocations from ARIN
> > qualify for an initial allocation of up to a /21, subject to ARIN's minimum
> > allocation size. Organizations may qualify for a larger initial allocation
> > by documenting how the requested allocation will be utilized within 24
> > months for specified transfers, or three months otherwise. ISPs renumbering
> > out of their previous address space will be given a reasonable amount of
> > time to do so, and any blocks they are returning will not count against
> > their utilization.
> >
> > Replace Section 4.3.2 to read:
> >
> > 4.3.2 Minimum assignment
> >
> > ARIN's minimum assignment for end-user organizations is a /24.
> >
> > End-user organizations without direct assignments or allocations from ARIN
> > qualify for an initial assignment of ARIN's minimum assignment size.
> >
> > Replace the first two sentences of Section 4.3.3. Utilization rate to read:
> >
> > Organizations may qualify for a larger initial allocation by providing
> > appropriate details to verify their 24-month growth projection for
> > specified transfers, or 12 months otherwise.
> >
> > Resulting new section 4.3.3 will be:
> >
> > Organizations may qualify for a larger initial allocation, by providing
> > appropriate details to verify their 24-month growth projection for
> > specified transfers, or 12 months otherwise.
> >
> > The basic criterion that must be met is a 50% utilization rate within one
> > year.
> >
> > A greater utilization rate may be required based on individual network
> > requirements. Please refer to RFC 2050 for more information on utilization
> > guidelines.
> >
> > Comments:
> >
> > Timetable for implementation: Immediate
> >
> > Anything else
> >
> > The text in 4.2.2 "for specified transfers, or three months otherwise" and
> > the text in 4.3.3 "for specified transfers, or 12 months otherwise" should
> > be stricken if ARIN-prop-227 is adopted.