RFC 4674: Requirements for Path Computation Element (PCE) Discovery
In plain English — editorial summary, not part of the RFC
This document presents a set of requirements for a Path Computation Element (PCE) discovery mechanism that would allow a Path Computation Client (PCC) to discover dynamically and automatically a set of PCEs along with certain information relevant for PCE selection. It is intended that solutions that specify procedures and protocols or extensions to existing protocols for such PCE discovery satisfy these requirements. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4674
- Published
- October 2006
- Authors
- J.L. Le Roux
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4657Path Computation Element (PCE) Communication Protocol Generic RequirementsCurrent
September 2006
- RFC 5088OSPF Protocol Extensions for Path Computation Element (PCE) DiscoveryUpdated
January 2008
- RFC 5089IS-IS Protocol Extensions for Path Computation Element (PCE) DiscoveryUpdated
January 2008
- RFC 5541Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP)Current
June 2009
- RFC 5557Path Computation Element Communication Protocol (PCEP) Requirements and Protocol Extensions in Support of Global Concurrent OptimizationCurrent
July 2009
- RFC 7025Requirements for GMPLS Applications of PCECurrent
September 2013
- RFC 4667Layer 2 Virtual Private Network (L2VPN) Extensions for Layer 2 Tunneling Protocol (L2TP)Current
September 2006
- RFC 4665Service Requirements for Layer 2 Provider-Provisioned Virtual Private NetworksCurrent
September 2006
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?