Interworking Requirements to Support operation of MPLS-TE over GMPLS networks

Document Type Replaced Internet-Draft (individual)
Author Kenji Kumaki 
Last updated 2006-12-21 (latest revision 2006-10-25)
Replaced by RFC 5146
Stream (None)
Intended RFC status (None)
Expired & archived
plain text pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-ccamp-mpls-gmpls-interwork-reqts
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


This document describes a framework and Service Provider requirements for operating Multiprotocol Label Switching (MPLS) traffic engineering (TE) networks over Generalized MPLS (GMPLS) networks. Operation of an MPLS-TE network as a client network to a GMPLS network has enhanced operational capabilities than provided by a co- existent protocol model (ships in the night). The GMPLS network may be a packet or a non-packet network, and may itself be a multi-layer network supporting both packet and non-packet technologies. A MPLS-TE Label Switched Path (LSP) originates and terminates on an MPLS Label Switching Router (LSR). The GMPLS network provides transparent transport for the end-to-end MPLS-TE LSP. Specification of solutions is out of scope for this document.


Kenji Kumaki (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)