PCEP Extensions for Associated Bidirectional Label Switched Paths (LSPs)
draft-ietf-pce-association-bidir-05

Document Type Active Internet-Draft (pce WG)
Last updated 2020-02-04
Replaces draft-barth-pce-association-bidir
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
PCE Working Group                                         R. Gandhi, Ed.
Internet-Draft                                       Cisco Systems, Inc.
Intended status: Standards Track                                C. Barth
Expires: August 7, 2020                                 Juniper Networks
                                                                  B. Wen
                                                                 Comcast
                                                        February 4, 2020

PCEP Extensions for Associated Bidirectional Label Switched Paths (LSPs)
                  draft-ietf-pce-association-bidir-05

Abstract

   The Path Computation Element Communication Protocol (PCEP) provides
   mechanisms for Path Computation Elements (PCEs) to perform path
   computations in response to Path Computation Clients (PCCs) requests.
   The Stateful PCE extensions allow stateful control of Multiprotocol
   Label Switching (MPLS) Traffic Engineering (TE) Label Switched Paths
   (LSPs) using PCEP.

   This document defines PCEP extensions for grouping two unidirectional
   MPLS TE LSPs (one in each direction in the network) into an
   Associated Bidirectional LSP.  The mechanisms defined in this
   document can be applied using a Stateful PCE for both PCE-Initiated
   and PCC-Initiated LSPs, as well as when using a Stateless PCE.  The
   procedures defined are applicable to the LSPs using Resource
   Reservation Protocol (RSVP) for signaling.

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 https://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 7, 2020.

Gandhi, et al.           Expires August 7, 2020                 [Page 1]
Internet-Draft    PCEP for Associated Bidirectional LSP    February 2020

Copyright Notice

   Copyright (c) 2020 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
   (https://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 . . . . . . . . . . . . . .   4
     2.1.  Key Word Definitions  . . . . . . . . . . . . . . . . . .   4
     2.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Single-sided Initiation . . . . . . . . . . . . . . . . .   5
     3.2.  Double-sided Initiation . . . . . . . . . . . . . . . . .   6
     3.3.  Co-routed Associated Bidirectional LSP  . . . . . . . . .   7
   4.  Protocol Extensions . . . . . . . . . . . . . . . . . . . . .   8
     4.1.  ASSOCIATION Object  . . . . . . . . . . . . . . . . . . .   8
     4.2.  Bidirectional LSP Association Group TLV . . . . . . . . .   9
   5.  PCEP Procedure  . . . . . . . . . . . . . . . . . . . . . . .  10
     5.1.  PCE Initiated LSPs  . . . . . . . . . . . . . . . . . . .  10
     5.2.  PCC Initiated LSPs  . . . . . . . . . . . . . . . . . . .  10
     5.3.  Stateless PCE . . . . . . . . . . . . . . . . . . . . . .  11
     5.4.  Bidirectional (B) Flag  . . . . . . . . . . . . . . . . .  11
     5.5.  PLSP-ID Usage . . . . . . . . . . . . . . . . . . . . . .  11
     5.6.  State Synchronization . . . . . . . . . . . . . . . . . .  12
     5.7.  Error Handling  . . . . . . . . . . . . . . . . . . . . .  12
   6.  Implementation Status . . . . . . . . . . . . . . . . . . . .  13
     6.1.  Implementation  . . . . . . . . . . . . . . . . . . . . .  13
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   8.  Manageability Considerations  . . . . . . . . . . . . . . . .  14
     8.1.  Control of Function and Policy  . . . . . . . . . . . . .  14
     8.2.  Information and Data Models . . . . . . . . . . . . . . .  14
     8.3.  Liveness Detection and Monitoring . . . . . . . . . . . .  14
     8.4.  Verify Correct Operations . . . . . . . . . . . . . . . .  14
Show full document text