RFC 8283 on An Architecture for Use of PCE and the PCE Communication Protocol (PCEP) in a Network with Central Control
rfc-editor@rfc-editor.org Thu, 21 December 2017 23:49 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28B3712D875; Thu, 21 Dec 2017 15:49:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zoT8wnuIeqRW; Thu, 21 Dec 2017 15:49:42 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49EBD12DA12; Thu, 21 Dec 2017 15:49:28 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 1B621B81B04; Thu, 21 Dec 2017 15:49:25 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8283 on An Architecture for Use of PCE and the PCE Communication Protocol (PCEP) in a Network with Central Control
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, teas@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20171221234925.1B621B81B04@rfc-editor.org>
Date: Thu, 21 Dec 2017 15:49:25 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/ya0BLCQJ6dnWgNkCs3MbOSS0wN4>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Dec 2017 23:49:57 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8283
Title: An Architecture for Use of
PCE and the PCE Communication Protocol
(PCEP) in a Network with Central
Control
Author: A. Farrel, Ed.,
Q. Zhao, Ed.,
Z. Li,
C. Zhou
Status: Informational
Stream: IETF
Date: December 2017
Mailbox: afarrel@juniper.net,
quintin.zhao@huawei.com,
lizhenbin@huawei.com,
chao.zhou@cisco.com
Pages: 25
Characters: 56368
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-teas-pce-central-control-05.txt
URL: https://www.rfc-editor.org/info/rfc8283
DOI: 10.17487/RFC8283
The Path Computation Element (PCE) is a core component of Software-
Defined Networking (SDN) systems. It can compute optimal paths for
traffic across a network and can also update the paths to reflect
changes in the network or traffic demands.
PCE was developed to derive paths for MPLS Label Switched Paths
(LSPs), which are supplied to the head end of the LSP using the Path
Computation Element Communication Protocol (PCEP).
SDN has a broader applicability than signaled MPLS traffic-engineered
(TE) networks, and the PCE may be used to determine paths in a range
of use cases including static LSPs, segment routing, Service Function
Chaining (SFC), and most forms of a routed or switched network. It
is, therefore, reasonable to consider PCEP as a control protocol for
use in these environments to allow the PCE to be fully enabled as a
central controller.
This document briefly introduces the architecture for PCE as a
central controller, examines the motivations and applicability for
PCEP as a control protocol in this environment, and introduces the
implications for the protocol. A PCE-based central controller can
simplify the processing of a distributed control plane by blending it
with elements of SDN and without necessarily completely replacing it.
This document does not describe use cases in detail and does not
define protocol extensions: that work is left for other documents.
This document is a product of the Traffic Engineering Architecture and Signaling Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC