[address-policy-wg] 2006-02 Last Call for Comments (IPv6 Address Allocation and Assignment Policy)

Nick Hilliard wrote:
> Jeroen Massar wrote:
>> It is then also very simple "become member, pay fees, justify space
>> requirement, get it, done presto"
> 
> The whole point is that it's even simpler: "become member, pay fees, get
> space, done presto"

And which prefix size does the organization get then? There are enough
end-site organizations that can easily justify a /42 worth of address
space, 64 /48's isn't that much if you give every separate building
where you have an office a /48 and those offices can definitely be
considered sites. Easy is great, but there should be a possibility for
sites to request a bit more. When the size becomes smaller than a /40
(eg /32) I do suggest that these prefixes are considered to be PA though
and that they cough up the normal LIR fees, at that size one is
hopefully running a nice internal ISP anyway who has LIR functions already.

> Incidentally, this is irrelevant to ULA-C, which is primarily intended
> for end-users.

ULA-C should never come in existence in the first place.

But why would an end-user not be able to request a /48 when they are
willing to pay the fees? (And fill in the paper work, justification,
come up with gear, connectivity, pay for all that etc).

I am pretty happy that we are running SixXS, as it allows me to simply
get the same /48 everywhere I go, the tunnel just moves along with me.
Same goes for quite some other users who move from city to city or from
country to country (this is my 3rd country for instance :) and I keep
the same prefix where-ever I go.

Same goes of course when you have PA space and work for an ISP and
simply tunnel your own /48 to where-ever you go. As long as you are
happy friends with them you can take it along with you.

As for folks "but that takes up a routing slot": we now got ~800 routes
in the IPv6 DFZ(*), that is a far cry from the 200k in IPv4. Before we
even reach 100k most likely (and hopefully) the smart folks have come up
with a nice id/loc mechanism. Then at that point the "Tier Wars" can
begin, if you are cool enough, and thus have a PA prefix, you can remain
in the DFZ, if you are not, thus with a /48 or so, you have to start
using id/loc. As the non-PA prefixes are being allocated from well known
blocks and they are non-/32 in size, filtering on the can become very
easy. Also to mitigate that an ISP has a /20 PA and simply announces
/32's one can of course easily handle that by having per-prefix filters.

Greets,
 Jeroen

* = before Randy jumps in, lets just define "IPv6 DFZ" as the prefixes
that are seen by RIPE's RIS and GRH, those systems are public and are
fed by a rather large amount of ISP's around the globe, when they have
the prefixes (especially when it is >20% in GRH for instance) then it
certainly can be said IMHO that the prefix is "on the Internet")


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 311 bytes
Desc: OpenPGP digital signature
URL: </ripe/mail/archives/address-policy-wg/attachments/20070626/e49aa975/attachment.sig>