--- 1/draft-ietf-ccamp-confirm-data-channel-status-05.txt	2009-08-14 11:12:10.000000000 +0200
+++ 2/draft-ietf-ccamp-confirm-data-channel-status-06.txt	2009-08-14 11:12:10.000000000 +0200
@@ -1,26 +1,26 @@
 Network Working Group                                             D. Li
 Internet Draft                                                    H. Xu
 Category: Standards Track                                        Huawei
                                                             S. Bardalai
                                                                 Fujitsu
                                                               J. Meuric
                                                          France Telecom
                                                             D. Caviglia
                                                                Ericsson
 
-Expires: November 2009                                    May 25, 2009
+Expires: February 2010                                 August 14, 2009
 
                 Data Channel Status Confirmation Extensions
                      for the Link Management Protocol
 
-            draft-ietf-ccamp-confirm-data-channel-status-05.txt
+            draft-ietf-ccamp-confirm-data-channel-status-06.txt
 
 Status of this Memo
 
    This Internet-Draft is submitted to IETF in full conformance with the
    provisions of BCP 78 and BCP 79.
 
    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF), its areas, and its working groups.  Note that
    other groups may also distribute working documents as Internet-Drafts.
 
@@ -432,21 +432,22 @@
 
 4.4. Backward Compatibility
 
    Some nodes running in the network may only support the LMP Message
    Type from 1 to 20, which are already defined in [RFC4204]. The three
    new types of LMP message (Message Type from 21 to 23) defined in this
    document can not be recognized by these nodes. The unknown message
    behavior is not being specified in [RFC4204], it's suggested to
    discard the unknown message silently. This document's defined
    mechanisms presume a certain non-standard behavior of existing/non-
-   document supporting nodes.
+   document supporting nodes. To use this mechanisms all nodes MUST have
+   the extensions described in this document for compatibility.
 
 5. Procedures
 
    The data channel status confirmation related LMP messages MAY be sent
    between adjacent nodes which are triggered by timer periodically or
    driven by some events to confirm the channel status for the data
    links. It's a local police decision to start the data channel status
    confirmation process. The procedure is described below:
 
    . The SENDER constructs a ConfirmDataChannelStatus message which
@@ -518,23 +519,23 @@
 
 7.1. LMP Message Types
 
    IANA maintains the "Link Management Protocol (LMP)" registry which
    has a subregistry called "LMP Message Type". IANA is requested to
    make three new allocations from this registry as follows. The message
    type values are suggested and to be confirmed by IANA.
 
    Value    Description
    ------   ---------------------------------
-     21     ConfirmDataChannelStatus
-     22     ConfirmDataChannelStatusAck
-     23     ConfirmDataChannelStatusNack
+     32     ConfirmDataChannelStatus
+     33     ConfirmDataChannelStatusAck
+     34     ConfirmDataChannelStatusNack
 
 7.2. LMP Data Link Object Subobject
 
    IANA maintains the "Link Management Protocol (LMP)" registry which
    has a subregistry called "LMP Object Class name space and Class type
    (C-Type)". This subregistry has an entry for the DATA_LINK object,
    and there is a further embedded registry called "DATA_LINK Sub-object
    Class name space". IANA is requested to make the following allocation
    from this embedded registry. The value shown is suggested and to be
    confirmed by IANA.