Automated Updates of DNS Security (DNSSEC) Trust Anchors
RFC 5011
also known as STD 74
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2023-12-12
|
(System) | Imported membership of rfc5011 in std74 via sync to the rfc-index |
|
2023-12-12
|
(System) | No history of STD74 is currently available in the datatracker before this point |
|
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'This document describes a means for automated, authenticated, and authorized updating of DNSSEC "trust anchors". The … Received changes through RFC Editor sync (changed abstract to '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]') |
|
2018-12-06
|
Jenny Bui | Removed related IPR disclosure: Todd S. Glassey, IP owner's Statement about IPR related to RFC 4033, RFC 4034, RFC 4035, RFC 5155 … |
|
2015-10-14
|
(System) | Notify list changed from dnsext-chairs@ietf.org to (None) |
|
2008-10-02
|
(System) | Posted related IPR disclosure: Todd S. Glassey, IP owner's Statement about IPR related to RFC 4033, RFC 4034, RFC 4035, RFC 5155 … |
|
2007-09-11
|
Amy Vezza | [Note]: 'RFC 5011' added by Amy Vezza |
|
2007-09-11
|
Amy Vezza | State Changes to RFC Published from RFC Ed Queue by Amy Vezza |
|
2007-09-06
|
(System) | RFC published |