BIND 10 #1696: lettuce test for NSEC3 responses

[BIND 10 Development]

#1696: lettuce test for NSEC3 responses
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  jinmei
  jinmei                             |                Status:  reviewing
                       Type:  task   |             Milestone:
                   Priority:         |  Sprint-20120306
  critical                           |            Resolution:
                  Component:         |             Sensitive:  0
  b10-auth                           |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  6
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 '''general'''
 - considering future extensions, is it easy to share the same scenario
   for in-memory and sqlite3 (or other database-based) data sources?
   not requiring it be addressed in this ticket, though.
 - if it's not too hard, I'd like to add tests for uncovered cases (I
   suspect there are some) of RFC5155 Sections 7.2.2 through 7.2.8.  We
   may find some other bugs like #1701.

 '''nsec3_auth.config'''
 - Do we need an explicit Boss (components) configuration?

 '''terrain/querying.py'''

 - I'd say 'response message' instead of 'response packet':
 {{{
 # (flags and edns_flags are both one string with all flags, in the order
 # in which they appear in the response packet.)
 }}}

 - check_last_query_section: I'm afraid it's technically not correct to
   convert all inputs to lower-cased:
 {{{#!python
     # replace whitespace of any length by one space
     response_string = re.sub("[ \t]+", " ", response_string)
     expect = re.sub("[ \t]+", " ", step.multiline)
 }}}
   e.g., RDATA of TXT RR should be considered case sensitive.  But,
   assuming (or hoping) we'll make these checks more reliable in
   future, for now I'm okay with keeping this probably with some
   warning comments.

-- 
Ticket URL: <http://bind10.isc.org/ticket/1696#comment:9>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development