RFC 8051 on Applicability of a Stateful Path Computation Element (PCE)
rfc-editor@rfc-editor.org Fri, 06 January 2017 21:04 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 6E552129ED5; Fri, 6 Jan 2017 13:04:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.302
X-Spam-Level:
X-Spam-Status: No, score=-7.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-3.1, SPF_HELO_PASS=-0.001, 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 626g-aj2KBmA; Fri, 6 Jan 2017 13:04:18 -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 D76D6129EFB; Fri, 6 Jan 2017 13:04:18 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id D1E45B8011F; Fri, 6 Jan 2017 13:04:18 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8051 on Applicability of a Stateful Path Computation Element (PCE)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170106210418.D1E45B8011F@rfc-editor.org>
Date: Fri, 06 Jan 2017 13:04:18 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/6atPZ17OFYS5mjIyhlWD3WhtxK0>
Cc: drafts-update-ref@iana.org, pce@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
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, 06 Jan 2017 21:04:21 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8051
Title: Applicability of a Stateful Path
Computation Element (PCE)
Author: X. Zhang, Ed.,
I. Minei, Ed.
Status: Informational
Stream: IETF
Date: January 2017
Mailbox: zhang.xian@huawei.com,
inaminei@google.com
Pages: 24
Characters: 58011
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-pce-stateful-pce-app-08.txt
URL: https://www.rfc-editor.org/info/rfc8051
DOI: 10.17487/RFC8051
A stateful Path Computation Element (PCE) maintains information about
Label Switched Path (LSP) characteristics and resource usage within a
network in order to provide traffic-engineering calculations for its
associated Path Computation Clients (PCCs). This document describes
general considerations for a stateful PCE deployment and examines its
applicability and benefits, as well as its challenges and
limitations, through a number of use cases. PCE Communication
Protocol (PCEP) extensions required for stateful PCE usage are
covered in separate documents.
This document is a product of the Path Computation Element Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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