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; and mechanisms for Operation, Administration, and Maintenance (OAM) for MPLS systems including the necessary management objects expressed as YANG 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, OPSAWG, SPRING, and TEAS working groups.

•	Maintain and evolve key MPLS protocols to meet new requirements: LDP (including tLDP and mLDP), RSVP-TE for packet networks, and LSP Ping.

•	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 the NETMOD and ONIONS working groups for core YANG models.

•	Define an overall OAM framework for topology-driven, traffic engineered, and transport profile MPLS applications to achieve a common set of approaches and tools across the full family of MPLS applications.

•	Document mechanisms for securing MPLS protocols and data plane.

•	Document use cases for MPLS protocols.

•	Define a framework and encapsulations for MPLS Network Actions (MNA). Document use cases for MNA and define solutions for those use cases.

•	Maintain existing MPLS-based static and LDP-signaled pseudowire and L2VPN requirements, mechanisms, and protocols as currently documented in RFCs, and enhance them as necessary. Ensure that MPLS can continue to support these applications, as well as other MPLS based signaled PWs as they evolve.