[Pce] RFC 8408 on Conveying Path Setup Type in PCE Communication Protocol (PCEP) Messages
rfc-editor@rfc-editor.org Tue, 24 July 2018 23:36 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 377CA130E7E; Tue, 24 Jul 2018 16:36:43 -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=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 5FNsY9RAkSEz; Tue, 24 Jul 2018 16:36:41 -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 33414126CB6; Tue, 24 Jul 2018 16:36:41 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B65DAB817F7; Tue, 24 Jul 2018 16:36:32 -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: <20180724233632.B65DAB817F7@rfc-editor.org>
Date: Tue, 24 Jul 2018 16:36:32 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/Cd1TyuXZF5y1X-ruJ4r6AYq02qs>
Subject: [Pce] RFC 8408 on Conveying Path Setup Type in PCE Communication Protocol (PCEP) Messages
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.27
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: Tue, 24 Jul 2018 23:36:44 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8408 Title: Conveying Path Setup Type in PCE Communication Protocol (PCEP) Messages Author: S. Sivabalan, J. Tantsura, I. Minei, R. Varga, J. Hardwick Status: Standards Track Stream: IETF Date: July 2018 Mailbox: msiva@cisco.com, jefftant.ietf@gmail.com, inaminei@google.com, nite@hq.sk, jonathan.hardwick@metaswitch.com Pages: 12 Characters: 26276 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pce-lsp-setup-type-10.txt URL: https://www.rfc-editor.org/info/rfc8408 DOI: 10.17487/RFC8408 A Path Computation Element (PCE) can compute Traffic Engineering (TE) paths through a network; these paths are subject to various constraints. Currently, TE paths are Label Switched Paths (LSPs) that are set up using the RSVP-TE signaling protocol. However, other TE path setup methods are possible within the PCE architecture. This document proposes an extension to the PCE Communication Protocol (PCEP) to allow support for different path setup methods over a given PCEP session. 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