--- 1/draft-ryoo-mpls-tp-aps-updates-02.txt 2016-03-03 21:16:27.441783988 -0800 +++ 2/draft-ryoo-mpls-tp-aps-updates-03.txt 2016-03-03 21:16:27.457784390 -0800 @@ -1,24 +1,24 @@ MPLS Working Group J. Ryoo Internet-Draft T. Cheung Updates: 7271 (if approved) ETRI Intended status: Standards Track H. van Helvoort -Expires: August 7, 2016 Hai Gaoming BV +Expires: September 4, 2016 Hai Gaoming BV I. Busi G. Weng Huawei Technologies - February 4, 2016 + March 3, 2016 Updates to MPLS Transport Profile (MPLS-TP) Linear Protection in Automatic Protection Switching (APS) Mode - draft-ryoo-mpls-tp-aps-updates-02.txt + draft-ryoo-mpls-tp-aps-updates-03.txt Abstract This document contains updates to MPLS Transport Profile (MPLS-TP) linear protection in Automatic Protection Switching (APS) mode defined in RFC 7271. The updates provide rules related to the initialization of the Protection State Coordination (PSC) Control Logic, in which the state machine resides, when operating in APS mode. @@ -30,21 +30,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 August 7, 2016. + This Internet-Draft will expire on September 4, 2016. Copyright Notice Copyright (c) 2016 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 @@ -199,22 +199,22 @@ It is worth noting that in some restart scenarios (e.g., cold rebooting) no valid SF/SD indications may be present at the input of the Local Request logic. In this case, the PSC Control Logic would restart as if no local requests are present. If a valid SF/SD indication is detected later, this would be notified to the PSC Control Logic and trigger state change. 4.2. State Transition Modification In addition to the initialization behavior described in Section 4.1, - four cells of remote state transition table need to be changed to - make two end nodes converged after initialization. State transition + four cells of the remote state transition table need to be changed to + make two end nodes converge after initialization. State transition by remote message defined in Section 11.2 of [RFC7271] is modified as follows (only modified cells are shown): | MS-W | MS-P | WTR | EXER | RR | DNR | NR --------+---------+---------+-----+------+----+------+---- N | | | (13)| | | DNR | PF:W:R | | | | | | DNR | PF:DW:R | | | | | | DNR | The changes in two rows of remote protecting failure states lead to