8234
PROPOSED STANDARD
Updates to MPLS Transport Profile (MPLS-TP) Linear Protection in Automatic Protection Switching (APS) Mode
Authors: J. Ryoo, T. Cheung, H. van Helvoort, I. Busi, G. Wen
Date: August 2017
Area: rtg
Working Group: mpls
Stream: IETF
Updates:
RFC 7271
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 the operation related to state transition table lookup.
RFC 8234
PROPOSED STANDARD
Internet Engineering Task Force (IETF) J. Ryoo
Request for Comments: 8234 T. Cheung
Updates: <a href="./rfc7271">7271</a> ETRI
Category: Standards Track H. van Helvoort
ISSN: 2070-1721 Hai Gaoming BV
I. Busi
G. Wen
Huawei Technologies
August 2017
<span class="h1">Updates to MPLS Transport Profile (MPLS-TP) Linear Protection in</span>
<span class="h1">Automatic Protection Switching (APS) Mode</span>
Abstract
This document contains updates to MPLS Transport Profile (MPLS-TP)
linear protection in Automatic Protection Switching (APS) mode
defined in <a href="./rfc7271">RFC 7271</a>. 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 the operation related to state transition table lookup.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in <a href="./rfc7841#section-2">Section 2 of RFC 7841</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="https://www.rfc-editor.org/info/rfc8234">http://www.rfc-editor.org/info/rfc8234</a>.
<span class="grey">Ryoo, et al. Standards Track [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc8234">RFC 8234</a> Updates to MPLS-TP LP in APS Mode August 2017</span>
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) 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
described in the Simplified BSD License.
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2">2</a>. Conventions Used in This Document . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3">3</a>. Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-4">4</a>. Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-4.1">4.1</a>. Initialization Behavior . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-4.2">4.2</a>. State Transition Modification . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-4.3">4.3</a>. Operation Related to State Transition Table Lookup . . . <a href="#page-6">6</a>
<a href="#section-5">5</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-6">6</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-7">7</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-7.1">7.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-7.2">7.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<span class="grey">Ryoo, et al. Standards Track [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc8234">RFC 8234</a> Updates to MPLS-TP LP in APS Mode August 2017</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
MPLS Transport Profile (MPLS-TP) linear protection in Automatic
Protection Switching (APS) mode is defined in <a href="./rfc7271">RFC 7271</a> [<a href="./rfc7271" title=""MPLS Transport Profile (MPLS-TP) Linear Protection to Match the Operational Expectations of Synchronous Digital Hierarchy, Optical Transport Network, and Ethernet Transport Network Operators"">RFC7271</a>]. It
defines a set of alternate and additional mechanisms to perform some
of the functions of linear protection described in <a href="./rfc6378">RFC 6378</a>
[<a href="./rfc6378" title=""MPLS Transport Profile (MPLS-TP) Linear Protection"">RFC6378</a>]. The actions performed at initialization of the Protection
State Coordination (PSC) Control Logic are not described in either
[<a href="./rfc7271" title=""MPLS Transport Profile (MPLS-TP) Linear Protection to Match the Operational Expectations of Synchronous Digital Hierarchy, Optical Transport Network, and Ethernet Transport Network Operators"">RFC7271</a>] or [<a href="./rfc6378" title=""MPLS Transport Profile (MPLS-TP) Linear Protection"">RFC6378</a>]. Although it is a common perception that the
state machine starts at the Normal state, this is not explicitly
specified in any of the documents and various questions have been
raised by implementers and in discussions on the MPLS working group
mailing list concerning the detailed actions that the PSC Control
Logic should take.
The state machine described in [<a href="./rfc7271" title=""MPLS Transport Profile (MPLS-TP) Linear Protection to Match the Operational Expectations of Synchronous Digital Hierarchy, Optical Transport Network, and Ethernet Transport Network Operators"">RFC7271</a>] operates under the
assumption that both end nodes of a linear protection domain start in
the Normal state. In the case that one node reboots while the other
node is still in operation, various scenarios may arise resulting in
problematic situations. This document resolves all the problematic
cases and minimizes traffic disruptions related to initialization,
including both cold and warm reboots that require re-initialization
of the PSC Control Logic.
This document contains updates to the MPLS-TP linear protection in
APS mode defined in [<a href="./rfc7271" title=""MPLS Transport Profile (MPLS-TP) Linear Protection to Match the Operational Expectations of Synchronous Digital Hierarchy, Optical Transport Network, and Ethernet Transport Network Operators"">RFC7271</a>]. The updates provide rules related to
initialization of the PSC Control Logic (in which the state machine
resides) when operating in APS mode. The updates also include
modifications to the state transition table defined in <a href="./rfc7271#section-11.2">Section 11.2
of [RFC7271]</a>. The changes in the state transition table have been
examined to make sure that no new problems are introduced.
This document does not introduce backward compatibility issues with
implementations of [<a href="./rfc7271" title=""MPLS Transport Profile (MPLS-TP) Linear Protection to Match the Operational Expectations of Synchronous Digital Hierarchy, Optical Transport Network, and Ethernet Transport Network Operators"">RFC7271</a>]. In case a node implementing this
document restarts, the new state changes will not cause problems at
the remote node implementing [<a href="./rfc7271" title=""MPLS Transport Profile (MPLS-TP) Linear Protection to Match the Operational Expectations of Synchronous Digital Hierarchy, Optical Transport Network, and Ethernet Transport Network Operators"">RFC7271</a>], and the two ends will
converge to the same local and remote states. In case a node
implementing [<a href="./rfc7271" title=""MPLS Transport Profile (MPLS-TP) Linear Protection to Match the Operational Expectations of Synchronous Digital Hierarchy, Optical Transport Network, and Ethernet Transport Network Operators"">RFC7271</a>] restarts, the two ends behave as they do
today.
This document also provides some clarifications on the operation
related to state transition table lookup.
The reader of this document is assumed to be familiar with [<a href="./rfc7271" title=""MPLS Transport Profile (MPLS-TP) Linear Protection to Match the Operational Expectations of Synchronous Digital Hierarchy, Optical Transport Network, and Ethernet Transport Network Operators"">RFC7271</a>].
<span class="grey">Ryoo, et al. Standards Track [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc8234">RFC 8234</a> Updates to MPLS-TP LP in APS Mode August 2017</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Conventions Used in This Document</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
<a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>] [<a href="./rfc8174" title=""Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"">RFC8174</a>] when, and only when, they appear in all
capitals, as shown here.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Abbreviations</span>
This document uses the following abbreviations:
APS Automatic Protection Switching
DNR Do-not-Revert
E::R Exercise state due to remote EXER message
EXER Exercise
MS-P Manual Switch to Protection path
MS-W Manual Switch to Working path
MPLS-TP MPLS Transport Profile
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
SA:MP:R Switching Administrative state due to remote MS-P message
SA:MW:R Switching Administrative state due to remote MS-W message
SD Signal Degrade
SD-W Signal Degrade on Working path
SF Signal Fail
SF-P Signal Fail on Protection path
SF-W Signal Fail on Working path
UA:P:L Unavailable state due to local SF-P
WTR Wait-to-Restore
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Updates</span>
This section specifies the actions that will be performed at the
initialization of the PSC Control Logic and the modifications of the
state transition table defined in <a href="./rfc7271#section-11.2">Section 11.2 of [RFC7271]</a>. Some
clarifications on the operation related to state transition table
lookup are also provided.
<span class="grey">Ryoo, et al. Standards Track [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc8234">RFC 8234</a> Updates to MPLS-TP LP in APS Mode August 2017</span>
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Initialization Behavior</span>
This section defines initialization behavior that is not described in
[<a href="./rfc7271" title=""MPLS Transport Profile (MPLS-TP) Linear Protection to Match the Operational Expectations of Synchronous Digital Hierarchy, Optical Transport Network, and Ethernet Transport Network Operators"">RFC7271</a>].
When the PSC Control Logic is initialized, the following actions MUST
be performed:
o Stop the WTR timer if it is running.
o Clear any operator command in the Local Request Logic.
o If an SF-W or SF-P exists as the highest local request, the node
being initialized starts at the PF:W:L or UA:P:L state,
respectively.
o If the node being initialized has no local request:
* If the node being initialized does not remember the active path
or if the node being initialized remembers the working path as
the active path, the node starts at the Normal state.
* Else (the node being initialized remembers the protection path
as the active path), the node starts at the WTR state sending
NR(0,1) or at the DNR state sending DNR(0,1) depending on the
configuration that allows or prevents automatic reversion to
the Normal state.
o In case any local SD exists, the local SD MUST be considered as an
input to the Local Request Logic only after the local node has
received the first protocol message from the remote node and
completed the processing (i.e., updated the PSC Control Logic and
decided which action, if any, is to be sent to the PSC Message
Generator).
o If the local node receives an EXER message as the first protocol
message after initialization and the remote EXER becomes the top-
priority global request, the local node MUST set the position of
the bridge and selector according to the Path value in the EXER
message and transit to the E::R state.
In the case of no local request, remembering the active path
minimizes traffic switchovers when the remote node is still in
operation. This approach does not cause a problem even if the
remembered active path is no longer valid due to any local input that
occurred at the remote node while the initializing node was out of
operation.
<span class="grey">Ryoo, et al. Standards Track [Page 5]</span><span id="page-6" ></span>
<span class="grey"><a href="./rfc8234">RFC 8234</a> Updates to MPLS-TP LP in APS Mode August 2017</span>
Note 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 restarts as if no local
requests are present. If a valid SF/SD indication is detected later,
the PSC Control Logic is notified and state change is triggered.
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. State Transition Modification</span>
In addition to the initialization behavior described in <a href="#section-4.1">Section 4.1</a>,
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 as defined in <a href="./rfc7271#section-11.2">Section 11.2 of [RFC7271]</a> 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
the replacement of note (10) with DNR; therefore, note (10) is no
longer needed. The resultant three rows read:
| MS-W | MS-P | WTR | EXER | RR | DNR | NR
--------+---------+---------+-----+------+----+------+----
N | SA:MW:R | SA:MP:R | (13)| E::R | i | DNR | i
PF:W:R | SA:MW:R | SA:MP:R | (9) | E::R | i | DNR | (11)
PF:DW:R | SA:MW:R | SA:MP:R | (9) | E::R | i | DNR | (11)
In the tables above, the letters 'i' and 'N' stand for "ignore" and
"Normal state", respectively. Other abbreviations can be found in
<a href="#section-3">Section 3</a>.
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Operation Related to State Transition Table Lookup</span>
In addition to the rules related to the state transition table lookup
listed in <a href="./rfc7271#section-11">Section 11 of [RFC7271]</a>, the following rule is also applied
to the operation related to the state transition table lookup:
o When the local SF-P is cleared and the priorities of the local and
remote requests are re-evaluated, the last received remote message
may no longer be valid due to the previous failure of the
protection path. Therefore, the last received message MUST be
treated as if it were NR and only the local request shall be
evaluated.
<span class="grey">Ryoo, et al. Standards Track [Page 6]</span><span id="page-7" ></span>
<span class="grey"><a href="./rfc8234">RFC 8234</a> Updates to MPLS-TP LP in APS Mode August 2017</span>
The last paragraph in <a href="./rfc7271#section-11">Section 11 of [RFC7271]</a> is modified as follows:
---------
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' is the
"ignore" flag; if it is set, it means that the top-priority
global request is ignored.
If re-evaluation is triggered, the ignore flag is checked. If it
is set, the state machine will transit to the supposed state, which
can be Normal or DNR as indicated in the footnotes to the state
transition table in <a href="./rfc7271#section-11.1">Section 11.1 of [RFC7271]</a>. 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, the ignore flag is checked. If
it is set, 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.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
No specific security issue is raised in addition to those ones
already documented in [<a href="./rfc7271" title=""MPLS Transport Profile (MPLS-TP) Linear Protection to Match the Operational Expectations of Synchronous Digital Hierarchy, Optical Transport Network, and Ethernet Transport Network Operators"">RFC7271</a>]. Note that tightening the
description of the initializing behavior may help to protect networks
from restart attacks.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span>
This document does not require any IANA actions.
<span class="grey">Ryoo, et al. Standards Track [Page 7]</span><span id="page-8" ></span>
<span class="grey"><a href="./rfc8234">RFC 8234</a> Updates to MPLS-TP LP in APS Mode August 2017</span>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span>
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Normative References</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>,
DOI 10.17487/RFC2119, March 1997,
<<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>>.
[<a id="ref-RFC7271">RFC7271</a>] Ryoo, J., Ed., Gray, E., Ed., van Helvoort, H.,
D'Alessandro, A., Cheung, T., and E. Osborne, "MPLS
Transport Profile (MPLS-TP) Linear Protection to Match the
Operational Expectations of Synchronous Digital Hierarchy,
Optical Transport Network, and Ethernet Transport Network
Operators", <a href="./rfc7271">RFC 7271</a>, DOI 10.17487/RFC7271, June 2014,
<<a href="https://www.rfc-editor.org/info/rfc7271">https://www.rfc-editor.org/info/rfc7271</a>>.
[<a id="ref-RFC8174">RFC8174</a>] Leiba, B., "Ambiguity of Uppercase vs Lowercase in <a href="./rfc2119">RFC</a>
<a href="./rfc2119">2119</a> Key Words", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc8174">RFC 8174</a>, DOI 10.17487/RFC8174,
May 2017, <<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>>.
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Informative References</span>
[<a id="ref-RFC6378">RFC6378</a>] Weingarten, Y., Ed., Bryant, S., Osborne, E., Sprecher,
N., and A. Fulignoli, Ed., "MPLS Transport Profile
(MPLS-TP) Linear Protection", <a href="./rfc6378">RFC 6378</a>,
DOI 10.17487/RFC6378, October 2011,
<<a href="https://www.rfc-editor.org/info/rfc6378">https://www.rfc-editor.org/info/rfc6378</a>>.
Acknowledgements
The authors would like to thank Joaquim Serra for raising the issue
related to initialization of the PSC Control Logic at the very
beginning. The authors would also like to thank Adrian Farrel and
Loa Andersson for their valuable comments and suggestions on this
document.
<span class="grey">Ryoo, et al. Standards Track [Page 8]</span><span id="page-9" ></span>
<span class="grey"><a href="./rfc8234">RFC 8234</a> Updates to MPLS-TP LP in APS Mode August 2017</span>
Authors' Addresses
Jeong-dong Ryoo
ETRI
Email: [email protected]
Taesik Cheung
ETRI
Email: [email protected]
Huub van Helvoort
Hai Gaoming BV
Email: [email protected]
Italo Busi
Huawei Technologies
Email: [email protected]
Guangjuan Wen
Huawei Technologies
Email: [email protected]
Ryoo, et al. Standards Track [Page 9]
Annotations
Select text to annotate