IETF-92 Proceedings

Introduction  |  Area, Working Goup & BoF Reports  |  Plenaries  |  Training  |  Internet Research Task Force

Multiprotocol Label Switching (mpls) (WG)

Minutes   |   Jabber Logs  |   Mailing List Archives

Additional information is available at



Routing Area Area Director(s):

Assigned Area Director


Meeting Slides:

Blue Sheets:


Request for Comments:

Charter (as of 2014-12-05):

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

The working group's responsibilities include procedures and
protocols for the distribution of labels between Label Switching
Routers (LSRs), MPLS packet encapsulation, and for Operation,
Administration, and Maintenance (OAM) for MPLS systems
including the necessary management objects expressed as
YANG models or MIB modules.

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
working groups.

- Evolve key MPLS protocols, including LDP, tLDP, mLDP, RSVP-TE
for packet networks, and LSP Ping to meet new requirements.

- Document MPLS-specific aspects of traffic engineering including
for 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 data models for MPLS working group related solutions.
YANG models and MIB modules may be considered. Coordinate with
the LIME and NETMOD 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.

- Define the necessary extensions for MPLS key protocols for dual-
stack and IPv6-only networks.

- Document current implementation practices for MPLS load sharing.

- Document mechanisms for securing MPLS protocols and data plane.

- Document mechanisms for adding multi-topology support to existing
MPLS protocols.

- Define the necessary protection protocols and scenarios for transport
profile MPLS applications

- Document use cases for MPLS protocols.