[address-policy-wg] IPv6 access to K-root

iljitsch at muada.com (Iljitsch van Beijnum) wrote:

> Well, there are more than a hundred TLDs and if they all want 11 IPv6 
> prefixes that would inflate the v6 table by more than 150%.

There are ways around this, and people are pretty reasonable.
I believe in other ccTLDs as well as in ours people know pretty
well what they are doing and what they should demand. Actually,
what would keep them from doing things together again for a try?

Anyway, v6 space is organized quite different from v4 space (let's
hope it's not becoming overorganized in the near future), and,
while you're right and the prefix tables will grow, they will
not hit the same technological boundaries v4 hit all the while.

Even if the table grows from the handful of prefixes (who sees more
than 2000?) to half a million, the then-current routers will easily
cope with that. And will 1100 prefixes (I'd expect around 300, mind)
make any difference?


> Everyone thinks they're special. That's how you get large routing 
> tables.

Who gets to decide? We're talking infrastructure here.

ARIN seems to have a picture of specialness quite different from RIPE's
view. If you ask me, it's closer to what's needed.

And I cannot see the v6 train pulling out of the yard before the
infrastructure all people are accustomed to does speak IPv6. And I
mean: In the way it speaks v4, not in a lab environment or in mini-
scale. In real life some things are more special than others.


> >Is everybody busy waiting for the IETF v6-multihoming group to come
> >to a conclusion?
> 
> In that case you won't have to wait much longer as this is going to 
> happen within a few weeks. However, the multi6 mechanisms (that still 
> have to be developed) aren't very suitable for multihoming DNS service.

I'm following the list, and, as well as a lot of people have worked on
proposals and design papers, I believe the whole thing is far from
deployment. But that's my $0.02. I have to find solutions now.

I could long ago have convinced my superiors to open a branch office
in $ELSEWHERE and go to the appropriate RIR, but I have always been
a friend and promoter of the "RIPE way of doing things", and I would
rather see the RIPE community get out of the ivory tower and into the
real world, where some things _are_ special. Alright, I'm repeating
myself.

Maybe we can restart the discussion that faded away after 2003, and
get things on the right track. Which of course means, afterwards all
people share my opinion. :-)

Elmar.