many questions about Bv9ARM-book.xml

[Jeremy C. Reed]

So I can supply patches for these, please provide answers for these many 
questions:

1) Bv9ARM-book says: The options statement has three clauses: 
default-server, default-key, and default-port.

Three doesn't sound right. What about default-source-address and 
default-source-address-v6?

2) 9.5 cvs log and bin/named/config.c says:
bin/named/config.c:     dnssec-validation no; /* Make yes for 9.5. */ \n\

Why still "no" or is comment wrong?

3) Should RFC 4431 be added to bibliography since DLV is mentioned a few 
times in ARM?

4) ARM mentions heartbeat-interval and "zone maintenance tasks" for dialup 
zones. What are these "zone maintenance tasks"?

5) Why does ARM document "topology" if not implemented? What is the plan 
or timeline for this?

6) Why is rrset-oder not yet fully implemented in BIND 9. Why? What does 
this mean to the administrator?

7) A lot of ARM's "server Statement Definition and Usage" is repeated 
elsewhere in ARM. Some with slight differences, for example, one section 
about transfer-format says: "The <command>many-answers</command> format is 
also supported by recent Microsoft Windows nameservers." but the other 
doesn't.

Maybe should just cross-reference instead of duplicating work.

8) ARM documents host-statistics and host-statistics-max -- will this ever 
be in BIND 9? BIND 10?

9) ARM documents rfc2308-type1. Why documented if not implemented? What is 
plan? Timeline?

10) ARM documents statistics-interval. Why documented if not implemented? 
What is plan? Timeline?

11) ARM documents min-roots but also not implemented. When? Why?

12) ARM says: "... current implementation of <command>acache</command> 
does not short-cut of additional section information from the DNS cache 
data." Since it says "current", what is the plan? When will this change?

13) What does it mean that the "zone Statement Grammar" has "not 
implemented" for check-names in hint zone? Will it be implemented?



  Jeremy C. Reed