BIND 10 #1582: auth::Query NSEC3 support: No Data, DS case

BIND 10 Development do-not-reply at isc.org
Tue Feb 14 11:36:37 UTC 2012


#1582: auth::Query NSEC3 support: No Data, DS case
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  jelte
  jinmei                             |                Status:  reviewing
                       Type:  task   |             Milestone:
                   Priority:  major  |  Sprint-20120221
                  Component:         |            Resolution:
  b10-auth                           |             Sensitive:  0
                   Keywords:         |           Sub-Project:  DNS
            Defect Severity:  N/A    |  Estimated Difficulty:  4
Feature Depending on Ticket:  NSEC3  |           Total Hours:  0.75
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by vorner):

 * owner:  vorner => jelte
 * totalhours:  0 => 0.75


Comment:

 Hello

 Replying to [comment:7 jelte]:
 > Ready for review. Due to the addition of a few names in the fake
 query_unittest data, I had make a few minor updates to another test.

 I think it looks OK and ready for merge.

 > BTW, should we unify that hardcoded hash-map a bit? (i.e. use the actual
 hash values for the names we use, for instance, we now use some from 5155,
 some mangled, and some that are actually based on the example.com. names,
 I realize we probably need a few slightly mangled ones, but the rest
 should be reproducible imo, and not randomly grabbed, so IMO we should
 either base them all on example.com, or change the zone origin to
 example., so that it matches the example zone in 5155)

 I don't know. I don't think this is important at all, they are just faked
 names, but if you feel like unifying them, feel free to do so.

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


More information about the bind10-tickets mailing list