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

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2016-07-01
Replaced by draft-ietf-mpls-egress-protection-framework
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: Informational                          Juniper Networks
Expires: January 2, 2017                                  Bruno Decraene
                                                                  Orange
                                                            July 1, 2016

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

Abstract

   This document specifies a fast reroute framework for protecting MPLS
   tunnels and IP/MPLS services against egress router failures.  In this
   framework, the penultimate-hop router of an MPLS tunnel pre-
   establishes a bypass tunnel to a protector, and performs local
   detection and local repair upon an egress router failure.  The router
   can restore service traffic in the order of tens of milliseconds, by
   rerouting the traffic through the bypass tunnel.  The protector in
   turn performs context label switching or IP forwarding to send the
   traffic towards service destination(s).  The 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.

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 January 2, 2017.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Yimin Shen, et al.       Expires January 2, 2017                [Page 1]
Internet-Draft      MPLS Egress Protection Framework           July 2016

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   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  . . . . . . . . . . . . . . . . . . . . .   6
     5.3.  Protector and PLR . . . . . . . . . . . . . . . . . . . .   7
     5.4.  Protected egress  . . . . . . . . . . . . . . . . . . . .   7
     5.5.  Egress-protected tunnel . . . . . . . . . . . . . . . . .   8
     5.6.  Egress-protected service  . . . . . . . . . . . . . . . .   8
     5.7.  Egress-protected service to egress-protected tunnel
           mapping . . . . . . . . . . . . . . . . . . . . . . . . .   8
     5.8.  Egress-protection bypass tunnel . . . . . . . . . . . . .   8
     5.9.  Context ID, context label, and context based forwarding .   9
     5.10. IGP advertisement and path computation for context ID . .  11
     5.11. Egress-protection bypass tunnel establishment . . . . . .  12
     5.12. Local Repair on PLR . . . . . . . . . . . . . . . . . . .  12
     5.13. Label distribution from egress router to protector  . . .  13
   6.  Global repair . . . . . . . . . . . . . . . . . . . . . . . .  13
   7.  Example:  Layer-3 VPN egress protection . . . . . . . . . . .  13
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  16
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  16
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  16
     11.2.  Informative References . . . . . . . . . . . . . . . . .  16
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  17

1.  Introduction

   In MPLS networks, LSPs (label switched paths) are widely used as
Show full document text