RFC 4657: Path Computation Element (PCE) Communication Protocol Generic Requirements
In plain English — editorial summary, not part of the RFC
The PCE model is described in the "PCE Architecture" document and facilitates path computation requests from Path Computation Clients (PCCs) to Path Computation Elements (PCEs). This document specifies generic requirements for a communication protocol between PCCs and PCEs, and also between PCEs where cooperation between PCEs is desirable. Subsequent documents will specify application-specific requirements for the PCE communication protocol. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4657
- Published
- September 2006
- Authors
- J. Ash; J.L. Le Roux
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 21
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4674Requirements for Path Computation Element (PCE) DiscoveryCurrent
October 2006
- RFC 5088OSPF Protocol Extensions for Path Computation Element (PCE) DiscoveryUpdated
January 2008
- RFC 5089IS-IS Protocol Extensions for Path Computation Element (PCE) DiscoveryUpdated
January 2008
- RFC 5541Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP)Current
June 2009
- RFC 5557Path Computation Element Communication Protocol (PCEP) Requirements and Protocol Extensions in Support of Global Concurrent OptimizationCurrent
July 2009
- RFC 7025Requirements for GMPLS Applications of PCECurrent
September 2013
- RFC 4655A Path Computation Element (PCE)-Based ArchitectureCurrent
August 2006
- RFC 4659BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPNCurrent
September 2006
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?