Parent's SIG over child's KEY
draft-ietf-dnsop-parent-sig-00

Document Type Expired Internet-Draft (dnsop WG)
Last updated 2001-01-25
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-dnsop-parent-sig-00.txt

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 KEY RR and the parent's SIG to reside in the child's zone and perhaps also in the parent's zone. We feel that this would lead to very complicated procedures for large TLD's. We propose a alternative scheme in which the parent zone stores the parent's signature over the child's key and also a copy of the child's key itself. The advantage of this proposal is that all signatures signed by a key are in the same zone file as the producing key. This allows for a simple key rollover and resigning mechanism. For large TLD's this is extremely important. We further discuss the impact on a secure aware resolver/forwarder.

Authors

Miek Gieben (miek@nlnetlabs.nl)
Miek Gieben (miek@nlnetlabs.nl)
Ted Lindgreen (ted@nlnetlabs.nl)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)