This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/address-policy-wg@ripe.net/
[address-policy-wg] IPv6 access to K-root
- Previous message (by thread): [address-policy-wg] IPv6 access to K-root
- Next message (by thread): [address-policy-wg] IPv6 access to K-root
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Elmar K. Bins
elmi at 4ever.de
Fri Feb 25 20:03:57 CET 2005
kurtis at kurtis.pp.se (Kurt Erik Lindqvist) wrote: > > 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. > > At the same time there are ccTLDs who are already running their slaves > on IPv6.... Oh, we certainly are. Two sets on two v6 addresses I cannot anycast, since they are somebody else's PA. Contrast this with eleven/fifteen v4 sets on five unicast (provider PA) and one anycast v4 (PI) address. Like Nils said, that's not real business, it's not even a start. Elmar. -- "Begehe nur nicht den Fehler, Meinung durch Sachverstand zu substituieren." (PLemken, <bu6o7e$e6v0p$2 at ID-31.news.uni-berlin.de>) --------------------------------------------------------------[ ELMI-RIPE ]---
- Previous message (by thread): [address-policy-wg] IPv6 access to K-root
- Next message (by thread): [address-policy-wg] IPv6 access to K-root
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]