[Teas] RFC 8735 on Scenarios and Simulation Results of PCE in a Native IP Network
rfc-editor@rfc-editor.org Sat, 29 February 2020 00:11 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C42A3A07BD; Fri, 28 Feb 2020 16:11:49 -0800 (PST)
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 tfdUqNriI50Y; Fri, 28 Feb 2020 16:11:46 -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 9A39D3A07DA; Fri, 28 Feb 2020 16:11:46 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id C5838F4072C; Fri, 28 Feb 2020 16:11:30 -0800 (PST)
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, teas@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200229001130.C5838F4072C@rfc-editor.org>
Date: Fri, 28 Feb 2020 16:11:30 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/dDVnAo1EySeDlbpcpfXj5LsNY5Q>
Subject: [Teas] RFC 8735 on Scenarios and Simulation Results of PCE in a Native IP Network
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Sat, 29 Feb 2020 00:11:54 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8735 Title: Scenarios and Simulation Results of PCE in a Native IP Network Author: A. Wang, X. Huang, C. Kou, Z. Li, P. Mi Status: Informational Stream: IETF Date: February 2020 Mailbox: wangaj3@chinatelecom.cn, huangxh@bupt.edu.cn, koucx@lsec.cc.ac.cn, li_zhenqiang@hotmail.com, mipenghui@huawei.com Pages: 16 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-teas-native-ip-scenarios-12.txt URL: https://www.rfc-editor.org/info/rfc8735 DOI: 10.17487/RFC8735 Requirements for providing the End-to-End (E2E) performance assurance are emerging within the service provider networks. While there are various technology solutions, there is no single solution that can fulfill these requirements for a native IP network. In particular, there is a need for a universal E2E solution that can cover both intra- and inter-domain scenarios. One feasible E2E traffic-engineering solution is the addition of central control in a native IP network. This document describes various complex scenarios and simulation results when applying the Path Computation Element (PCE) in a native IP network. This solution, referred to as Centralized Control Dynamic Routing (CCDR), integrates the advantage of using distributed protocols and the power of a centralized control technology, providing traffic engineering for native IP networks in a manner that applies equally to intra- and inter-domain scenarios. 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