Applicability of Path Computation Element (PCE) for Abstraction and Control of TE Networks (ACTN)
draft-dhody-pce-applicability-actn-02

Document Type Active Internet-Draft (individual)
Last updated 2017-03-13
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                                                    Y. Lee
Intended status: Informational                       Huawei Technologies
Expires: September 14, 2017                                D. Ceccarelli
                                                                Ericsson
                                                          March 13, 2017

  Applicability of Path Computation Element (PCE) for Abstraction and
                     Control of TE Networks (ACTN)
                 draft-dhody-pce-applicability-actn-02

Abstract

   Abstraction and Control of TE Networks (ACTN) refers to the set of
   virtual network operations needed to orchestrate, control and manage
   large-scale multi-domain TE networks so as to facilitate network
   programmability, automation, efficient resource sharing, and end-to-
   end virtual service aware connectivity and network function
   virtualization services.

   The Path Computation Element Communication Protocol (PCEP) provides
   mechanisms for Path Computation Elements (PCEs) to perform path
   computations in response to Path Computation Clients (PCCs) requests.

   This document examines the applicability of PCE to the ACTN
   framework.

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 September 14, 2017.

Dhody, et al.          Expires September 14, 2017               [Page 1]
Internet-Draft                  PCE-ACTN                      March 2017

Copyright Notice

   Copyright (c) 2017 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.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Path Computation Element (PCE)  . . . . . . . . . . . . .   2
       1.1.1.  Role of PCE in SDN  . . . . . . . . . . . . . . . . .   3
       1.1.2.  PCE in multi-domain and multi-layer deployments . . .   4
     1.2.  Abstraction and Control of TE Networks (ACTN) . . . . . .   4
     1.3.  PCE and ACTN  . . . . . . . . . . . . . . . . . . . . . .   5
   2.  Architectural Considerations  . . . . . . . . . . . . . . . .   6
     2.1.  Multi domain coordination via Hierarchy . . . . . . . . .   6
     2.2.  Virtualization/Abstraction function . . . . . . . . . . .   7
     2.3.  Customer mapping function . . . . . . . . . . . . . . . .   8
     2.4.  Virtual Network Operations  . . . . . . . . . . . . . . .   8
   3.  Interface Considerations  . . . . . . . . . . . . . . . . . .   9
   4.  Realizining ACTN with PCE (and PCEP)  . . . . . . . . . . . .   9
   5.  Relationship to PCE based central control . . . . . . . . . .  12
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  13
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  13
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  13
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  13
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  17

1.  Introduction

1.1.  Path Computation Element (PCE)

   The Path Computation Element communication Protocol (PCEP) [RFC5440]
   provides mechanisms for Path Computation Elements (PCEs) [RFC4655] to
   perform path computations in response to Path Computation Clients
   (PCCs) requests.

Dhody, et al.          Expires September 14, 2017               [Page 2]
Show full document text