[arin-ppml] new policy idea for PA allocations
jim at tgasolutions.com
Thu Aug 7 17:30:46 EDT 2008
I agree. A policy should be a guideline but the staff needs latitude for irregularities that can not be predicted by something that takes on as many facets as the internet.
Please forgive the typos, Sent from my blackberry handheld.
----- Original Message -----
From: arin-ppml-bounces at arin.net <arin-ppml-bounces at arin.net>
To: arin-ppml at arin.net <arin-ppml at arin.net>
Sent: Thu Aug 07 17:03:59 2008
Subject: Re: [arin-ppml] new policy idea for PA allocations
This seems to be an operational issue with ambiguous policy guidance.
Section 4.1.5 allows staff the flexibility to do what is necessary.
There is no clear cut policy as to what staff should do when a single block
cannot be allocated. It would probably be better to let staff attempt to
balance deaggregation, increased requests, and equity of distribution than
try to micro-manage it via the policy process.
------------------ Previous Message -----------------------
Date: Thu, 7 Aug 2008 05:00:12 +0000
From: bmanning at vacation.karoshi.com
Subject: [arin-ppml] [Remco.vanMook at eu.equinix.com:
[address-policy-wg] new policy idea for PA allocations]
To: ppml at arin.net
Message-ID: <20080807050012.GC13934 at vacation.karoshi.com.>
Content-Type: text/plain; charset=us-ascii
how does this idea strike your fancy?
----- Forwarded message from Remco van Mook <Remco.vanMook at eu.equinix.com> -----
X-Original-To: address-policy-wg at lists.ripe.net
Thread-Topic: new policy idea for PA allocations
From: "Remco van Mook" <Remco.vanMook at eu.equinix.com>
I want to hear your feedback on an idea that I've been playing with for a while - it has to do with the way the RIR allocates blocks of space to an approved IPv4 PA allocation request.
Currently that's very simple. Once the request is approved for, say, a /15, you get a single routable block of space, a /15. But what do we do when the RIR does not have that size block anymore? Allocate multiple blocks to that request (so, for example, 2 /17s, 1 /18, 5 /19s and 2 /20s)?
What I would suggest is that we set into policy that the RIR, in cases like this, allocates a single best-fit routable block of IPv4 space. So, if the request is for a /12 and the biggest block the RIR has left is a /14, you get a /14. The rationale behind this is quite simple: the requester is not going to be happy to get a bunch of /24s from all over the swamp space to fill his request, and at the same time we remove the risk that a single request is able to wipe out the entire RIR reserves.
Smaller requests can still be fulfilled and the LIRs that need more space simply need to come back more often - the 80% usage rule still applies.
As long as the RIR has a supply from IANA, this rule will have no operational impact as far as I can see.
Let me know what you think.
----- End forwarded message -----
LR Mack McBride
Alpha Red, Inc.
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