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

On Mon, 2005-02-28 at 16:43 +0100, Elmar K. Bins wrote:
>gert at space.net (Gert Doering) wrote:
>
>> So far, nobody has proposed a 
>> 
>>  "globally visible v6 to <important end sites>" 
>> 
>> policy yet.  People are clearly unhappy, and blaiming policies, but are
>> not making specific proposals.
>
>Like said - it should have been underway already...

As you so 'badly' want one, write something up and describe exactly what
you want, now you are just running up to the walls.
>
>> still shipping "top of the line" products that can't do more than 
>> 256k IPv4 prefixes).
>
>In the forwarding table, not in the BGP table. Or did I understand
>that wrongly?

BGP is only 'limited' in the number of updates that can be handled. The
likelyhood that more entries cause more updates will rise, next to that,
we only have max ~60k ASN's anyway at this moment, thus even if every
ASN would announce 1 IPv6 prefix it would stop at max ~60k entries...
>
>> OTOH, one might see this "IPv6 deployment isn't happening because
>> we can't get addresses!!!" as a pretty lame excuse - /48 multihoming 
>> has serious problems, but if you really *want* to get started with IPv6,
>> it works, for the time being.
>
>... as long as your transit providers know each other, agree not to
>filter, and you're happy with the fallback connectivity through the
>block owner. We're in a lucky position, not everybody is.

You can also ask the other transit upstream to announce your /48 for
you. Nevertheless, for real end-sites, like my house, most websites and
other 'endsites', if you want to multihome, have some patience shim6 to
be done or as Gert said, make a really neat proposal.

Multihoming on IP is silly in most cases anyway, because most of the
time the cable-path is the same, thus one single silly fiber cut would
take you out anyhow... and if you can pay for multiple differentiated
uplinks you are most likely also big enough to claim you (will) have 200
endsites.

And indeed, this ivory wall says: endsites should use the upcoming shim6
mechanism for multihoming.

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: </ripe/mail/archives/address-policy-wg/attachments/20050228/0ff54148/attachment.sig>