]> University of Tuebingen

Tuebingen Germany fabian.ihle@uni-tuebingen.de

University of Tuebingen

Tuebingen Germany michael.menth@uni-tuebingen.de

Routing Multiprotocol Label Switching egress protection resilience The MPLS Network Action (MNA) framework provides a general mechanism for the encoding and processing of network actions and their data. The MPLS Egress Protection Framework specifies a fast reroute framework for protecting IP/MPLS services. To that, end bypass tunnels have to be signaled to the Point of Local Repair (PLR). Further, the PLR must maintain the bypass forwarding state on a per-transport-tunnel basis. This document defines the encoding for the Stateless MNA-based Egress Protection (SMEP) network action. The SMEP network action protects egress routers by providing an alternative MPLS egress label in-stack. SMEP does not require a bypass forwarding state in PLRs. About This Document The latest revision of this draft can be found at . Status information for this document may be found at . Discussion of this document takes place on the Multiprotocol Label Switching Working Group mailing list (), which is archived at . Subscribe at . Source for this draft and an issue tracker can be found at .

Introduction The MPLS egress protection framework in establishes bypass tunnels for egress routers on an egress failure, i.e., on a node or a link failure. This is referred to as egress protection. The protection mechanism relies on a Point of Local Repair (PLR) to perform local failure detection and local repair. Typically, this PLR is the penultimate router. When an egress failure occurs, packets are rerouted to an alternative egress router. The PLR node maintains the bypass forwarding state, which is a mapping of specific labels to bypass tunnels. The bypass tunnels are signaled using existing mechanisms, i.e., via an IGP, or topology-driven label distribution protocols such as LDP. With the MPLS Network Action (MNA) framework, network actions are encoded in the MPLS stack. defines the encoding of such network actions and their data in the MPLS stack. These network actions are processed by all nodes on a path (hop-by-hop), by only selected nodes, or on an ingress-to-egress basis. This document defines the Stateless MNA-based Egress Protection (SMEP) network action. With SMEP, egress bypass tunnels are carried in a network action in the MPLS stack. The egress bypass tunnel is indicated by one or multiple alternative MPLS forwarding labels in-stack. We call those labels Bypass MPLS Labels (BML). The ingress router pushes the MPLS stack containing the SMEP network action. On an egress failure, the BML in the network action is used to protect the egress tunnel. The PLR node is required to install the MPLS forwarding entries for the bypass tunnels using the BML. Besides that, no signaling between the egress node / the protector, and the PLR is required. The PLR is not required to maintain the state of bypass tunnel mappings. The egress protection framework defined in is comprehensive. It provides a mechanism for rerouting traffic in the event of an egress failure, and explains how rerouted services and their associated context can be restored. SMEP provides an alternative to the rerouting mechanism defined for the PLR, allowing the PLR to be stateless. Thus, the PLR does not need to maintain a table that maps transport tunnels to backup paths. Likewise, the PLR is not involved in the signaling of such information. Instead, this information is supplied from the ingress to the PLR in the network action. Signaling is only needed between ingress, egress, and the protector, but not with the PLR anymore. Details of the signaling are not contained in this draft. The general concepts and mechanisms described in still apply.

Terminology 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 BCP 14 when, and only when, they appear in all capitals, as shown here.

Abbreviations This document makes use of the terms defined in and in . Further abbreviations used in this document: Abbreviations.

Abbreviation	Meaning	Reference
BML	BML	This document
SMEP	Stateless MNA-based Egress Protection	This document

MPLS Network Action for Stateless Egress Protection In this section, we describe the encoding of SMEP and the processing of SMEP in an LSR.

Encoding

MNA for Stateless Egress Protection.

MNA for Stateless Egress Protection using a list of bypass labels.

The network action for stateless MNA-based egress protection is encoded as follows:

• Network Action Indication: The SMEP network action is indicated by opcode TBA1.
• Format: The SMEP network action MUST be encoded using an Format C LSE as defined in , see . Optionally, a list of BMLs MAY be carried as Format D LSE, see .
• Scope: The SMEP network action is only valid in the select scope.
• Ancillary Data: The SMEP network action requires 20 bits of in-stack ancillary data to encode the BML. The most-significant 16 bits of the BML are located in the first data field of an Format C LSE. The least-significant 4 bits are located in the second datafield of an Format C LSE. If Format D LSEs are provided, the BML is encoded in the least-significant bits of the first data field of an Format D LSE. The two most-significant bits of the first data field, and the 8 bits of the second data field MUST be set to zero. No post-stack data is required.

Processing The ingress LER which pushes an MPLS label stack onto a packet includes the BML in a network action. The BML encodes the bypass tunnel to an alternative egress router. The SMEP network action MUST be placed in the MPLS stack such that the PLR (Point of Local Repair), i.e., the penultimate node, is able to process the network action. This means that the SMEP network action is only processed by the penultimate node using the select scope. On an egress node failure or an egress link failure, the penultimate node MUST use the BML to route traffic to an alternative egress router. To that end, the PLR pushes the BML from the Format C and D LSEs to the MPLS stack and pops the incoming label. A list of BMLs MAY be provided as Format D LSEs to encode a bypass tunnel constructed by Segment Routing.

Example A simple example topology using MNA-based egress protection with an SR bypass tunnel is shown in . Labels A and B are used to forward to the penultimate router. From here, one path is available to the egress node, and one path to the protector. Label C is used to route to the egress node, and labels C' and C'' are used to route to the protector. If the egress link or router C fails, the PLR can use the bypass tunnel of router C' and C''. The MPLS stack pushed by the ingress LER that encodes this functionality for the example topology is shown in . The Network Action Sub-Stack (NAS) for SMEP contains an Format A LSE to indicate the MNA sub-stack and an Format B LSE. This is required by . The Format B LSE can contain arbitrary network actions. In the example, LSR A and B pop the labels A and B. On an egress failure, the PLR pops the incoming label C, and the NAS, and pushes the list of BMLs onto the stack. The label stack after SMEP is applied is shown in .

Example network topology with protected egress routers.

Example MPLS stack pushed by the ingress LER for above topology.

Example MPLS stack after SMEP is applied.

Security Considerations The security issues discussed in and in apply to this document.

IANA Considerations This document requests that IANA allocates a new codepoint with the name "Stateless MNA-based Egress Protection" in the "Network Action Opcodes Registry". SMEP Opcode IANA allocation.

MNA Opcode	Description	Reference
TBA1	Stateless MNA-based Egress Protection	This document

References Normative References In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. Informative References This document specifies a fast reroute framework for protecting IP/MPLS services and MPLS transport tunnels against egress node and egress link failures. For each type of egress failure, it defines the roles of Point of Local Repair (PLR), protector, and backup egress router and the procedures of establishing a bypass tunnel from a PLR to a protector. It describes the behaviors of these routers in handling an egress failure, including local repair on the PLR and context-based forwarding on the protector. The framework can be used to develop egress protection mechanisms to reduce traffic loss before global repair reacts to an egress failure and control-plane protocols converge on the topology changes due to the egress failure. Cisco Systems, Inc. Cisco Systems, Inc. Broadcom Futurewei Technologies Juniper Networks This document defines the MPLS Network Action (MNA) sub-stack solution for carrying Network Actions and Ancillary Data in the label stack. MPLS Network Actions can be used to influence packet forwarding decisions, carry additional Operations, Administration, and Maintenance (OAM) information in the MPLS packet or perform user- defined operations. This solution document specifies In-stack network action and In-stack data (ISD) specific requirements found in "Requirements for MPLS Network Actions". This document follows the architectural framework for the MPLS Network Actions (MNA) technologies specified in "MPLS Network Actions (MNA) Framework".