File formats:

Also available: XML file for editing

 

Status:

INFORMATIONAL

Authors:

H. Zheng
Y. Lin
Y. Zhao
Y. Xu
D. Beller

Stream:

IETF

Source:

teas (rtg)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC9730

Discuss this RFC: Send questions or comments to the mailing list teas@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 9730

Abstract

Generalized Multiprotocol Label Switching (GMPLS) control allows each network element (NE) to perform local resource discovery, routing, and signaling in a distributed manner.

The advancement of software-defined transport networking technology enables a group of NEs to be managed through centralized controller hierarchies. This helps to tackle challenges arising from multiple domains, vendors, and technologies. An example of such a centralized architecture is the Abstraction and Control of Traffic-Engineered Networks (ACTN) controller hierarchy, as described in RFC 8453.

Both the distributed and centralized control planes have their respective advantages and should complement each other in the system, rather than compete. This document outlines how the GMPLS distributed control plane can work together with a centralized controller system in a transport network.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.