(1) This RFC is being requested as Best Current Practice (BCP), and this is the
proper type of RFC, and it is indicated as such.
(2)
Technical Summary:
NSEC3 is a DNSSEC mechanism providing proof of non-existence by
promising there are no names that exist between two domainnames
within a zone. Unlike its counterpart NSEC, NSEC3 avoids directly
disclosing the bounding domainname pairs. This document provides
guidance on setting NSEC3 parameters based on recent operational
deployment experience.
Working Group Summary:
Working group consensus took some time, as the discussion about what were the
correct values to recommend. After iterative testing, recommended values were
agreed via working group consensus.
Document Quality:
There are existing implementations that are described in Appendix E.
Personnel:
Tim Wicinski is the Document Shepherd.
Warren Kumari is the R. A. D.
(3) The Document Shepherd did a detailed review of the document
for content as well as simple editorial checks (spelling/grammar).
The shepherd feels the document is ready for publication.
(4) The Document Shepherd has no concerns on the depth or breadth
of the reviews.
(5) There is no need for broader review.
(6) There are no concerns from the document shepherd.
(7) No IPR disclosures
(8) There is no IPR
(9) The WG Consensus on this document is very solid.
(10) There has been no appeals.
(11) All nits found have been addressed by the authors.
(12) No formal review needed
(13) All references have been identified as normative or informative.
(14) All normative references are in a clear state.
(15) There are no downward normative references
(16) This RFC will not change any existing RFCs.
(17) The document shepherd confirmed the consistency and references of
the IANA Considerations section are accurate.
(18) N/A
(19) N/A
(20) No Yang Necessary