ObsoletedPROPOSED STANDARDIETF stream

RFC 7150: Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7470.

Current version: RFC 7470Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol

In plain English — editorial summary, not part of the RFC

The Path Computation Element Communication Protocol (PCEP) is used to convey path computation requests and responses both between Path Computation Clients (PCCs) and Path Computation Elements (PCEs) and between cooperating PCEs. In PCEP, the path computation requests carry details of the constraints and objective functions that the PCC wishes the PCE to apply in its computation. This document defines a facility to carry vendor-specific information in PCEP using a dedicated object and a new Type-Length-Variable that can be carried in any existing PCEP object.

Document record

Document ID
RFC7150
Published
March 2014
Authors
F. Zhang; A. Farrel
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
12
Also known as
Obsoleted by:
RFC 7470

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/7150-conveying-vendor-specific-constraints-in-the-path-computation-element-communicat