RFC 7025: Requirements for GMPLS Applications of PCE
In plain English — editorial summary, not part of the RFC
The initial effort of the PCE (Path Computation Element) WG focused mainly on MPLS. As a next step, this document describes functional requirements for GMPLS applications of PCE.
Document record
- Document ID
- RFC7025
- Published
- September 2013
- Authors
- T. Otani; K. Ogaki; D. Caviglia; F. Zhang; C. Margaria
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7399Unanswered Questions in the Path Computation Element ArchitectureCurrent
October 2014
- RFC 7823Performance-Based Path Selection for Explicitly Routed Label Switched Paths (LSPs) Using TE Metric ExtensionsCurrent
May 2016
- RFC 8413Framework for Scheduled Use of ResourcesCurrent
July 2018
- RFC 4558Node-ID Based Resource Reservation Protocol (RSVP) Hello: A Clarification StatementCurrent
June 2006
- RFC 4209Link Management Protocol (LMP) for Dense Wavelength Division Multiplexing (DWDM) Optical Line SystemsUpdated
October 2005
- RFC 3812Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)Current
June 2004
- RFC 3480Signalling Unnumbered Links in CR-LDP (Constraint-Routing Label Distribution Protocol)Current
February 2003
- RFC 3785Use of Interior Gateway Protocol (IGP) Metric as a second MPLS Traffic Engineering (TE) MetricCurrent
May 2004
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?