BIND 10 #1808: support NSEC for normal NXRRSET in in-memory
BIND 10 Development
do-not-reply at isc.org
Fri May 11 05:02:32 UTC 2012
#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 jinmei):
Replying to [comment:13 kevin_tes]:
> > 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 be done 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?
No, it should *also* be addressed in this branch, and the RFC4035 B.7
case certainly belongs to this branch. Since we're running out of
time, if you don't get it could I propose a possible fix to that?
--
Ticket URL: <http://bind10.isc.org/ticket/1808#comment:15>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list