[ppml] 2005-1 status

Jeroen Massar jeroen at unfix.org
Sat Feb 4 12:18:34 EST 2006


On Fri, 2006-02-03 at 10:04 -0500, Kevin Loch wrote:
[..]
>          3) Be currently multihomed using IPv6 connectivity to two
>             or more separate ARIN LIR's using at least one /48 assigned
>             to them by each LIR.

From this point *everybody* can request at least a /48. Just make a
tunnel to Hurricane Electric and one to Hexago or a number of other
sites where you can get such an allocation.

Putting down criteria is hard, probably too hard though.
In either case scrap the "ARIN" part from the above. Some site might
have arranged connectivity from a party in the LACNIC and one in the
ARIN region and then they would be excluded from the above.

Of course the question 'what is multihoming' is another nice one:
 - one prefix and multiple physically seperate links
   to the same provider
 - one prefix and multiple physically seperate links
   to multiple providers
 - multiple prefixes over one/multiple links
and a large number of other possiblities. Good one of course: is a
tunnel a seperate link? Probably a reference to the wording on getting
an ASN would be good to include here.

The main thing I read from 2005-1 is that it gives the folks that want
it the possiblity to acquire a globally unique address space block.
Which is a good thing. But there should be a hard note, which is also
given in the other allocation policies, that the RIR in question does
not guarantee routability of that prefix.

IMHO something along the lines of: Pay an initial high fee (say $2k US)
and then every year a renewal fee ($500 US?) accomplishes the same
thing.

(Not that having a renewel currently makes sure the prefix is not used
any more but (S-)BGP(-S) could solve that problem one day ;)

Greets,
 Jeroen

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 240 bytes
Desc: This is a digitally signed message part
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20060204/744dd607/attachment.sig>


More information about the ARIN-PPML mailing list