Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Obsoletes:

RFC 7150

Updated by:

RFC 9752

Authors:

F. Zhang
A. Farrel

Stream:

IETF

Source:

pce (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC7470

Discuss this RFC: Send questions or comments to the mailing listpce@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 7470

Abstract

The Path Computation Element Communication Protocol (PCEP) is used toconvey path computation requests and responses both between PathComputation Clients (PCCs) and Path Computation Elements (PCEs) andbetween cooperating PCEs. In PCEP, the path computation requests carrydetails of the constraints and objective functions that the PCC wishesthe PCE to apply in its computation.

This document defines a facility to carry vendor-specific informationin PCEP using a dedicated object and a new Type-Length-Value (TLV) thatcan be carried in any PCEP object that supports TLVs.

This document obsoletes RFC 7150. The only changes from that documentare a clarification of the use of the new Type-Length-Value and the allocationof a different code point for the VENDOR-INFORMATION object.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.