API Build-data JSON Resources
Theme

Choose how MSRBot.io looks on this device.

Auto (match system) Light mode Dark mode

Preference is stored in this browser only.

IETF RFC 5557
[ACTIVE]

Path Computation Element Communication Protocol (PCEP) Requirements and Protocol Extensions in Support of Global Concurrent Optimization

Metadata

Publisher
IETF
Doc Type
Standard
Pages
26
Abstract
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]
Publication Date
2009-07-01
Status Note
Proposed Standard
DOI
10.17487/RFC5557
Link
https://doi.org/10.17487/RFC5557
Author(s)
Young Lee
Jean-Louis Le Roux
Daniel King
Eiji Oki
Keyword(s)
PCE, Global Concurrent Optimization, NMS, Network Management System
Latest version of IETF RFC 5557

Document Versions — IETF RFC 5557

  • ▶ IETF RFC 5557 (2009-07-01)
    THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

Bibliographic Reference(s)

  • Koushik, K. and E. Stephan, "PCE communication protocol (PCEP) Management Information Base", Work in Progress, November 2008. EXTERNAL
  • Oki, E., Takeda, T., Le Roux, JL., and A. Farrel, "Framework for PCE-Based Inter-Layer MPLS and GMPLS Traffic Engineering", Work in Progress, March 2009. EXTERNAL
  • IETF RFC 4655 [Active*]
  • IETF RFC 4657 [Active*]
  • IETF RFC 4674 [Active*]
  • IETF RFC 5212 [Active*]
  • IETF RFC 5511 [Active*]
Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC5557.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree
Reference this Doc

Plain text (ISO 690 compliant)

Preview:
IETF RFC 5557, Path Computation Element Communication Protocol (PCEP) Requirements and Protocol Extensions in Support of Global Concurrent Optimization. Available at https://doi.org/10.17487/RFC5557
Snippet:
IETF RFC 5557, Path Computation Element Communication Protocol (PCEP) Requirements and Protocol Extensions in Support of Global Concurrent Optimization. Available at https://doi.org/10.17487/RFC5557

HTML (ISO 690 compliant)

Preview:
IETF RFC 5557, Path Computation Element Communication Protocol (PCEP) Requirements and Protocol Extensions in Support of Global Concurrent Optimization. Available at https://doi.org/10.17487/RFC5557
Snippet:
<span class="citation"><cite>IETF RFC 5557</cite>, Path Computation Element Communication Protocol (PCEP) Requirements and Protocol Extensions in Support of Global Concurrent Optimization. Available at <a href="https://doi.org/10.17487/RFC5557" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5557</a></span>

SMPTE Icon SMPTE's HTML Pub

Preview:
IETF RFC 5557, Path Computation Element Communication Protocol (PCEP) Requirements and Protocol Extensions in Support of Global Concurrent Optimization
doi: 10.17487/RFC5557
url: https://doi.org/10.17487/RFC5557
Snippet:
<li>
<cite id="bib-rfc5557">IETF RFC 5557</cite>, Path Computation Element Communication Protocol (PCEP) Requirements and Protocol Extensions in Support of Global Concurrent Optimization
<span class="doi">10.17487/RFC5557</span>
</li>

Referenced By