RFC 5623 on Framework for PCE-Based Inter-Layer MPLS and GMPLS Traffic Engineering

rfc-editor@rfc-editor.org Thu, 17 September 2009 23:09 UTC

Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 0CE1C3A6B45; Thu, 17 Sep 2009 16:09:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.889
X-Spam-Status: No, score=-16.889 tagged_above=-999 required=5 tests=[AWL=0.710, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id XDxvKeIhg5Sx; Thu, 17 Sep 2009 16:09:45 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu []) by core3.amsl.com (Postfix) with ESMTP id B3C6E28C16A; Thu, 17 Sep 2009 16:08:43 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 528193256F8; Thu, 17 Sep 2009 16:09:08 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5623 on Framework for PCE-Based Inter-Layer MPLS and GMPLS Traffic Engineering
From: rfc-editor@rfc-editor.org
Message-Id: <20090917230908.528193256F8@bosco.isi.edu>
Date: Thu, 17 Sep 2009 16:09:08 -0700
Cc: pce@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Thu, 17 Sep 2009 23:09:46 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 5623

        Title:      Framework for PCE-Based Inter-Layer MPLS 
                    and GMPLS Traffic Engineering 
        Author:     E. Oki, T. Takeda,
                    JL. Le Roux, A. Farrel
        Status:     Informational
        Date:       September 2009
        Mailbox:    oki@ice.uec.ac.jp, 
        Pages:      34
        Characters: 81033
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pce-inter-layer-frwk-10.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5623.txt

A network may comprise multiple layers.  It is important to globally
optimize network resource utilization, taking into account all
layers rather than optimizing resource utilization at each layer
independently.  This allows better network efficiency to be achieved
through a process that we call inter-layer traffic engineering.  The
Path Computation Element (PCE) can be a powerful tool to achieve
inter-layer traffic engineering.

This document describes a framework for applying the PCE-based
architecture to inter-layer Multiprotocol Label Switching (MPLS) and
Generalized MPLS (GMPLS) traffic engineering.  It provides
suggestions for the deployment of PCE in support of multi-layer
networks.  This document also describes network models where PCE
performs inter-layer traffic engineering, and the relationship
between PCE and a functional component called the Virtual Network
Topology Manager (VNTM).  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

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