Secure parent-child DNS update use cases
draft-wouters-dnsop-secure-update-use-cases-00

 
Document Type Expired Internet-Draft (individual)
Last updated 2013-01-10 (latest revision 2012-07-09)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Expired
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-wouters-dnsop-secure-update-use-cases-00.txt

Abstract

DNS zone administrators occasionally need to update data published by a parent zone, such as NS and DS records. Traditionally these updates have happened out-of-band: through DNS registrar interfaces, EPP, websites, or manually by operators. Some updates could also be done using DNS Dynamic Update [RFC2136]. The IETF's DNSOP working group is considering proposing additional mechanisms for such updates, possibly leveraging DNSSEC for authentication. This document presents some use cases to drive this design work.

Authors

Paul Wouters (pwouters@redhat.com)

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