On Mon, 24 Jun 2013, Joe Abley wrote:
Nevil needs additional reviewers. If you have a spare ten minutes to read
through this revision and send feedback to Nevil (or to this list, and I'll
forward) that'd be great.
textual:
"L-Root, one of the thirteen root servers, is deployed in this fashion."
This could be misread to mean only L-root is deployed with anycast
Using HOSTNAME.BIND/CH/TXT (Section 4.2), ID.SERVER/CH/TXT
(Section 4.3) or IDENTITY.L.ROOT-SERVERS.ORG/IN/TXT or .../IN/A
(Section 4.4) to identify a node for the purposes of reporting a
problem is frequently reasonable, but it should be acknowledged that
there is potential for re-routing between successive queries: an
observed problem might relate to one node, whilst a subsequent query
using one of those three techniques could be answered by a different
node. Use of the NSID option can obviate this possibility (see
Section 4.1).
This section is confusing, especially since the previous paragraph sets
things up to be followed by a list of methods, not a sentence of a list
of methods and their usage. It should probably be moved towards the end
of section 4. Or moved up one paragraph. It would also be useful to
state that the listed methods below each have their pros and conns, and
that _that_ is the reason all of them are done (some of this can only be
indirectly concluded, and could be stated more explicitly, like:
- This method works through recursive DNS
- This method could fail because some DNS software does not allow the CHAOS
class
- This method is currently not supported on most authoritative DS servers
Or perhaps state earlier in the document why more then one
method for identifying name servers is deployed.
Note while doing some testing I accidentally did:
dig +nsid org @l.root-servers.org
which just gave me a timeout error. It worked using the IP. Only then
did I notice my brain had caught IDENTITY.L.ROOT-SERVERS.ORG and used
"root-servers.org" instead of "root-servers.net" for the query.
Perhaps bring up the text "(note the use of ORG, not NET)" to an earlier
point in the draft? :)
Paul
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
