RFC 4471: Derivation of DNS Name Predecessor and Successor
In plain English — editorial summary, not part of the RFC
This document describes two methods for deriving the canonically-ordered predecessor and successor of a DNS name. These methods may be used for dynamic NSEC resource record synthesis, enabling security-aware name servers to provide authenticated denial of existence without disclosing other owner names in a DNSSEC secured zone. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC4471
- Published
- September 2006
- Authors
- G. Sisson; B. Laurie
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- int
- Pages
- 23
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4035Protocol Modifications for the DNS Security ExtensionsUpdated
March 2005
- RFC 4034Resource Records for the DNS Security ExtensionsUpdated
March 2005
- RFC 4033DNS Security Introduction and RequirementsUpdated
March 2005
- RFC 4955DNS Security (DNSSEC) ExperimentsCurrent
July 2007
- RFC 4956DNS Security (DNSSEC) Opt-InCurrent
July 2007
- RFC 3845DNS Security (DNSSEC) NextSECure (NSEC) RDATA FormatObsoleted
August 2004
- RFC 3757Domain Name System KEY (DNSKEY) Resource Record (RR) Secure Entry Point (SEP) FlagObsoleted
May 2004
- RFC 3755Legacy Resolver Compatibility for Delegation Signer (DS)Obsoleted
May 2004
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?