datatracker.ietf.org
Sign in
Version 5.6.2.p3, 2014-07-31
Report a bug

Path Computation Element (PCE) Database Requirements
draft-dugeon-pce-ted-reqs-03

Document type: Active Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2014-02-14
Intended RFC status: Unknown
Other versions: plain text, xml, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

Path Computation Element Working Group                         O. Dugeon
Internet-Draft                                                 J. Meuric
Intended status: Informational                                    Orange
Expires: August 18, 2014                                     R. Douville
                                                          Alcatel-Lucent
                                                             R. Casellas
                                                                    CTTC
                                                     O. Gonzalez de Dios
                                   Telefonica Investigacion y Desarrollo
                                                       February 14, 2014

          Path Computation Element (PCE) Database Requirements
                      draft-dugeon-pce-ted-reqs-03

Abstract

   The Path Computation Element (PCE) working group (WG) has produced a
   set of RFCs to standardize the behavior of the Path Computation
   Element as a tool to help MPLS-TE and GMPLS LSP tunnels placement.
   In the PCE architecture, a main assumption has been done concerning
   the information that the PCE needs to perform its computation.  In a
   fist approach, the PCE embeds a Traffic Engineering Database (TED)
   containing all pertinent and suitable information regarding the
   network that is in the scope of a PCE.  Nevertheless, the TED
   requirements as well as the TED information have not yet been
   formalized.  In addition, some recent RFC (like the Backward
   Recursive Path Computation procedure or PCE Hierarchy) or WG draft
   (like draft-ietf-pce-stateful-pce ...) suffer from a lack of
   information in the TED, leading to a non optimal result or to some
   difficulties to deploy them.  This memo tries to identify some
   Database, at large, requirements for the PCE.  It is split in two
   main sections: the identification of the specific information to be
   stored in the PCE Database and how it may be populated.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

Status of This Memo

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

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

Dugeon, et al.           Expires August 18, 2014                [Page 1]
Internet-Draft                PCE TED Req.                 February 2014

   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

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

   This Internet-Draft will expire on August 18, 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 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.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  PCE Assumption and Hypothesis . . . . . . . . . . . . . .   3
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   5
   2.  PCE DataBase Requirements . . . . . . . . . . . . . . . . . .   6
     2.1.  Intra-Domain  . . . . . . . . . . . . . . . . . . . . . .   6
       2.1.1.  MPLS  . . . . . . . . . . . . . . . . . . . . . . . .   6
       2.1.2.  GMPLS . . . . . . . . . . . . . . . . . . . . . . . .   6
     2.2.  Inter-Domain  . . . . . . . . . . . . . . . . . . . . . .   7
     2.3.  TE LSPs . . . . . . . . . . . . . . . . . . . . . . . . .   7
     2.4.  Operational Information . . . . . . . . . . . . . . . . .   8
   3.  PCE-DB model  . . . . . . . . . . . . . . . . . . . . . . . .   8
     3.1.  Intra-domain  . . . . . . . . . . . . . . . . . . . . . .   8
       3.1.1.  MPLS  . . . . . . . . . . . . . . . . . . . . . . . .   8

[include full document text]