draft-ietf-dnsop-child-syncronization-06.txt		draft-ietf-dnsop-child-syncronization-07.txt
	DNSOP W. Hardaker		DNSOP W. Hardaker
	Internet-Draft Parsons, Inc.		Internet-Draft Parsons, Inc.
	Intended status: Standards Track December 31, 2014		Intended status: Standards Track January 6, 2015
	Expires: July 4, 2015		Expires: July 10, 2015
	Child To Parent Synchronization in DNS		Child To Parent Synchronization in DNS
	draft-ietf-dnsop-child-syncronization-06		draft-ietf-dnsop-child-syncronization-07
	Abstract		Abstract
	This document specifies how a child zone in the DNS can publish a		This document specifies how a child zone in the DNS can publish a
	record to indicate to a parental agent that the parental agent may		record to indicate to a parental agent that the parental agent may
	copy and process certain records from the child zone. The existence		copy and process certain records from the child zone. The existence
	of the record and any change in its value can be monitored by a		of the record and any change in its value can be monitored by a
	parental agent and acted on depending on local policy.		parental agent and acted on depending on local policy.
	Status of this Memo		Status of this Memo
	skipping to change at page 1, line 34		skipping to change at page 1, line 34
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on July 4, 2015.		This Internet-Draft will expire on July 10, 2015.
	Copyright Notice		Copyright Notice
	Copyright (c) 2014 IETF Trust and the persons identified as the		Copyright (c) 2015 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	skipping to change at page 13, line 29		skipping to change at page 13, line 29
	Parameters" registry (http://www.iana.org/assignments/dns-parameters)		Parameters" registry (http://www.iana.org/assignments/dns-parameters)
	for this record.		for this record.
	TYPE Value Meaning Reference		TYPE Value Meaning Reference
	----- ------ -------------------------- -----------		----- ------ -------------------------- -----------
	CSYNC TBD Child To Parent Synchronization [This document]		CSYNC TBD Child To Parent Synchronization [This document]
	The IANA is also requested to create and maintain a sub-registry (the		The IANA is also requested to create and maintain a sub-registry (the
	"Child Synchronization (CSYNC) Flags" registry) of the "Domain Name		"Child Synchronization (CSYNC) Flags" registry) of the "Domain Name
	System (DNS) Parameters" registry. The initial values for this		System (DNS) Parameters" registry. The initial values for this
	registry are below. Assignment of new flag values are subject to		registry are below.
	"RFC Required" specifications [RFC5226]. The published RFC must be a
	standards track RFC.		A "Standards Action" [RFC5226] is required for the assignment of new
			flag value.
	This registry will hold a set of single-bit "Flags" for use in the		This registry will hold a set of single-bit "Flags" for use in the
	CSYNC record within the 16 bit Flags field. Thus, a maximum of 16		CSYNC record within the 16 bit Flags field. Thus, a maximum of 16
	flags may be defined.		flags may be defined.
	The initial assignments in this registry are:		The initial assignments in this registry are:
	Bit Flag Description Reference		Bit Flag Description Reference
	---- ------ ------------- -----------		---- ------ ------------- -----------
	Bit 0 immediate Immediately process this [This document,		Bit 0 immediate Immediately process this [This document,
End of changes. 5 change blocks.
	8 lines changed or deleted		9 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/