--- 1/draft-ietf-mpls-tp-aps-updates-01.txt 2017-01-03 17:13:23.185252849 -0800 +++ 2/draft-ietf-mpls-tp-aps-updates-02.txt 2017-01-03 17:13:23.205253319 -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: March 19, 2017 Hai Gaoming BV +Expires: July 7, 2017 Hai Gaoming BV I. Busi - G. Weng + G. Wen Huawei Technologies - September 15, 2016 + January 3, 2017 Updates to MPLS Transport Profile (MPLS-TP) Linear Protection in Automatic Protection Switching (APS) Mode - draft-ietf-mpls-tp-aps-updates-01.txt + draft-ietf-mpls-tp-aps-updates-02.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, and clarify some operation related to state transition table lookup. @@ -31,25 +31,25 @@ 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 March 19, 2017. + This Internet-Draft will expire on July 7, 2017. Copyright Notice - Copyright (c) 2016 IETF Trust and the persons identified as the + Copyright (c) 2017 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 carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as @@ -60,23 +60,23 @@ 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Conventions Used in This Document . . . . . . . . . . . . . . 3 3. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4.1. Initialization Behavior . . . . . . . . . . . . . . . . . 4 4.2. State Transition Modification . . . . . . . . . . . . . . 5 4.3. Operation related to State Transition Table Lookup . . . 6 5. Security Considerations . . . . . . . . . . . . . . . . . . . 7 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 - 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 - 8.1. Normative References . . . . . . . . . . . . . . . . . . 7 - 8.2. Informative References . . . . . . . . . . . . . . . . . 7 + 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 + 8.1. Normative References . . . . . . . . . . . . . . . . . . 8 + 8.2. Informative References . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 1. Introduction MPLS Transport Profile (MPLS-TP) linear protection in Automatic Protection Switching (APS) mode is defined in RFC 7271 [RFC7271]. It defines a set of alternate and additional mechanisms to perform some of the functions of linear protection described in RFC 6378 [RFC6378]. The actions performed at initialization of the Protection State Coordination (PSC) Control Logic are not described in either @@ -249,26 +249,36 @@ --------- Old text: --------- In the state transition tables below, the letter 'i' stands for "ignore" and is an indication to remain in the current state and continue transmitting the current PSC message. --------- New text: --------- - In the state transition tables below, the letter 'i' stands for - "ignore" and the top-priority global request is ignored. - Therefore, the next state can be either the current state - transmitting the current PSC message or the supposed state - (Normal or DNR depending on the footnotes to the state transition - tables) in case of re-evaluation. + In the state transition tables below, the letter 'i' is the + "ignore" flag, and if it is set it means that the top-priority + global request is ignored. + + If re-evaluation is triggered, it is checked if the ignore flag is + set. If it is, the state machine will transit to the supposed state, + which can be Normal or DNR as indicated in the footnotes to the + state transition tables. If the ignore flag is not set, the state + machine will transit to the state indicated in the cell of the state + transition table. + + If re-evaluation is not triggered, it is checked if the ignore flag + is set. If it is, the state machine will remain in the current state, + and the current PSC message continues to be transmitted. If the + ignore flag is not set, the state machine will transit to the state + indicated in the cell of the state transition table. 5. Security Considerations No specific security issue is raised in addition to those ones already documented in [RFC7271]. It may be noted that tightening the description of initializing behavior may help to protect networks from re-start attacks. 6. IANA Considerations @@ -322,15 +332,14 @@ Huub van Helvoort Hai Gaoming BV EMail: huubatwork@gmail.com Italo Busi Huawei Technologies EMail: Italo.Busi@huawei.com - - Guangjuan Weng + Guangjuan Wen Huawei Technologies EMail: wenguangjuan@huawei.com