Home > Research > Publications & Outputs > Unanswered Questions in the Path Computation El...

Research

Links

Text available via DOI:

View graph of relations

Unanswered Questions in the Path Computation Element Architecture

Research output: Book/Report/Proceedings › Commissioned report

Published

Standard

Unanswered Questions in the Path Computation Element Architecture. / King, Daniel Edward.
2014. 29 p.

Research output: Book/Report/Proceedings › Commissioned report

Harvard

King, DE 2014, Unanswered Questions in the Path Computation Element Architecture. https://doi.org/10.17487/rfc7399

APA

King, D. E. (2014). Unanswered Questions in the Path Computation Element Architecture. https://doi.org/10.17487/rfc7399

Vancouver

King DE. Unanswered Questions in the Path Computation Element Architecture. 2014. 29 p. doi: 10.17487/rfc7399

Author

King, Daniel Edward. / Unanswered Questions in the Path Computation Element Architecture. 2014. 29 p.

Bibtex

@book{2346582b629143c49673ba789d264560,
title = "Unanswered Questions in the Path Computation Element Architecture",
abstract = "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 (VNTM) in RFC 5623 and generalized to Hierarchical PCE (H-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 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.",
author = "King, {Daniel Edward}",
year = "2014",
month = oct,
day = "1",
doi = "10.17487/rfc7399",
language = "English",

}

RIS

TY - BOOK

T1 - Unanswered Questions in the Path Computation Element Architecture

AU - King, Daniel Edward

PY - 2014/10/1

Y1 - 2014/10/1

N2 - 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 (VNTM) in RFC 5623 and generalized to Hierarchical PCE (H-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 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.

AB - 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 (VNTM) in RFC 5623 and generalized to Hierarchical PCE (H-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 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.

U2 - 10.17487/rfc7399

DO - 10.17487/rfc7399

M3 - Commissioned report

BT - Unanswered Questions in the Path Computation Element Architecture

ER -