Rollover of statically configured resolver keys
draft-ietf-dnsop-resolver-rollover-00
This document is an Internet-Draft (I-D).
Anyone may submit an I-D to the IETF.
This I-D is not endorsed by the IETF and has no formal standing in the
IETF standards process.
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Olaf Kolkman | ||
| Last updated | 2021-06-19 (Latest revision 2001-06-28) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Key rollovers will be needed for secure deployment of the DNS secu- rity extensions (DNSSEC). From an end-user perspective these rollovers should be transparent i.e. at any point in time an end-user should be able to verify the chain of trust from a statically config- ured secure entry point.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)