RFC 5468: Performance Analysis of Inter-Domain Path Computation Methodologies
In plain English — editorial summary, not part of the RFC
This document presents a performance comparison between the per-domain path computation method and the Path Computation Element (PCE) Architecture-based Backward Recursive Path Computation (BRPC) procedure. Metrics to capture the significant performance aspects are identified, and detailed simulations are carried out on realistic scenarios. A performance analysis for each of the path computation methods is then undertaken. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5468
- Published
- April 2009
- Authors
- S. Dasgupta; J. de Oliveira; JP. Vasseur
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5376Inter-AS Requirements for the Path Computation Element Communication Protocol (PCECP)Current
November 2008
- RFC 4927Path Computation Element Communication Protocol (PCECP) Specific Requirements for Inter-Area MPLS and GMPLS Traffic EngineeringCurrent
June 2007
- RFC 8413Framework for Scheduled Use of ResourcesCurrent
July 2018
- RFC 5455Diffserv-Aware Class-Type Object for the Path Computation Element Communication ProtocolCurrent
March 2009
- RFC 5441A Backward-Recursive PCE-Based Computation (BRPC) Procedure to Compute Shortest Constrained Inter-Domain Traffic Engineering Label Switched PathsCurrent
April 2009
- RFC 5394Policy-Enabled Path Computation FrameworkCurrent
December 2008
- RFC 5557Path Computation Element Communication Protocol (PCEP) Requirements and Protocol Extensions in Support of Global Concurrent OptimizationCurrent
July 2009
- RFC 7420Path Computation Element Communication Protocol (PCEP) Management Information Base (MIB) ModuleCurrent
December 2014
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?