MPLS Egress Protection Framework
draft-shen-mpls-egress-protection-framework-04

Document Type Active Internet-Draft (individual)
Last updated 2017-02-01
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                               Yimin Shen
Internet-Draft                                           Minto Jeyananth
Intended status: Standards Track                        Juniper Networks
Expires: August 5, 2017                                   Bruno Decraene
                                                                  Orange
                                                          Hannes Gredler
                                                             RtBrick Inc
                                                          Carsten Michel
                                                        Deutsche Telekom
                                                        February 1, 2017

                    MPLS Egress Protection Framework
             draft-shen-mpls-egress-protection-framework-04

Abstract

   This document specifies the framework of a fast reroute mechanism for
   protecting IP/MPLS services and MPLS transport tunnels against egress
   node and egress link failures.  In this framework, the penultimate-
   hop router of an MPLS tunnel acts as the point of local repair (PLR)
   for egress node failure, and the egress router of the MPLS tunnel
   acts as the PLR for egress link failure.  They each pre-establishes a
   bypass tunnel to a protector.  Upon an egress node or link failure,
   the PLR performs local failure detection and local repair, by
   rerouting packets over the bypass tunnel.  The protector in turn
   performs context label switching or context IP forwarding to send the
   packets to ultimate service destination(s).  This mechanism can be
   used to reduce traffic loss before global repair reacts to the
   failure and control plane protocols converge on the topology changes
   due to the failure.  The framework is applicable to all types of IP/
   MPLS services and MPLS tunnels.  Under the framework, service
   protocol extensions may be further specified to support service label
   distribution to protector.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   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

Yimin Shen, et al.       Expires August 5, 2017                 [Page 1]
Internet-Draft      MPLS Egress Protection Framework       February 2017

   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 August 5, 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
   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Specification of Requirements . . . . . . . . . . . . . . . .   5
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   6
   5.  Egress node protection  . . . . . . . . . . . . . . . . . . .   8
     5.1.  Reference topology  . . . . . . . . . . . . . . . . . . .   8
     5.2.  Egress node failure . . . . . . . . . . . . . . . . . . .   8
     5.3.  Protector and PLR . . . . . . . . . . . . . . . . . . . .   9
     5.4.  Protected egress  . . . . . . . . . . . . . . . . . . . .   9
     5.5.  Egress-protected tunnel . . . . . . . . . . . . . . . . .  10
     5.6.  Egress-protected service  . . . . . . . . . . . . . . . .  10
     5.7.  Egress-protected service to egress-protected tunnel
           mapping . . . . . . . . . . . . . . . . . . . . . . . . .  10
     5.8.  Egress-protection bypass tunnel . . . . . . . . . . . . .  11
     5.9.  Context ID, context label, and context based forwarding .  11
     5.10. IGP advertisement and path resolution for context ID  . .  13
     5.11. Egress-protection bypass tunnel establishment . . . . . .  14
     5.12. Local Repair on PLR . . . . . . . . . . . . . . . . . . .  14
Show full document text