[Teas] Document Action: 'Use Cases for a PCE as a Central Controller (PCECC)' to Informational RFC (draft-ietf-teas-pcecc-use-cases-18.txt)
The IESG <iesg-secretary@ietf.org> Fri, 31 May 2024 19:42 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: teas@ietf.org
Delivered-To: teas@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 74531C180B47; Fri, 31 May 2024 12:42:03 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.13.0
Auto-Submitted: auto-generated
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <171718452347.11224.6612100720598621127@ietfa.amsl.com>
Date: Fri, 31 May 2024 12:42:03 -0700
Message-ID-Hash: ZH5RUYJYTLEGXRWGDIOISVMK5ISIC4ER
X-Message-ID-Hash: ZH5RUYJYTLEGXRWGDIOISVMK5ISIC4ER
X-MailFrom: iesg-secretary@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-teas.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: The IESG <iesg@ietf.org>, draft-ietf-teas-pcecc-use-cases@ietf.org, james.n.guichard@futurewei.com, rfc-editor@rfc-editor.org, teas-chairs@ietf.org, teas@ietf.org, vishnupavan@gmail.com
X-Mailman-Version: 3.3.9rc4
Subject: [Teas] Document Action: 'Use Cases for a PCE as a Central Controller (PCECC)' to Informational RFC (draft-ietf-teas-pcecc-use-cases-18.txt)
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/g16YGOZ7pI_xnrB-Twc4z4fTrcs>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Owner: <mailto:teas-owner@ietf.org>
List-Post: <mailto:teas@ietf.org>
List-Subscribe: <mailto:teas-join@ietf.org>
List-Unsubscribe: <mailto:teas-leave@ietf.org>
The IESG has approved the following document: - 'Use Cases for a PCE as a Central Controller (PCECC)' (draft-ietf-teas-pcecc-use-cases-18.txt) as Informational RFC This document is the product of the Traffic Engineering Architecture and Signaling Working Group. The IESG contact persons are Gunter Van de Velde, Jim Guichard and John Scudder. A URL of this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-teas-pcecc-use-cases/ Technical Summary The PCE is a core component of a Software-Defined Networking (SDN) system. It can be used to compute optimal paths for network traffic and update existing paths to reflect changes in the network or traffic demands. PCE was developed to derive traffic-engineered paths in MPLS networks, which are supplied to the head end of the paths using the Path Computation Element Communication Protocol (PCEP). SDN has a much broader applicability than signal MPLS traffic- engineered (TE) paths and the PCE may be used to determine paths in a range of use cases including static Label Switched Paths (LSPs), Segment Routing (SR), 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. 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. This document describes general considerations for PCECC deployment and examines its applicability and benefits, as well as its challenges and limitations, through a number of use cases. PCEP extensions which are required for the PCECC use cases are covered in separate documents. Personnel The Document Shepherd for this document is Vishnu Pavan Beeram. The Responsible Area Director is Jim Guichard.