BIND 10 #1808: support NSEC for normal NXRRSET in in-memory

[BIND 10 Development]

#1808: support NSEC for normal NXRRSET in in-memory
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  kevin_tes
  jinmei                             |                Status:  reviewing
                       Type:  task   |             Milestone:
                   Priority:         |  Sprint-20120515
  medium                             |            Resolution:
                  Component:  data   |             Sensitive:  0
  source                             |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  3
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:  in-    |
  memory NSEC                        |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by kevin_tes):

 Replying to [comment:12 jinmei]:
 > One more thing: we need to make sure wildcard substitution doesn't
 > happen for NSEC in the "wildcard no data" case.  Otherwise Section B.7
 > case of RFC4035 will fail (we'd replace *.w.example/NSEC with
 > a.z.w.example/NSEC).
 Yes，I think it should do in those codes below:
 {{{
 // If there is an exact match but the node is empty, it's equivalent
 // to NXRRSET.
 if (node->isEmpty()) {
     LOG_DEBUG(logger, DBG_TRACE_DATA, DATASRC_MEM_DOMAIN_EMPTY).
               arg(name);
     return (createFindResult(NXRRSET, ConstRBNodeRRsetPtr(), rename));
 }
 }}}
 And I think it should not be done in this task,should we?

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