[rfc-dist] RFC 5623 on Framework for PCE-Based Inter-Layer MPLS and GMPLS Traffic Engineering
rfc-editor at rfc-editor.org
Thu Sep 17 16:09:08 PDT 2009
A new Request for Comments is now available in online RFC libraries.
Title: Framework for PCE-Based Inter-Layer MPLS
and GMPLS Traffic Engineering
Author: E. Oki, T. Takeda,
JL. Le Roux, A. Farrel
Date: September 2009
Mailbox: oki at ice.uec.ac.jp,
takeda.tomonori at lab.ntt.co.jp,
jeanlouis.leroux at orange-ftgroup.com,
adrian at olddog.co.uk
I-D Tag: draft-ietf-pce-inter-layer-frwk-10.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
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 at rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
The RFC Editor Team
USC/Information Sciences Institute
More information about the rfc-dist