[Pce] RFC 9059 on Path Computation Element Communication Protocol (PCEP) Extensions for Associated Bidirectional Label Switched Paths (LSPs)

rfc-editor@rfc-editor.org Wed, 23 June 2021 13:22 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB4373A37CD; Wed, 23 Jun 2021 06:22:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 Jl8PVSXJVhZs; Wed, 23 Jun 2021 06:22:39 -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 2B8D33A37DF; Wed, 23 Jun 2021 06:22:36 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4F3AAF40782; Wed, 23 Jun 2021 06:22:30 -0700 (PDT)
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, pce@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210623132230.4F3AAF40782@rfc-editor.org>
Date: Wed, 23 Jun 2021 06:22:30 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/D6xzeaWE8eKizVa0ItdRfK_Qj8Y>
Subject: [Pce] =?utf-8?q?RFC_9059_on_Path_Computation_Element_Communicati?= =?utf-8?q?on_Protocol_=28PCEP=29_Extensions_for_Associated_Bidirectional_?= =?utf-8?q?Label_Switched_Paths_=28LSPs=29?=
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jun 2021 13:22:45 -0000

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

        
        RFC 9059

        Title:      Path Computation Element Communication Protocol 
                    (PCEP) Extensions for Associated Bidirectional Label 
                    Switched Paths (LSPs) 
        Author:     R. Gandhi, Ed.,
                    C. Barth,
                    B. Wen
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2021
        Mailbox:    rgandhi@cisco.com,
                    cbarth@juniper.net,
                    bin_wen@cable.comcast.com
        Pages:      20
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pce-association-bidir-14.txt

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

        DOI:        10.17487/RFC9059

This document defines Path Computation Element Communication Protocol
(PCEP) extensions for grouping two unidirectional MPLS-TE Label
Switched Paths (LSPs), one in each direction in the network, into an
associated bidirectional LSP.  These PCEP extensions can be applied
either using a stateful PCE for both PCE-initiated and PCC-initiated
LSPs or using a stateless PCE. The PCEP procedures defined are
applicable to the LSPs using RSVP-TE for signaling.

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