Last Call: <draft-ietf-dnsop-child-syncronization-01.txt> (Child To Parent Synchronization in DNS) to Informational RFC

The IESG <iesg-secretary@ietf.org> Mon, 09 June 2014 14:09 UTC

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-dnsop-child-syncronization-01.txt> (Child To Parent Synchronization in DNS) to Informational RFC
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
Message-ID: <20140609140901.2827.30141.idtracker@ietfa.amsl.com>
Date: Mon, 09 Jun 2014 07:09:01 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/hI5VXCbSJoLyv1LdhUnj8dAal50
Cc: dnsop@ietf.org
Reply-To: ietf@ietf.org

The IESG has received a request from the Domain Name System Operations WG
(dnsop) to consider the following document:
- 'Child To Parent Synchronization in DNS'
  <draft-ietf-dnsop-child-syncronization-01.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2014-06-23. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

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 of and value
   change of the record may be monitored by a parental agent and acted
   on as appropriate.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-dnsop-child-syncronization/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-dnsop-child-syncronization/ballot/


No IPR declarations have been submitted directly on this I-D.

Last Call: <draft-ietf-dnsop-child-syncronization… The IESG