Skip to main content

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

Document Type Replaced Internet-Draft (candidate for pce WG)
Expired & archived
Authors Cheng Li , Haomian Zheng , Siva Sivabalan , Samuel Sidor , Zafar Ali
Last updated 2023-07-25 (Latest revision 2023-01-11)
Replaced by draft-ietf-pce-stateful-pce-vendor
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Additional resources Mailing list discussion
Stream WG state Call For Adoption By WG Issued
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-pce-stateful-pce-vendor
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

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.

Authors

Cheng Li
Haomian Zheng
Siva Sivabalan
Samuel Sidor
Zafar Ali

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)