Requirements for Automated Key Rollover in DNSsec
draft-ietf-dnsop-key-rollover-requirements-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Gilles Guette | ||
| Last updated | 2021-06-19 (Latest revision 2005-01-19) | ||
| 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
This document describes problems that appear during an automated rollover and gives the requirements for the design of communication between parent zone and child zone during an automated rollover process. This document is essentially about in-band key rollover.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)