BIND 10 #1574: Add support for loading NSEC3 RRsets to in memory data source
BIND 10 Development
do-not-reply at isc.org
Wed Jan 18 06:56:59 UTC 2012
#1574: Add support for loading NSEC3 RRsets to in memory data source
-------------------------------------+-------------------------------------
Reporter: jinmei | Owner:
Type: task | Status: new
Priority: major | Milestone: Next-
Component: data source | Sprint-Proposed
Sensitive: 0 | Keywords:
Sub-Project: DNS | Defect Severity: N/A
Estimated Difficulty: 0 | Feature Depending on Ticket: NSEC3
Total Hours: 0 | Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
We use a separate storage for NSEC3 RR sets in the in memory data
source. That could even be a straightforward STL map<Name,
(Const)RRsetPtr> (this is not efficient in terms of memory
footprint, but should be okay for the initial implementation).
For simplicity, I propose ensuring consistency of NSEC3 parameters
at load time: As we add NSEC3s to that storage, check the hash
algorithm, iteration, and salt are the same for all RRs. At the end
of loading check the existence of NSEC3PARAM RR at the apex, and
check the parameters of NSEC3PARAM and of NSEC3 RRs are the same.
Reject loading if these aren't met.
--
Ticket URL: <http://bind10.isc.org/ticket/1574>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list