Skip to main content

Interworking of GMPLS Control and Centralized Controller System

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Haomian Zheng , Xianlong Luo , Yang Zhao , Yunbin Xu , Sergio Belotti , Dieter Beller
Last updated 2018-06-29
Replaced by draft-zheng-teas-gmpls-controller-inter-work
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-zheng-teas-gmpls-controller-inter-work
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


Generalized Multi-Protocol Label Switching (GMPLS) control allows each network element (NE) to perform local resource discovery (e.g., LMP), routing (e.g., OSPF-TE) and signaling (e.g., RSVP-TE) in a distributed manner. On the other hand, with the development of software-defined transport networking technology, a set of NEs can be controlled via centralized controller hierarchies to address the issue from multi- domain, multi-vendor and multi-technology. An example of such centralized architecture is ACTN controller hierarchy [I-D.ietf- teas-actn-framework]. Instead of competing with each other, both the distributed and the centralized control plane have their own advantage, and should be complementary in the system. This document describes how the GMPLS distributed control plane can interwork with a centralized controller system in a transport network.


Haomian Zheng
Xianlong Luo
Yang Zhao
Yunbin Xu
Sergio Belotti
Dieter Beller

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