Fast Reroute Procedures For Associated Co-routed Bidirectional Label Switched Paths (LSPs)
draft-gandhishah-teas-assoc-corouted-bidir-02

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2016-09-10
Replaces draft-gandhi-shah-teas-assoc-corouted-bidir
Replaced by draft-ietf-teas-assoc-corouted-bidir-frr
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)
TEAS Working Group                                        R. Gandhi, Ed.
Internet-Draft                                             Cisco Systems
Intended Status: Standards Track                                 H. Shah
Expires: March 14, 2017                                            Ciena
                                                        Jeremy Whittaker
                                                                 Verizon
                                                      September 10, 2016

      Fast Reroute Procedures For Associated Co-routed Bidirectional 
                      Label Switched Paths (LSPs)
            draft-gandhishah-teas-assoc-corouted-bidir-02

Abstract

   In packet transport networks, there are requirements where reverse
   unidirectional LSP of a bidirectional LSP needs to follow the same
   path as its forward unidirectional LSP.  The bidirectional LSP needs
   to maintain co-routed-ness even after a failure event in the network.
    This document describes RSVP signaling to unambiguously bind two co-
   routed point-to-point LSPs into an associated co-routed bidirectional
   LSP.  Fast-reroute procedures are defined to ensure that the traffic
   flows on the co-routed path after a failure event.

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."

Copyright Notice

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

 

Gandhi, et al.           Expires March 14, 2017                 [Page 1]
Internet-Draft    FRR For Co-routed Bidirectional LSP September 10, 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 . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Conventions Used in This Document  . . . . . . . . . . . . . .  3
     2.1.  Key Word Definitions . . . . . . . . . . . . . . . . . . .  3
     2.2.  Reverse Co-routed Unidirectional LSPs  . . . . . . . . . .  3
   3.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  4
   4.  Message and Object Definitions . . . . . . . . . . . . . . . .  6
     4.1.  Extended ASSOCIATION Object  . . . . . . . . . . . . . . .  6
   5.  Signaling Procedure  . . . . . . . . . . . . . . . . . . . . .  7
     5.1.  Co-routed Bidirectional LSP Association  . . . . . . . . .  7
     5.2.  Fast-Reroute For Associated Co-routed Bidirectional LSP  .  8
   6.  Compatibility  . . . . . . . . . . . . . . . . . . . . . . . .  8
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . .  9
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  9
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
     9.1.  Normative References . . . . . . . . . . . . . . . . . . . 10
     9.2.  Informative References . . . . . . . . . . . . . . . . . . 10
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11

 

Gandhi, et al.           Expires March 14, 2017                 [Page 2]
Internet-Draft    FRR For Co-routed Bidirectional LSP September 10, 2016

1.  Introduction

   In packet transport networks, there are requirements where a reverse
   Multi-Protocol Label Switching (MPLS) Label Switched Path (LSP) of a
   bidirectional LSP needs to follow the same path as its forward LSP
   [RFC6373].  The bidirectional LSP needs to maintain co-routed-ness
   even after a failure event in the network.  

   The Resource Reservation Protocol (RSVP) Extended ASSOCIATION Object
   is specified in [RFC6780] which can be used generically to associate
   (G)MPLS LSPs.  [RFC7551] defines mechanisms for binding two point-to-
   point unidirectional LSPs [RFC3209] into an associated bidirectional
Show full document text