BIND 10 #1894: use labelsequence in findNSEC3

BIND 10 Development do-not-reply at isc.org
Mon Feb 3 16:42:56 UTC 2014


#1894: use labelsequence in findNSEC3
-------------------------------------+-------------------------------------
            Reporter:  jelte         |                        Owner:  muks
                Type:  enhancement   |                       Status:
            Priority:  high          |  reviewing
           Component:  Unclassified  |                    Milestone:
            Keywords:                |  bind10-1.2-release-freeze
           Sensitive:  0             |                   Resolution:
         Sub-Project:  DNS           |                 CVSS Scoring:
Estimated Difficulty:  5             |              Defect Severity:  N/A
         Total Hours:  0             |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by pselkirk):

 * owner:  UnAssigned => muks


Comment:

 This seems to work. However, it could be yet more efficient if we didn't
 have to repeatedly copy and downcase the name - e.g. if we could hand
 {{{calculate()}}} a {{{Name}}} or {{{LabelSequence}}} that was already
 downcased. But that's a minor optimization, and probably out of scope for
 this ticket.

 Of much greater concern is that the {{{Name::split()}}} technique is still
 used in {{{DatabaseClient::Finder::findNSEC3()}}}, and the ticket
 description explicitly says "for db and mem backends".

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


More information about the bind10-tickets mailing list