Stateful Path Computation Element (PCE) Inter-domain Considerations
draft-dhody-pce-stateful-pce-interdomain-05

Document Type Active Internet-Draft (individual)
Last updated 2017-09-18
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
PCE Working Group                                               D. Dhody
Internet-Draft                                                  X. Zhang
Intended status: Informational                       Huawei Technologies
Expires: March 22, 2018                               September 18, 2017

  Stateful Path Computation Element (PCE) Inter-domain Considerations
              draft-dhody-pce-stateful-pce-interdomain-05

Abstract

   A stateful Path Computation Element (PCE) maintains information about
   Label Switched Path (LSP) characteristics and resource usage within a
   network in order to provide traffic engineering path calculations for
   its associated Path Computation Clients (PCCs).  Furthermore, PCEs
   are used to compute shortest constrained Traffic Engineering Label
   Switched Paths (TE LSPs) in Multiprotocol Label Switching (MPLS) and
   Generalized MPLS (GMPLS) networks across multiple domains.

   This document describes general considerations for the deployment of
   stateful PCE(s) in inter-domain scenarios including inter-area and
   inter-AS.  The inter-layer considerations will be described in a
   separate document.  This document does not specify any extensions to
   PCEP.

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 https://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 March 22, 2018.

Copyright Notice

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

Dhody & Zhang            Expires March 22, 2018                 [Page 1]
Internet-Draft            STATEFUL-INTERDOMAIN            September 2017

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  LSP State Synchronization . . . . . . . . . . . . . . . .   4
   3.  Stateful PCE Deployments  . . . . . . . . . . . . . . . . . .   4
     3.1.  Single Stateful PCE, Multiple Domains . . . . . . . . . .   5
     3.2.  Multiple Stateful PCE, Multiple Domains . . . . . . . . .   5
       3.2.1.  Per Domain Path Computation . . . . . . . . . . . . .   6
       3.2.2.  Backward-Recursive PCE-based Computation  . . . . . .   7
       3.2.3.  Hierarchical PCE  . . . . . . . . . . . . . . . . . .   8
   4.  Other Considerations  . . . . . . . . . . . . . . . . . . . .   8
     4.1.  Delegation  . . . . . . . . . . . . . . . . . . . . . . .   8
     4.2.  PCE-initiated LSP . . . . . . . . . . . . . . . . . . . .   9
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   6.  Manageability Considerations  . . . . . . . . . . . . . . . .   9
     6.1.  Control of Function and Policy  . . . . . . . . . . . . .   9
     6.2.  Information and Data Models . . . . . . . . . . . . . . .   9
     6.3.  Liveness Detection and Monitoring . . . . . . . . . . . .   9
     6.4.  Verify Correct Operations . . . . . . . . . . . . . . . .  10
     6.5.  Requirements On Other Protocols . . . . . . . . . . . . .  10
     6.6.  Impact On Network Operations  . . . . . . . . . . . . . .  10
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  10
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Appendix A.  Contributor Addresses  . . . . . . . . . . . . . . .  13
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   The Path Computation Element communication Protocol (PCEP) provides
Show full document text