metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 3755: Legacy Resolver Compatibility for Delegation Signer (DS)

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4033, RFC 4034, RFC 4035.

Current document in this lineage: RFC 4033 — DNS Security Introduction and Requirements; RFC 4034 — Resource Records for the DNS Security Extensions; RFC 4035 — Protocol Modifications for the DNS Security Extensions

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

As the DNS Security (DNSSEC) specifications have evolved, the syntax and semantics of the DNSSEC resource records (RRs) have changed. Many deployed nameservers understand variants of these semantics. Dangerous interactions can occur when a resolver that understands an earlier version of these semantics queries an authoritative server that understands the new delegation signer semantics, including at least one failure scenario that will cause an unsecured zone to be unresolvable. This document changes the type codes and mnemonics of the DNSSEC RRs (SIG, KEY, and NXT) to avoid those interactions. [STANDARDS-TRACK]

Document record

Document ID
RFC3755
Published
May 2004
Authors
S. Weiler
Status
PROPOSED STANDARD
Stream
IETF
Area
int
Pages
9
Also known as
—
Obsoleted by:
RFC 4033, RFC 4034, RFC 4035
Updates:
RFC 2535, RFC 3658
Updated by:
RFC 3757, RFC 3845

Topics

Standards lineage

This document is one revision in a chain of 13 RFCs, each formally replacing the one before it.

  1. RFC 2065 (1997)
  2. RFC 2535 (1999)
  3. RFC 3008 (2000)
  4. RFC 3090 (2001)
  5. RFC 3445 (2002)
  6. RFC 3655 (2003)
  7. RFC 3658 (2003)
  8. RFC 3755 (2004)
  9. RFC 3757 (2004)
  10. RFC 3845 (2004)
  11. RFC 4033 (2005)
  12. RFC 4034 (2005)
  13. RFC 4035 (2005) ✓

Read the full history of Protocol Modifications for the DNS Security Extensions →

Referenced by

5 later RFCs formally update or obsolete part of this document.

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/3755-legacy-resolver-compatibility-for-delegation-signer-ds