RFC 5557: Path Computation Element Communication Protocol (PCEP) Requirements and Protocol Extensions in Support of Global Concurrent Optimization
In plain English — editorial summary, not part of the RFC
The Path Computation Element Communication Protocol (PCEP) allows Path Computation Clients (PCCs) to request path computations from Path Computation Elements (PCEs), and lets the PCEs return responses. When computing or reoptimizing the routes of a set of Traffic Engineering Label Switched Paths (TE LSPs) through a network, it may be advantageous to perform bulk path computations in order to avoid blocking problems and to achieve more optimal network-wide solutions. Such bulk optimization is termed Global Concurrent Optimization (GCO). A GCO is able to simultaneously consider the entire topology of the network and the complete set of existing TE LSPs, and their respective constraints, and look to optimize or reoptimize the entire network to satisfy all constraints for all TE LSPs. A GCO may also be applied to some subset of the TE LSPs in a network. The GCO application is primarily a Network Management System (NMS) solution. This document provides application-specific requirements and the PCEP extensions in support of GCO applications. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5557
- Published
- July 2009
- Authors
- Y. Lee; JL. Le Roux; D. King; E. Oki
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 26
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5541Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP)Current
June 2009
- RFC 5455Diffserv-Aware Class-Type Object for the Path Computation Element Communication ProtocolCurrent
March 2009
- RFC 5394Policy-Enabled Path Computation FrameworkCurrent
December 2008
- RFC 5376Inter-AS Requirements for the Path Computation Element Communication Protocol (PCECP)Current
November 2008
- RFC 5089IS-IS Protocol Extensions for Path Computation Element (PCE) DiscoveryUpdated
January 2008
- RFC 5088OSPF Protocol Extensions for Path Computation Element (PCE) DiscoveryUpdated
January 2008
- RFC 4927Path Computation Element Communication Protocol (PCECP) Specific Requirements for Inter-Area MPLS and GMPLS Traffic EngineeringCurrent
June 2007
- RFC 4674Requirements for Path Computation Element (PCE) DiscoveryCurrent
October 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?