metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 4033: DNS Security Introduction and Requirements

Still current, but amended. Parts of this document are changed or extended by RFC 6014, RFC 6840. Read both.

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

The Domain Name System Security Extensions (DNSSEC) add data origin authentication and data integrity to the Domain Name System. This document introduces these extensions and describes their capabilities and limitations. This document also discusses the services that the DNS security extensions do and do not provide. Last, this document describes the interrelationships between the documents that collectively describe DNSSEC. [STANDARDS-TRACK]

Document record

Document ID
RFC4033
Published
March 2005
Authors
R. Arends; R. Austein; M. Larson; D. Massey; S. Rose
Status
PROPOSED STANDARD
Stream
IETF
Area
int
Pages
21
Also known as
—
Obsoletes:
RFC 2535, RFC 3008, RFC 3090, RFC 3445, RFC 3655, RFC 3658, RFC 3755, RFC 3757, RFC 3845
Updates:
RFC 1034, RFC 1035, RFC 2136, RFC 2181, RFC 2308, RFC 3225, RFC 3226, RFC 3597
Updated by:
RFC 6014, RFC 6840

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

2 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/4033-dns-security-introduction-and-requirements