RFC 9789: MPLS Network Actions (MNAs) Framework
In plain English — editorial summary, not part of the RFC
This document describes an architectural framework for MPLS Network Action (MNA) technologies. MNA technologies are used to indicate actions that impact the forwarding or other processing (such as monitoring) of the packet along the Label Switched Path (LSP) of the packet and to transfer any additional data needed for these actions. This document provides the foundation for the development of a common set of network actions and information elements supporting additional operational models and capabilities of MPLS networks.
Document record
- Document ID
- RFC9789
- Published
- July 2025
- Authors
- L. Andersson; S. Bryant; M. Bocci; T. Li
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 19
- Also known as
- —
- Updated by:
- RFC 9994
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9790IANA Registry and Processing Recommendations for the First Nibble Following a Label StackCurrent
July 2025
- RFC 9791Use Cases for MPLS Network Action Indicators and Ancillary DataCurrent
July 2025
- RFC 9786EVPN Port-Active Redundancy ModeCurrent
June 2025
- RFC 9792Prefix Flag Extension for OSPFv2 and OSPFv3Current
June 2025
- RFC 9785Preference-Based EVPN Designated Forwarder (DF) ElectionCurrent
June 2025
- RFC 9793BGP Extensions for Bit Index Explicit Replication (BIER)Current
June 2025
- RFC 9784Virtual Ethernet Segments for EVPN and Provider Backbone Bridge EVPNCurrent
June 2025
- RFC 9780Bidirectional Forwarding Detection (BFD) for Multipoint Networks over Point-to-Multipoint MPLS Label Switched Paths (LSPs)Current
May 2025
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?