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/[email protected]/
[ipv6-wg at ripe.net] IPv6 access to K-root
- Previous message (by thread): [ipv6-wg at ripe.net] IPv6 access to K-root
- Next message (by thread): [ipv6-wg at ripe.net] inet6num missing for allocation - more?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andrei Robachevsky
andrei at ripe.net
Tue Aug 3 06:06:55 CEST 2004
Hi Robert, Robert Martin-Legène wrote: [...] > And.. do you consider to get this into the root-servers.net zone itself? > I suppose it would then actually get picked up as a glue and upset > conservative parties? (but it might make the root v6-reachable - except > at bootstrap). > Definitely. And not only in the root-servers.net but also in the hints file and in the root zone itself. And not only for K, but for all other root servers that have IPv6 transport enabled. But as we know it's more complex than just updating relevant files. This requires careful consideration of possible technical issues, so that RSSAC can provide clear recommendations to IANA. As far as I know this work in underway. > And finally, why is it that k.root-servers.net and k.root-servers.org > has different IPv4-addresses? > The first one is the server itself, the second is the website containing information about K. > -- Robert Martin-Legene > DK Hostmaster Regards, Andrei -- Andrei Robachevsky RIPE NCC
- Previous message (by thread): [ipv6-wg at ripe.net] IPv6 access to K-root
- Next message (by thread): [ipv6-wg at ripe.net] inet6num missing for allocation - more?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]