[arin-ppml] Lower End User IPv4 threshold to /24
Steven E. Petty
spetty at iconnect-corp.com
Tue Aug 4 10:28:37 EDT 2009
While I am very much in favor of this idea, I think there needs to be very stringent/serious language to prevent these microallocations from being abused with respect to the recent 'ip market' discussions.
I would also expect an explicit statement that there is a return of space requirement if multihoming ceases. Hmmm.. How do do that without muddying Arin's (non)role in routing...
From: arin-ppml-bounces at arin.net [mailto:arin-ppml-bounces at arin.net] On Behalf Of Member Services
Sent: Monday, August 03, 2009 4:37 PM
To: arin-ppml at arin.net
Subject: Re: [arin-ppml] Lower End User IPv4 threshold to /24
ARIN received the following policy proposal and is posting it to the Public Policy Mailing List (PPML) in accordance with Policy Development Process.
This proposal is in the first stage of the Policy Development Process.
ARIN staff will perform the Clarity and Understanding step. Staff does not evaluate the proposal at this time, their goal is to make sure that they understand the proposal and believe the community will as well.
Staff will report their results to the ARIN Advisory Council (AC) within 10 days.
The AC will review the proposal at their next regularly scheduled meeting (if the period before the next regularly scheduled meeting is less than 10 days, then the period may be extended to the subsequent regularly scheduled meeting). The AC will decide how to utilize the proposal and announce the decision to the PPML.
In the meantime, the AC invites everyone to comment on the proposal on the PPML, particularly their support or non-support and the reasoning behind their opinion. Such participation contributes to a thorough vetting and provides important guidance to the AC in their deliberations.
The ARIN Policy Development Process can be found at:
Mailing list subscription information can be found
American Registry for Internet Numbers (ARIN)
## * ##
Owen DeLong wrote:
> TEMPLATE: ARIN-POLICY-PROPOSAL-TEMPLATE-2.0
> 1. Policy Proposal Name: /24 End User Minimum Allocation Unit
> 2. Proposal Originator: Owen DeLong
> 3. Proposal Version: 0.9
> 4. Date: 8/3/09
> 5. Proposal type: new
> 6. Policy term: permanent
> 7. Policy statement:
> Replace section 184.108.40.206 of the NRPM with the following:
> 220.127.116.11 Multihomed Connection
> For end-users who demonstrate an intent to announce the requested
> space in a multihomed fashion to two or more distinct providers, the
> minimum block of IP address space assigned is a /24. If assignments
> smaller than a /24 are needed, multihomed end-users should contact
> their upstream providers. When prefixes are assigned which are longer
> than /20, they will be from a block reserved for that purpose so long
> as that is feasible. End-users may not receive a block smaller than
> /22 under this policy if they already have resources from ARIN, except
> as specified in section 18.104.22.168.
> Renumber the existing paragraph under the 4.3.6 to
> 22.214.171.124 Utilization requirements for additional Assignment
> Add the following paragraph 126.96.36.199
> 188.8.131.52 Replacement assignments for small multi-homers
> Any end-user that possesses an assignment smaller than /22 under any
> part of section 4.3 shall not be able to get an additional assignment
> unless they agree to return all existing assignments within 12 months
> of receiving a new assignment.
> The new assignment shall be sized to accommodate their existing
> utilization in addition to their justified additional growth space
> under section 184.108.40.206.
> The common cases for this are expected to be a /24 returned after
> receipt of a /23, or a /23 returned after receipt of a /22.
> 8. Rationale:
> This policy attempts to incorporate the recent and historical
> discussions of policy for multi-home users on PPML. The intent is to
> provide as fair a process as possible for multi-homed organizations
> down to the smallest feasible size while still preserving some control over growth in the routing table.
> It has been repeatedly noted that /24 multi-homers exist today with PA
> space and still occupy a routing table slot, so, it is unlikely that
> moving this boundary to /24 would significantly impact the routing table.
> By requiring smaller assignments to renumber and return, rather than
> add more small blocks to their assignments, this policy seeks to
> further reduce the chances of unnecessary growth in the routing table
> and encourage good aggregation where possible.
> 9. Timetable for implementation: Immediate
> END OF TEMPLATE
> You are receiving this message because you are subscribed to the ARIN
> Public Policy Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> Please contact info at arin.net if you experience any issues.
You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
Unsubscribe or manage your mailing list subscription at:
Please contact info at arin.net if you experience any issues.
More information about the ARIN-PPML