A new Request for Comments is now available in online RFC libraries.
RFC 9730
Title: Interworking of GMPLS Control and
Centralized Controller Systems
Author: H. Zheng,
Y. Lin,
Y. Zhao,
Y. Xu,
D. Beller
Status: Informational
Stream: IETF
Date: March 2025
Mailbox: [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
Pages: 32
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-teas-gmpls-controller-inter-work-17.txt
URL: https://www.rfc-editor.org/info/rfc9730
DOI: 10.17487/RFC9730
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.
This document is a product of the Traffic Engineering Architecture and
Signaling Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
_______________________________________________
rfc-dist mailing list -- [email protected]
To unsubscribe send an email to [email protected]
http://www.rfc-editor.org
