[Pce] RFC 5376 on Inter-AS Requirements for the Path Computation Element Communication Protocol (PCECP)
rfc-editor@rfc-editor.org Fri, 14 November 2008 21:41 UTC
Return-Path: <pce-bounces@ietf.org>
X-Original-To: pce-archive@megatron.ietf.org
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1BAA128C193; Fri, 14 Nov 2008 13:41:38 -0800 (PST)
X-Original-To: pce@core3.amsl.com
Delivered-To: pce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3957F3A6A06; Fri, 14 Nov 2008 13:41:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level:
X-Spam-Status: No, score=-17.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2JJwBCx1G1i7; Fri, 14 Nov 2008 13:41:34 -0800 (PST)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 61D1E3A6944; Fri, 14 Nov 2008 13:41:34 -0800 (PST)
Received: by bosco.isi.edu (Postfix, from userid 70) id A1F0D175000; Fri, 14 Nov 2008 13:41:34 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20081114214134.A1F0D175000@bosco.isi.edu>
Date: Fri, 14 Nov 2008 13:41:34 -0800
Cc: pce@ietf.org, rfc-editor@rfc-editor.org
Subject: [Pce] RFC 5376 on Inter-AS Requirements for the Path Computation Element Communication Protocol (PCECP)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org
A new Request for Comments is now available in online RFC libraries.
RFC 5376
Title: Inter-AS Requirements for the Path
Computation Element Communication Protocol (PCECP)
Author: N. Bitar, R. Zhang, K. Kumaki
Status: Informational
Date: November 2008
Mailbox: nabil.n.bitar@verizon.com,
ke-kumaki@kddi.com,
Raymond.zhang@bt.com
Pages: 14
Characters: 33114
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-pce-interas-pcecp-reqs-06.txt
URL: http://www.rfc-editor.org/rfc/rfc5376.txt
Multiprotocol Label Switching Traffic Engineered (MPLS TE) Label
Switched Paths (LSPs) may be established wholly within an Autonomous
System (AS) or may cross AS boundaries.
The Path Computation Element (PCE) is a component that is capable of
computing constrained paths for (G)MPLS TE LSPs. The PCE Communication Protocol (PCECP) is defined to allow communication between Path Computation Clients (PCCs) and PCEs, as well as between PCEs.
The PCECP is used to request constrained paths and to supply computed
paths in response. Generic requirements for the PCECP are set out in
"Path Computation Element (PCE) Communication Protocol Generic
Requirements", RFC 4657. This document extends those requirements to
cover the use of PCECP in support of inter-AS MPLS TE. This memo provides
information for the Internet community.
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
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
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
USC/Information Sciences Institute
_______________________________________________
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce