RFC 5145: Framework for MPLS-TE to GMPLS Migration
In plain English — editorial summary, not part of the RFC
The migration from Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) to Generalized MPLS (GMPLS) is the process of evolving an MPLS-TE control plane to a GMPLS control plane. An appropriate migration strategy will be selected based on various factors including the service provider's network deployment plan, customer demand, and operational policy. This document presents several migration models and strategies for migrating from MPLS-TE to GMPLS. In the course of migration, MPLS-TE and GMPLS devices, or networks, may coexist that may require interworking between MPLS-TE and GMPLS protocols. Aspects of the required interworking are discussed as it will influence the choice of a migration strategy. This framework document provides a migration toolkit to aid the operator in selection of an appropriate strategy. This framework document also lists a set of solutions that may aid in interworking, and highlights a set of potential issues. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5145
- Published
- March 2008
- Authors
- K. Shiomoto
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5146Interworking Requirements to Support Operation of MPLS-TE over GMPLS NetworksCurrent
March 2008
- RFC 4561Definition of a Record Route Object (RRO) Node-Id Sub-ObjectCurrent
June 2006
- RFC 6041Forwarding and Control Element Separation (ForCES) Applicability StatementCurrent
October 2010
- RFC 4139Requirements for Generalized MPLS (GMPLS) Signaling Usage and Extensions for Automatically Switched Optical Network (ASON)Current
July 2005
- RFC 9015BGP Control Plane for the Network Service Header in Service Function ChainingCurrent
June 2021
- RFC 9730Interworking of GMPLS Control and Centralized Controller SystemsCurrent
March 2025
- RFC 6404Session PEERing for Multimedia INTerconnect (SPEERMINT) Security Threats and Suggested CountermeasuresCurrent
November 2011
- RFC 5148Jitter Considerations in Mobile Ad Hoc Networks (MANETs)Current
February 2008
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?