Multiprotocol Label Switching (mpls) Internet Drafts

      
 YANG Data Model for MPLS mLDP
 
 draft-ietf-mpls-mldp-yang-13.txt
 Date: 07/07/2025
 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).
 MPLS Network Action (MNA) Sub-Stack Solution
 
 draft-ietf-mpls-mna-hdr-13.txt
 Date: 20/07/2025
 Authors: Jaganbabu Rajamanickam, Rakesh Gandhi, Royi Zigler, Haoyu Song, Kireeti Kompella
 Working Group: Multiprotocol Label Switching (mpls)
 This document defines the MPLS Network Actions (MNA) sub-stack solution for carrying Network Actions and Ancillary Data in the label stack. MNA 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 solution document specifies In-stack network action and In-stack data specific requirements found in "Requirements for MPLS Network Actions". This document follows the architectural framework for the MNA technologies specified in "MPLS Network Actions (MNA) Framework".
 Label Switched Path Ping for Segment Routing Path Segment Identifier with MPLS Data Plane
 
 draft-ietf-mpls-spring-lsp-ping-path-sid-13.txt
 Date: 06/06/2025
 Authors: Xiao Min, Shaofu Peng, Liyan Gong, Rakesh Gandhi, Carlos Pignataro
 Working Group: Multiprotocol Label Switching (mpls)
 Segment Routing (SR) leverages source routing to steer packets through an ordered list of instructions, called segments. SR can be instantiated over the MPLS data plane. Path Segment Identifiers (PSIDs) are used to identify and correlate bidirectional or end-to- end paths in Segment Routing networks. This document defines procedures (i.e. six new Target forwarding Equivalence Class (FEC) Stack sub-TLVs) for the use of LSP Ping to support connectivity verification and fault isolation for SR paths that include Path Segment Identifiers. The mechanisms described enable the validation and tracing of SR paths with Path SIDs in MPLS networks, complementing existing SR-MPLS OAM capabilities.
 Encapsulation of Simple Two-Way Active Measurement Protocol for Pseudowires and LSPs in MPLS Networks
 
 draft-ietf-mpls-stamp-pw-01.txt
 Date: 05/06/2025
 Authors: Rakesh Gandhi, Patrice Brissette, Eddie Leyton, Xiao Min
 Working Group: Multiprotocol Label Switching (mpls)
 Pseudowires (PWs) and Label Switched Paths (LSPs) are used in MPLS networks for various services including carrying layer 2 and layer 3 data packets. This document describes the procedure for encapsulation of the Simple Two-Way Active Measurement Protocol (STAMP) defined in RFC 8762 and its optional extensions defined in RFC 8972 for PWs and LSPs in MPLS networks. The procedure uses Generic Associated Channel (G-ACh) to encapsulate the STAMP test packets with or without adding an IP/UDP header for PWs and LSPs.
 Supporting In Situ Operations,Administration and Maintenance Using MPLS Network Actions
 
 draft-ietf-mpls-mna-ioam-03.txt
 Date: 30/05/2025
 Authors: Rakesh Gandhi, Greg Mirsky, Tony Li, Haoyu Song, Bin Wen
 Working Group: Multiprotocol Label Switching (mpls)
 In situ Operations, Administration, and Maintenance (IOAM), defined in RFC 9197, is an on-path telemetry method to collect and record the operational state and telemetry information using, for example, Pre- allocated, Proof-of-Transit, Edge-To-Edge or Incremental IOAM Option, that can be used to calculate various performance metrics. RFC 9326 defined the IOAM Direct Export (IOAM-DEX) Option in which the operational state and telemetry information are collected according to the specified profile and exported in a manner and format defined by a local policy on each node along the path. MPLS Network Actions (MNA) techniques are meant to indicate actions to be performed on any combination of Label Switched Paths, MPLS packets, and the node itself, and to transfer data needed for these actions. This document explores the MNA mechanisms to collect and transport the on-path operational state, and telemetry information IOAM data fields, including IOAM-DEX Option.
 Post-Stack MPLS Network Action (MNA) Solution
 
 draft-ietf-mpls-ps-mna-hdr-00.txt
 Date: 16/02/2025
 Authors: Jaganbabu Rajamanickam, Rakesh Gandhi, Royi Zigler, Tony Li, Jie Dong
 Working Group: Multiprotocol Label Switching (mpls)
 This document defines the Post-Stack MPLS Network Action (MNA) solution for carrying Network Actions and Ancillary Data after the MPLS label stack based on In-Stack MNA solution defined in "MPLS Network Action (MNA) Sub-Stack Solution". MPLS Network Actions can be used to influence packet forwarding decisions, carry additional Operations, Administration, and Maintenance (OAM) information in the MPLS packet or perform user-defined operations. This solution document addresses the Post-stack network action and Post-stack data (PSD) specific requirements found in "Requirements for MPLS Network Actions". This document follows the architectural framework for the MPLS Network Actions (MNA) technologies specified in "MPLS Network Actions (MNA) Framework".
 MPLS Network Actions for Network Resource Partition Selector
 
 draft-ietf-mpls-mna-nrp-selector-00.txt
 Date: 13/05/2025
 Authors: Tony Li, John Drake, Vishnu Beeram, 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 provided the same forwarding treatment. The packets associated with a Slice-Flow Aggregate may carry a marking in the packet's network layer header to identify this association and this marking is referred to as NRP Selector. The NRP Selector is used to map the packet to the associated NRP and provide 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 discusses options for using MPLS Network Actions (MNAs) to carry the NRP Selector in MPLS packets.
 Post-Stack MPLS Network Action (MNA) Solution
 
 draft-ietf-mpls-mna-ps-hdr-01.txt
 Date: 30/05/2025
 Authors: Jaganbabu Rajamanickam, Rakesh Gandhi, Royi Zigler, Tony Li, Jie Dong
 Working Group: Multiprotocol Label Switching (mpls)
 This document defines the Post-Stack MPLS Network Action (MNA) solution for carrying Network Actions and Ancillary Data after the MPLS label stack, based on the In-Stack MNA solution defined in "MPLS Network Action (MNA) Sub-Stack Solution." MPLS Network Actions can be used to influence packet forwarding decisions, carry additional Operations, Administration, and Maintenance (OAM) information in the MPLS packet, or perform user-defined operations. This solution document addresses the Post-Stack network action and Post-Stack data specific requirements found in "Requirements for MPLS Network Actions." This document follows the architectural framework for the MPLS Network Actions (MNA) technologies specified in "MPLS Network Actions (MNA) Framework."
 Carrying NRP related Information in MPLS Packets
 
 draft-ietf-mpls-mna-psd-nrp-selector-00.txt
 Date: 13/08/2025
 Authors: Zhenbin Li, Jie Dong
 Working Group: Multiprotocol Label Switching (mpls)
 A Network Resource Partition (NRP) is a subset of the network resources and associated policies on each of a connected set of links in the underlay network. An NRP could be used as the underlay to support one or a group of enhanced VPN services. Multiple NRPs can be created by network operator to meet the diverse requirements of different enhanced VPN services. In packet forwarding, some fields in the data packet needs to be used as the NRP Selector to identify the NRP the packet belongs to, so that the NRP-specific processing can be executed on the packet. This document proposes a mechanism to carry the NRP Selector ID and related information in MPLS packets. The procedure for processing the NRP Selector ID and related information is also specified.

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 mpls@ietf.org
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
Jun 2026 Publication request for Encapsulation of Simple Two-Way Active Measurement Protocol for Pseudowires and LSPs in MPLS Networks draft-ietf-mpls-stamp-pw
Feb 2026 Publication request for Supporting In Situ Operations, Administration and Maintenance Using MPLS Network Actions draft-ietf-mpls-mna-ioam
Dec 2025 Publication request for Post-Stack MPLS Network Action (MNA) Solution draft-ietf-mpls-mna-ps-hdr
Nov 2025 Publication request for MPLS Network Actions for Network Resource Partition Selector draft-ietf-mpls-mna-nrp-selector
Sep 2025 Publication request for MPLS Network Action (MNA) Sub-Stack Solution draft-ietf-mpls-mna-hdr
Aug 2025 Publication request for YANG Data Model for MPLS mLDP draft-ietf-mpls-mldp-yang