Browse Prior Art Database

Unanswered Questions in the Path Computation Element Architecture (RFC7399)

IP.com Disclosure Number: IPCOM000239357D
Original Publication Date: 2014-Oct-01
Included in the Prior Art Database: 2014-Nov-01
Document File: 58 page(s) / 71K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A. Farrel: AUTHOR [+2]

Abstract

Over the years since the architecture for the Path Computation Element (PCE) was documented in [RFC4655], many new people have become involved in the work of the PCE working group and wish to use or understand the PCE architecture. These people often missed out on early discussions within the working group and are unfamiliar with questions that were raised during the development of the documentation.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 4% of the total text.

Internet Engineering Task Force (IETF)                         A. Farrel Request for Comments: 7399                              Juniper Networks Category: Informational                                          D. King ISSN: 2070-1721                                       Old Dog Consulting                                                             October 2014

    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.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Not all documents    approved by the IESG are a candidate for any level of Internet    Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7399.

 Farrel & King                 Informational                     [Page 1]
 RFC 7399              Questions in PCE Architecture         October 2014

 Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Componen...