Extensions to Path Computation Element Communication Protocol (PCEP) for Hierarchical Path Computation Elements (PCE)
draft-ietf-pce-hierarchy-extensions-00

The information below is for an old version of the document
Document Type Active Internet-Draft (pce WG)
Last updated 2013-11-06 (latest revision 2013-08-18)
Replaces draft-zhang-pce-hierarchy-extensions
Stream IETF
Intended RFC status (None)
Formats pdf htmlized 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                                      F. Zhang, Ed.
Internet-Draft                                                   Q. Zhao
Intended status: Experimental                                     Huawei
Expires: February 18, 2014                      O. Gonzalez de Dios, Ed.
                                                          Telefonica I+D
                                                             R. Casellas
                                                                    CTTC
                                                                 D. King
                                                      Old Dog Consulting
                                                         August 18, 2013

Extensions to Path Computation Element Communication Protocol (PCEP) for
              Hierarchical Path Computation Elements (PCE)
                 draft-ietf-pce-hierarchy-extensions-00

Abstract

   The Hierarchical Path Computation Element (H-PCE) architecture,
   defined in the companion framework document [RFC6805], provides a
   mechanism to allow the optimum sequence of domains to be selected,
   and the optimum end-to-end path to be derived through the use of a
   hierarchical relationship between domains.

   This document defines the Path Computation Element Protocol (PCEP)
   extensions for the purpose of implementing Hierarchical PCE
   procedures which are described in the aforementioned document. These
   extensions are experimental and published for examination, 
   discussion, implementation, and evaluation.
   
   
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
   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 January 14, 2014.

Copyright Notice

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

Zhang, et al.              February 18, 2014                [Page 1]
Internet-Draft          PCEP Extensions for H-PCE        August 2013

   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.  Scope  . . . . . . . . . . . . . . . . . . . . . . . . . . 3
     1.2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . 4
     1.3.  Requirements Language  . . . . . . . . . . . . . . . . . . 4
   2.  Requirements for H-PCE . . . . . . . . . . . . . . . . . . . . 4
     2.1.  PCEP Requests  . . . . . . . . . . . . . . . . . . . . . . 4
       2.1.1.  Qualification of PCEP Requests . . . . . . . . . . . . 4
       2.1.2.  Multi-domain Objective Functions . . . . . . . . . . . 5
       2.1.3.  Multi-domain Metrics . . . . . . . . . . . . . . . . . 6
     2.2.  Parent PCE Capability Discovery  . . . . . . . . . . . . . 6
     2.3.  PCE Domain and PCE ID Discovery  . . . . . . . . . . . . . 6
   3.  PCEP Extensions (Encoding) . . . . . . . . . . . . . . . . . . 6
     3.1.  OPEN Object  . . . . . . . . . . . . . . . . . . . . . . . 6
       3.1.1.  OF Codes . . . . . . . . . . . . . . . . . . . . . . . 6
       3.1.2.  OPEN Object Flags  . . . . . . . . . . . . . . . . . . 7
       3.1.3.  Domain-ID TLV  . . . . . . . . . . . . . . . . . . . . 7
       3.1.4.  PCE-ID TLV . . . . . . . . . . . . . . . . . . . . . . 9
     3.2.  RP object  . . . . . . . . . . . . . . . . . . . . . . . . 9
       3.2.1.  RP Object Flags  . . . . . . . . . . . . . . . . . . . 9
       3.2.2.  Domain-ID TLV  . . . . . . . . . . . . . . . . . . . . 9
     3.3.  Metric Object  . . . . . . . . . . . . . . . . . . . . . .10 
     3.4.  PCEP-ERROR Object  . . . . . . . . . . . . . . . . . . . .10 
       3.4.1.  Hierarchy PCE Error-Type . . . . . . . . . . . . . . .10 
     3.5.  NO-PATH Object . . . . . . . . . . . . . . . . . . . . . .10
   4.  H-PCE Procedures . . . . . . . . . . . . . . . . . . . . . . .10 
     4.1.  OPEN Procedure between Child PCE and Parent PCE  . . . . .11 
Show full document text