On Sat, May 17, 2014 at 5:21 AM, ARIN <[email protected]> wrote: > On 15 May 2014 the ARIN Advisory Council (AC) accepted "ARIN-prop-209 Change > Utilization Requirements from last-allocation to total-aggregate" as a Draft > Policy. > > Draft Policy ARIN-2014-17 is below and can be found at: > https://www.arin.net/policy/proposals/2014_17.html > > You are encouraged to discuss the merits and your concerns of Draft > Policy 2014-17 on the Public Policy Mailing List. > > 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 PDP. Specifically, these principles are: > > * Enabling Fair and Impartial Number Resource Administration > * Technically Sound > * Supported by the Community > > The ARIN Policy Development Process (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-2014-17 > Change Utilization Requirements from last-allocation to total-aggregate > > Date: 16 May 2014 > > Problem Statement: > > Utilization requirements for new requests is being calculated on a per > allocation basis rather than in aggregate. For example, if an organization > has 4 x /22 and 3 of them are utilized 100% and the fourth utilized at 75%, > that request would be denied. This is a bit out of balance as an > organization with a single /20 utilized at 80% would have less efficient > utilization but would be eligible to request additional space. > > Policy statement: > > Section 4.2.4.1- Change text to read: "ISPs must have efficiently utilized > all previous allocations, in aggregate, to at least 80% in order to receive > additional space. This includes all space reassigned to their customers. > Please note that until your prior utilization is verified to meet the 80% > requirement, ARIN can neither process nor approve a request for additional > addresses." > > Section 4.3.6.1- Change text to read: "End-users must have efficiently > utilized all previous assignments, in aggregate, to at least 80% in order to > receive additional space, and must provide ARIN with utilization details. > The prefix size for an additional assignment is determined by applying the > policies found in Section 4.3 of the NRPM." > > Comments: > > a. Timetable for implementation: Immediate, possibly through board action. > b. Per originator, This does not currently extend into MDN (aka 4.5.4), and > I'm not really sure how to reconcile it against 4.5.5, but OP expressed some > concern that there may be undue restrictions there. It might be better > served by a separate proposal. > c. There should probably also be an attempt to clean up the language between > 4.2.4.1 and 4.3.6.1, as they're both currently very clunky. > _______________________________________________ > 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.
My concern re: MDN requests is that the draft policy, if enacted, should consider each discrete network in aggregate (vs. all MDN in aggregate). -- Jeffrey A. Lyon, CISSP-ISSMP Fellow, Black Lotus Communications mobile: (757) 304-0668 | gtalk: [email protected] | skype: blacklotus.net _______________________________________________ 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.
