Parent stores the child's zone KEYs
draft-ietf-dnsext-parent-stores-zone-keys-01
| Document | Type |
Expired Internet-Draft
(dnsext WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Miek Gieben , Ted Lindgreen | ||
| Last updated | 2001-05-09 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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
When dealing with large amounts of keys the procedures to update a zone and to sign a zone need to be clearly defined and practically possible. The current idea is to have the zone KEY RR and the parent's SIG to reside in the child's zone and perhaps also in the parent's zone. Operational experiences have prompted us to develop an alternative scheme in which the parent zone stores the parent's signature over the child's key and also the child's key itself.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)