[spring] Fwd: [Pce] RFC 8664 on Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing

<julien.meuric@orange.com> Mon, 09 December 2019 13:40 UTC

Return-Path: <julien.meuric@orange.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B213120089 for <spring@ietfa.amsl.com>; Mon, 9 Dec 2019 05:40:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 fQKqfnrweGI4 for <spring@ietfa.amsl.com>; Mon, 9 Dec 2019 05:40:53 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AB4112007A for <spring@ietf.org>; Mon, 9 Dec 2019 05:40:53 -0800 (PST)
Received: from opfednr05.francetelecom.fr (unknown [xx.xx.xx.69]) by opfednr23.francetelecom.fr (ESMTP service) with ESMTP id 47Wkq80kBSz5vnD for <spring@ietf.org>; Mon, 9 Dec 2019 14:40:52 +0100 (CET)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.104]) by opfednr05.francetelecom.fr (ESMTP service) with ESMTP id 47Wkq800mKzyQ5 for <spring@ietf.org>; Mon, 9 Dec 2019 14:40:52 +0100 (CET)
Received: from [10.193.71.21] (10.114.13.245) by OPEXCAUBM5F.corporate.adroot.infra.ftgroup (10.114.13.104) with Microsoft SMTP Server (TLS) id 14.3.468.0; Mon, 9 Dec 2019 14:40:51 +0100
References: <20191206215342.672B9F4074E@rfc-editor.org>
To: spring@ietf.org
From: julien.meuric@orange.com
Organization: Orange
X-Forwarded-Message-Id: <20191206215342.672B9F4074E@rfc-editor.org>
Message-ID: <8228800f-2db9-f253-eb9b-e56058cf3e47@orange.com>
Date: Mon, 09 Dec 2019 14:40:48 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <20191206215342.672B9F4074E@rfc-editor.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms000001010006070801090000"
X-Originating-IP: [10.114.13.245]
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/OvFtvQXS-VNZ9dosgSxG_U45Zmw>
Subject: [spring] Fwd: [Pce] RFC 8664 on Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Dec 2019 13:40:55 -0000

FYI

-------- Forwarded Message --------
Date: 	Fri, 6 Dec 2019 13:53:42 -0800
From: 	rfc-editor@rfc-editor.org


A new Request for Comments is now available in online RFC libraries.

RFC 8664

Title: Path Computation Element Communication Protocol (PCEP) Extensions
for Segment Routing
Author: S. Sivabalan,
C. Filsfils,
J. Tantsura,
W. Henderickx,
J. Hardwick
Status: Standards Track
Stream: IETF
Date: December 2019
Mailbox: msiva@cisco.com, cfilsfil@cisco.com, jefftant.ietf@gmail.com,
wim.henderickx@nokia.com, jonathan.hardwick@metaswitch.com
Pages: 29
Updates: RFC 8408

I-D Tag: draft-ietf-pce-segment-routing-16.txt

URL: https://www.rfc-editor.org/info/rfc8664

DOI: 10.17487/RFC8664

Segment Routing (SR) enables any head-end node to select any path
without relying on a hop-by-hop signaling technique (e.g., LDP or
RSVP-TE). It depends only on "segments" that are advertised by
link-state Interior Gateway Protocols (IGPs). An SR path can be
derived from a variety of mechanisms, including an IGP Shortest Path
Tree (SPT), an explicit configuration, or a Path Computation Element
(PCE). This document specifies extensions to the Path Computation
Element Communication Protocol (PCEP) that allow a stateful PCE to
compute and initiate Traffic-Engineering (TE) paths, as well as a
Path Computation Client (PCC) to request a path subject to certain
constraints and optimization criteria in SR networks.

This document updates RFC 8408.

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

_______________________________________________
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce