RFC 8745 on Path Computation Element Communication Protocol (PCEP) Extensions for Associating Working and Protection Label Switched Paths (LSPs) with Stateful PCE
rfc-editor@rfc-editor.org Sun, 29 March 2020 21:52 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5D613A0DB4; Sun, 29 Mar 2020 14:52:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[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 V_wrJwxalz7g; Sun, 29 Mar 2020 14:52:12 -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 9D1DE3A0DB3; Sun, 29 Mar 2020 14:52:12 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 12A34F4073D; Sun, 29 Mar 2020 14:52:11 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8745 on Path Computation Element Communication Protocol (PCEP) Extensions for Associating Working and Protection Label Switched Paths (LSPs) with Stateful PCE
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: <20200329215211.12A34F4073D@rfc-editor.org>
Date: Sun, 29 Mar 2020 14:52:11 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/mNp3dMXnDQecguFR3QqR3RaH7OQ>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Mar 2020 21:52:14 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8745
Title: Path Computation Element Communication Protocol
(PCEP) Extensions for Associating Working and
Protection Label Switched Paths (LSPs) with
Stateful PCE
Author: H. Ananthakrishnan,
S. Sivabalan,
C. Barth,
I. Minei,
M. Negi
Status: Standards Track
Stream: IETF
Date: March 2020
Mailbox: hari@netflix.com,
msiva@cisco.com,
cbarth@juniper.net,
inaminei@google.com,
mahend.ietf@gmail.com
Pages: 15
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-pce-stateful-path-protection-11.txt
URL: https://www.rfc-editor.org/info/rfc8745
DOI: 10.17487/RFC8745
An active stateful Path Computation Element (PCE) is capable of
computing as well as controlling via Path Computation Element
Communication Protocol (PCEP) Multiprotocol Label Switching Traffic
Engineering (MPLS-TE) Label Switched Paths (LSPs). Furthermore, it is
also possible for an active stateful PCE to create, maintain, and
delete LSPs. This document defines the PCEP extension to associate
two or more LSPs to provide end-to-end path protection.
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