RFC 8231 on Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE

rfc-editor@rfc-editor.org Fri, 22 September 2017 05:19 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 5C4FF133072; Thu, 21 Sep 2017 22:19:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 Nh0YY3eNEiRU; Thu, 21 Sep 2017 22:19:45 -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 E3D32133032; Thu, 21 Sep 2017 22:19:45 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 8612CB80DFC; Thu, 21 Sep 2017 22:19:24 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8231 on Path Computation Element Communication Protocol (PCEP) Extensions for 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
Message-Id: <20170922051924.8612CB80DFC@rfc-editor.org>
Date: Thu, 21 Sep 2017 22:19:24 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/rvO5AUxcxbftytEMyQ5b_VNabls>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 22 Sep 2017 05:19:47 -0000

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

        
        RFC 8231

        Title:      Path Computation Element Communication Protocol 
                    (PCEP) Extensions for Stateful PCE 
        Author:     E. Crabbe, 
                    I. Minei,
                    J. Medved, 
                    R. Varga
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2017
        Mailbox:    edward.crabbe@oracle.com, 
                    inaminei@google.com, 
                    jmedved@cisco.com,  
                    robert.varga@pantheon.tech
        Pages:      57
        Characters: 128096
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pce-stateful-pce-21.txt

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

        DOI:        10.17487/RFC8231

The Path Computation Element Communication Protocol (PCEP) provides
mechanisms for Path Computation Elements (PCEs) to perform path
computations in response to Path Computation Client (PCC) requests.

Although PCEP explicitly makes no assumptions regarding the
information available to the PCE, it also makes no provisions for PCE
control of timing and sequence of path computations within and across
PCEP sessions.  This document describes a set of extensions to PCEP to
enable stateful control of MPLS-TE and GMPLS Label Switched Paths
(LSPs) via PCEP.

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