[Teas] I-D Action: draft-ietf-teas-pcecc-use-cases-09.txt
internet-drafts@ietf.org Mon, 07 March 2022 17:58 UTC
Return-Path: <internet-drafts@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 B7C4C3A1160; Mon, 7 Mar 2022 09:58:21 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: teas@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.46.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: teas@ietf.org
Message-ID: <164667590170.14744.3411063026968430755@ietfa.amsl.com>
Date: Mon, 07 Mar 2022 09:58:21 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/vSvvRLILb1oF-ebMSdODPc-6rPg>
Subject: [Teas] I-D Action: draft-ietf-teas-pcecc-use-cases-09.txt
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Mar 2022 17:58:22 -0000
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Traffic Engineering Architecture and Signaling WG of the IETF. Title : The Use Cases for Path Computation Element (PCE) as a Central Controller (PCECC). Authors : Zhenbin (Robin) Li Dhruv Dhody Quintin Zhao King Ke Boris Khasanov Filename : draft-ietf-teas-pcecc-use-cases-09.txt Pages : 40 Date : 2022-03-07 Abstract: The Path Computation Element (PCE) is a core component of a Software- Defined Networking (SDN) system. 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 (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 required for stateful PCE usage are covered in separate documents. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-teas-pcecc-use-cases/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-teas-pcecc-use-cases-09 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-teas-pcecc-use-cases-09 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts
- [Teas] I-D Action: draft-ietf-teas-pcecc-use-caseā¦ internet-drafts