DNSSEC KSK rollover failure recovery practices
draft-yoneya-dnssec-kskro-failure-recovery-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Yoshiro Yoneya , Patrik Wallstrom | ||
| Last updated | 2013-03-11 (Latest revision 2012-09-04) | ||
| 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 a set of common problems and possible recovery methods for DNSSEC when there is a DS published in the parent zone which does no longer match any DNSKEY in the child zone. As DNSSEC validators are becoming widely deployed, this will have serious effect on the availability of the zone, and the need for a quick recovery is needed.
Authors
Yoshiro Yoneya
Patrik Wallstrom
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)