--- 1/draft-ietf-nfsv4-lfs-registry-03.txt	2015-03-27 14:15:09.917652358 -0700
+++ 2/draft-ietf-nfsv4-lfs-registry-04.txt	2015-03-27 14:15:09.937652850 -0700
@@ -1,22 +1,22 @@
 
 NFSv4                                                         D. Quigley
 Internet-Draft
 Intended status: Standards Track                                   J. Lu
-Expires: September 27, 2015                                       Oracle
+Expires: September 28, 2015                                       Oracle
                                                                T. Haynes
                                                             Primary Data
-                                                          March 26, 2015
+                                                          March 27, 2015
 
 Registry Specification for Mandatory Access Control (MAC) Security Label
                                 Formats
-                  draft-ietf-nfsv4-lfs-registry-03.txt
+                  draft-ietf-nfsv4-lfs-registry-04.txt
 
 Abstract
 
    In the past Mandatory Access Control (MAC) systems have used very
    rigid policies which were implemented in particular protocols and
    platforms.  As MAC systems became more widely deployed, additional
    flexibility in mechanism and policy will be required.  While
    traditional trusted systems implemented Multi-Level Security (MLS)
    and integrity models, modern systems have expanded to include
    technologies such as type enforcement.  Due to the wide range of
@@ -38,21 +38,21 @@
    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 September 27, 2015.
+   This Internet-Draft will expire on September 28, 2015.
 
 Copyright Notice
 
    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
@@ -317,25 +317,25 @@
                Example Label Format Specifier Updated Ranges
 
                                   Table 2
 
 5.4.  Modifying an Existing Entry in the Registry
 
    A request to modify either the Description or the published label
    format specification will also require the Specification Required
    IANA policy to be applied.  The Designated Expert reviewer will need
    to determine if the published label format specification either
-
-   obsoletes the Label Format Specifier -  follow the process in
-      Section 5.3
-
-   updates the label syntax and/or model -   approve the change.
+   obsoletes the Label Format Specifier or updates the label syntax and/
+   or model.  If the Label Format Specifier is obsoleted, then the
+   reviewer will follow the process defined in Section 5.3.  Otherwise
+   for the update of either the label syntax and/or the model, the
+   reviewer will approve the change.
 
 6.  References
 
 6.1.  Normative References
 
    [RFC20]    Cerf, V., "ASCII format for network interchange", RFC 20,
               October 1969.
 
    [RFC5226]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
               IANA Considerations Section in RFCs", BCP 26, RFC 5226,