FYI, this new version is generally complete. There has been text
inserted to talk about the fact that it's only doing NS/A/AAAA records
and that it expects a secure working DNSSEC environment, and to look
toward CDS for doing DNSSEC synchronization.
--- Begin Message ---
A new version of I-D, draft-hardaker-dnsop-csync-02.txt
has been successfully submitted by Wes Hardaker and posted to the
IETF repository.
Filename: draft-hardaker-dnsop-csync
Revision: 02
Title: Child To Parent Synchronization in DNS
Creation date: 2013-10-21
Group: Individual Submission
Number of pages: 12
URL:
http://www.ietf.org/internet-drafts/draft-hardaker-dnsop-csync-02.txt
Status: http://datatracker.ietf.org/doc/draft-hardaker-dnsop-csync
Htmlized: http://tools.ietf.org/html/draft-hardaker-dnsop-csync-02
Diff: http://www.ietf.org/rfcdiff?url2=draft-hardaker-dnsop-csync-02
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.
Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.
The IETF Secretariat
--- End Message ---
--
Wes Hardaker
Parsons
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
