Path Computation Element (PCE) Protocol Extensions for Stateful PCE Usage in GMPLS-controlled Networks
draft-ietf-pce-pcep-stateful-pce-gmpls-08

Document Type Active Internet-Draft (pce WG)
Last updated 2018-02-26
Stream IETF
Intended RFC status (None)
Formats plain text pdf html 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                                            Xian Zhang
Internet-Draft                                       Young Lee (Editor)
Intended status: Standards Track                            Fatai Zhang
                                                                 Huawei
                                                         Ramon Casellas
                                                                   CTTC
                                                 Oscar Gonzalez de Dios
                                                         Telefonica I+D
                                                              Zafar Ali
                                                          Cisco Systems

Expires: August 26, 2018                              February 26, 2018

  Path Computation Element (PCE) Protocol Extensions for Stateful PCE
                   Usage in GMPLS-controlled Networks

               draft-ietf-pce-pcep-stateful-pce-gmpls-08.txt

Abstract

   The Path Computation Element (PCE) facilitates Traffic Engineering
   (TE) based path calculation in large, multi-domain, multi-region, or
   multi-layer networks. The PCE communication Protocol (PCEP) has been
   extended to support stateful PCE functions where the PCE retains
   information about the paths already present in the network, but
   those extensions are technology-agnostic. This memo provides
   extensions required for PCEP so as to enable the usage of a stateful
   PCE capability in GMPLS-controlled networks.

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

Zhang et al              Expires August 2018                   [Page 1]
Internet-Draft         Stateful PCEP for GMPLS            February 2018

   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/ietf/1id-abstracts.txt.

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

   This Internet-Draft will expire on August 26, 2018.

Copyright Notice

   Copyright (c) 2018 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.

Conventions used in this document

   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 RFC-2119 [RFC2119].

Table of Contents

   Table of Contents.................................................2
   1. Introduction...................................................3
   2. Context of Stateful PCE and PCEP for GMPLS.....................4
   3. Main Requirements..............................................4
   4. PCEP Extensions................................................5
      4.1. LSP Update in GMPLS-controlled Networks...................5
      4.2. LSP Synchronization in GMPLS-controlled Networks..........5
      4.3. Modification of Existing PCEP Messages and Procedures.....7
         4.3.1. Modification for LSP Re-optimization.................7
         4.3.2. Modification for Route Exclusion.....................8

Zhang et al              Expires August 2018                   [Page 2]
Internet-Draft         Stateful PCEP for GMPLS            February 2018

         4.3.3. Modification for SRP Object to indicate Bi-directional
         LSP.........................................................9
      4.4. Object Encoding...........................................9
   5. IANA Considerations...........................................10
      5.1. New PCEP Error Codes.....................................10
      5.2. New Subobject for the Exclude Route Object...............10
      5.3. New "B" Flag in the SRP Object...........................10
Show full document text