Guidance for NSEC3 Parameter Settings
RFC 9276
also known as BCP 236
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2026-05-20
|
(System) | Changed metadata: changed keywords to '['DNSSEC', 'DNS', 'NSEC3', 'NSEC', 'Denial of Existence']' from '[]' |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2026-05-20
|
(System) | Changed author "V. Dukhovni": changed name from "Viktor Dukhovni" to "V. Dukhovni", changed affiliation from "Bloomberg, L.P." to "Bloomberg L.P." |
|
2026-05-20
|
(System) | Changed author "W. Hardaker": changed name from "Wes Hardaker" to "W. Hardaker" |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2023-12-12
|
(System) | Imported membership of rfc9276 in bcp236 via sync to the rfc-index |
|
2023-12-12
|
(System) | No history of BCP236 is currently available in the datatracker before this point |
|
2022-08-26
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
|
2022-08-26
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
|
2022-08-11
|
(System) | Received changes through RFC Editor sync (created alias RFC 9276, changed title to 'Guidance for NSEC3 Parameter Settings', changed abstract to 'NSEC3 is a … Received changes through RFC Editor sync (created alias RFC 9276, changed title to 'Guidance for NSEC3 Parameter Settings', changed abstract to 'NSEC3 is a DNSSEC mechanism providing proof of nonexistence by asserting that there are no names that exist between two domain names within a zone. Unlike its counterpart NSEC, NSEC3 avoids directly disclosing the bounding domain name pairs. This document provides guidance on setting NSEC3 parameters based on recent operational deployment experience. This document updates RFC 5155 with guidance about selecting NSEC3 iteration and salt parameters.', changed pages to 10, changed standardization level to Best Current Practice, changed state to RFC, added RFC published event at 2022-08-11, changed IESG state to RFC Published, created updates relation between draft-ietf-dnsop-nsec3-guidance and RFC 5155, created alias BCP 236) |
|
2022-08-11
|
(System) | RFC published |