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

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2016-10-21
Replaced by draft-ietf-mpls-egress-protection-framework
Stream (None)
Intended RFC status (None)
Formats pdf htmlized 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: April 24, 2017                                   Bruno Decraene
                                                                  Orange
                                                          Hannes Gredler
                                                             RtBrick Inc
                                                        October 21, 2016

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

Abstract

   This document specifies a fast reroute framework for protecting IP/
   MPLS services and MPLS transport tunnels against egress router
   failures.  In this framework, the penultimate-hop router of an MPLS
   tunnel pre-establishes a bypass tunnel to a protector.  Upon an
   egress router failure, the penultimate-hop router performs local
   failure detection and local repair, by rerouting traffic over the
   bypass tunnel.  The protector in turn performs context label
   switching or context IP forwarding to send the traffic 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 facilitate 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
   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 April 24, 2017.

Yimin Shen, et al.       Expires April 24, 2017                 [Page 1]
Internet-Draft      MPLS Egress Protection Framework        October 2016

Copyright Notice

   Copyright (c) 2016 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 . . . . . . . . . . . . . . . .   4
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   5
   5.  Theory of Operation . . . . . . . . . . . . . . . . . . . . .   6
     5.1.  Reference model . . . . . . . . . . . . . . . . . . . . .   6
     5.2.  Egress failure  . . . . . . . . . . . . . . . . . . . . .   7
     5.3.  Protector and PLR . . . . . . . . . . . . . . . . . . . .   7
     5.4.  Protected egress  . . . . . . . . . . . . . . . . . . . .   8
     5.5.  Egress-protected tunnel . . . . . . . . . . . . . . . . .   9
     5.6.  Egress-protected service  . . . . . . . . . . . . . . . .   9
     5.7.  Egress-protected service to egress-protected tunnel
           mapping . . . . . . . . . . . . . . . . . . . . . . . . .   9
     5.8.  Egress-protection bypass tunnel . . . . . . . . . . . . .   9
     5.9.  Context ID, context label, and context based forwarding .  10
     5.10. IGP advertisement and path resolution for context ID  . .  12
     5.11. Egress-protection bypass tunnel establishment . . . . . .  12
     5.12. Local Repair on PLR . . . . . . . . . . . . . . . . . . .  13
     5.13. Service label distribution from egress router to
           protector . . . . . . . . . . . . . . . . . . . . . . . .  14
     5.14. Centralized protector mode  . . . . . . . . . . . . . . .  14
   6.  Global repair . . . . . . . . . . . . . . . . . . . . . . . .  16
   7.  Example:  Layer-3 VPN egress protection . . . . . . . . . . .  16
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  18
Show full document text