RFC 3833: Threat Analysis of the Domain Name System (DNS)
In plain English — editorial summary, not part of the RFC
Although the DNS Security Extensions (DNSSEC) have been under development for most of the last decade, the IETF has never written down the specific set of threats against which DNSSEC is designed to protect. Among other drawbacks, this cart-before-the-horse situation has made it difficult to determine whether DNSSEC meets its design goals, since its design goals are not well specified. This note attempts to document some of the known threats to the DNS, and, in doing so, attempts to measure to what extent (if any) DNSSEC is a useful tool in defending against these threats. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3833
- Published
- August 2004
- Authors
- D. Atkins; R. Austein
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3007Secure Domain Name System (DNS) Dynamic UpdateCurrent
November 2000
- RFC 8915Network Time Security for the Network Time ProtocolCurrent
September 2020
- RFC 3647Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices FrameworkCurrent
November 2003
- RFC 4217Securing FTP with TLSUpdated
October 2005
- RFC 4302IP Authentication HeaderCurrent
December 2005
- RFC 4303IP Encapsulating Security Payload (ESP)Current
December 2005
- RFC 4305Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)Obsoleted
December 2005
- RFC 4306Internet Key Exchange (IKEv2) ProtocolObsoleted
December 2005
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?