RFC 5394: Policy-Enabled Path Computation Framework
In plain English — editorial summary, not part of the RFC
The Path Computation Element (PCE) architecture introduces the concept of policy in the context of path computation. This document provides additional details on policy within the PCE architecture and also provides context for the support of PCE Policy. This document introduces the use of the Policy Core Information Model (PCIM) as a framework for supporting path computation policy. This document also provides representative scenarios for the support of PCE Policy. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5394
- Published
- December 2008
- Authors
- I. Bryskin; D. Papadimitriou; L. Berger; J. Ash
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 36
- 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 5455Diffserv-Aware Class-Type Object for the Path Computation Element Communication ProtocolCurrent
March 2009
- RFC 5557Path Computation Element Communication Protocol (PCEP) Requirements and Protocol Extensions in Support of Global Concurrent OptimizationCurrent
July 2009
- RFC 4927Path Computation Element Communication Protocol (PCECP) Specific Requirements for Inter-Area MPLS and GMPLS Traffic EngineeringCurrent
June 2007
- RFC 7420Path Computation Element Communication Protocol (PCEP) Management Information Base (MIB) ModuleCurrent
December 2014
- RFC 7792RSVP-TE Signaling Extensions in Support of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM) NetworksCurrent
March 2016
- RFC 7896Update to the Include Route Object (IRO) Specification in the Path Computation Element Communication Protocol (PCEP)Current
June 2016
- RFC 7897Domain Subobjects for the Path Computation Element Communication Protocol (PCEP)Current
June 2016
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?