RFC 8741 on Ability for a Stateful Path Computation Element (PCE) to Request and Obtain Control of a Label Switched Path (LSP)

rfc-editor@rfc-editor.org Tue, 10 March 2020 04:50 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 492F53A0529; Mon, 9 Mar 2020 21:50:33 -0700 (PDT)
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 TThB9xcSSePT; Mon, 9 Mar 2020 21:50:29 -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 402473A0496; Mon, 9 Mar 2020 21:50:29 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 78801F406F0; Mon, 9 Mar 2020 21:50:26 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg3NDEgb24gQWJpbGl0eSBmb3IgYSBTdGF0ZWZ1bCBQYXRoIENvbXB1dGF0aW9uIEVsZW1lbnQgKFBDRSkgdG8gUmVxdWVzdCBhbmQgT2J0YWluIENvbnRyb2wgb2YgYSBMYWJlbCBTd2l0Y2hlZCBQYXRoIChMU1Ap?=
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: <20200310045026.78801F406F0@rfc-editor.org>
Date: Mon, 9 Mar 2020 21:50:26 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/dTTIJBIkGdkbc49ihMqHGvp7o9A>
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: Tue, 10 Mar 2020 04:50:34 -0000

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

        
        RFC 8741

        Title:      Ability for a Stateful Path Computation 
                    Element (PCE) to Request and Obtain 
                    Control of a Label Switched Path (LSP) 
        Author:     A. Raghuram,
                    A. Goddard,
                    J. Karthik, 
                    S. Sivabalan,
                    M. Negi
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2020
        Mailbox:    ar2521@att.com, 
                    ag6941@att.com, 
                    jakarthi@cisco.com,
                    msiva@cisco.com, 
                    mahend.ietf@gmail.com
        Pages:      11
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pce-lsp-control-request-11.txt

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

        DOI:        10.17487/RFC8741

A stateful Path Computation Element (PCE) retains information about
the placement of Multiprotocol Label Switching (MPLS) Traffic
Engineering Label Switched Paths (TE LSPs). When a PCE has stateful
control over LSPs, it may send indications to LSP head-ends to modify
the attributes (especially the paths) of the LSPs. A Path Computation
Client (PCC) that has set up LSPs under local configuration may
delegate control of those LSPs to a stateful PCE.

There are use cases in which a stateful PCE may wish to obtain
control of locally configured LSPs that it is aware of but have not
been delegated to the PCE.

This document describes an extension to the Path Computation Element
Communication Protocol (PCEP) to enable a PCE to make requests for
such control.

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