RFC 9730: Interworking of GMPLS Control and Centralized Controller Systems
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9730
- Published
- March 2025
- Authors
- H. Zheng; Y. Lin; Y. Zhao; Y. Xu; D. Beller
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 32
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9731A YANG Data Model for Virtual Network (VN) OperationsCurrent
March 2025
- RFC 10028Updates to Dynamic IPv6 Multicast Address Group IDsCurrent
August 2026
- RFC 9299An Architectural Introduction to the Locator/ID Separation Protocol (LISP)Current
October 2022
- RFC 9015BGP Control Plane for the Network Service Header in Service Function ChainingCurrent
June 2021
- RFC 8637Applicability of the Path Computation Element (PCE) to the Abstraction and Control of TE Networks (ACTN)Current
July 2019
- RFC 6041Forwarding and Control Element Separation (ForCES) Applicability StatementCurrent
October 2010
- RFC 5145Framework for MPLS-TE to GMPLS MigrationCurrent
March 2008
- RFC 4364BGP/MPLS IP Virtual Private Networks (VPNs)Updated
February 2006
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?