RFC 7470: Conveying 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-Value (TLV) that can be carried in any PCEP object that supports TLVs. This document obsoletes RFC 7150. The only changes from that document are a clarification of the use of the new Type-Length-Value and the allocation of a different code point for the VENDOR-INFORMATION object.
Document record
- Document ID
- RFC7470
- Published
- March 2015
- Authors
- F. Zhang; A. Farrel
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 14
- Also known as
- —
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.
- RFC 7471OSPF Traffic Engineering (TE) Metric ExtensionsCurrent
March 2015
- RFC 7473Controlling State Advertisements of Non-negotiated LDP ApplicationsUpdated
March 2015
- RFC 7474Security Extension for OSPFv2 When Using Manual Key ManagementCurrent
April 2015
- RFC 7466An Optimization for the Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)Current
March 2015
- RFC 7456Loss and Delay Measurement in Transparent Interconnection of Lots of Links (TRILL)Current
March 2015
- RFC 7455Transparent Interconnection of Lots of Links (TRILL): Fault ManagementCurrent
March 2015
- RFC 7453MPLS Transport Profile (MPLS-TP) Traffic Engineering (TE) Management Information Base (MIB)Current
February 2015
- RFC 7487Configuration of Proactive Operations, Administration, and Maintenance (OAM) Functions for MPLS-Based Transport Networks Using RSVP-TECurrent
March 2015
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?