--- 1/draft-ietf-dnsop-child-syncronization-06.txt	2015-01-06 21:14:49.872977943 -0800
+++ 2/draft-ietf-dnsop-child-syncronization-07.txt	2015-01-06 21:14:49.904978722 -0800
@@ -1,18 +1,18 @@
 
 DNSOP                                                        W. Hardaker
 Internet-Draft                                             Parsons, Inc.
-Intended status: Standards Track                       December 31, 2014
-Expires: July 4, 2015
+Intended status: Standards Track                         January 6, 2015
+Expires: July 10, 2015
 
                  Child To Parent Synchronization in DNS
-                draft-ietf-dnsop-child-syncronization-06
+                draft-ietf-dnsop-child-syncronization-07
 
 Abstract
 
    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
    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
    parental agent and acted on depending on local policy.
 
 Status of this Memo
@@ -23,25 +23,25 @@
    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF).  Note that other groups may also distribute
    working documents as Internet-Drafts.  The list of current Internet-
    Drafts is at http://datatracker.ietf.org/drafts/current/.
 
    Internet-Drafts are draft documents valid for a maximum of six months
    and may be updated, replaced, or obsoleted by other documents at any
    time.  It is inappropriate to use Internet-Drafts as reference
    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 (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.
 
    This document is subject to BCP 78 and the IETF Trust's Legal
    Provisions Relating to IETF Documents
    (http://trustee.ietf.org/license-info) in effect on the date of
    publication of this document.  Please review these documents
    carefully, as they describe your rights and restrictions with respect
    to this document.  Code Components extracted from this document must
    include Simplified BSD License text as described in Section 4.e of
    the Trust Legal Provisions and are provided without warranty as
@@ -567,23 +567,24 @@
    Parameters" registry (http://www.iana.org/assignments/dns-parameters)
    for this record.
 
       TYPE    Value    Meaning                           Reference
       -----   ------   --------------------------        -----------
       CSYNC   TBD      Child To Parent Synchronization   [This document]
 
    The IANA is also requested to create and maintain a sub-registry (the
    "Child Synchronization (CSYNC) Flags" registry) of the "Domain Name
    System (DNS) Parameters" registry.  The initial values for this
-   registry are below.  Assignment of new flag values are subject to
-   "RFC Required" specifications [RFC5226].  The published RFC must be a
-   standards track RFC.
+   registry are below.
+
+   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
    CSYNC record within the 16 bit Flags field.  Thus, a maximum of 16
    flags may be defined.
 
    The initial assignments in this registry are:
 
       Bit      Flag        Description               Reference
       ----     ------      -------------             -----------
       Bit 0    immediate   Immediately process this  [This document,