An Architecture for IP/LDP Fast-Reroute Using Maximally Redundant Trees
draft-ietf-rtgwg-mrt-frr-architecture-10

Document Type Active Internet-Draft (rtgwg WG)
Last updated 2016-02-05
Replaces draft-atlas-rtgwg-mrt-frr-architecture
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Stream WG state Submitted to IESG for Publication Jul 2015
Document shepherd Janos Farkas
Shepherd write-up Show (last changed 2015-12-10)
IESG IESG state Approved-announcement to be sent::AD Followup
Consensus Yes
Telechat date
Responsible AD Alvaro Retana
Send notices to "Janos Farkas" <janos.farkas@ericsson.com>, aretana@cisco.com
IANA IANA review state Version Changed - Review Needed
IANA action state None
Routing Area Working Group                                      A. Atlas
Internet-Draft                                                 C. Bowers
Intended status: Standards Track                        Juniper Networks
Expires: August 8, 2016                                        G. Enyedi
                                                                Ericsson
                                                        February 5, 2016

An Architecture for IP/LDP Fast-Reroute Using Maximally Redundant Trees
                draft-ietf-rtgwg-mrt-frr-architecture-10

Abstract

   This document defines the architecture for IP and LDP Fast-Reroute
   using Maximally Redundant Trees (MRT-FRR).  MRT-FRR is a technology
   that gives link-protection and node-protection with 100% coverage in
   any network topology that is still connected after 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 August 8, 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

Atlas, et al.            Expires August 8, 2016                 [Page 1]
Internet-Draft        MRT Unicast FRR Architecture         February 2016

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Importance of 100% Coverage . . . . . . . . . . . . . . .   4
     1.2.  Partial Deployment and Backwards Compatibility  . . . . .   5
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   5
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Maximally Redundant Trees (MRT) . . . . . . . . . . . . . . .   7
   5.  Maximally Redundant Trees (MRT) and Fast-Reroute  . . . . . .   9
   6.  Unicast Forwarding with MRT Fast-Reroute  . . . . . . . . . .   9
     6.1.  Introduction to MRT Forwarding Options  . . . . . . . . .  10
       6.1.1.  MRT LDP labels  . . . . . . . . . . . . . . . . . . .  10
         6.1.1.1.  Topology-scoped FEC encoded using a single label
                   (Option 1A) . . . . . . . . . . . . . . . . . . .  10
         6.1.1.2.  Topology and FEC encoded using a two label stack
                   (Option 1B) . . . . . . . . . . . . . . . . . . .  11
         6.1.1.3.  Compatibility of MRT LDP Label Options 1A and 1B   12
         6.1.1.4.  Required support for MRT LDP Label options  . . .  12
       6.1.2.  MRT IP tunnels (Options 2A and 2B)  . . . . . . . . .  12
     6.2.  Forwarding LDP Unicast Traffic over MRT Paths . . . . . .  13
       6.2.1.  Forwarding LDP traffic using MRT LDP Label Option 1A   13
       6.2.2.  Forwarding LDP traffic using MRT LDP Label Option 1B   14
       6.2.3.  Other considerations for forwarding LDP traffic using
               MRT LDP Labels  . . . . . . . . . . . . . . . . . . .  14
       6.2.4.  Required support for LDP traffic  . . . . . . . . . .  14
     6.3.  Forwarding IP Unicast Traffic over MRT Paths  . . . . . .  14
       6.3.1.  Tunneling IP traffic using MRT LDP Labels . . . . . .  15
         6.3.1.1.  Tunneling IP traffic using MRT LDP Label Option
                   1A  . . . . . . . . . . . . . . . . . . . . . . .  15
         6.3.1.2.  Tunneling IP traffic using MRT LDP Label Option
                   1B  . . . . . . . . . . . . . . . . . . . . . . .  15
       6.3.2.  Tunneling IP traffic using MRT IP Tunnels . . . . . .  16
       6.3.3.  Required support for IP traffic . . . . . . . . . . .  16
   7.  MRT Island Formation  . . . . . . . . . . . . . . . . . . . .  16
     7.1.  IGP Area or Level . . . . . . . . . . . . . . . . . . . .  17
     7.2.  Support for a specific MRT profile  . . . . . . . . . . .  17
Show full document text