Unanswered Questions in the Path Computation Element Architecture

Document Type Replaced Internet-Draft (pce WG)
Authors Adrian Farrel  , Daniel King 
Last updated 2013-07-17 (latest revision 2013-04-28)
Replaced by RFC 7399
Stream IETF
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream WG state Adopted by a WG
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-pce-questions
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


The Path Computation Element (PCE) architecture is set out in RFC 4655. The architecture is extended for multi-layer networking with the introduction of the Virtual Network Topology Manager in RFC 5623, and generalized to Hierarchical PCE in RFC 6805. These three architectural views of PCE deliberately leave some key questions unanswered especially with respect to the interactions between architectural components. This document draws out those questions and discusses them in an architectural context with reference to other architectural components, existing protocols, and recent IETF work efforts. This document does not update the architecture documents and does not define how protocols or components must be used. It does, however, suggest how the architectural components might be combined to provide advanced PCE function.


Adrian Farrel (adrian@olddog.co.uk)
Daniel King (daniel@olddog.co.uk)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)