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] ICANN Board to implement IPv6 in root servers
- Previous message (by thread): [ipv6-wg at ripe.net] ICANN Board to implement IPv6 in root servers
- Next message (by thread): [ipv6-wg at ripe.net] ICANN Board to implement IPv6 in root servers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
JORDI PALET MARTINEZ
jordi.palet at consulintel.es
Sun May 30 16:23:22 CEST 2004
Hi Johan, The examples I've in mind didn't required connectivity to the rest of the IPv4 world at all ..., so actually not having IPv6 connectivity in the root servers creates a "two (or even many) Internets" problem, because some of this people opted also for using their own "root" DNS servers. I know, in the future may be they may need to connect to the rest of the world, but IPv6 is a stand-alone solution for them right now ... So, I will really strongly encourage the root servers, the ccTLDs, etc., to have IPv6 connectivity ASAP, to avoid this situation being replicated. Regards, Jordi ----- Original Message ----- From: "Johan Ihren" <johani at autonomica.se> To: "JORDI PALET MARTINEZ" <jordi.palet at consulintel.es> Cc: <ipv6-wg at ripe.net> Sent: Sunday, May 30, 2004 4:14 PM Subject: Re: [ipv6-wg at ripe.net] ICANN Board to implement IPv6 in root servers > "JORDI PALET MARTINEZ" <jordi.palet at consulintel.es> writes: > > Jordi, > > > I agree in general with all your points, but I've seen already a > > couple of situations where someone was asking me for a IPv6-only > > network, and the lack of IPv6 in the root server created a problem, > > that of course has been solved hosting the DNS somewhere else (even > > if IPv4 was not used !). > > Yes, I hear from those folks too. And my guess is that if they *did* > (or rather when they do) get v6 transport to the roots they would in > some cases shut off v4 and thereby shoot themselves in the foot. > > This has been used as an argument *against* v6 transport to the roots > since as long as they need v4 lookup capability to reach the roots > they will get the other 40M+ zones that are only availably over v4 > transport too. I.e. since they are forced to do v4 to reach the roots > they do see the entire tree rather than just the lame stump with five > broken twigs on it. > > However, my personal view (since about the Atlanta IETF I think) is > that it is probably better with a spectacular failure in the face of > people who turn off v4 lookup capability entirely when the roots get > v6 transport than to wait a long time (until larger parts of the tree > are dual stack). The reason is that the failure modes will then be > much more subtle. > > And therefore I believe that v6 glue for the roots would be a good thing. > > > I can't provide more details, but there are real cases. > > I know they are. > > Johan Ihrén > Autonomica > > ********************************** Madrid 2003 Global IPv6 Summit Presentations and videos on line at: http://www.ipv6-es.com This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
- Previous message (by thread): [ipv6-wg at ripe.net] ICANN Board to implement IPv6 in root servers
- Next message (by thread): [ipv6-wg at ripe.net] ICANN Board to implement IPv6 in root servers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]