On Tue, Dec 18, 2007 at 02:05:05PM -0800, Bill Manning wrote:
my appologies to Ted, you happend to be the nearest
lighting rod.
Heh. I hadn't realized how sensitive people are to the whole concept
of "hijacking the root". To me, I was thinking merely of taking the
official root zone data and making it available on an IPv6 visible
host, on site at the IETF meeting if that's what's necessary to make
things work. I don't think of that as being particularly
controversial, just an engineering expediency. What I had in mind is
very different from taking the official root zone data and then adding
or subtracting root entries, quite a different idea of "hijacking the
root". Perhaps that's what you had in mind?
In any case, I did some more looking into it, and it seems that 5 of
the 13 official root name servers have IPv6 addresses, and while that
doesn't necessarily mean global connectivity (some of them may only
have very limited service to a small IPv6 island), it shouldn't be
*that* hard for the IETF network ops to arrange a one or more
tunnel(s) to root servers with IPv6 addresses. But in any case, the
point is let's come up with the appropriate engineering solutions so
that an IPv6-only network at an IETF meeting is in fact a viable and
productive resource to the attendees. And if people continue to
insist that it's not possible, what does that say about IPv6?
As far as my having any authority as an official spokesmodel by virtue
of my Sargeant-at-Arms role, I just got a great big chuckle out of
that. That title and two dollars will get me a small coffee at
Starbucks!
- Ted
There really isn't connectivity problems with the IPv6
roots. I've been using them for years. They need some
test traffic. I've also reported to the various operators
when they have been broken and always got a swift fix as a
response.
Only B is playing up at the moment.
% dig -6 soa . @f.root-servers.net +noall +answer
. 86400 IN SOA A.ROOT-SERVERS.NET.
NSTLD.VERISIGN-GRS.COM. 2007121800 1800 900 604800 86400
% dig -6 soa . @k.root-servers.net +noall +answer
. 86400 IN SOA a.root-servers.net.
nstld.verisign-grs.com. 2007121800 1800 900 604800 86400
% dig -6 soa . @m.root-servers.net +noall +answer
. 86400 IN SOA A.ROOT-SERVERS.NET.
NSTLD.VERISIGN-GRS.COM. 2007121800 1800 900 604800 86400
% dig -6 soa . @f.root-servers.net +noall +answer
. 86400 IN SOA A.ROOT-SERVERS.NET.
NSTLD.VERISIGN-GRS.COM. 2007121800 1800 900 604800 86400
% dig -6 soa . @b.root-servers.net +noall +answer
;; connection timed out; no servers could be reached
%
The problem is getting the AAAA records for them published.
A local copy of "root-servers.net" with the AAAA records
added will suffice. "www.root-servers.org" will supply
you with the necessary information to construct such a
zone.
Note: the root zone remains untouched and all servers
return the same root zone content.
Mark
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews(_at_)isc(_dot_)org
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf