Skip to content

NSEC3 optimization

Libor Peltan requested to merge nsec3_optim_proof_no_wildc into master

An optimization of NSEC3 responses. This might make us almost as fast as NSD ;)

We pre-link on load time the nodes with their respective wildcard-proving NSEC3s.

Details: On NSEC3 NXDOMAIN answer, we need to compute three NSEC3 hashes: 1 for the name in question 2 for closest encloser 3 for wildcard child of closest encloser Actually, 2 and 3 can be pre-computed. In Knot, only 2 had been pre-computed, this adds 3.

Edited by Daniel Salzman

Merge request reports