BIND 10 #1305: auth NSEC support: some more updates to data source

[BIND 10 Development]

#1305: auth NSEC support: some more updates to data source
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  jinmei
  jinmei                             |                Status:  accepted
                       Type:  task   |             Milestone:
                   Priority:  major  |  Sprint-20111025
                  Component:  data   |            Resolution:
  source                             |             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      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 The trac1305 branch is ready for review.

 This branch basically does what was described in the parent ticket
 (#1244) in a pretty straightforward way, but I guess I need to make
 notes about a few things.

 - This branch does not introduce the new "WILDCARD_EMPTY" code.
   On a closer look, it seemed we actually don't need it - in the end
   we should be able to handle both "EMPTY" and "NXRRSET" cases in the
   same way (although why they can be same is not that straightforward
   as it might look).  I'll update the corresponding followup tickets
   about this.
 - The WILDCARD_CNAME code was added, but right now b10-auth does not
   handle it (even for the non DNSSEC case).  It doesn't do real harm
   in practice (yet), however, because the only available datasrc for
   b10-auth right now (i.e. in-memory) doesn't (yet) return this new
   code anyway.
 - On a related note to the previous bullet, I guess we should probably
   separate the notion of wildcard related result and other result
   codes, rather than integrating everything in the same enum space.
   But that would be a separate discussion.
 - I made straightforward updates to the python wrapper, but the test
   is not so detailed as the C++ tests.  This is actually not specific
   to this ticket - before we start this task the python tests are much
   more limited than C++ versions.  I believe we should eventually
   port the C++ versions of tests (maybe also porting the mock
   database accessor) for the python wrappers, but I'd suggest doing it
   in a separate ticket.

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