Conveying Vendor-Specific Information in the Path Computation Element (PCE) Communication Protocol (PCEP) extensions for Stateful PCE.
draft-dhody-pce-stateful-pce-vendor-11

Document Type Active Internet-Draft (individual)
Authors Cheng Li  , Haomian Zheng  , Siva Sivabalan  , Samuel Sidor  , Zafar Ali 
Last updated 2020-11-01
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized 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)
PCE Working Group                                                  C. Li
Internet-Draft                                                  H. Zheng
Intended status: Standards Track                     Huawei Technologies
Expires: May 5, 2021                                        S. Sivabalan
                                                                   Ciena
                                                                S. Sidor
                                                                  Z. Ali
                                                     Cisco Systems, Inc.
                                                        November 1, 2020

 Conveying Vendor-Specific Information in the Path Computation Element
    (PCE) Communication Protocol (PCEP) extensions for Stateful PCE.
                 draft-dhody-pce-stateful-pce-vendor-11

Abstract

   A Stateful Path Computation Element (PCE) maintains information on
   the current network state, including: computed Label Switched Path
   (LSPs), reserved resources within the network, and the pending path
   computation requests.  This information may then be considered when
   computing new traffic engineered LSPs, and for the associated and the
   dependent LSPs, received from a Path Computation Client (PCC).

   RFC 7470 defines a facility to carry vendor-specific information in
   Path Computation Element Communication Protocol (PCEP).

   This document extends this capability for the Stateful PCEP messages.

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 May 5, 2021.

Li, et al.                 Expires May 5, 2021                  [Page 1]
Internet-Draft               VENDOR-STATEFUL               November 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Procedures for the Vendor Information Object  . . . . . . . .   3
   3.  Procedures for the Vendor Information TLV . . . . . . . . . .   6
   4.  Vendor Information Object and TLV . . . . . . . . . . . . . .   6
   5.  Manageability Considerations  . . . . . . . . . . . . . . . .   7
     5.1.  Control of Function and Policy  . . . . . . . . . . . . .   7
     5.2.  Information and Data Models . . . . . . . . . . . . . . .   7
     5.3.  Liveness Detection and Monitoring . . . . . . . . . . . .   7
     5.4.  Verify Correct Operations . . . . . . . . . . . . . . . .   7
     5.5.  Requirements On Other Protocols . . . . . . . . . . . . .   7
     5.6.  Impact On Network Operations  . . . . . . . . . . . . . .   7
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   7.  Implementation Status . . . . . . . . . . . . . . . . . . . .   8
     7.1.  Cisco Systems . . . . . . . . . . . . . . . . . . . . . .   8
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   9
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   9
     10.2.  Informative References . . . . . . . . . . . . . . . . .  10
   Appendix A.  Contributor Addresses  . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   The Path Computation Element Communication Protocol (PCEP) [RFC5440]
   provides mechanisms for a Path Computation Element (PCE) to perform
   path computation in response to a Path Computation Client (PCC)
   request.

Li, et al.                 Expires May 5, 2021                  [Page 2]
Show full document text