Its more complicated than that. I’ve submitted the proposed policy change below to the AC. Obviously at this early stage I don’t know if the Community will accept this or not but 2014-13 complicates this proposal. That is part of the reason why I suggested changing 2014-13 to specify a range rather than a fixed allocation. I would be fine with having this proposal included with 2014-13 if the AC though that made sense. Otherwise it can remain separate.
TEMPLATE: ARIN-POLICY-PROPOSAL-TEMPLATE-3.0 1. Policy Proposal Name: Simplifying Minimum Allocations and Assignments 2. Proposal Originator a. name: Steven Ryerse b. email: [email protected] c. telephone: 770.656.1460 (c) 770.399.9099 (w) d. organization: Eclipse Networks Inc. 3. Date: 06-JUN-2014 4. Problem Statement: New and small organizations are having a difficult time receiving resource allocations from ARIN because of the economic, administrative and time burdens of making their way through ARIN's needs testing process. For small allocations, the burdens of needs testing may exceed the value of the resources, or may deter small, less well-funded organizations' ability to receive an allocation from ARIN. As ARIN was created to provide Internet resources to ALL organizations within its geographic territory, this disparity in the Policy Manual needs to be addressed. The problem can be remedied by removing needs testing for any organization that applies to receive the current minimum block size allocation. 5. Policy statement: "A Minimum IP allocation size(s) has been defined per Section 4 of the ARIN Number Resource Policy Manual. Regardless of any policy requirement(s) defined in any other active Section of the Policy Manual, all organizations may apply and shall automatically qualify for the current Minimum IP Block Allocation upon completing the normal administrative application process and fee requirements, and all organizations shall be eligible for such an allocation once every 12 months. Where this is in conflict with any other Section in the Policy Manual, this Section shall be controlling." 6. Comments: a. Timetable for implementation: Immediate b. Anything else: Steven Ryerse President 100 Ashford Center North, Suite 110, Atlanta, GA 30338 www.eclipse-networks.com 770.656.1460 - Cell 770.399.9099- Office [Description: Description: Eclipse Networks Logo_small.png]℠ Eclipse Networks, Inc. Conquering Complex Networks℠ From: John Curran [mailto:[email protected]] Sent: Sunday, July 13, 2014 8:47 AM To: Kevin Blumberg Cc: Steven Ryerse; [email protected] Subject: Re: [arin-ppml] ARIN 2014-13 On Jul 12, 2014, at 10:02 AM, Kevin Blumberg <[email protected]<mailto:[email protected]>> wrote: Steven, I’ve double checked with staff and this proposal will not make allocations or assignments larger than /24 more difficult than today. In the revised section 4.2.1.5 Minimum allocation the text allows for /24 and larger prefixes, it isn’t limited to only a /24. Correct. An updated staff assessment is forthcoming which adds the sentence: "If implemented, staff would continue using these well established criteria and guidelines for initial requests larger than /24." FYI, /John John Curran President and CEO ARIN
_______________________________________________ PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List ([email protected]). Unsubscribe or manage your mailing list subscription at: http://lists.arin.net/mailman/listinfo/arin-ppml Please contact [email protected] if you experience any issues.
