Draft Policies and Proposals
Implemented 17 September 2014
Formal introduction on PPML on 26 November 2013
Origin - ARIN-prop-191
Draft Policy - 26 November 2013
Recommended Draft Policy - 29 January 2014
Revised - 4 March 2014
Reverted to Draft - 12 April 2014
Recommended Draft Policy - 16 May 2014
Last Call 24 June 2014 through 8 July 2014
AC moved to Board - 22 July 2014
Adopted, to be implemented - 13 August 2014
Implemented - 17 September 2014
|Public Policy Mailing List|
|ARIN Public Policy Meeting:|
|ARIN Advisory Council:||
|ARIN Board of Trustees:||18 July 2014|
|Previous version(s)||17 September 2014|
Recommended Draft Policy ARIN-2013-8
Subsequent Allocations for New Multiple Discrete Networks
Date: 16 May 2014
AC's assessment of conformance with the Principles of Internet Number Resource Policy:
This proposal enables fair and impartial number resource administration by documenting how to get a new block for a new discrete network. Previous versions of the policy did have this information and over time it has been removed.
This proposal is technically sound. There is a need for discrete networks and an organization should have a policy that would allow it to create a new discrete network.
This proposal is supported by the community. There has been some concern about the criterial that will be used and this version has been updated with the current thinking on the criteria.
Add the following statement to section 4.5.4.
Upon verification that the organization has shown evidence of deployment of the new discrete network site, the new network(s) shall be allocated the minimum allocation size under section 184.108.40.206 unless the organization can demonstrate additional need using the immediate need criteria (220.127.116.11).
Add an additional reference to section 6.11.5.b such that it references both the initial allocation and subsequent allocation sections of the IPv6 LIR policy.
"Each network will be judged against the existing utilization criteria specified in 6.5.2 and 6.5.3 as if it were a separate organization..."
a. Timetable for implementation: immediate
b. This policy is being proposed based upon the Policy Implementation & Experience Report from ARIN 32.
c: Older versions of the MDN policy did contain new network criteria. This criteria appears to have been dropped during subsequent rewrites of the MDN policy. "The organization must not allocate a CIDR block larger than the current minimum assignment size of the RIR (currently /20 for ARIN) to a new network." (https://www.arin.net/policy/archive/nrpm_20041015.pdf)
STAFF ASSESSMENT of earlier version of text
ARIN Staff and Legal Assessment
ARIN-prop-2013-8 – “Subsequent Allocations for Additional Discrete Network Sites”
Date of Assessment: 04 Mar 2014
1. Summary (Staff Understanding)
This proposal adds missing criteria to existing policy NRPM 4.5 Multiple Discrete Networks and NRPM 6.11 IPv6 Multiple Discrete Networks to assist staff and the community in determining allocation sizes for the new sites of existing MDN customers.
A. ARIN Staff Comments
The revised text removed the requirement to have obtained connectivity at the new site and replaced it with a requirement that "the organization has demonstrated need at its new discrete network site".
· If implemented, ARIN would continue to interpret "has demonstrated need" to mean "has obtained connectivity" at a new site. As stated, it seems to leave this open ended and up to staff to determine what “demonstrated need” is.
· If the author desires the policy to be implemented in some other way, the text should be revised with specific details as to exactly what an organization must show to qualify for space for a new discrete network.
· If an organization has only to tell staff that they need address space for a new site without any means of verification, this policy could enable them to obtain IPv4 address space without any actual need.
B. ARIN General Counsel - Legal Assessment
The policy does not create legal concerns.
3. Resource Impact
This policy would have minimal resource impact from an implementation aspect. It is estimated that implementation would occur within 3 months after ratification by the ARIN Board of Trustees. The following would be needed in order to implement:
· Updated guidelines and internal procedures
· Staff training