datatracker.ietf.org
Sign in
Version 5.7.4, 2014-11-12
Report a bug

Remote LFA FRR
draft-ietf-rtgwg-remote-lfa-09

Document type: Active Internet-Draft (rtgwg WG)
Document stream: IETF
Last updated: 2014-12-17 (latest revision 2014-12-16)
Intended RFC status: Proposed Standard
Other versions: plain text, xml, pdf, html

IETF State: Submitted to IESG for Publication Nov 2014
Consensus: Unknown
Document shepherd: Alvaro Retana
Shepherd Write-Up: Last changed 2014-09-29

IESG State: In Last Call (ends 2014-12-25)
IANA Review State: IANA OK - No Actions Needed
IANA Action State: None
Responsible AD: Alia Atlas
Send notices to: rtgwg-chairs@tools.ietf.org, draft-ietf-rtgwg-remote-lfa@tools.ietf.org

Network Working Group                                          S. Bryant
Internet-Draft                                               C. Filsfils
Intended status: Standards Track                              S. Previdi
Expires: June 19, 2015                                     Cisco Systems
                                                                M. Shand
                                                 Independent Contributor
                                                                   N. So
                                                           Vinci Systems
                                                       December 16, 2014

                             Remote LFA FRR
                     draft-ietf-rtgwg-remote-lfa-09

Abstract

   This draft describes an extension to the basic IP fast re-route
   mechanism described in RFC5286, that provides additional backup
   connectivity for point to point link failures when none can be
   provided by the basic mechanisms.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC2119 [RFC2119].

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 June 19, 2015.

Bryant, et al.            Expires June 19, 2015                 [Page 1]
Internet-Draft               Remote LFA FRR                December 2014

Copyright Notice

   Copyright (c) 2014 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.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Repair Paths  . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Tunnels as Repair Paths . . . . . . . . . . . . . . . . .   6
     3.2.  Tunnel Requirements . . . . . . . . . . . . . . . . . . .   6
   4.  Construction of Repair Paths  . . . . . . . . . . . . . . . .   7
     4.1.  Identifying Required Tunneled Repair Paths  . . . . . . .   7
     4.2.  Determining Tunnel End Points . . . . . . . . . . . . . .   8
       4.2.1.  Computing Repair Paths  . . . . . . . . . . . . . . .   8
       4.2.2.  Selecting Repair Paths  . . . . . . . . . . . . . . .  11
     4.3.  A Cost Based RLFA Algorithm . . . . . . . . . . . . . . .  11
     4.4.   Interactions with IS-IS Overload, RFC6987, and Costed
           Out Links . . . . . . . . . . . . . . . . . . . . . . . .  16
   5.  Example Application of Remote LFAs  . . . . . . . . . . . . .  17
   6.  Node Failures . . . . . . . . . . . . . . . . . . . . . . . .  18
   7.  Operation in an LDP environment . . . . . . . . . . . . . . .  19
   8.  Analysis of Real World Topologies . . . . . . . . . . . . . .  20
     8.1.  Topology Details  . . . . . . . . . . . . . . . . . . . .  21
     8.2.  LFA only  . . . . . . . . . . . . . . . . . . . . . . . .  21
     8.3.  RLFA  . . . . . . . . . . . . . . . . . . . . . . . . . .  22
     8.4.  Comparison of LFA an RLFA results . . . . . . . . . . . .  23
   9.  Management Considerations . . . . . . . . . . . . . . . . . .  24
   10. Historical Note . . . . . . . . . . . . . . . . . . . . . . .  25
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  25
   12. Security Considerations . . . . . . . . . . . . . . . . . . .  25
   13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  25
   14. References  . . . . . . . . . . . . . . . . . . . . . . . . .  26

[include full document text]