[ppml] proposed updates to 2006-4

Houle, Joseph D (Joe), CMO jdhoule at att.com
Fri Mar 31 13:27:46 EST 2006

   You sparked a thought...
   This "reserve" concept is a little orthogonal to ARINs standard Mode
of Operating, isn't it?   Isn't ARINs normal model something like:
"We'll allocate you this block, now go away until you've demonstrated
good usage?"
   We're likely talking about fairly big corporate IT organizations here
right?   These organizations are likely going to have multiple "sites"?
(Whatever a site ends up really being.)   
    Why doesn't ARIN just allocate a large enough block in the aggregate
to the corporation.    Block size should be large enough that most (95%
maybe) corporations will never need to come back to the ARIN trough.  I
don't know if a /40 or a /44 or whatever is that size.
    Keeping ARIN allocations above the "site-level size" keeps open the
opportunity for maintaining some level of aggregation in the IPv6 global
routing tables.  
    Also, allocating the whole block should have a significant lower
administrative cost on ARIN than managing the reserve concept and
responding to each /48-sized request.  
    We shouldn't be overly wasteful here, but the trade-off between
address conservation and simplicity should be somewhat different here in
IPv6 than it was in IPv4.

Joe Houle


-----Original Message-----
From: ppml-bounces at arin.net [mailto:ppml-bounces at arin.net] On Behalf Of
Andrew Dul
Sent: Friday, March 31, 2006 12:38 PM
To: ppml at arin.net
Subject: [ppml] proposed updates to 2006-4


As I've discussed this policy, a couple of parts of the existing text
may need to be revised.

1. We should reserve a larger block than a /44.  Reserving larger blocks
at this point can likely only benefit us in the future as networks grow.
I've proposed updating 2006-4 to a /40 reserved block, but I'm open to
discussing larger blocks if people think that is needed.

2. Some people have raised concerns, that the original proposed text
would restrict very large networks to only a single /48.  The updated
text allows a organization to be assigned at least 1 /48 per assigned

If you have comments on these two changes, I'd certainly appreciate

A copy of the proposed updated text is below.



6.5.8. Direct assignments to end sites To qualify for a direct end site assignment, an organization

   1. not be an LIR;
   2. be an end site;
   3. be currently multihomed using IPv4;
   4. have a direct assignment from ARIN of at least a IPv4 /19 and can
show the current utilization of 80% 
       of an IPv4 /19 equivalent. Direct assignment size to end sites

Organizations that meet the direct end site assignment criteria are
eligible to receive a direct assignment of /48 out of a reserved /40.
Organizations with multiple ASNs may be assigned a prefix large enough
to permit a /48 to be assigned to each ASN.

Direct Assignments shall be allocated from a separate super-block to
allow for LIRs to filter based upon assignment size.    Subsequent direct assignments to end sites

Organizations assignment size may be increased by 1 bit (to a maximum of
/40) when they demonstrate the active usage of 50% of the assigned /64
subnets or are actively using at least 50% of their /48 per ASN

Organizations which can demonstrate active usage of more than 50% of /64
networks from a /40 assignment may apply for an additional allocation as
an LIR.

Only one direct assignment may be made to an end site organization under
Section 6.5.8.
PPML mailing list
PPML at arin.net

More information about the ARIN-PPML mailing list