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/ipv6-wg@ripe.net/
[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] IPv6 access to K-root
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Iljitsch van Beijnum
iljitsch at muada.com
Mon Aug 2 22:19:42 CEST 2004
On 2-aug-04, at 21:50, Jon Lawrence wrote: >> it was discussed already, that it depends not on RIR, but on ICANN. >> When >> these guys will finish tests&checks, we will get that game to our >> painful >> collection. > and I suppose the question is when are ICANN actually going to get > around to > it. They seem to have waited long enough to add some ccTLD AAAA > records, but to me that seems kind of pointless without the root > containing AAAA's. I'm not so much concerned about how long this step took for exactly the reason you mention: there is little advantage in having TLD AAAA glue records (you say ccTLDs, what about the gTLDs then??) without the same for the root itself. What I _am_ worried about is the way they presented this fairly small step as a huge deal. As I wrote on my website: "One small step for mankind... but a huge step for ICANN." (With the announcement pretty much on the 35th anniversary of the moon landing and all.) -- Iljitsch van Beijnum - http://www.bgpexpert.com/ (updated: Jul 22, 1:28:10)
- Previous message (by thread): [ipv6-wg at ripe.net] IPv6 access to K-root
- Next message (by thread): [ipv6-wg at ripe.net] IPv6 access to K-root
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]