Multiprotocol Label Switching (mpls) Internet Drafts

      
 Bidirectional Forwarding Detection (BFD) Directed Return Path for MPLS Label Switched Paths (LSPs)
 
 draft-ietf-mpls-bfd-directed-30.txt
 Date: 16/04/2024
 Authors: Greg Mirsky, Jeff Tantsura, Ilya Varlashkin, Mach Chen
 Working Group: Multiprotocol Label Switching (mpls)
 Bidirectional Forwarding Detection (BFD) is expected to be able to monitor a wide variety of encapsulations of paths between systems. When a BFD session monitors an explicitly routed unidirectional path there may be a need to direct the egress BFD peer to use a specific path for the reverse direction of the BFD session. This document describes an extension to the MPLS Label Switched Path (LSP) echo request that allows a BFD system to request that the remote BFD peer transmits BFD control packets over the specified LSP.
 A YANG Data Model for MPLS Static LSPs
 
 draft-ietf-mpls-static-yang-14.txt
 Date: 01/03/2024
 Authors: Tarek Saad, Rakesh Gandhi, Xufeng Liu, Vishnu Beeram, Igor Bryskin
 Working Group: Multiprotocol Label Switching (mpls)
 This document contains the specification for the MPLS Static Label Switched Paths (LSPs) YANG model. The model allows for the provisioning of static LSP(s) on Label Edge Router(s) LER(s) and Label Switched Router(s) LSR(s) devices along a LSP path without the dependency on any signaling protocol. The MPLS Static LSP model augments the MPLS base YANG model with specific data to configure and manage MPLS Static LSP(s).
 Refresh-interval Independent FRR Facility Protection
 
 draft-ietf-mpls-ri-rsvp-frr-16.txt
 Date: 22/12/2023
 Authors: Chandrasekar R, Tarek Saad, Ina Minei, Dante Pacella
 Working Group: Multiprotocol Label Switching (mpls)
 RSVP-TE Fast ReRoute extensions specified in RFC 4090 defines two local repair techniques to reroute Label Switched Path (LSP) traffic over pre-established backup tunnel. Facility backup method allows one or more LSPs traversing a connected link or node to be protected using a bypass tunnel. The many-to-one nature of local repair technique is attractive from scalability point of view. This document enumerates facility backup procedures in RFC 4090 that rely on refresh timeout and hence make facility backup method refresh- interval dependent. The RSVP-TE extensions defined in this document will enhance the facility backup protection mechanism by making the corresponding procedures refresh-interval independent and hence compatible with Refresh-interval Independent RSVP (RI-RSVP) specified in RFC 8370. Hence, this document updates RFC 4090 in order to support RI-RSVP capability specified in RFC 8370.
 YANG Data Model for MPLS mLDP
 
 draft-ietf-mpls-mldp-yang-11.txt
 Date: 29/02/2024
 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).
 RFC6374 Synonymous Flow Labels
 
 draft-ietf-mpls-rfc6374-sfl-10.txt
 Date: 05/03/2021
 Authors: Stewart Bryant, George Swallow, Mach Chen, Giuseppe Fioccola, Greg Mirsky
 Working Group: Multiprotocol Label Switching (mpls)
 RFC 6374 describes methods of making loss and delay measurements on Label Switched Paths (LSPs) primarily as used in MPLS Transport Profile (MPLS-TP) networks. This document describes a method of extending RFC 6374 performance measurements from flows carried over MPLS-TP to flows carried over generic MPLS LSPs. In particular, it extends the technique to allow loss and delay measurements to be made on multi-point to point LSPs and introduces some additional techniques to allow more sophisticated measurements to be made in both MPLS-TP and generic MPLS networks.
 Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering Segment Identifiers (SIDs) with MPLS Data Planes
 
 draft-ietf-mpls-sr-epe-oam-13.txt
 Date: 21/03/2024
 Authors: Shraddha Hegde, Mukul Srivastava, Kapil Arora, Samson Ninan, Xiaohu Xu
 Working Group: Multiprotocol Label Switching (mpls)
 Egress Peer Engineering (EPE) is an application of Segment Routing to solve the problem of egress peer selection. The Segment Routing based BGP-EPE solution allows a centralized controller, e.g. a Software Defined Network (SDN) controller to program any egress peer. The EPE solution requires a node to program the PeerNode Segment Identifier(SID) describing a session between two nodes, the PeerAdj SID describing the link (one or more) that is used by sessions between peer nodes, and the PeerSet SID describing an arbitrary set of sessions or links between a local node and its peers. This document provides new sub-TLVs for EPE Segment Identifiers (SID) that would be used in the MPLS Target stack TLV (Type 1), in MPLS Ping and Traceroute procedures.
 Performance Measurement for Segment Routing Networks with MPLS Data Plane
 
 draft-ietf-mpls-rfc6374-sr-09.txt
 Date: 09/02/2024
 Authors: Rakesh Gandhi, Clarence Filsfils, Dan Voyer, Stefano Salsano, Mach Chen
 Working Group: Multiprotocol Label Switching (mpls)
 Segment Routing (SR) leverages the source routing paradigm. SR is applicable to Multiprotocol Label Switching data plane (SR-MPLS) as specified in RFC 8402. RFC 6374 and RFC 7876 specify protocol mechanisms to enable efficient and accurate measurement of packet loss, one-way and two-way delay, as well as related metrics such as delay variation in MPLS networks. RFC 9341 defines Alternate-Marking Method using Block Number (BN) for data correlation mechanism for packet loss measurement. This document utilizes these mechanisms for Performance Delay and Loss Measurements in SR-MPLS networks, for both links and end-to-end SR-MPLS paths including Policies.
 Encapsulation For MPLS Performance Measurement with Alternate Marking Method
 
 draft-ietf-mpls-inband-pm-encapsulation-11.txt
 Date: 09/04/2024
 Authors: Weiqiang Cheng, Xiao Min, Tianran Zhou, Jinyou Dai, Yoav Peleg
 Working Group: Multiprotocol Label Switching (mpls)
 This document defines the encapsulation for MPLS performance measurement with alternate marking method, which performs flow-based packet loss, delay, and jitter measurements on MPLS live traffic.
 Egress Validation in Label Switched Path Ping and Traceroute Mechanisms
 
 draft-ietf-mpls-egress-tlv-for-nil-fec-12.txt
 Date: 01/03/2024
 Authors: Deepti Rathi, Shraddha Hegde, Kapil Arora, Zafar Ali, Nagendra Nainar
 Working Group: Multiprotocol Label Switching (mpls)
 The MPLS ping and traceroute mechanism as described in RFC 8029 and related extensions for Segment Routing(SR) as defined in RFC 8287 is very useful to validate the control plane and data plane synchronization. In some environments, only some intermediate or transit nodes may have been upgraded to support these validation procedures. A simple MPLS ping and traceroute mechanism allows traversing any path without validating the control plane state. RFC 8029 supports this mechanism with Nil Forwarding Equivalence Class (FEC). The procedures described in RFC 8029 mostly apply when the Nil FEC is used as an intermediate FEC in the label stack. When all labels in the label stack are represented using Nil FEC, it poses some challenges. This document introduces a new Type-Length-Value (TLV) as an extension to exisiting Nil FEC. It describes MPLS ping and traceroute procedures using Nil FEC with this extension to overcome these challenges.
 Path Monitoring System/Head-end based MPLS Ping and Traceroute in Inter-domain Segment Routing Networks
 
 draft-ietf-mpls-spring-inter-domain-oam-12.txt
 Date: 19/02/2024
 Authors: Shraddha Hegde, Kapil Arora, Mukul Srivastava, Samson Ninan, Nagendra Nainar
 Working Group: Multiprotocol Label Switching (mpls)
 The Routing (SR) architecture leverages source routing and tunneling paradigms and can be directly applied to the use of a Multiprotocol Label Switching (MPLS) data plane. A network may consist of multiple IGP domains or multiple Autonomous Systems(ASes) under the control of the same organization. It is useful to have the Label Switched Path (LSP) ping and traceroute procedures when an SR end-to-end path spans across multiple ASes or domains. This document describes mechanisms to facilitate LSP ping and traceroute in inter-AS/inter-domain SR- MPLS networks in an efficient manner with a simple Operations, Administration and Maintenance (OAM) protocol extension which uses data plane forwarding alone for forwarding echo replies on transit nodes.
 BFD for Multipoint Networks over Point-to-Multi-Point MPLS LSP
 
 draft-ietf-mpls-p2mp-bfd-07.txt
 Date: 02/03/2024
 Authors: Greg Mirsky, Gyan Mishra, Donald Eastlake
 Working Group: Multiprotocol Label Switching (mpls)
 This document describes procedures for using Bidirectional Forwarding Detection (BFD) for multipoint networks to detect data plane failures in Multiprotocol Label Switching (MPLS) point-to-multipoint (p2mp) Label Switched Paths (LSPs) and Segment Routing (SR) point-to- multipoint policies with SR-MPLS data plane. Furthermore, this document also updates RFC 8562 and recommends the use of an IPv6 loopback address (:::1/128) and discourages the use of an IPv4 loopback address mapped to IPv6. It also describes the applicability of LSP Ping, as in-band, and the control plane, as out-band, solutions to bootstrap a BFD session. It also describes the behavior of the active tail for head notification.
 Use Cases for MPLS Network Action Indicators and MPLS Ancillary Data
 
 draft-ietf-mpls-mna-usecases-04.txt
 Date: 10/02/2024
 Authors: Tarek Saad, Kiran Makhijani, Haoyu Song, Greg Mirsky
 Working Group: Multiprotocol Label Switching (mpls)
 This document presents a number of use cases that have a common need for encoding network action indicators and associated ancillary data inside MPLS packets. There has been significant recent interest in extending the MPLS data plane to carry such indicators and ancillary data to address a number of use cases that are described in this document. The use cases described in this document are not an exhaustive set, but rather the ones that are actively discussed by members of the IETF MPLS, PALS, and DetNet.
 Requirements for Solutions that Support MPLS Network Actions
 
 draft-ietf-mpls-mna-requirements-12.txt
 Date: 05/04/2024
 Authors: Matthew Bocci, Stewart Bryant, John Drake
 Working Group: Multiprotocol Label Switching (mpls)
 This document specifies requirements for the development of MPLS Network Actions which affect the forwarding or other processing of MPLS packets. These requirements are informed by a number of proposals for additions to the MPLS information in the labeled packet to allow such actions to be performed, either by a transit or terminating Label Switching Router (i.e., the Label Edge Router - LER).
 mLDP Extensions for Multi-Topology Routing
 
 draft-ietf-mpls-mldp-multi-topology-05.txt
 Date: 18/04/2024
 Authors: IJsbrand Wijnands, Mankamana Mishra, Syed Raza, Zhaohui Zhang, Arkadiy Gulko
 Working Group: Multiprotocol Label Switching (mpls)
 Multi-Topology Routing (MTR) is a technology to enable service differentiation within an IP network. Flexible Algorithm (FA) is another mechanism of creating a sub-topology within a topology using defined topology constraints and computation algorithm. In order to deploy mLDP (Multipoint label distribution protocol) in a network that supports MTR and/or FA, mLDP is required to become topology and FA aware. This document specifies extensions to mLDP to support MTR with FA such that when building a Multipoint LSPs(Label Switched Paths) it can follow a particular topology and algorithm.
 MPLS Network Actions (MNA) Framework
 
 draft-ietf-mpls-mna-fwk-07.txt
 Date: 05/04/2024
 Authors: Loa Andersson, Stewart Bryant, Matthew Bocci, Tony Li
 Working Group: Multiprotocol Label Switching (mpls)
 This document specifies an architectural framework for the MPLS Network Actions (MNA) technologies. MNA technologies are used to indicate actions for Label Switched Paths (LSPs) and/or MPLS packets and to transfer data needed for these actions. The 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. Some of these actions are defined in existing MPLS specifications, while others require extensions to existing specifications to meet the requirements found in "Requirements for MPLS Network Actions".
 A YANG Model for MPLS MSD
 
 draft-ietf-mpls-msd-yang-05.txt
 Date: 24/01/2024
 Authors: Yingzhen Qu, Acee Lindem, Stephane Litkowski, Jeff Tantsura
 Working Group: Multiprotocol Label Switching (mpls)
 This document defines a YANG data model augmenting the IETF MPLS YANG model to provide support for MPLS Maximum SID Depths (MSDs) as defined in RFC 8476 and RFC 8491.
 MPLS Network Action (MNA) Sub-Stack Solution
 
 draft-ietf-mpls-mna-hdr-04.txt
 Date: 21/10/2023
 Authors: Jaganbabu Rajamanickam, Rakesh Gandhi, Royi Zigler, Haoyu Song, Kireeti Kompella
 Working Group: Multiprotocol Label Switching (mpls)
 This document defines the MPLS Network Action (MNA) sub-stack solution for carrying Network Actions and Ancillary Data in the label stack. MPLS Network Actions can be used to influence packet forwarding decisions, carry additional OAM information in the MPLS packet, or perform user-defined operations. This document addresses the MNA requirements specified in draft-ietf-mpls-mna-requirements. This document follows the MNA framework specified in draft-ietf-mpls- mna-fwk.
 Deprecating the Use of Router Alert in LSP Ping
 
 draft-ietf-mpls-lspping-norao-08.txt
 Date: 01/03/2024
 Authors: Kireeti Kompella, Ron Bonica, Greg Mirsky
 Working Group: Multiprotocol Label Switching (mpls)
 The MPLS echo request and MPLS echo response messages, defined in RFC 8029 "Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures" (usually referred to as LSP ping messages), are encapsulated in IP whose headers include a Router Alert Option (RAO). In actual deployments, the RAO was neither required nor used. Furthermore, RFC 6398 identifies security vulnerabilities associated with the RAO in non-controlled environments, e.g., the case of using the MPLS echo request/reply as inter-area Operations, Administration, and Maintenance (OAM), and recommends against its use outside of controlled environments. Therefore, this document retires the RAO for MPLS OAM and updates RFC 8029 to remove the RAO from LSP ping message encapsulations. Furthermore, this document explains why RFC 7506 has been reclassified as Historic. Also, the use of an IPv6 loopback address (::1/128) as the IPv6 destination address for an MPLS echo request message is RECOMMENDED.
 IANA Registry for the First Nibble Following a Label Stack
 
 draft-ietf-mpls-1stnibble-04.txt
 Date: 29/02/2024
 Authors: Kireeti Kompella, Stewart Bryant, Matthew Bocci, Greg Mirsky, Loa Andersson, Jie Dong
 Working Group: Multiprotocol Label Switching (mpls)
 The goal of this memo is to create a new IANA registry (called the Post-stack First Nibble registry) for the first nibble (4-bit field) immediately following an MPLS label stack. The memo offers a rationale for such a registry, describes how the registry should be managed, and provides some initial entries. Furthermore, this memo sets out some documentation requirements for registering new values. Finally, it provides some recommendations that make processing MPLS packets easier and more robust. The relationship between the IANA IP Version Numbers (RFC 2780) and the Post-stack First Nibble registry is described in this document. This memo, if published, would update RFC 4928.
 Label Switched Path (LSP) Ping for Segment Routing (SR) Path Segment Identifiers (SIDs) with MPLS Data Planes
 
 draft-ietf-mpls-spring-lsp-ping-path-sid-00.txt
 Date: 18/03/2024
 Authors: Xiao Min, Shaofu Peng, Liyan Gong, Rakesh Gandhi, Carlos Pignataro
 Working Group: Multiprotocol Label Switching (mpls)
 Path Segment is a type of Segment Routing (SR) segment, which is used to identify an SR path. This document provides Target Forwarding Equivalence Class (FEC) Stack TLV definitions for Path Segment Identifiers.

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-07 Approved
Status update Show Changed 2018-11-10
Document dependencies
Additional resources Issue tracker, Wiki, Zulip Stream
Personnel Chairs Nicolai Leymann, 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 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
    BESS, BFD, CCAMP, OPSAWG, PALS, SPRING, and TEAS
    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.

Abandoned milestones

Date Milestone Associated documents
Abandoned Submit draft-ietf-mpls-seamless-mpls for publication draft-ietf-mpls-seamless-mpls

Done milestones

Date Milestone Associated documents
Done Submit draft-ietf-mpls-tp-linear-protection-mib draft-ietf-mpls-tp-linear-protection-mib
Done Submit draft-ietf-mpls-lsp-ping-lag-multipath for publication draft-ietf-mpls-lsp-ping-lag-multipath
Done Submit draft-ietf-mpls-tp-temporal-hitless-psm for publication draft-ietf-mpls-tp-temporal-hitless-psm
Done Submit draft-ietf-mpls-ldp-mrt for publication draft-ietf-mpls-ldp-mrt
Done ++ Progress draft-ietf-mpls-oam-ipv6-rao to publication draft-ietf-mpls-oam-ipv6-rao
Done ++ Progress draft-ietf-mpls-proxy-lsp-ping to publication draft-ietf-mpls-proxy-lsp-ping
Done ++ Progress draft-ietf-mpls-in-udp to publication draft-ietf-mpls-in-udp
Done Submit draft-ietf-mpls-entropy-lsp-ping for publication draft-ietf-mpls-entropy-lsp-ping
Done Submit draft-ietf-mpls-lsp-ping-mpls-tp-oam-conf for publication draft-ietf-mpls-lsp-ping-mpls-tp-oam-conf
Done Submit draft-ietf-mpls-lsp-ping-reply-mode-simple for publication draft-ietf-mpls-lsp-ping-reply-mode-simple
Done ++ Progress draft-ietf-mpls-ldp-ipv6 for publication to publication draft-ietf-mpls-ldp-ipv6
Done ++ Progress draft-ietf-mpls-seamless-mcast to publication draft-ietf-mpls-seamless-mcast
Done Submit draft-ietf-mpls-oam-ipv6-rao for publication
Done Submit draft-ietf-mpls-lsp-ping-registry for publication
Done Submit draft-ietf-mpls-lsp-ping-relay-reply for publication draft-ietf-mpls-lsp-ping-relay-reply
Done Submit draft-ietf-mpls-mldp-node-protection for publication draft-ietf-mpls-mldp-node-protection
Done Submit draft-ietf-mpls-rfc6374-udp-return-path for publicatiion draft-ietf-mpls-rfc6374-udp-return-path
Done ++ Progress draft-ietf-mpls-ldp-ip-pw-capability to publication
Done ++ Progress draft-ietf-mpls-lsp-ping-registry to publication
Done Submit draft-ietf-mpls-proxy-lsp-ping fpr publication
Done Submit draft-ietf-mpls-in-udp for publication
Done ** Progress draft-ietf-mpls-pim-sm-over-mldp to publication
Done Submit draft-ietf-mpls-tp-oam-id-mib for publication draft-ietf-mpls-tp-oam-id-mib
Done Submit draft-ietf-mpls-seamless-mcast for publication
Done Submit draft-ietf-mpls-ldp-ipv6 for publication
Done Submit draft-ietf-mpls-ldp-ip-pw-capability for publication
Done Submit draft-ietf-mpls-ipv6-only-gap for publication
Done Submit draft-ietf-mpls-p2mp-loose-path-reopt for publicatiion
Done Submit draft-ietf-mpls-tp-te-mib for publication
Done Submit draft-ietf-mpls-pim-sm-over-mldp
Done Submit draft-ietf-mpls-mldp-in-band-wildcard-encoding for publication
Done Submit draft-ietf-mpls-deprecate-bgp-entropy-label for publication
Done Submit draft-ietf-mpls-smp-requirements for publication
Done Submit draft-ietf-mpls-lsp-ping-ttl-tlv for publication
Done Submit draft-ietf-mpls-ldp-multi-topology for publication
Done Submit draft-ietf-mpls-ldp-applicability-label-adv for publication
Done Submit draft-ietf-mpls-psc-updates for publication
Done Submit draft-ietf-mpls-ldp-hello-crypto-auth for publication
Done Submit draft-ietf-mpls-extended-admin-group for publication
Done Submit draft-ietf-mpls-forwardig for publication
Done Submit draft-ietf-mpls-special-purpose-labels
Done Submit draft-ietf-mpls-moving-iana-registries for publication
Done draft-ietf-mpls-tp-psc-itu
Done Submit draft-ietf-mpls-tp-p2mp-framework for publication
Done Submit draft-ietf-mpls-mldp-hsmp for publication
Done Submit draft-ietf-mpls-tp-rosetta-stone for publication
Done Submit draft-ietf-mpls-return-path-specified-lsp-ping for publication
Done Submit draft-ietf-mpls-tp-mip-mep-map for publication
Done Submit draft-ietf-mpls-targeted-mldp for publication
Done Submit draft-ietf-mpls-ldp-dod for publication
Done Submit draft-ietf-mpls-retire-ach-tlv for publication
Done Submit draft-ietf-mpls-tp-ethernet-addressing for publication
Done Submit draft-ietf-mpls-gach-adv for publication
Done Submit draft-ietf-mpls-tp-ring-protection for publication
Done Submit draft-ietf-mpls-tp-use-cases-and-design for publication
Done Submit draft-ietf-mpls-tp-security-framework for publication
Done Submit draft-ietf-mpls-mldp-in-band-signaling for publication
Done Submit draft-ietf-mpls-ipv6-pw-lsp-ping for publication
Done Submit draft-ietf-mpls-tp-itu-t-identifiers for publication
Done Submit draft-ietf-mpls-entropy-label for publication
Done Submit draft-ietf-mpls-ldp-gtsm for publication
Done Submit requirements for point-to-multipoint extensions to LDP
Done Submit MPLS security framework for publication as an informational RFC
Done Submit LDP extensions for P2MP LSPs
Done Submit a specification on Soft Pre-emption of LSP Tunnels to the IESG for publication as a Proposed Standard
Done Submit EXP field clarification document to IESG as proposed standard
Done Submit point to multipoint TE MIB to IESG as proposed standard
Done Submit document(s) specifying protocol extensions, enhancements and mechanisms for setup of P2MP TE LSPs
Done Submit specification on LSR Self Test to the IESG for publication as a Proposed Standard
Done Submit a BCP on MPLS load sharing to the IESG
Done Submit an OAM Framework Document to the IESG for publication as an Informational RFC
Done Submit specification on LSP Ping to the IESG for publication as a Proposed Standard
Done Submit a document defining the scope, requirements, and issues to resolve for setup of P2MP TE LSPs (MPLS and GMPLS)
Done Submit a specification on Encapsulations to carry MPLS over IP and GRE to the IESG for as a Proposed Standard
Done Submit the Traffic Engineering Link MIB to the IESG for as a Proposed Standard
Done Submit Multiprotocol Label Switching (MPLS) Label Switching Router (LSR), Management Information Base to the IESG for publication as Proposed Standards
Done Submit Multiprotocol Label Switching (MPLS) Forward Equivalency Class-To-Next Hop Label Forwarding Entry Management Information Base to the IESG for publication as Proposed Standards
Done Specification for MPLS-specific recovery ready for advancement.
Done Submit Definitions of Managed Objects for MultoiProtocol Label Switching, Label Distribution Protocol (LDP) to the IESG for publication as Proposed Standards
Done Submit Multiprotocol Label Switching (MPLS) Traffic Engineering Management Information Base to the IESG for publication as Proposed Standards
Done Submit Multiprotocol Label Switching (MPLS) Management Overview to the IESG for publication as Proposed Standards
Done Submit Definitions of Textual Conventions for Multiprotocol Label Switching (MPLS) Management to the IESG for publication as Proposed Standards
Done LDP fault tolerance specification ready for advancement to Proposed Standard.
Done Framework for IP multicast over label-switched paths ready for advancement.
Done Submit documents from original MPLS effort to IESG

Moved To Teas milestones

Date Milestone Associated documents
Moved To Teas Submit draft-ietf-mpls-te-express-path draft-ietf-teas-te-express-path
draft-ietf-mpls-te-express-path