MPLS Egress Protection Framework
RFC 8679

Document Type RFC - Proposed Standard (December 2019; No errata)
Last updated 2019-12-06
Replaces draft-shen-mpls-egress-protection-framework
Stream IETF
Formats plain text html xml pdf htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Loa Andersson
Shepherd write-up Show (last changed 2019-06-01)
IESG IESG state RFC 8679 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Deborah Brungard
Send notices to Loa Andersson <loa@pi.nu>
IANA IANA review state Version Changed - Review Needed
IANA action state No IANA Actions


Internet Engineering Task Force (IETF)                           Y. Shen
Request for Comments: 8679                                  M. Jeyananth
Category: Standards Track                               Juniper Networks
ISSN: 2070-1721                                              B. Decraene
                                                                  Orange
                                                              H. Gredler
                                                            RtBrick Inc.
                                                               C. Michel
                                                        Deutsche Telekom
                                                                 H. Chen
                                                               Futurewei
                                                           December 2019

                    MPLS Egress Protection Framework

Abstract

   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.

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 Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   https://www.rfc-editor.org/info/rfc8679.

Copyright Notice

   Copyright (c) 2019 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
   (https://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
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction
   2.  Specification of Requirements
   3.  Terminology
   4.  Requirements
   5.  Egress Node Protection
     5.1.  Reference Topology
     5.2.  Egress Node Failure and Detection
     5.3.  Protector and PLR
     5.4.  Protected Egress
     5.5.  Egress-Protected Tunnel and Service
     5.6.  Egress-Protection Bypass Tunnel
     5.7.  Context ID, Context Label, and Context-Based Forwarding
     5.8.  Advertisement and Path Resolution for Context ID
     5.9.  Egress-Protection Bypass Tunnel Establishment
     5.10. Local Repair on PLR
     5.11. Service Label Distribution from Egress Router to Protector
     5.12. Centralized Protector Mode
   6.  Egress Link Protection
   7.  Global Repair
   8.  Operational Considerations
   9.  General Context-Based Forwarding
   10. Example: Layer 3 VPN Egress Protection
     10.1.  Egress Node Protection
     10.2.  Egress Link Protection
     10.3.  Global Repair
     10.4.  Other Modes of VPN Label Allocation
   11. IANA Considerations
   12. Security Considerations
   13. References
     13.1.  Normative References
     13.2.  Informative References
   Acknowledgements
   Authors' Addresses

1.  Introduction

   In MPLS networks, Label Switched Paths (LSPs) are widely used as
   transport tunnels to carry IP and MPLS services across MPLS domains.
   Examples of MPLS services are Layer 2 VPNs, Layer 3 VPNs,
   hierarchical LSPs, and others.  In general, a tunnel may carry
   multiple services of one or multiple types, if the tunnel satisfies
   both individual and aggregate requirements (e.g., Class of Service
   (CoS) and QoS) of these services.  The egress router of the tunnel
   hosts the service instances of the services.  An MPLS service
   instance forwards service packets via an egress link to the service
   destination, based on a service label.  An IP service instance does
   the same, based on an IP service address.  The egress link is often
   called a Provider Edge - Customer Edge (PE-CE) link or Attachment
Show full document text