[Pce] RFC 9050 on Path Computation Element Communication Protocol (PCEP) Procedures and Extensions for Using the PCE as a Central Controller (PCECC) of LSPs
rfc-editor@rfc-editor.org Thu, 15 July 2021 18:03 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FA543A16D3; Thu, 15 Jul 2021 11:03:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, 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 dcXe04zVbQsr; Thu, 15 Jul 2021 11:03:21 -0700 (PDT)
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 08DA13A16DD; Thu, 15 Jul 2021 11:03:17 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id DF3E7F4070A; Thu, 15 Jul 2021 11:03:11 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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, pce@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210715180311.DF3E7F4070A@rfc-editor.org>
Date: Thu, 15 Jul 2021 11:03:11 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/MW1HhQ4srWSIH_g1mJ63Y4ojDyQ>
Subject: [Pce] RFC 9050 on Path Computation Element Communication Protocol (PCEP) Procedures and Extensions for Using the PCE as a Central Controller (PCECC) of LSPs
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jul 2021 18:03:28 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9050
Title: Path Computation Element Communication Protocol
(PCEP) Procedures and Extensions for Using
the PCE as a Central Controller
(PCECC) of LSPs
Author: Z. Li,
S. Peng,
M. Negi,
Q. Zhao,
C. Zhou
Status: Standards Track
Stream: IETF
Date: July 2021
Mailbox: lizhenbin@huawei.com,
pengshuping@huawei.com,
mahend.ietf@gmail.com,
qzhao@ethericnetworks.com,
chaozhou_us@yahoo.com
Pages: 33
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-pce-pcep-extension-for-pce-controller-14.txt
URL: https://www.rfc-editor.org/info/rfc9050
DOI: 10.17487/RFC9050
The Path Computation Element (PCE) is a core component of
Software-Defined Networking (SDN) systems.
A PCE as a Central Controller (PCECC) can simplify the processing of
a distributed control plane by blending it with elements of SDN and
without necessarily completely replacing it. Thus, the Label Switched
Path (LSP) can be calculated/set up/initiated and the
label-forwarding entries can also be downloaded through a centralized
PCE server to each network device along the path while leveraging the
existing PCE technologies as much as possible.
This document specifies the procedures and Path Computation Element
Communication Protocol (PCEP) extensions for using the PCE as the
central controller for provisioning labels along the path of the
static LSP.
This document is a product of the Path Computation Element Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. 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