Information on RFC 4033 » RFC Editor (original) (raw)

File formats:

icon for text file icon for PDF icon for HTML icon for inline errata

Status:

PROPOSED STANDARD

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 3597, RFC 3226

Updated by:

RFC 6014, RFC 6840

Authors:

R. Arends
R. Austein
M. Larson
D. Massey
S. Rose

Stream:

IETF

Source:

dnsext (int)

Cite this RFC: TXT | XML | BibTeX

DOI: https://doi.org/10.17487/RFC4033

Discuss this RFC: Send questions or comments to the mailing list dnsext@ietf.org

Other actions:View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 4033


Abstract

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]


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.