BIND 10 #1431: NSEC3: closest provable encloser proof
BIND 10 Development
do-not-reply at isc.org
Fri Jan 20 08:12:42 UTC 2012
#1431: NSEC3: closest provable encloser proof
-------------------------------------+-------------------------------------
Reporter: | Owner: jinmei
stephen | Status: accepted
Type: | Milestone:
enhancement | Sprint-20120124
Priority: major | Resolution:
Component: | Sensitive: 0
Unclassified | Sub-Project: DNS
Keywords: | Estimated Difficulty: 6
Defect Severity: N/A | Total Hours: 0
Feature Depending on Ticket: NSEC3 |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by jinmei):
trac1431 is ready for review.
On thinking about the interface further as I wrote the mock
implementation, I thought the interface could be (hopefully) better
with some modifications. So the resulting interface is slightly
different from the very original one. See the documentation for
details.
One possible controversial point is whether to allow 'known_encloser'
parameter for possible optimization. Right now we don't necessarily
need it because the underlying data source won't be optimized so soon.
I thought it's quite clear we'll eventually want to provide some
information that encapsulates data source specific knowledge to
findNSEC3() once we reach the point of optimizing things and it would
be nice if the auth code expects it from this stage, but if this
specific feature is considered premature, I'm okay with removing it
for now.
While this is a new API, it's not provide any user visible feature, so
I don't plan to add changelog for this ticket.
--
Ticket URL: <http://bind10.isc.org/ticket/1431#comment:13>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list