Unanswered Questions in the Path Computation Element Architecture
draft-ietf-pce-questions-04

The information below is for an old version of the document
Document Type Active Internet-Draft (pce WG)
Last updated 2014-03-17
Replaces draft-farrkingel-pce-questions
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Reviews
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                          A. Farrel
Internet Draft                                          Juniper Networks
Category: Informational                                          D. King
Expires: 17 September 2014                            Old Dog Consulting
                                                           17 March 2014

   Unanswered Questions in the Path Computation Element Architecture
                  draft-ietf-pce-questions-04.txt

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 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.

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups. Note that other
   groups may also distribute working documents as Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time. It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the

Farrel and King         Expires September 2014                  [Page 1]
draft-ietf-pce-questions-04.txt                               March 2014

   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 Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction .................................................. 3
   1.1.  Terminology ................................................. 3
   2.  What Is Topology Information? ................................. 3
   3.  How Is Topology Information Gathered? ......................... 4
   4.  How Do I Find My PCE? ......................................... 5
   5.  How Do I Select Between PCEs? ................................. 6
   6.  How Do Redundant PCEs Synchronize TEDs? ....................... 7
   7.  Where Is the Destination? ..................................... 8
   8.  Who Runs Or Owns a Parent PCE? ............................... 10
   9.  How Do I Find My Parent PCE? ................................. 10
   10.  How Do I Find My Child PCEs? ................................ 10
   11.  How Is The Parent PCE Domain Topology Built? ................ 11
   12.  Does H-PCE Solve The Internet? .............................. 11
   13.  What are Sticky Resources? .................................. 12
   14.  What Is A Stateful PCE For? ................................. 12
   15.  How Is the LSP-DB Built? .................................... 13
   16.  How Do Redundant Stateful PCEs Synchronize State? ........... 14
   17.  What Is An Active PCE? What is a Passive PCE? ............... 15
   18.  What is LSP Delegation? ..................................... 16
   19.  Is An Active PCE with LSP Delegation Just a Fancy NMS? .....  16
   20.  Comparison of Stateless and Stateful PCE .................... 17
   21.  How Does a PCE Work With A Virtual Network Topology? ........ 17
   22.  How Does PCE Communicate With VNTM .......................... 19
   23.  How Does Service Scheduling and Calendering Work? ........... 19
   24.  Where Does Policy Fit In? ................................... 20
   25.  Does PCE Play a Role in SDN? ................................ 21
Show full document text