Skip to main content

Interworking of GMPLS Control and Centralized Controller System
draft-zheng-teas-gmpls-controller-inter-work-03

Document Type Replaced Internet-Draft (candidate for teas WG)
Authors Haomian Zheng , Xianlong Luo , Yang Zhao , Yunbin Xu , Sergio Belotti , Dieter Beller
Last updated 2019-05-27 (Latest revision 2019-02-15)
Replaces draft-zheng-ccamp-gmpls-controller-inter-work
Replaced by draft-ietf-teas-gmpls-controller-inter-work
Stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Expired & archived
Stream WG state Call For Adoption By WG Issued
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-teas-gmpls-controller-inter-work
Consensus boilerplate Unknown
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:

Abstract

Generalized Multi-Protocol Label Switching (GMPLS) control allows each network element (NE) to perform local resource discovery, routing and signaling 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 described in RFC 8453. Instead of competing with each other, both the distributed and the centralized control plane have their own advantages, 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.

Authors

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.)