Multiprotocol Label Switching (mpls) Internet Drafts

      
 YANG Data Model for MPLS mLDP
 
 draft-ietf-mpls-mldp-yang-16.txt
 Date: 03/02/2026
 Authors: Syed Raza, Xufeng Liu, Santosh Esale, Loa Andersson, Jeff Tantsura
 Working Group: Multiprotocol Label Switching (mpls)
 This document describes a YANG data model for the Multiprotocol Label Switching (MPLS) Multipoint Label Distribution Protocol (mLDP). The mLDP YANG data model augments the MPLS LDP YANG data model. The YANG modules in this document conform to the Network Management Datastore Architecture (NMDA).
 Encapsulation of Simple Two-Way Active Measurement Protocol for LSPs and Pseudowires in MPLS Networks
 
 draft-ietf-mpls-stamp-pw-21.txt
 Date: 10/09/2026
 Authors: Rakesh Gandhi, Patrice Brissette, Eddie Leyton, Xiao Min
 Working Group: Multiprotocol Label Switching (mpls)
 This document specifies encapsulations for the Simple Two-Way Active Measurement Protocol (STAMP), defined in RFC 8762, and its optional extensions, defined in RFC 8972, in MPLS networks. It specifies the encapsulation of STAMP test packets for point-to-point Label Switched Paths (LSPs) and point-to-point single-segment Pseudowires (PWs), with or without an IP/UDP header, so that the test packets experience the same forwarding and Equal-Cost Multi-Path (ECMP) behavior as the data traffic being measured. In addition, two new MPLS Generic Associated Channel (G-ACh) types are defined. The procedures specified in this document are intended for deployment in a single network administrative domain. This document updates RFC 8762 and RFC 8972 to allow STAMP to operate without an IP/UDP header when STAMP test packets are carried over MPLS LSPs and PWs, and specifies the resulting changes to the processing of the STAMP session identifier, the IPv4 TTL and IPv6 Hop Limit, and the STAMP TLV extensions.
 MPLS Network Actions for In Situ Operations,Administration,and Maintenance
 
 draft-ietf-mpls-mna-ioam-14.txt
 Date: 11/09/2026
 Authors: Rakesh Gandhi, Greg Mirsky, Haoyu Song, Bin Wen, Voitek Kozak
 Working Group: Multiprotocol Label Switching (mpls)
 In situ Operations, Administration, and Maintenance (IOAM), defined in RFC 9197, collects operational and telemetry information in the packet using IOAM-Data-Fields while the packet traverses a path between two points in the network. Several IOAM Option-Types are available, for example, Pre-allocated Trace, Proof of Transit (POT), Edge-to-Edge (E2E), and Incremental Trace, that can be used to collect information for calculating various performance metrics. RFC 9326 defines the IOAM Direct Export (IOAM-DEX) Option-Type, which is used as a trigger for IOAM data to be directly exported or locally aggregated without being pushed into in-flight data packets. MPLS Network Action (MNA) mechanisms indicate actions to be performed on any combination of Label Switched Paths, MPLS packets, and the node itself, and to transport data needed for these actions. This document defines MNAs to collect and transport the operational state and telemetry information using IOAM-Data-Fields as well as IOAM-DEX.
 MPLS Network Actions for Network Resource Partition Selector
 
 draft-ietf-mpls-mna-nrp-selector-07.txt
 Date: 11/06/2026
 Authors: Tony Li, Vishnu Beeram, John Drake, Tarek Saad, Israel Meilik
 Working Group: Multiprotocol Label Switching (mpls)
 An IETF Network Slice service provides connectivity coupled with a set of network resource commitments and is expressed in terms of one or more connectivity constructs. A Network Resource Partition (NRP) is a collection of resources identified in the underlay network to support IETF Network Slice services. A Slice-Flow Aggregate refers to the set of traffic streams from one or more connectivity constructs belonging to one or more IETF Network Slices that are mapped to a specific NRP and provide the same forwarding treatment. The packets associated with a Slice-Flow Aggregate may carry markings in the packet's network layer header to identify this association and each is referred to as NRP Selector. The NRP Selector is used to map the packet to the associated NRP and provides the corresponding forwarding treatment to the packet. MPLS Network Actions (MNA) technologies are used to indicate actions for Label Switched Paths (LSPs) and/or MPLS packets and to transfer data needed for these actions. This document specifies options for using MPLS Network Actions (MNAs) to carry the NRP Selector in MPLS packets.
 MPLS Network Action (MNA) Post-Stack Header Specification
 
 draft-ietf-mpls-mna-ps-hdr-19.txt
 Date: 06/08/2026
 Authors: Jaganbabu Rajamanickam, Rakesh Gandhi, Royi Zigler, Jie Dong, Jisu Bhattacharya
 Working Group: Multiprotocol Label Switching (mpls)
 This document specifies the MPLS Network Action (MNA) Post-Stack Header encoding and procedures for carrying Network Action encodings and Ancillary Data after the MPLS label stack, based on the MNA Sub- Stack including In-Stack Network Actions and Data specified in RFC 9994. MPLS Network Actions can be used to influence packet forwarding decisions, carry additional Operations, Administration, and Maintenance information in the MPLS packet, or perform user- defined operations. This document follows the framework specified in RFC 9789. This document updates RFC 9994: the "Network Action Opcodes" registry fields, the Post-Stack MNA applicability of the opcodes, MNA scope, and Unknown action handling. This document updates RFC 9789: the definition of Readable Label Depth (RLD).
 Simple Two-way Active Measurement Protocol (STAMP) for MPLS Label Switched Paths (LSPs)
 
 draft-ietf-mpls-stamp-01.txt
 Date: 16/06/2026
 Authors: Greg Mirsky, Li Zhang, Loa Andersson
 Working Group: Multiprotocol Label Switching (mpls)
 Simple Two-way Active Measurement Protocol (STAMP), defined in RFC 8762 and RFC 8972, is expected to be able to monitor the performance of paths between systems that use a wide variety of encapsulations. This document defines encapsulation and bootstrapping of a STAMP test session over an MPLS Label Switched Path.
 MPLS Network Action for Deterministic Networking
 
 draft-ietf-mpls-mna-detnet-01.txt
 Date: 29/06/2026
 Authors: Xueyan Song, Greg Mirsky, Balazs Varga, Rakesh Gandhi, Quan Xiong
 Working Group: Multiprotocol Label Switching (mpls)
 This document specifies formats and mechanisms for using MPLS Network Actions (MNA) to support Deterministic Networking (DetNet) services, including bounded latency, low loss and in-order delivery. It defines MPLS In-Stack and Post-Stack MNA for carrying DetNet-specific information, such as flow identification, sequence number, and latency information, which are forwarded over an MPLS technology- based network domain.
 LSP Ping/Traceroute for Enabled In-situ OAM Capabilities
 
 draft-ietf-mpls-lsp-ping-ioam-conf-state-02.txt
 Date: 27/07/2026
 Authors: Xiao Min, Greg Mirsky, Loa Andersson
 Working Group: Multiprotocol Label Switching (mpls)
 This document describes the application of the mechanism of discovering In-situ OAM (IOAM) capabilities, described in RFC 9359 "Echo Request/Reply for Enabled In Situ OAM (IOAM) Capabilities", in MPLS networks. The MPLS Node IOAM Information Query functionality uses the MPLS echo request/reply messages, allowing the IOAM encapsulating node to discover the enabled IOAM capabilities of each IOAM transit and IOAM decapsulating node.
 MPLS On-Path Telemetry Network Action Flag for OAM
 
 draft-ietf-mpls-on-path-telemetry-flag-04.txt
 Date: 16/09/2026
 Authors: Haoyu Song, Giuseppe Fioccola, Rakesh Gandhi
 Working Group: Multiprotocol Label Switching (mpls)
 This document describes postcard-based on-path telemetry with packet marking (PBT-M) using an MPLS Network Actions (MNA) flag to support Operations, Administration, and Maintenance (OAM) in MPLS networks. The scheme uses a single flag bit carried in a Flag-Based Network Action Indicator (Opcode 1) of the MNA Sub-Stack as defined in RFC 9994. In addition to addressing the protocol requirements for applying PBT-M, this document provides comprehensive operational, manageability, and security considerations.
 Signaling Optimization Objective and Bounded Metrics for MPLS Fast Reroute Backup LSP Tunnels
 
 draft-ietf-mpls-frr-ext-00.txt
 Date: 23/08/2026
 Authors: Abhishek Deshmukh, Vishnu Beeram, Tarek Saad
 Working Group: Multiprotocol Label Switching (mpls)
 This document introduces RSVP-TE signaling procedures that enable the head-end Label Switched Router (LSR) of a local-protection-desiring Label Switched Path (LSP) to influence the optimization objective and bounded metric constraints used for the path computation of a backup LSP tunnel at a Point of Local Repair (PLR).

data-group-menu-data-url="/group/groupmenu.json">

Multiprotocol Label Switching (mpls)

WG Name Multiprotocol Label Switching
Acronym mpls
Area Routing Area (rtg)
State Active
Charter charter-ietf-mpls-08 Approved
Status update Show Changed 2018-11-10
Document dependencies
Additional resources Issue tracker, Wiki, Zulip Stream
Personnel Chairs Adrian Farrel, Tarek Saad, Tony Li
Area Director Jim Guichard
Secretary Mach Chen
Mailing list Address [email protected]
To subscribe https://www.ietf.org/mailman/listinfo/mpls
Archive https://mailarchive.ietf.org/arch/browse/mpls/
Chat Room address https://zulip.ietf.org/#narrow/stream/mpls

Charter for Working Group

The MPLS working group is responsible for standardizing technology for label switching and for the implementation of label-switched paths over packet based link-level technologies.

The working group's responsibilities include: procedures and protocols for the distribution of labels between Label Switching Routers (LSRs); MPLS encapsulation and emulation of Layer 1, Layer 2, and Layer 3 frames, packets, and services that run over MPLS; and mechanisms for Operation, Administration, and Maintenance (OAM) for MPLS systems including the necessary management objects expressed as YANG data models.

The current WG focus areas and work items are:

• Maintain existing MPLS requirements, mechanisms, and protocols, as currently documented in RFCs, in coordination with other working groups that work in overlapping areas including the BESS, BFD, BIER, CCAMP, DETNET, IDR, IPPM, OPSAWG, SPRING, and TEAS working groups.
• Maintain and evolve key MPLS protocols to meet new requirements: LDP (including Targeted LDP (tLDP) and Multipoint LDP (mLDP)), RSVP-TE for packet networks, and LSP Ping.
• Maintain existing MPLS-based static and LDP-signaled pseudowire and L2VPN requirements, mechanisms, and protocols as currently documented in RFCs, and enhance them. Ensure that MPLS can continue to support these applications, as well as other MPLS based signaled PWs as they evolve.
• Document use cases for MPLS protocols.
• Document MPLS-specific aspects of traffic engineering including multi-areas/multi-AS scenarios in cooperation with the TEAS working group.
• Coordinate the work on RSVP-TE with CCAMP and TEAS. In the cases where there is an overlap, generic parts will be done by the TEAS working group, MPLS data plane specific parts will be done by the MPLS working group, and support for any other specific data planes will be done by the CCAMP working group. The TEAS working group acts as the hub for coordinating this work, and the MPLS working group will track agreements about work to be done in this working group through milestones in this charter.
• Define YANG data models for MPLS working group related solutions. Coordinate with other working groups (such as NETMOD) for core YANG data models.
• Define an overall OAM framework for applications that are topology-driven, traffic engineered or utilize transport profile MPLS to achieve a common set of approaches and mechanisms across the full family of applications that use MPLS.
• Document mechanisms for securing MPLS protocols and data plane.
• Define a framework and encapsulations for MPLS Network Actions (MNA). Document use cases for MNA and define solutions for those use cases.

Note: All documents will be standards track unless otherwise specified in the milestones.

Milestones

Date Milestone Associated documents
Sep 2027 Request publication for Signaling Optimization Objective and Bounded Metrics for MPLS Fast Reroute Backup LSP Tunnels draft-ietf-mpls-frr-ext
Jun 2027 Request publication for MPLS Network Action for Deterministic Networking draft-ietf-mpls-mna-detnet
Mar 2027 Request publication for LSP Ping/Traceroute for Enabled In-situ OAM Capabilities draft-ietf-mpls-lsp-ping-ioam-conf-state
Mar 2027 Request publication for Simple Two-way Active Measurement Protocol (STAMP) for MPLS Label Switched Paths (LSPs) draft-ietf-mpls-stamp
Jan 2027 Request publication for Carrying NRP related Information in MPLS Packets draft-ietf-mpls-mna-psd-nrp-selector

Done milestones

Date Milestone Associated documents
Done Request publication for MPLS On-Path Telemetry Network Action Flag for OAM draft-ietf-mpls-on-path-telemetry-flag
Done Adopt Signaling Optimization Objective and Bounded Metrics for MPLS Fast Reroute Backup LSP Tunnels draft-deshmukh-mpls-frr-ext
Done Publication request for Encapsulation of Simple Two-Way Active Measurement Protocol for Pseudowires and LSPs in MPLS Networks draft-ietf-mpls-stamp-pw
Done Publication request for Supporting In Situ Operations, Administration and Maintenance Using MPLS Network Actions draft-ietf-mpls-mna-ioam
Done Publication request for Post-Stack MPLS Network Action (MNA) Solution draft-ietf-mpls-mna-ps-hdr
Done Publication request for MPLS Network Actions for Network Resource Partition Selector draft-ietf-mpls-mna-nrp-selector
Done Publication request for MPLS Network Action (MNA) Sub-Stack Solution rfc9994 (was draft-ietf-mpls-mna-hdr)
Done Publication request for YANG Data Model for MPLS mLDP draft-ietf-mpls-mldp-yang