--- 1/draft-ietf-ccamp-confirm-data-channel-status-01.txt 2008-11-03 02:12:02.000000000 +0100 +++ 2/draft-ietf-ccamp-confirm-data-channel-status-02.txt 2008-11-03 02:12:02.000000000 +0100 @@ -3,26 +3,26 @@ Huawei Snigdho Bardalai Fujitsu Julien Meuric France Telecom Diego Caviglia Ericsson Internet Draft Category: Standards Track -Expires: April 2009 October 30, 2008 +Expires: May 2009 November 3, 2008 Data Channel Status Confirmation Extensions for the Link Management Protocol - draft-ietf-ccamp-confirm-data-channel-status-01.txt + draft-ietf-ccamp-confirm-data-channel-status-02.txt Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering @@ -455,26 +455,26 @@ The data channel status mismatch results MAY be stored, and this information MAY be queried in the future. The data channel status mismatch issue warned about by LMP may be automatically resolved by RSVP restart. For example, the restarting node may also have damaged its data plane. This leaves the data channels mismatched. But RSVP restart will re-install the data plane state in the restarting node. If the ConfirmDataChannelStatus message is not recognized by the - RECEIVER, and the RECEIVER may not send out an acknowledgement - message to the SENDER. In this case, if the - ConfirmDataChannelStatusAck or ConfirmDataChannelStatusNack message - is not received by the SENDER within the configured time, the SENDER - SHOULD terminate the data channel confirmation procedure. A default - value of 1 minutes is suggested for this timer. + RECEIVER, the RECEIVER will not send out an acknowledgement message + to the SENDER. In this case, if the ConfirmDataChannelStatusAck or + ConfirmDataChannelStatusNack message is not received by the SENDER + within the configured time, the SENDER SHOULD terminate the data + channel confirmation procedure. A default value of 1 minutes is + suggested for this timer. 6. Security Considerations [RFC4204] describes how LMP messages between peers can be secured, and these measures are equally applicable to the new messages defined in this document. The operation of the procedures described in this document does not of themselves constitute a security risk since they do not cause any change in network state. It would be possible, if the messages were @@ -547,21 +547,21 @@ Multi-Protocol Label Switching (GMPLS)", RFC 4205, October 2005 10. Authors' Addresses Dan Li Huawei Technologies F3-5-B R&D Center, Huawei Base, Shenzhen 518129 P.R.China - Phone: +86 755-289-71184 + Phone: +86 755-289-70230 Email: danli@huawei.com Huiying Xu Huawei Technologies F3-5-B R&D Center, Huawei Base, Shenzhen 518129 P.R.China Phone: +86 755-289-72909 Email: xuhuiying@huawei.com @@ -576,20 +576,21 @@ Snigdho C. Bardalai Fujitsu Network Communications 2801 Telecom Parkway, Richardson, Texas 75082 United States of America Phone: +1 972 479 2951 Email: snigdho.bardalai@us.fujitsu.com Julien Meuric France Telecom + Orange Labs 2, avenue Pierre Marzin 22307 Lannion Cedex France Phone: +33 2 96 05 28 28 Email: julien.meuric@orange-ftgroup.com Diego Caviglia Ericsson Via A. Negrone 1/A 16153