BIND 10 #1177: NSEC support in new data source

[BIND 10 Development]

#1177: NSEC support in new data source
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  vorner
  jinmei                             |                Status:  reviewing
                       Type:  task   |             Milestone:
                   Priority:  major  |  Sprint-20110927
                  Component:  data   |            Resolution:
  source                             |             Sensitive:  0
                   Keywords:         |           Sub-Project:  DNS
            Defect Severity:  N/A    |  Estimated Difficulty:  5
Feature Depending on Ticket:         |           Total Hours:  0
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:5 vorner]:

 > I don't know what is the correct way to handle empty nonterminal
 asterisk cases (eg. if there's a.*.example.org, then *.example.org is
 empty nonterminal and therefore b.example.org must give NXRRSET to the
 user, but what is the correct proof in this case? I think I got lost in
 the RFCs enough). Or, should we say this doesn't happen and we don't
 really care much?

 I believe I've answered this question in the review comment (for the
 database test).  But I'm not 100% sure about it either.  I'd suggest
 you trying that case with other implementations.

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