--- 1/draft-ietf-mpls-tp-aps-updates-02.txt 2017-02-21 19:13:11.033216414 -0800 +++ 2/draft-ietf-mpls-tp-aps-updates-03.txt 2017-02-21 19:13:11.057216984 -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: July 7, 2017 Hai Gaoming BV +Expires: August 25, 2017 Hai Gaoming BV I. Busi G. Wen Huawei Technologies - January 3, 2017 + February 21, 2017 Updates to MPLS Transport Profile (MPLS-TP) Linear Protection in Automatic Protection Switching (APS) Mode - draft-ietf-mpls-tp-aps-updates-02.txt + draft-ietf-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, and clarify some operation related to state transition table lookup. @@ -31,21 +31,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 July 7, 2017. + This Internet-Draft will expire on August 25, 2017. Copyright Notice 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 @@ -122,20 +122,21 @@ "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. 3. Acronyms This document uses the following acronyms: APS Automatic Protection Switching DNR Do-not-Revert E::R Exercise state due to remote EXER message EXER Exercise + i ignore MS-P Manual Switch to Protection path MS-W Manual Switch to Working path MPLS-TP MPLS Transport Profile N Normal state NR No Request PF:DW:R Protecting Failure state due to remote SD-W message PF:W:L Protecting Failure state due to local SF-W PF:W:R Protecting Failure state due to remote SF-W message PSC Protection State Coordination RR Reverse Request @@ -284,22 +285,23 @@ This document makes no request of IANA. Note to RFC Editor: this section may be removed on publication as an RFC. 7. Acknowledgements The authors would like to thank Joaquim Serra for bringing up the issue related to initialization of the PSC Control Logic at the very - beginning. The authors would also like to thank Adrian Farrel for - his valuable comments and suggestions on this document. + beginning. The authors would also like to thank Adrian Farrel and + Loa Andersson for their valuable comments and suggestions on this + document. 8. References 8.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, .