Movatterモバイル変換


[0]ホーム

URL:


Search RFCs

Advanced Search

RFC Editor

RFC 5557

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

File formats:
icon for text fileicon for PDFicon for HTML
Status:
PROPOSED STANDARD
Authors:
Y. Lee
JL. Le Roux
D. King
E. Oki
Stream:
IETF
Source:
pce (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC5557

Discuss this RFC: Send questions or comments to the mailing listpce@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 5557


Abstract

The Path Computation Element Communication Protocol (PCEP) allows PathComputation Clients (PCCs) to request path computations from PathComputation Elements (PCEs), and lets the PCEs return responses. Whencomputing or reoptimizing the routes of a set of Traffic EngineeringLabel Switched Paths (TE LSPs) through a network, it may beadvantageous to perform bulk path computations in order to avoidblocking 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 thenetwork and the complete set of existing TE LSPs, and their respectiveconstraints, and look to optimize or reoptimize the entire network tosatisfy all constraints for all TE LSPs. A GCO may also be applied tosome subset of the TE LSPs in a network. The GCO application isprimarily a Network Management System (NMS) solution.

This document provides application-specific requirements and the PCEPextensions in support of GCO applications. [STANDARDS-TRACK]


For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.




IABIANAIETFIRTFISEISOCIETF Trust
ReportsPrivacy StatementSite MapContact Us

Advanced Search

[8]ページ先頭

©2009-2026 Movatter.jp