metasystema.org
CurrentBEST CURRENT PRACTICEIETF streamBCP236

RFC 9276: Guidance for NSEC3 Parameter Settings

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC9276
Published
August 2022
Authors
W. Hardaker; V. Dukhovni
Status
BEST CURRENT PRACTICE
Stream
IETF
Area
ops
Pages
10
Also known as
BCP236
Updates:
RFC 5155

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/9276-guidance-for-nsec3-parameter-settings