RFC 8306 on Extensions to the Path Computation Element Communication Protocol (PCEP) for Point-to-Multipoint Traffic Engineering Label Switched Paths
rfc-editor@rfc-editor.org Fri, 01 December 2017 05:22 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 A8B92127978; Thu, 30 Nov 2017 21:22:38 -0800 (PST)
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 0gSH3ylvtZdz; Thu, 30 Nov 2017 21:22:37 -0800 (PST)
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 6E5B8127909; Thu, 30 Nov 2017 21:22:35 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 6840CB8127C; Thu, 30 Nov 2017 21:22:22 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8306 on Extensions to the Path Computation Element Communication Protocol (PCEP) for Point-to-Multipoint Traffic Engineering Label Switched Paths
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: <20171201052222.6840CB8127C@rfc-editor.org>
Date: Thu, 30 Nov 2017 21:22:22 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/Ffdd99jdr8kuhdeCP1N2XZNTWZE>
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, 01 Dec 2017 05:22:38 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8306
Title: Extensions to the Path Computation Element
Communication Protocol (PCEP) for
Point-to-Multipoint Traffic Engineering
Label Switched Paths
Author: Q. Zhao,
D. Dhody, Ed.,
R. Palleti,
D. King
Status: Standards Track
Stream: IETF
Date: November 2017
Mailbox: quintin.zhao@huawei.com,
dhruv.ietf@gmail.com,
ramanjaneya.palleti@huawei.com,
daniel@olddog.co.uk
Pages: 43
Characters: 81269
Obsoletes: RFC 6006
I-D Tag: draft-ietf-pce-rfc6006bis-04.txt
URL: https://www.rfc-editor.org/info/rfc8306
DOI: 10.17487/RFC8306
Point-to-point Multiprotocol Label Switching (MPLS) and Generalized
MPLS (GMPLS) Traffic Engineering Label Switched Paths (TE LSPs) may
be established using signaling techniques, but their paths may first
need to be determined. The Path Computation Element (PCE) has been
identified as an appropriate technology for the determination of the
paths of point-to-multipoint (P2MP) TE LSPs.
This document describes extensions to the PCE Communication Protocol
(PCEP) to handle requests and responses for the computation of paths
for P2MP TE LSPs.
This document obsoletes RFC 6006.
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