[arin-ppml] [Remco.vanMook at eu.equinix.com: [address-policy-wg] newpolicy idea for PA allocations]

Alexander, Daniel Daniel_Alexander at Cable.Comcast.com
Thu Aug 7 16:40:32 EDT 2008

Is the goal of the thought to throttle demand or to stretch out
available supply? By itself, it would not change either. The idea would
need to incorporate a time restriction, in addition to the single best
fit, in order for it to change anything other than creating more
application requests. 

To use the example below, an organization needs a /15, but the only
blocks left are 2 /17s, 1 /18, 5 /19s and 2 /20s. If the idea became
policy, an organization shows it needs a /15 for the next 12 months.
ARIN would allocate the /17. That would accommodate the org for an
average of three months. Three months later, all things the same, they
would apply again for a /15 for the next 12 months. They would get a
/17, and so the loop continues. 12 months later, they would have a /15,
but through submitting ten applications instead of one.

By only restricting allocations to a single best fit, it does not change
demand or the IP consumption rate. It only changes how many times an
organization has to go to the well for a drink. A single best fit
proposal would also need to say that x is the only allocation the org
can have for x months, in order to also control the frequency of
allocations made.


-----Original Message-----
From: arin-ppml-bounces at arin.net [mailto:arin-ppml-bounces at arin.net] On
Behalf Of bmanning at vacation.karoshi.com
Sent: Thursday, August 07, 2008 1:00 AM
To: ppml at arin.net
Subject: [arin-ppml] [Remco.vanMook at eu.equinix.com: [address-policy-wg]
newpolicy idea for PA allocations]

 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>

Dear all,

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

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

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 -----
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 mailing list