--- 1/draft-ietf-ccamp-lmp-behavior-negotiation-04.txt	2012-01-19 03:14:00.462671829 +0100
+++ 2/draft-ietf-ccamp-lmp-behavior-negotiation-05.txt	2012-01-19 03:14:00.482670977 +0100
@@ -1,23 +1,23 @@
 Network Working Group                                          Dan Li
 Internet Draft                                                 Huawei
 Updates: 4204, 4207,4209, 5818                          D. Ceccarelli
 Category: Standards Track                                    Ericsson
                                                            Lou Berger
                                                                  LabN
 
-Expires: December 2011                                   June 7, 2011
+Expires: July 2012                                   January 17, 2012
 
              Link Management Protocol Behavior Negotiation and
                        Configuration Modifications
 
-             draft-ietf-ccamp-lmp-behavior-negotiation-04.txt
+             draft-ietf-ccamp-lmp-behavior-negotiation-05.txt
 
 Abstract
 
    The Link Management Protocol (LMP) is used to coordinate the
    properties, use, and faults of data links in Generalized
    Multiprotocol Label Switching (GMPLS) networks. This document
    defines an extension to LMP to negotiate capabilities and indicate
    support for LMP extensions. The defined extension is compatible
    with non-supporting implementations.
 
@@ -35,21 +35,21 @@
    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."
 
    The list of current Internet-Drafts can be accessed at
    http://www.ietf.org/ietf/1id-abstracts.txt
 
    The list of Internet-Draft Shadow Directories can be accessed at
    http://www.ietf.org/shadow.html
 
-   This Internet-Draft will expire on December 7, 2011.
+   This Internet-Draft will expire on July 16, 2012.
 
 Copyright Notice
 
    Copyright (c) 2010 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
@@ -280,21 +280,21 @@
 
       Other bits may be defined in future documents, in which case the
       number of MBZ bits field is expected to change.
 
 3.2. Processing
 
    The inclusion of a BehaviorConfig type object in a message is
    discussed above in Section 2.2.
 
    When sending a BehaviorConfig type object, the N-bit (negotiable) in
-   the LMP object header must be set (N=1) in the LMP object header.
+   the LMP object header MUST be set (N=1) in the LMP object header.
 
    When sending a BehaviorConfig type object in Config and ConfigNack
    messages, the flags field SHOULD be set based on the supported
    capabilities of the sending node. When sending a ConfigAck message,
    the flags field MUST be set to the value received in the
    corresponding Config message.
 
    When receiving a BehaviorConfig type object, the node compares the
    flags field against its capacities.  Any bit set in the MBZ portion
    of the flags field MUST be interpreted as unacceptable. Processing
@@ -445,21 +445,21 @@
              Systems", RFC 4209, October 2005.
 
    [RFC5818] D. Li, Ed., "Data Channel Status Confirmation Extensions
              for the Link Management Protocol", RFC 5818, April 2010.
 
 9.2. Informative References
 
    [LMP TEST] D. Ceccarelli, Ed., "Link Management Protocol (LMP) Test
              Messages Extensions for Evolutive Optical Transport
              Networks (OTN)" draft-ceccarelli-ccamp-gmpls-g709-lmp-
-             test-02.txt, May, 2010.
+             test-03.txt, April, 2011.
 
 10. Authors' Addresses
 
       Dan Li
       Huawei Technologies
       F3-5-B R&D Center, Huawei Industrial Base,
       Shenzhen 518129 China
       Phone: +86 755-289-70230
       Email: danli@huawei.com