Child To Parent Synchronization in DNS
draft-hardaker-dnsop-csync-02
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Wes Hardaker | ||
| Last updated | 2014-04-24 (Latest revision 2013-10-21) | ||
| Replaced by | draft-ietf-dnsop-child-syncronization | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-dnsop-child-syncronization | |
| 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 specifies how a child zone in the DNS can publish a record to indicate to a parental agent that it may copy and process certain records from the child zone. The existence and change of the record may be monitored by a parental agent, after which the parent may act on the data appropriately.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)