RSVP-TE Extensions For Associated Co-routed Bidirectional Label Switched Paths (LSPs)
draft-gandhishah-teas-assoc-corouted-bidir-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2016-03-08 (latest revision 2016-03-07)
Replaces draft-gandhi-shah-teas-assoc-corouted-bidir
Replaced by draft-ietf-teas-assoc-corouted-bidir-frr, rfc8537
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Additional URLs
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: September 8, 2016                                         Ciena
                                                        Jeremy Whittaker
                                                                 Verizon
                                                           March 7, 2016

         RSVP-TE Extensions For Associated Co-routed Bidirectional 
                        Label Switched Paths (LSPs)
             draft-gandhishah-teas-assoc-corouted-bidir-00

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.  This document describes how
   RSVP Extended ASSOCIATION Object can be used to bind two co-routed
   point-to-point unidirectional LSPs into an associated co-routed
   bidirectional LSP in single-sided provisioning case.  The RSVP
   REVERSE_LSP Object is used to enable an endpoint to trigger creation
   of the reverse LSP along the same path as the forward LSP. 
   Fast-reroute procedures to ensure that the traffic flows on the
   co-routed path after a failure event are also described.

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

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

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html
 

Gandhi, et al.         Expires September 8, 2016                [Page 1]
Internet-Draft        Co-routed Bidirectional LSP          March 7, 2016

Copyright and License 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.  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 . . . . . . . . . . . . . . . .  4
     4.1.  Extended ASSOCIATION Object  . . . . . . . . . . . . . . .  4
   5.  Signaling Procedure  . . . . . . . . . . . . . . . . . . . . .  6
     5.1.  Co-routed Bidirectional LSP Association  . . . . . . . . .  6
     5.2.  Fast-Reroute For Associated Co-routed Bidirectional LSP  .  6
   6.  Compatibility  . . . . . . . . . . . . . . . . . . . . . . . .  7
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . .  7
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  7
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . .  8
     9.1.  Normative References . . . . . . . . . . . . . . . . . . .  8
     9.2.  Informative References . . . . . . . . . . . . . . . . . .  8
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .  9

 

Gandhi, et al.         Expires September 8, 2016                [Page 2]
Internet-Draft        Co-routed Bidirectional LSP          March 7, 2016

1.  Introduction

   In packet transport networks, there are requirements where a reverse
   LSP of a bidirectional LSP needs to follow the same path as its
   forward LSP [RFC6373]. 

   The 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
Show full document text