On Wed, Dec 19, 2007 at 12:05:36AM -0500, Theodore Tso wrote:
On Wed, Dec 19, 2007 at 02:20:32PM +1100, Mark Andrews wrote:
On Wed, Dec 19, 2007 at 11:36:34AM +1100, Mark Andrews wrote:
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.
Ok, so I'm sure this is a REALLY dumb question, but what has prevented
anyone from taking the informatoin from www.root-servers.org and
creating a named.boot file with both the A and AAAA records for the
root nameservers, and started telling people to install it?
named.boot is not used after the priming succeeds.
Ah, right. So that's why we would need to hijack the root zone
information --- so we can add the AAAA records to the root zones.
OK, next stupid question? Why aren't the AAAA records being published
in the official root zone today? Is there some good reason, like say
the size of the records returned for the root zone being too big? And
is something being done to address whatever reasons might exist,
whether they are at the technical or political layer?
- Ted
indeed.
I point to the the RSSAC(*) meeting minutes from Chicago
and Vancouver for the ICANN statements as to why the AAAA
records for the root servers have not been added to date.
e.g. its not a technical problem.
the good news is that the issue is on the ICANN board meeting
for the 18th. One can only hope that the pending requests
will be approved ... then the IETF/IAB won't have to have the
problem of publicly supporting a unified root/namespace and
practically having to hijack the space to get the functionality
desired.
(*) http://www.rssac.org
--
--bill
Opinions expressed may not even be mine by the time you read them, and
certainly don't reflect those of any other entity (legal or otherwise).
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf