1 / 8

Draft Policy ARIN-2014 -18: Simplifying Minimum Allocations and Assignments

Draft Policy ARIN-2014 -18: Simplifying Minimum Allocations and Assignments. The Gist. The AC understands the idea proposed here is: Remove the needs test for small allocations (/24 and possibly larger depending on current state of minimum allocations)

brynne-vang
Download Presentation

Draft Policy ARIN-2014 -18: Simplifying Minimum Allocations and Assignments

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Draft Policy ARIN-2014-18: Simplifying Minimum Allocations and Assignments

  2. The Gist The AC understands the idea proposed here is: • Remove the needs test for small allocations (/24 and possibly larger depending on current state of minimum allocations) • Impose a rate limit of once a year under this policy.

  3. 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.

  4. Policy Statement Insert into the NRPM (possibly as 4.2.1.7): “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.”

  5. Observations • There is some support for loosening needs-based number policy. This is one of multiple policies in the queue. Does it represent the right approach? • What is a “minimum allocation”? /24 everywhere? This seems to be likely to have unintended side-effects.

  6. More Observations • How does this rate-limited approach interact with traditional needs-based allocation/assignment? Does order of execution matter? Would the addresses obtained under the rate limited policy be counted in future audits or not? • “this Section shall be controlling” verbiage unique within NRPM. Problem?

  7. Mailing List Feedback • Little support. • A fair amount of opposition.

  8. Discussion

More Related