[Pce] RFC 6457 on PCC-PCE Communication and PCE Discovery Requirements for Inter-Layer Traffic Engineering
rfc-editor@rfc-editor.org Sat, 03 December 2011 00:21 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 4368611E80D1; Fri, 2 Dec 2011 16:21:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.957
X-Spam-Level:
X-Spam-Status: No, score=-101.957 tagged_above=-999 required=5 tests=[AWL=0.643, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Utx03gspnlGm; Fri, 2 Dec 2011 16:21:54 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 4717A11E80C8; Fri, 2 Dec 2011 16:21:54 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 6039172E010; Fri, 2 Dec 2011 16:21:37 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20111203002137.6039172E010@rfc-editor.org>
Date: Fri, 02 Dec 2011 16:21:37 -0800
Cc: pce@ietf.org, rfc-editor@rfc-editor.org
Subject: [Pce] RFC 6457 on PCC-PCE Communication and PCE Discovery Requirements for Inter-Layer Traffic Engineering
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Sat, 03 Dec 2011 00:21:55 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6457
Title: PCC-PCE Communication and PCE Discovery
Requirements for Inter-Layer Traffic Engineering
Author: T. Takeda, Ed.,
A. Farrel
Status: Informational
Stream: IETF
Date: December 2011
Mailbox: takeda.tomonori@lab.ntt.co.jp,
adrian@olddog.co.uk
Pages: 12
Characters: 29107
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-pce-inter-layer-req-15.txt
URL: http://www.rfc-editor.org/rfc/rfc6457.txt
The Path Computation Element (PCE) provides functions of path
computation in support of traffic engineering in networks controlled by
Multi-Protocol Label Switching (MPLS) and Generalized MPLS (GMPLS).
MPLS and GMPLS networks may be constructed from layered client/server
networks. It is advantageous for overall network efficiency to
provide end-to-end traffic engineering across multiple network
layers. PCE is a candidate solution for such requirements.
Generic requirements for a communication protocol between Path
Computation Clients (PCCs) and PCEs are presented in RFC 4657, "Path
Computation Element (PCE) Communication Protocol Generic
Requirements". Generic requirements for a PCE discovery protocol are
presented in RFC 4674, "Requirements for Path Computation Element
(PCE) Discovery".
This document complements the generic requirements and presents
detailed sets of PCC-PCE communication protocol requirements and PCE
discovery protocol requirements for inter-layer traffic engineering.
This document is not an Internet Standards Track specification; it is
published for informational purposes.
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
Association Management Solutions, LLC