BIND 10 #1078: Update RESLIB/RESOLVER message descriptions

[BIND 10 Development]

#1078: Update RESLIB/RESOLVER message descriptions
-------------------------------------+-------------------------------------
            Reporter:  stephen       |                        Owner:
                Type:  enhancement   |                       Status:  new
            Priority:  minor         |                    Milestone:
           Component:  logging       |  Sprint-20110712
           Sensitive:  0             |                     Keywords:
         Sub-Project:  DNS           |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 some string formating have brackets... use %1 or <%1>  ? or is  that for a
 "tuple" only?

 RESLIB_TESTSERV says conflicting debugging and not debug and " As it
 should never be seen in normal operation, it is a warning message instead
 of a debug message." is too verbose, not needed here

 RESLIB_TIMEOUT error will be reported where?

 RESOLVER_AXFRTCP says "AXFR request" and "received a NOTIFY" and
 RESOLVER_AXFRUDP says "AXFR request" and "received a NOTIFY" -- well which
 is it?  (a NOTIFY is a hint to do an SOA serial check)

 RESOLVER_CLTMOSMALL  does BIND 10 fail to start? then what is  used?
 default? minimum?

 RESOLVER_CLTMOSMALL  is there a corresponding too large?

 Can RESOLVER_CONFIGERR be separated into programmer error and  user error
 with different log ID? Should it say to file a bug report?

 style: some have incomplete / poor grammar for saying it is a debug
 message while some have complete separate sentence for that.

 RESOLVER_DNSMSGSENT  what details?

 RESOLVER_FAILED  does this means that b10-resolver process will end?

 RESOLVER_FWDADDR why could it appear multiple times?

 RESOLVER_FWDQUERY  what checks?

 RESOLVER_LKTMOSMALL does BIND 10 fail to start? Or what does it  use? The
 default? minimum?

 RESOLVER_LKTMOSMALL is there a too large too?

 RESOLVER_NFYNOTAUTH how to correspond this to the sender of the message?
 (log that too?)

 RESOLVER_NORMQUERY what checks?

 RESOLVER_NOROOTADDR add more details? Should this really be a  warning?
 (isn't it just informational and normal?)

 RESOLVER_NOTIN  why can't handle other classes in a query? (And
 description should say this is a query?)

 RESOLVER_NOTONEQUES typo: "entires"? (entries?) (while I don't recall
 seeing it, where is it documented one question is limit? even RFC 1035
 hints multiple questions could be asked.)

 RESOLVER_QUTMOSMALL  should it show the minimum? does BIND 10 fail to
 start? Or does it use default? or minimum?

 RESOLVER_QUTMOSMALL  is there a corresponding too large error?   (but
 maybe the existing ID should be for both: out of range.)

 RESOLVER_RECVMSG description say "DNS"?

 RESOLVER_ROOTADDR why multiple times?

 RESOLVER_SETPARAM "interval to resolver" and "continuing to resolver"
 should be "resolve"?  Too many colons? "resolve gives up" should be
 "resolver"?

 Maybe this description is way too long -- two paragraphs is too long?

 RESOLVER_SHUTDOWN, RESOLVER_STARTED are too noisy for default logging?
 should be debug mode only?

 RESOLVER_STARTING description should mention command line  arguments?

 RESOLVER_UNEXRESP  not enough information? so response doesn't match up
 with an existing outbound query (wrong port, address, name, class)?

-- 
Ticket URL: <http://bind10.isc.org/ticket/1078>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development