DNSSEC Trust Anchor Publication for the Root Zone
RFC 7958
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2020-01-27
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
|
2019-11-18
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
|
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'The root zone of the Domain Name System (DNS) has been cryptographically signed using DNS Security … Received changes through RFC Editor sync (changed abstract to 'The root zone of the Domain Name System (DNS) has been cryptographically signed using DNS Security Extensions (DNSSEC). In order to obtain secure answers from the root zone of the DNS using DNSSEC, a client must configure a suitable trust anchor. This document describes the format and publication mechanisms IANA has used to distribute the DNSSEC trust anchors.') |
|
2016-09-01
|
(System) | Received changes through RFC Editor sync (created alias RFC 7958, changed abstract to 'The root zone of the Domain Name System (DNS) has been … Received changes through RFC Editor sync (created alias RFC 7958, changed abstract to 'The root zone of the Domain Name System (DNS) has been cryptographically signed using DNS Security Extensions (DNSSEC).', changed standardization level to Informational, changed state to RFC, added RFC published event at 2016-08-31, changed ISE state to Published RFC) |
|
2016-08-31
|
(System) | RFC published |