RFC 5011: Automated Updates of DNS Security (DNSSEC) Trust Anchors
In plain English — editorial summary, not part of the RFC
This document describes a means for automated, authenticated, and authorized updating of DNSSEC "trust anchors". The method provides protection against N-1 key compromises of N keys in the trust point key set. Based on the trust established by the presence of a current anchor, other anchors may be added at the same place in the hierarchy, and, ultimately, supplant the existing anchor(s). This mechanism will require changes to resolver management behavior (but not resolver resolution behavior), and the addition of a single flag bit to the DNSKEY record. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5011
- Published
- September 2007
- Authors
- M. StJohns
- Status
- INTERNET STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 14
- Also known as
- STD74
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5010The Dynamic Host Configuration Protocol Version 4 (DHCPv4) Relay Agent Flags SuboptionCurrent
September 2007
- RFC 5007DHCPv6 LeasequeryCurrent
September 2007
- RFC 5001DNS Name Server Identifier (NSID) OptionCurrent
August 2007
- RFC 5026Mobile IPv6 Bootstrapping in Split ScenarioUpdated
October 2007
- RFC 4994DHCPv6 Relay Agent Echo Request OptionCurrent
September 2007
- RFC 5030Mobile IPv4 RADIUS RequirementsCurrent
October 2007
- RFC 4988Mobile IPv4 Fast HandoversCurrent
October 2007
- RFC 4986Requirements Related to DNS Security (DNSSEC) Trust Anchor RolloverCurrent
August 2007
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?