On 8-Nov-2007, at 23:18, Dean Anderson wrote:
On Wed, 7 Nov 2007, Antonio Querubin wrote:
With all the on-going discussion in various circles going on about
IPv6
it's a pity the root hints is still missing IPv6 addresses.
There's no room for IPv6 hints. The 512 byte maximum size is full.
A priming query response which includes a full set of IPv4 courtesy
glue in the additional section is 436 bytes long (see below).
It's not clear that there is a requirement for the additional section
to contain courtesy glue which is represents a complete set of all
addresses of the thirteen root servers; the practical requirement is
that it contains enough courtesy glue that an address for at least one
reachable server is provided.
There is a massive installed base of DNS clients, some very old, and
hence some degree of caution in adding AAAA glue seems prudent. Such
caution seems evident in the testbed and associated testing that was
described in those RSSAC/SSAC URLs that were mentioned earlier.
From a protocol perspective, however, I think it's clear that a
response to a priming query which includes AAAA courtesy glue will not
necessary require EDNS0, or TCP transport.
Turning on ENDSO or requiring TCP connections entangles all sorts of
problems with DNS Root Anycast, because those services aren't
stateless,
and Anycast isn't reliable with stateful services.
I will refrain on commenting on your assertions about the suitability
of anycast for DNS services, since I have no points to make here that
have not been made in public many times before.
Of course, there really isn't any reason to have the same 13 IPv4
servers handle IPv6 addresses. A different set of IPv6 root servers
(not anycasted) is what is needed for IPv6 operation.
No, there is no requirement to use different servers for IPv6
operation, and also no need for whichever servers are used not to be
distributed using anycast.
Joe
[calamari:~]% dig . ns
; <<>> DiG 9.4.1-P1 <<>> . ns
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33203
;; flags: qr rd ra; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 13
;; QUESTION SECTION:
;. IN NS
;; ANSWER SECTION:
. 518400 IN NS A.ROOT-SERVERS.NET.
. 518400 IN NS B.ROOT-SERVERS.NET.
. 518400 IN NS C.ROOT-SERVERS.NET.
. 518400 IN NS D.ROOT-SERVERS.NET.
. 518400 IN NS E.ROOT-SERVERS.NET.
. 518400 IN NS F.ROOT-SERVERS.NET.
. 518400 IN NS G.ROOT-SERVERS.NET.
. 518400 IN NS H.ROOT-SERVERS.NET.
. 518400 IN NS I.ROOT-SERVERS.NET.
. 518400 IN NS J.ROOT-SERVERS.NET.
. 518400 IN NS K.ROOT-SERVERS.NET.
. 518400 IN NS L.ROOT-SERVERS.NET.
. 518400 IN NS M.ROOT-SERVERS.NET.
;; ADDITIONAL SECTION:
A.ROOT-SERVERS.NET. 19107 IN A 198.41.0.4
B.ROOT-SERVERS.NET. 27214 IN A 192.228.79.201
C.ROOT-SERVERS.NET. 27214 IN A 192.33.4.12
D.ROOT-SERVERS.NET. 27214 IN A 128.8.10.90
E.ROOT-SERVERS.NET. 27214 IN A 192.203.230.10
F.ROOT-SERVERS.NET. 19107 IN A 192.5.5.241
G.ROOT-SERVERS.NET. 27214 IN A 192.112.36.4
H.ROOT-SERVERS.NET. 27214 IN A 128.63.2.53
I.ROOT-SERVERS.NET. 27214 IN A 192.36.148.17
J.ROOT-SERVERS.NET. 19107 IN A 192.58.128.30
K.ROOT-SERVERS.NET. 19107 IN A 193.0.14.129
L.ROOT-SERVERS.NET. 27214 IN A 199.7.83.42
M.ROOT-SERVERS.NET. 27214 IN A 202.12.27.33
;; Query time: 168 msec
;; SERVER: 199.212.90.6#53(199.212.90.6)
;; WHEN: Fri Nov 9 11:48:32 2007
;; MSG SIZE rcvd: 436
[calamari:~]%
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www1.ietf.org/mailman/listinfo/dnsop
