metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 3008: Domain Name System Security (DNSSEC) Signing Authority

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

This document proposes a revised model of Domain Name System Security (DNSSEC) Signing Authority. The revised model is designed to clarify earlier documents and add additional restrictions to simplify the secure resolution process. Specifically, this affects the authorization of keys to sign sets of records. [STANDARDS-TRACK]

Document record

Document ID
RFC3008
Published
November 2000
Authors
B. Wellington
Status
PROPOSED STANDARD
Stream
IETF
Area
int
Pages
7
Also known as
—
Obsoleted by:
RFC 4033, RFC 4034, RFC 4035
Updates:
RFC 2535
Updated by:
RFC 3658

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

4 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/3008-domain-name-system-security-dnssec-signing-authority