MPLS Working Group K. Raza, Ed. Internet-Draft Cisco Systems Intended status: Standards Track Expires: 20 May 2027 X. Liu Individual S. Easale Juniper Networks L. Andersson Huawei Technologies J. Tantsura Microsoft Corporation 16 November 2026 A YANG Data Model for MPLS mLDP draft-ietf-mpls-mldp-yang-17 Abstract This document specifies 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). Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on 20 May 2027. Copyright Notice Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved. Raza, et al. Expires 20 May 2027 [Page 1] Internet-Draft A YANG Model for MPLS mLDP November 2026 This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/ license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Base and Extended . . . . . . . . . . . . . . . . . . . . 3 2. Specification of Requirements . . . . . . . . . . . . . . . . 4 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.1. mLDP IANA Types . . . . . . . . . . . . . . . . . . . . . 5 3.2. mLDP Functionality . . . . . . . . . . . . . . . . . . . 5 3.2.1. Multipoint LSP FECs . . . . . . . . . . . . . . . . . 8 4. YANG Data Model (mLDP base and extended) . . . . . . . . . . 9 4.1. Configuration . . . . . . . . . . . . . . . . . . . . . . 9 4.1.1. High-level Hierarchy . . . . . . . . . . . . . . . . 9 4.1.2. Base Parameters . . . . . . . . . . . . . . . . . . . 10 4.1.3. Capabilities Parameters . . . . . . . . . . . . . . . 11 4.1.4. Forwarding Parameters . . . . . . . . . . . . . . . . 12 4.2. Operational State . . . . . . . . . . . . . . . . . . . . 12 4.2.1. Root State . . . . . . . . . . . . . . . . . . . . . 12 4.2.2. Bindings State . . . . . . . . . . . . . . . . . . . 14 4.2.3. Capabilities State . . . . . . . . . . . . . . . . . 17 4.3. Notifications . . . . . . . . . . . . . . . . . . . . . . 19 5. YANG Specification . . . . . . . . . . . . . . . . . . . . . 19 5.1. mLDP Opaque Value Element Basic Types . . . . . . . . . . 19 5.2. mLDP Opaque Value Element Extended Types . . . . . . . . 22 5.3. mLDP Status Value Element Types . . . . . . . . . . . . . 24 5.4. mLDP Base . . . . . . . . . . . . . . . . . . . . . . . . 26 5.5. mLDP Extended . . . . . . . . . . . . . . . . . . . . . . 36 6. Operational Considerations . . . . . . . . . . . . . . . . . 56 6.1. Migration path from LDP YANG (RFC 9070) . . . . . . . . . 56 6.2. Deployment and Feature Modularity . . . . . . . . . . . . 57 6.3. Telemetry, Monitoring, and State Synchronization . . . . 57 6.4. Scale, Churn, and Resource Management . . . . . . . . . . 57 6.5. Fault Handling, Diagnostics, and Notifications . . . . . 58 7. Security Considerations . . . . . . . . . . . . . . . . . . . 58 7.1. Writable Data Nodes . . . . . . . . . . . . . . . . . . . 59 7.2. Readable Data Nodes . . . . . . . . . . . . . . . . . . . 60 7.3. RPC and Action Operations . . . . . . . . . . . . . . . . 60 7.4. Notifications . . . . . . . . . . . . . . . . . . . . . . 61 7.5. IANA Types Modules . . . . . . . . . . . . . . . . . . . 61 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 61 Raza, et al. Expires 20 May 2027 [Page 2] Internet-Draft A YANG Model for MPLS mLDP November 2026 8.1. mLDP Opaque Value Element basic types . . . . . . . . . . 62 8.2. mLDP Opaque Value Element extended types . . . . . . . . 63 8.3. mLDP Status Value Element types . . . . . . . . . . . . . 64 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 65 9.1. Normative References . . . . . . . . . . . . . . . . . . 65 9.2. Informative References . . . . . . . . . . . . . . . . . 68 Appendix A. YANG Data Model: Complete tree . . . . . . . . . . . 69 Appendix B. Data Tree Example . . . . . . . . . . . . . . . . . 76 Appendix C. Acknowledgments . . . . . . . . . . . . . . . . . . 84 Appendix D. Contributors . . . . . . . . . . . . . . . . . . . . 84 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 85 1. Introduction This document specifies a YANG data model for the MPLS Multipoint Label Distribution Protocol (mLDP). The mLDP YANG data model being defined here is dependent on the LDP YANG data model [RFC9070]. This implies that an operator will need to use the LDP base YANG data model to configure and manage the control plane for mLDP. For example, an operator would enable LDP discovery on MPLS interface to establish LDP session for mLDP peering on which mLDP bindings could be exchanged. Similarly, an operator could query state information for an LDP peer to verify peering attributes, etc. Moreover, it is important to note here that any assumptions made in the LDP YANG data model [RFC9070] also hold true in this document, unless otherwise explicitly stated. Like its parent LDP data model, this mLDP model also defines the following constructs for managing the mLDP protocol: * Configuration * Operational State * Executables (Actions) * Notifications This document is organized to define the data model for each of the above constructs in the sequence as listed above. 1.1. Base and Extended Like the LDP model, the configuration and state items are divided into the following two broad categories: * Base Raza, et al. Expires 20 May 2027 [Page 3] Internet-Draft A YANG Model for MPLS mLDP November 2026 * Extended The "base" category contains the basic and fundamental functionality that is covered in the mLDP base specification [RFC6388] (and some important extensions like the targeted mLDP [RFC7060]) and constitute the minimum requirements for a typical base mLDP deployment, whereas the "extended" category contains all other non-base functionality. All the items in the base category are mandatory and, hence, no "if- feature" is allowed under the "base" category. The base and extended categories are defined in their own modules as described later. The examples of base mLDP functionality include the enablement of mLDP and its capabilities, and static configuration of leaf IPv4 LSPs with generic LSP Id, whereas the examples of extended mLDP functionality include enhanced mLDP capabilities, Recursive FEC [RFC6512], traffic protection [RFC7715] [RFC7431], static leaf IPv6 LSPs with generic LSP Id, and static leaf IPv4/IPv6 LSPs of other opaque types (transit, bidir). It is worth highlighting that any IPv6 related functionality support is categorized as an extended functionality. While "base" model support will suffice most deployments requiring base functionality only, it is expected that functionality-rich deployments will require both the "base" and "extended" model support from the vendors. The YANG modules in this document conform to the Network Management Datastore Architecture (NMDA) defined in [RFC8342]. The meaning of the symbols used in the YANG tree diagrams in this document are defined in [RFC8340]. 2. Specification of Requirements The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. In this document, the word "IP" is used to refer to both IPv4 and IPv6, unless otherwise explicitly stated. For example, "IP address family" should be read as "IPv4 and/or IPv6 address family". 3. Overview This document specifies following new YANG modules: Raza, et al. Expires 20 May 2027 [Page 4] Internet-Draft A YANG Model for MPLS mLDP November 2026 +=====================+==========================+=============+ | Name | Specification | IANA- | | | | maintained? | +=====================+==========================+=============+ | iana-ldp-mp-opaque- | LDP MP Opaque Value | Yes | | value-element- | Element basic types | | | basic-types | [IANA-LDP-MP-OPAQUE] | | +---------------------+--------------------------+-------------+ | iana-ldp-mp-opaque- | LDP MP Opaque Value | Yes | | value-element- | Element extended types | | | extended-types | [IANA-LDP-MP-OPAQUE-EXT] | | +---------------------+--------------------------+-------------+ | iana-ldp-mp-status- | LDP MP Status Value | Yes | | value-element-types | Element types | | | | [IANA-LDP-MP-STATUS] | | +---------------------+--------------------------+-------------+ | ietf-mpls-mldp | mLDP base functionality | No | +---------------------+--------------------------+-------------+ | ietf-mpls-mldp- | mLDP extended | No | | extended` | functionality | | +---------------------+--------------------------+-------------+ Table 1: YANG modules 3.1. mLDP IANA Types LDP IANA registry [IANA-LDP] maintains the following types for mLDP use * LDP MP Opaque Value Element basic types * LDP MP Opaque Value Element extended types * LDP MP Status Value Element types The mLDP YANG data model specifies the YANG modules corresponding to the above IANA types. The specified YANG modules specify the initial set of values and are IANA-maintained. The YANG modules are named "iana-ldp-mp-opaque-value-element-basic- types", "iana-ldp-mp-opaque-value-element-ext-types", and "iana- ldp-mp-status-value-element-types" accordingly. 3.2. mLDP Functionality Both mLDP base and extended modules augment the LDP module (/rt:routing/rt:control-plane-protocols/rt:control-plane- protocol/ ldp:mpls-ldp) as defined in [RFC9070] Raza, et al. Expires 20 May 2027 [Page 5] Internet-Draft A YANG Model for MPLS mLDP November 2026 The document defines mLDP configuration under (Section 4.1), operational state under (Section 4.2), and notifications under (Section 4.3). Currently, no RPCs for executing commands to perform some actions are defined in our mLDP modules. In mLDP YANG modules, the operational state follows the NMDA [RFC8342]. The following diagram depicts module augmentation and relationship flow between LDP and mLDP modules: +--------------------------------------------------------+ | ietf-routing (RFC 8349) | | /routing/control-plane-protocols | +---------------------------+----------------------------+ | | (Augmented by RFC 9070) v +--------------------------------------------------------+ | ietf-mpls-ldp (RFC 9070) | | .../control-plane-protocol/mpls-ldp | +---------------------------+----------------------------+ | | (Augmented with /mldp container) v +--------------------------------------------------------+ | ietf-mpls-mldp (Base) | | * Base P2MP capabilities, address-family config | | * Root, Upstream LSR, and FEC-Label bindings state | +---------------------------+----------------------------+ | | (Augmented with mldp-ext features) v +--------------------------------------------------------+ | ietf-mpls-mldp-extended (Ext) | | * MP2MP trees, Node Protection | | * MoFRR (Multicast-only Fast Reroute), Backup NHLFE | | * Recursive, Extended Opaque Value elements | +--------------------------------------------------------+ Figure 1: mLDP YANG Tree Organization Before going into data model details, following important points need to be noted: Raza, et al. Expires 20 May 2027 [Page 6] Internet-Draft A YANG Model for MPLS mLDP November 2026 * This model aims to address the core mLDP constructs, parameters, and functionality as per their IETF specifications, as well as well-known and widely deployed manageability controls (such as timers, delays etc.). * This model does not cover any applications or clients running on top of mLDP, nor does it cover any Operations, Administration, and Maintenance (OAM) procedures for mLDP. * This mLDP model builds on top of LDP YANG data model [RFC9070] which is a VRF-centric model. A "network-instance", as defined in [RFC8529], refers to a VRF instance (both default and non-default) within the scope of this model. * This model supports two address families, namely, "ipv4" and "ipv6". The mLDP areas and functionality that are within the scope of this modeling effort are as follows: * Base functionality: - mLDP Base Specification [RFC6388] - Targeted mLDP [RFC7060] - Static LSPs at Leaf node (manually provisioned) * Extended functionality: - mLDP Recursive FEC [RFC6512] - mLDP Fast-Reroute (FRR): o Node Protection [RFC7715] o Multicast-only [RFC7431] - Hub-and-Spoke Multipoint LSPs [RFC7140] - In-band Signaling: o mLDP In-band Signaling [RFC6826] o mLDP In-band signaling in a VRF [RFC7246] o mLDP In-band Signaling with Wildcards [RFC7438] Raza, et al. Expires 20 May 2027 [Page 7] Internet-Draft A YANG Model for MPLS mLDP November 2026 3.2.1. Multipoint LSP FECs A Multipoint LSP is associated with a FEC which is represented as (root-address, opaque-element) tuple. We can categorize the opaque types into following four base categories: * Generic LSP Identifier * Transit Source * Transit Bidir * Recursive Furthermore, there are VPN variants that can be applied on top of the base categories. The following table lists various type of opaque elements with their keys, as later used in the configuration and state model: +=============+=============+=====================+===========+ | Opaque Type | Variant | Opaque specific Key | RFCs | +=============+=============+=====================+===========+ | Generic LSP | Base | LSP Id | [RFC6388] | | Identifier | | | | +-------------+-------------+---------------------+-----------+ | Transit | Base (IPv4/ | Source, Group | [RFC6826] | | Source | IPv6) | | | | +-------------+---------------------+-----------+ | | VPN | Source, Group, RD | [RFC7246] | +-------------+-------------+---------------------+-----------+ | Transit | Base (IPv4/ | Masklen, RP, Group | [RFC6826] | | Bidir | IPv6) | | | | +-------------+---------------------+-----------+ | | VPN | Masklen, RP, Group, | [RFC7246] | | | | RD | | +-------------+-------------+---------------------+-----------+ | Recursive | Base | Opaque Value | [RFC6512] | | | | Element Octets | | | +-------------+---------------------+-----------+ | | VPN | RD, Opaque Value | [RFC6512] | | | | Element Octets | | +-------------+-------------+---------------------+-----------+ Table 2: Opaque Types and Keys Raza, et al. Expires 20 May 2027 [Page 8] Internet-Draft A YANG Model for MPLS mLDP November 2026 It is to be noted that key for an MP LSP is a combination of the FEC's "root address" and FEC opaque value element specific keys (as listed above) The "base" data model includes only the "Generic LSP Identifier" opaque type (for ipv4), while rest of the above types are covered by the "extended" model. 4. YANG Data Model (mLDP base and extended) The YANG specification for mLDP base and extended modules is captured in Section 5. A complete simplified graphical tree representation of the same is presented in Appendix A (Figure 14). While presenting the YANG tree view and actual specification, this document assumes readers are familiar with the concepts of YANG data modeling, its presentation and its compilation. 4.1. Configuration This specification defines the parameters for configuring the base and extended mLDP functionality. As stated earlier, mLDP configuration items augment relevant LDP configuration hierarchy. 4.1.1. High-level Hierarchy The following presents a high-level view of configuration hierarchy for mLDP with respect to LDP: Raza, et al. Expires 20 May 2027 [Page 9] Internet-Draft A YANG Model for MPLS mLDP November 2026 augment /rt:routing/rt:control-plane-protocols/ rt:control-plane-protocol: +-- mpls-ldp +-- global +-- ... +-- mldp | +-- ... | +-- address-families | +-- ipv4 (similar tree for ipv6) | | +-- roots | | +-- root [addr] | | +-- bindings (state) | | +-- ... | ... | | +-- ... +-- capability | +-- mldp | +-- ... | +-- mldp-ext: ... | +-- ... +-- forwarding-nexthop +--- interfaces +--- interface* [name] +--- mldp-ext: ... Figure 2: Configuration Hierarchy The above hierarchy illustrates that mLDP configuration parameters are distributed amongst the following three sections: * mldp base functionality * mldp capabilities * mldp forwarding The following subsections describe the above mLDP sub-tree along with their configuration items. 4.1.2. Base Parameters mldp container falls directly under mpls-ldp:global and holds the configuration related to items that are mLDP specific. The main items under this container are: Raza, et al. Expires 20 May 2027 [Page 10] Internet-Draft A YANG Model for MPLS mLDP November 2026 * mLDP enablement: To enable mLDP under a (VRF) routing instance, mldp is enabled in the mldp container under LDP. It is to remind that the LDP modules reside under a network-instance and the scope of any configuration defined under this tree is network-instance (VRF) scoped. Given that mLDP requires LDP signaling, it is not sensible to allow disabling the LDP control plane under a network- instance while requiring mLDP to be enabled for the same. However, if a user wants to only allow signaling for multipoint FECs on an LDP/mLDP enabled VRF instance, he/she can use LDP label-policies to disable unicast FECs under the VRF. Alternatively, the same can be achieved by advertising the capabilities and the procedures defined in [RFC7473]. * Per address-family mLDP functionality: mLDP manages its own list of IP address-families and the functionality enabled underneath. The per-AF mLDP configuration items include: - Multicast-only FRR: This enables Multicast-only FRR functionality for a given AF under mLDP. The functionality allows route-policy to be configured for finer control/ applicability. - Recursive FEC: The recursive-fec functionality [RFC6512] can be enabled per-AF with a route-policy. - Configured Leaf LSPs: To provision multipoint leaf LSPs manually, a per-AF container is provided under LDP. The configuration is flexible and allows a user to specify MP LSPs of type p2mp or mp2mp with IPv4 or IPv6 root address(es) by using either LSP-Id or (S,G). Targeted mLDP specification [RFC7060] does not require any mLDP specific configuration. It, however, requires LDP upstream-label- assignment capability [RFC6389] to be enabled. 4.1.3. Capabilities Parameters mldp capabilities are enabled under mldp specific container under ldp:global:capability container. In the scope of this document, the most important capabilities related to mLDP are p2mp, mp2mp, make- before-break, hub-and-spoke, and node-protection. It is worth reminding that mLDP requires LDP discovery and peer procedures to form mLDP peering but a peer is considered as an mLDP peer only when either p2mp or mp2mp capabilities have been successfully exchanged with the peer. Raza, et al. Expires 20 May 2027 [Page 11] Internet-Draft A YANG Model for MPLS mLDP November 2026 4.1.4. Forwarding Parameters The container ldp:global:forwarding-nexthop is used to hold configuration to controlling LDP/mLDP forwarding behavior. One example of a such a configuration is to allow a user in disabling the use of LDP interface(s) as an mLDP forwarding egress interface for MP LSPs(s). This example configuration makes sense only when there are more than one interface available for the selection. 4.2. Operational State The following are the main areas for which mLDP operational state is defined: * Root * Bindings (FEC-label) * Capabilities 4.2.1. Root State The root address is a fundamental construct for MP FEC bindings and LSPs. The root state provides information on all the known roots in a given address-family and their root reachability information (as learnt from RIB). In case of multi-path reachability to a root, the selection of the upstream path is done on per-LSP basis at the time of LSP setup. Similarly, when protection mechanisms like Make- before-break (MBB) or Multicast-only FRR (MoFRR) are in place, the path designation as active/standby or primary/backup is also done on per-LSP basis. It should be noted that a given root can be shared amongst multiple P2MP and/or MP2MP LSPs. Moreover, an LSP can be signaled to more than one root for Root Node Redundancy (RNR) purposes. The following example illustrates a root database on a branch/transit LSR: Raza, et al. Expires 20 May 2027 [Page 12] Internet-Draft A YANG Model for MPLS mLDP November 2026 root 203.0.113.1: path1: RIB: GigEthernet 1/0, 198.51.100.1; LDP: peer 192.0.2.1:0 path2: RIB: GigEthernet 2/0, 198.51.100.16; LDP: peer 192.0.2.2:0 root 203.0.113.2: path1: RIB: 198.51.100.100; (NOTE: recursive path) LDP: peer 192.0.2.100:0 (NOTE: T-mLDP peer) root 2001:db8:0:9::1: path1: RIB: GigEthernet 1/0, 2001:db8:0:1::1 LDP: peer 192.0.2.1:0 root . . . . Figure 3: Example Root database A root entry on a root LSR itself will be presented as follows: root 203.0.113.10: is-self root 2001:db8:0:9::1: is-self Figure 4: Example Root entry on a Root node The following diagram captures the high-level tree hierarchy for state of an mLDP root The tree is shown for ipv4 roots only; a similar tree exists for ipv6 roots as well. Raza, et al. Expires 20 May 2027 [Page 13] Internet-Draft A YANG Model for MPLS mLDP November 2026 augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/ldp:mpls-ldp/ldp:global: +--rw mldp +--rw enabled? boolean +--rw address-families +--rw ipv4! +--ro roots +--ro root* [root-address] +--ro root-address inet:ipv4-address +--ro is-self? boolean +--ro reachability* [address interface] +--ro address inet:ipv4-address +--ro interface if:interface-ref +--ro peer? leafref Figure 5: Root state tree (ipv4) 4.2.2. Bindings State Binding state provides information on mLDP FEC-label bindings for both the P2MP and MP2MP FEC types. The state includes both the inbound (received) and the outbound (advertised) bindings. Like LDP, the state of FEC-label binding is presented per address-family in a FEC-centric view per address-family. An mLDP FEC is presented as (root-address, opaque-value-element) tuple as described earlier in Section 3, along with its direction (upstream or downstream) as picked with respect to the root reachability. The role of a given peer binding is also provided in case of MBB (as active or standby) and/or MoFRR (as primary or backup). The following example illustrates a FEC-label binding database on a branch/transit LSR for both P2MP and MP2MP FECs of Transit Source type: Transit IPv4 Source: FEC (root 203.0.113.1, S=198.51.100.1, G=224.1.1.1): type: p2mp upstream: advertised: peer 192.0.2.1:0, label 16000 (local) downstream: received: peer 192.0.2.2:0, label 17000 (remote) peer 192.0.2.3:0, label 18000 (remote) Raza, et al. Expires 20 May 2027 [Page 14] Internet-Draft A YANG Model for MPLS mLDP November 2026 FEC (root 203.0.113.1, S=198.51.100.2, G=224.1.1.1): type: mp2mp upstream: advertised: peer 192.0.2.1:0, label 26000 (local) received: peer 192.0.2.1:0, label 27000 (remote) downstream: advertised: peer 192.0.2.2:0, label 26001 (local), MBB role=active peer 192.0.2.3:0, label 26002 (local), MBB role=standby received: peer 192.0.2.2:0, label 27001 (remote) peer 192.0.2.3:0, label 28001 (remote) Transit IPv6 Source: FEC (root 203.0.113.1, S=2001:db8:0:9::1, G=ff39:1::1): type: p2mp upstream: advertised: peer 192.0.2.1:0, label 16100 (local) downstream: received: peer 192.0.2.2:0, label 17100 (remote) peer 192.0.2.3:0, label 18100 (remote) FEC (root 203.0.113.1, S=2001:db8:0:9::2, G=ff39:1::1): type: mp2mp upstream: advertised: peer 192.0.2.1:0, label 26100 (local) received: peer 192.0.2.1:0, label 27100 (remote) downstream: advertised: peer 192.0.2.2:0, label 26101 (local), MBB role=active peer 192.0.2.3:0, label 26102 (local), MBB role=standby received: peer 192.0.2.2:0, label 27101 (remote) peer 192.0.2.3:0, label 28101 (remote) Figure 6: Example Binding database Raza, et al. Expires 20 May 2027 [Page 15] Internet-Draft A YANG Model for MPLS mLDP November 2026 The following captures the high-level tree hierarchy for mLDP bindings state. The tree snippet shown below corresponds to "Transit source" type FEC-label binding with ipv4 root; The bindings for other types and other address-families follow the same hierarchy with type specific FEC-label key. augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/ldp:mpls-ldp/ldp:global: +--rw mldp +--rw address-families +--rw ipv4! +--ro roots +--ro root* [root-address] +--ro root-address inet:ipv4-address +--ro bindings +--ro mldp-ext:opaque-value-element-transit-source +--ro mldp-ext:fec-label* [source-address group-address rd] +--ro mldp-ext:source-address | inet:ipv4-address +--ro mldp-ext:group-address | inet:ipv4-address +--ro mldp-ext:rd | rt-types:route-distinguisher +--ro mldp-ext:multipoint-type? | mldp:multipoint-type +--ro mldp-ext:opaque-value-element-type? | identityref +--ro mldp-ext:peer* [direction peer advertisement-type] +--ro mldp-ext:peer | leafref +--ro mldp-ext:direction | ldp:downstream-upstream +--ro mldp-ext:advertisement-type | ldp:advertised-received +--ro mldp-ext:label? | rt-types:mpls-label +--ro mldp-ext:mbb-status? | lsp-mbb-role +--ro mldp-ext:mofrr-status? lsp-mofrr-role Figure 7: Binding state tree (transit-source-v4 with ipv4 root) Raza, et al. Expires 20 May 2027 [Page 16] Internet-Draft A YANG Model for MPLS mLDP November 2026 mLDP binding state is organized and presented per root address; hence, the bindings container is under a root node in the module. The bindings state is made available for FECs pertaining to different types of opaque elements, with some state available under the "base" tree and the rest under the "extended" tree. In the above tree, the various opaque types along with their type specific key(s) refer to the Table 2 as captured earlier in the document. For example, if the opaque type is a Generic LSP Identifier, then the type-specific-key will be a uint32 LSP-Id key. Please see the complete modules for all other types. It is worth highlighting that the address-family ipv4/ipv6 applies to "root" address in the mLDP binding tree. The other addresses (source, group, Rendezvous-Point (RP) etc.) do not have to be of the same address family type as the root. 4.2.2.1. Recursive FEC The binding state for an MP LSP with recursive opaque value element applies only at a backbone node for MP LSP that is set up over a BGP- free backbone. In this scenario, the backbone node needs to maintain the binding state for a "recursive" FEC, where the root address is the recursive root and the opaque value element encodes the original FEC. It is to be noted that the original FEC relates to LSP's original root and opaque type (such as lspid, transit-source, transit-bidir, etc.). The backbone node does not interpret the fields of the original FEC; instead, the node treats it as a opaque binary stream for keying, storage, and display purposes. 4.2.3. Capabilities State Like LDP, mLDP capabilities state comprises two types of information: * global: augments ldp:global/ldp:capability * per-peer: augments ldp:peers/ldp:peer/ldp:capability The following tree captures the high-level tree hierarchy for mLDP capabilities state. Raza, et al. Expires 20 May 2027 [Page 17] Internet-Draft A YANG Model for MPLS mLDP November 2026 +--rw mpls-ldp +--rw global | +--rw capability | | +--rw mldp:mldp | | +--rw mldp:p2mp | | | +--rw mldp:enabled? boolean | | +--rw mldp:mp2mp | | | +--rw mldp:enabled? boolean | | +--rw mldp:make-before-break | | | +--rw mldp:enabled? boolean | | | +--rw mldp:switchover-delay? uint16 | | | +--rw mldp:timeout? uint16 | | +--rw mldp-ext:hub-and-spoke {capability-mldp-hsmp}? | | | +--rw mldp-ext:enabled? boolean | | +--rw mldp-ext:node-protection | | {capability-mldp-node-protection}? | | +--rw mldp-ext:plr? boolean | | +--rw mldp-ext:merge-point | | +--rw mldp-ext:enabled? boolean | | +--rw mldp-ext:targeted-session-teardown-delay? | | uint16 | . . . | . . . +--rw peers +--rw peer* [lsr-id label-space-id] +--rw lsr-id rt-types:router-id +--rw label-space-id uint16 +--rw address-families +--ro received-peer-state +--ro capability +--ro mldp:mldp +--ro mldp:p2mp | +--ro mldp:is-capable? boolean +--ro mldp:mp2mp | +--ro mldp:is-capable? boolean +--ro mldp:make-before-break | +--ro mldp:is-capable? boolean +--ro mldp-ext:hub-and-spoke | +--ro mldp-ext:is-capable? boolean +--ro mldp-ext:node-protection +--ro mldp-ext:is-plr-capable? boolean +--ro mldp-ext:is-merge-point-capable? boolean Figure 8: Capabilities state tree Raza, et al. Expires 20 May 2027 [Page 18] Internet-Draft A YANG Model for MPLS mLDP November 2026 4.3. Notifications The mLDP notification consists of notifications related to changes in the operational state of an mLDP FEC. The "base" mLDP module includes only the "Generic LSP Identifier" opaque FEC type (for ipv4), while rest of the FEC types are covered by the "extended" mLDP module. A simplified graphical representation of mLDP notifications is illustrated in Appendix A (Figure 14). 5. YANG Specification The following sections specify the actual YANG (module) specification for mLDP types and constructs defined earlier in the document. 5.1. mLDP Opaque Value Element Basic Types The initial version of the "iana-ldp-mp-opaque-value-element-basic- types" YANG module matches the "LDP MP Opaque Value Element basic type" [IANA-LDP-MP-OPAQUE] registry. This module references [RFC6388], [RFC6826], [RFC6512], [RFC7246], [RFC7442], and [RFC8338]. file "iana-ldp-mp-opaque-value-element-basic-types@2026-11-16.yang" // RFC Editor: replace the above date with the date of // publication and remove this note. module iana-ldp-mp-opaque-value-element-basic-types { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:" + "iana-ldp-mp-opaque-value-element-basic-types"; prefix iana-mldp-opaque-element-basic-types; organization "IANA"; contact "Internet Assigned Numbers Authority Postal: ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 United States of America Tel: +1 310 301 5800 "; description Raza, et al. Expires 20 May 2027 [Page 19] Internet-Draft A YANG Model for MPLS mLDP November 2026 "This module contains a collection of IANA-maintained YANG data types as defined in 'LDP MP Opaque Value Element basic type' IANA registry. This module is available from the IANA YANG Parameters registry (https://www.iana.org/assignments/yang-parameters). Copyright (c) 2026 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Revised BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXX; see the RFC itself for full legal notices."; // RFC editor: Please replace XXX with this document RFC number revision 2026-11-16 { description "First revision."; reference "RFC XXX: A YANG Data Model for MPLS mLDP."; } // RFC editor: Please replace XXX with this document RFC number identity iana-ldp-mp-opaque-value-element-basic-type { description "Base identity for LDP MP Opaque Value Element basic type."; reference "LDP Parameters IANA registry for LDP MP Opaque Value Element basic type"; } identity lspid { base iana-ldp-mp-opaque-value-element-basic-type; description "Generic LSP identifier type"; reference "RFC 6388"; } identity transit-source-v4 { base iana-ldp-mp-opaque-value-element-basic-type; description "Transit IPv4 Source TLV type"; reference "RFC 6826"; } Raza, et al. Expires 20 May 2027 [Page 20] Internet-Draft A YANG Model for MPLS mLDP November 2026 identity transit-source-v6 { base iana-ldp-mp-opaque-value-element-basic-type; description "Transit IPv6 Source TLV type"; reference "RFC 6826"; } identity transit-bidir-v4 { base iana-ldp-mp-opaque-value-element-basic-type; description "Transit IPv4 Bidir TLV type"; reference "RFC 6826"; } identity transit-bidir-v6 { base iana-ldp-mp-opaque-value-element-basic-type; description "Transit IPv6 Bidir TLV type"; reference "RFC 6826"; } identity recur-opaque { base iana-ldp-mp-opaque-value-element-basic-type; description "Recursive Opaque value"; reference "RFC 6512"; } identity recur-opaque-vpn { base iana-ldp-mp-opaque-value-element-basic-type; description "VPN-Recursive Opaque value"; reference "RFC 6512"; } identity transit-bidir-vpnv4 { base iana-ldp-mp-opaque-value-element-basic-type; description "Transit VPNv4 Bidir TLV type"; reference "RFC 7246"; } identity transit-bidir-vpnv6 { base iana-ldp-mp-opaque-value-element-basic-type; description "Transit VPNv6 Bidir TLV type"; reference "RFC 7246"; } identity transit-shared-v4 { base iana-ldp-mp-opaque-value-element-basic-type; description "Transit IPv4 Shared Tree TLV"; reference "RFC 7442"; } Raza, et al. Expires 20 May 2027 [Page 21] Internet-Draft A YANG Model for MPLS mLDP November 2026 identity transit-shared-v6 { base iana-ldp-mp-opaque-value-element-basic-type; description "Transit IPv6 Shared Tree TLV"; reference "RFC 7442"; } identity l2vpn-mcast-app { base iana-ldp-mp-opaque-value-element-basic-type; description "L2VPN-MCAST application TLV"; reference "RFC 8338"; } identity transit-source-vpnv4 { base iana-ldp-mp-opaque-value-element-basic-type; description "Transit VPNv4 Source TLV type"; reference "RFC 7246"; } identity transit-source-vpnv6 { base iana-ldp-mp-opaque-value-element-basic-type; description "Transit VPNv6 Source TLV type"; reference "RFC 7246"; } identity extended-type-is-present { base iana-ldp-mp-opaque-value-element-basic-type; description "Extended Type field is present in the following two bytes"; reference "RFC 6388"; } } // module Figure 9: module 5.2. mLDP Opaque Value Element Extended Types Currently, IANA's LDP MP Opaque Value Element extended type reigstry [IANA-LDP-MP-OPAQUE-EXT] does not specify any registered value. Hence, the initial version of the "iana-ldp-mp-opaque-value-element- extended-types" YANG module matches IANA and only defines the base identify. This module does not reference any RFC. Raza, et al. Expires 20 May 2027 [Page 22] Internet-Draft A YANG Model for MPLS mLDP November 2026 file "iana-ldp-mp-opaque-value-element-ext-types@2026-11-16.yang" // RFC Editor: replace the above date with the date of // publication and remove this note. module iana-ldp-mp-opaque-value-element-ext-types { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:" + "iana-ldp-mp-opaque-value-element-ext-types"; prefix iana-mldp-opaque-element-ext-types; organization "IANA"; contact "Internet Assigned Numbers Authority Postal: ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 United States of America Tel: +1 310 301 5800 "; description "This module contains a collection of IANA-maintained YANG data types as defined in 'LDP MP Opaque Value Element extended type' IANA registry. This module is available from the IANA YANG Parameters registry (https://www.iana.org/assignments/yang-parameters). Copyright (c) 2026 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Revised BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXX; see the RFC itself for full legal notices."; // RFC editor: Please replace XXX with this document RFC number revision 2026-11-16 { description "First revision."; reference "RFC XXX: A YANG Data Model for MPLS mLDP."; Raza, et al. Expires 20 May 2027 [Page 23] Internet-Draft A YANG Model for MPLS mLDP November 2026 } // RFC editor: Please replace XXX with this document RFC number identity iana-ldp-mp-opaque-value-element-ext-type { description "Base identity for LDP MP Opaque Value Element extended type."; reference "LDP Parameters IANA registry for LDP MP Opaque Value Element extended type"; } // No child identities define at this time. } // module Figure 10: module 5.3. mLDP Status Value Element Types The initial version of the "iana-ldp-mp-status-value-element-types" YANG module matches the "LDP MP Status Value Element type" [IANA-LDP-MP-STATUS] registry. This module references [RFC6388] and [RFC7715]. file "iana-ldp-mp-status-value-element-types@2026-11-16.yang" // RFC Editor: replace the above date with the date of // publication and remove this note. module iana-ldp-mp-status-value-element-types { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:" + "iana-ldp-mp-status-value-element-types"; prefix iana-mldp-status-value-element-types; organization "IANA"; contact "Internet Assigned Numbers Authority Postal: ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 United States of America Tel: +1 310 301 5800 "; description Raza, et al. Expires 20 May 2027 [Page 24] Internet-Draft A YANG Model for MPLS mLDP November 2026 "This module contains a collection of IANA-maintained YANG data types as defined in 'LDP MP Status Value Element type' IANA registry. This module is available from the IANA YANG Parameters registry (https://www.iana.org/assignments/yang-parameters). Copyright (c) 2026 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Revised BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXX; see the RFC itself for full legal notices."; // RFC editor: Please replace XXX with this document RFC number revision 2026-11-16 { description "First revision."; reference "RFC XXX: A YANG Data Model for MPLS mLDP."; } // RFC editor: Please replace XXX with this document RFC number identity iana-ldp-mp-status-value-element-type { description "Base identity for LDP MP Status Value Element type."; reference "LDP Parameters IANA registry for LDP MP Status Value Element type"; } identity mbb-status { base iana-ldp-mp-status-value-element-type; description "MBB Status"; reference "RFC 6388"; } identity plr-status { base iana-ldp-mp-status-value-element-type; description "PLR Status Value Element"; reference "RFC 7715"; } Raza, et al. Expires 20 May 2027 [Page 25] Internet-Draft A YANG Model for MPLS mLDP November 2026 identity protected-node-status { base iana-ldp-mp-status-value-element-type; description "Protected Node Status Value Element"; reference "RFC 7715"; } } // module Figure 11: module 5.4. mLDP Base This YANG module imports types defined in [RFC9911], [RFC8343], [RFC8349], [RFC9070], and [RFC8294]. file "ietf-mpls-mldp@2026-11-16.yang" // RFC Editor: replace the above date with the date of // publication and remove this note. module ietf-mpls-mldp { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-mldp"; prefix "mldp"; import ietf-inet-types { prefix "inet"; reference "RFC 9911: Common YANG Data Types"; } import ietf-interfaces { prefix "if"; reference "RFC 8343: A YANG Data Model for Interface Management"; } import ietf-mpls-ldp { prefix "ldp"; reference "RFC 9070: YANG Data Model for MPLS LDP"; } import ietf-routing { prefix "rt"; reference "RFC 8349: A YANG Data Model for Routing Management (NMDA version)"; } Raza, et al. Expires 20 May 2027 [Page 26] Internet-Draft A YANG Model for MPLS mLDP November 2026 import ietf-routing-types { prefix "rt-types"; reference "RFC 8294: Common YANG Data Types for the Routing Area"; } import iana-ldp-mp-opaque-value-element-basic-types { prefix "iana-mldp-opaque"; reference "RFC XXX: XXXX"; // RFC editor: replace XXX with the RFC number of this document } organization "IETF MPLS Working Group"; contact "WG Web: WG List: Editor: Kamran Raza Editor: Xufeng Liu Editor: Santosh Easale Editor: Loa Andersson Editor: Jeff Tantsura "; description "This YANG module defines the essential components for the management of Multiprotocol Label Switching (MPLS) Multipoint LDP (mLDP). The types and groupings defined in this module are intended exclusively for use within this module itself or any other module that augments this module. This module is available from the IANA YANG Parameters registry (https://www.iana.org/assignments/yang-parameters). Copyright (c) 2026 IETF Trust and the persons identified as authors of the code. All rights reserved. Raza, et al. Expires 20 May 2027 [Page 27] Internet-Draft A YANG Model for MPLS mLDP November 2026 Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Revised BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; // RFC Ed: replace 'date-revision' with the module publication date // the format is (YYYY-MM-DD) // replace XXXX with actual RFC number and remove // this note revision 2026-11-16 { description "Initial revision."; reference "RFC XXXX: A YANG Data Model for MPLS mLDP."; // RFC Editor: replace XXXX with actual RFC number and remove // this note } /* * Typedefs */ typedef multipoint-type { type enumeration { enum p2mp { description "Point to multipoint"; } enum mp2mp { description "Multipoint to multipoint"; } } description "The type of a multipoint LSP: either Point to multipoint (p2mp) or Multipoint to multipoint (mp2mp)"; } typedef lsp-mbb-role { type enumeration { enum none { description "Make-before-break (MBB) is not enabled."; } enum active { Raza, et al. Expires 20 May 2027 [Page 28] Internet-Draft A YANG Model for MPLS mLDP November 2026 description "This LSP is active."; } enum inactive { description "This LSP is inactive."; } } description "This type represents the Make-before-break role of an LSP."; } /* * Groupings */ grouping mldp-capabilities-base { description "A grouping describing the protocol capabilities of mLDP"; reference "RFC6388: Label Distribution Protocol Extensions for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths."; container p2mp { description "Configuration and state information for the point-to-multipoint capability"; leaf enabled { type boolean; description "Enables the point-to-multipoint capability when set to 'true'."; } } container mp2mp { description "Configuration and state information for the multipoint-to-multipoint capability"; leaf enabled { type boolean; description "Enables the multipoint-to-multipoint capability when set to 'true'."; } } container make-before-break { description "Configuration and state information for the make-before-break capability."; Raza, et al. Expires 20 May 2027 [Page 29] Internet-Draft A YANG Model for MPLS mLDP November 2026 leaf enabled { type boolean; description "Enables the make-before-break capability when set to 'true'."; } leaf switchover-delay { type uint16; units seconds; description "Switchover delay (in seconds) for activating an inactive element"; } leaf timeout { type uint16; units seconds; description "To prevent waiting indefinitely for the MBB Notification to arrive, a timeout should be applied. As soon as the timer expires, the MBB procedures, same as those applied at the receipt of an MBB notification, are applied on the inactive element."; } } } // mldp-capabilities-base grouping mldp-binding-label-peer-state-attributes { description "mLDP label binding per peer attributes"; leaf direction { type ldp:downstream-upstream; description "Downstream or upstream label binding"; } leaf advertisement-type { type ldp:advertised-received; description "Advertised (outbound) or received label (inbound) binding"; } leaf label { type rt-types:mpls-label; description "Advertised (outbound) or received (inbound) label"; } leaf mbb-status { when "../direction = 'upstream'" { description "This leaf is used for MBB upstream direction only."; Raza, et al. Expires 20 May 2027 [Page 30] Internet-Draft A YANG Model for MPLS mLDP November 2026 } type lsp-mbb-role; description "The MBB status of this LSP"; } } // mldp-binding-label-peer-state-attributes grouping mldp-binding-label-state-attributes { description "mLDP label binding attributes"; list peer { key "direction peer advertisement-type"; description "List of peers with bindings exchanged (sent and/or received)"; leaf peer { type leafref { path "../../../../../../../../../../../ldp:peers/ldp:peer/" + "ldp:lsr-id"; } description "[m]LDP peer from which this binding is received, or to which this binding is advertised. The referenced node is an item in the peer list of mpls-ldp, with the hierarchy mpls-ldp/peers/peer/lsr-id, in the configuration plus state data datastore."; } uses mldp-binding-label-peer-state-attributes; } // peer } // mldp-binding-label-state-attributes /* * Configuration data and operational state data nodes */ augment "/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:global/" + "ldp:capability" { description "Augmentation for mLDP global capability"; container mldp { description "This container contains the configuration and state information for multipoint LDP capabilities."; uses mldp-capabilities-base; } } /* Raza, et al. Expires 20 May 2027 [Page 31] Internet-Draft A YANG Model for MPLS mLDP November 2026 * Operational state data nodes */ augment "/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:peers/ldp:peer/" + "ldp:received-peer-state/ldp:capability" { description "Augmentation for mLDP received peer state capability"; container mldp { description "Operational state information for the protocol capabilities of mLDP peer"; container p2mp { description "Operational state information for the point-to-multipoint capability of a peer"; leaf is-capable { type boolean; description "Set to 'true' when point-to-multipoint capability is received from peer"; } } container mp2mp { description "Operational state information for the multipoint-to-multipoint capability of a peer"; leaf is-capable { type boolean; description "Set to 'true' when multipoint-to-multipoint capability is received from peer"; } } container make-before-break { description "Operational state information for the make-before-break capability of a peer"; leaf is-capable { type boolean; description "Set to 'true' when make-before-break capability is received from peer"; } } } // mldp } Raza, et al. Expires 20 May 2027 [Page 32] Internet-Draft A YANG Model for MPLS mLDP November 2026 /* * Global augmentation */ augment "/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:global" { description "mLDP global augmentation."; container mldp { description "mLDP attributes at per instance level. Defining attributes here does not enable any MP capabilities. MP capabilities need to be explicitly enabled under capability container"; leaf enabled { type boolean; description "Enables the mLDP protocol when set to 'true'."; } container address-families { description "Per-address-family configuration and operational state. The address family can be either IPv4 or IPv6."; container ipv4 { presence "Enables IPv4 mLDP support unless the 'enabled' leaf is set to 'false'."; description "Containing data related to the IPv4 address family."; leaf enabled { type boolean; default "true"; description "Disables the IPv4 address family when set to 'false'."; } container roots { config false; description "IPv4 multicast LSP roots"; list root { key "root-address"; description "List of roots for configured multicast LSPs"; leaf root-address { type inet:ipv4-address; Raza, et al. Expires 20 May 2027 [Page 33] Internet-Draft A YANG Model for MPLS mLDP November 2026 description "Root address."; } leaf is-self { type boolean; description "Set to 'true' when the node itself is the root node"; } list reachability { key "address interface"; description "Root reachability information in form of a next-hop"; leaf address { type inet:ipv4-address; description "The next-hop address to reach root"; } leaf interface { type if:interface-ref; description "The next-hop interface to reach root"; } leaf peer { type leafref { path "../../../../../../../../ldp:peers/" + "ldp:peer/ldp:lsr-id"; } description "LDP peer associated with the nexthop (address, interface). The referenced node is an item in the peer list of mpls-ldp, with the hierarchy mpls-ldp/peers/peer/lsr-id, in the configuration plus state data datastore."; } } container bindings { description "mLDP FEC-label bindings"; container opaque-value-element-lspid { description "Generic LSP identifier opaque element FEC-label Raza, et al. Expires 20 May 2027 [Page 34] Internet-Draft A YANG Model for MPLS mLDP November 2026 bindings container"; reference "RFC6388: Label Distribution Protocol Extensions for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths."; list fec-label { key "lsp-id"; description "List of FEC-label bindings"; leaf lsp-id { type uint32; description "LSP identifier"; } leaf multipoint-type { type multipoint-type; description "The type of multipoint: p2mp or mp2mp"; } leaf opaque-value-element-type { type identityref { base iana-mldp-opaque:iana-ldp-mp-opaque-value-element-basic-type; } description "Type of Opaque value element"; } uses mldp-binding-label-state-attributes; } // fec-label } // opaque-value-element-lspid } // bindings } // list root } // roots } // ipv4 } // list address-family } // mldp } /* * Notifications */ notification mpls-mldp-fec-event { description "Notification event for a change of FEC status"; leaf event-type { type ldp:oper-status-event-type; description "Event type"; Raza, et al. Expires 20 May 2027 [Page 35] Internet-Draft A YANG Model for MPLS mLDP November 2026 } choice opaque-value-element { description "The type of opaque value element"; case opaque-value-element-lspid { container opaque-value-element-lspid { description "Generic LSP identifier opaque element"; reference "RFC6388: Label Distribution Protocol Extensions for Point-to-Multipoint and Paths."; leaf root-address { type inet:ip-address; description "Root address. When this module is implemented as mLDP base, the system sends a notification containing root-address with type ipv4-address. When mLDP extended module is implemented, the type will be expanded to cover ipv6-address. The notification format is kept the same."; } leaf lsp-id { type uint32; description "LSP identifier"; } leaf multipoint-type { type multipoint-type; description "The type of multipoint: p2mp or mp2mp"; } } // container opaque-value-element-lspid } } } } Figure 12: mLDP base module 5.5. mLDP Extended This YANG module imports types defined in [RFC9911], [RFC8343], [RFC8349], [RFC9070], and [RFC8294]. Raza, et al. Expires 20 May 2027 [Page 36] Internet-Draft A YANG Model for MPLS mLDP November 2026 file "ietf-mpls-mldp-extended@2026-11-16.yang" // RFC Editor: replace the above date with the date of // publication and remove this note. module ietf-mpls-mldp-extended { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-mldp-extended"; prefix "mldp-ext"; import ietf-inet-types { prefix "inet"; reference "RFC 9911: Common YANG Data Types"; } import ietf-interfaces { prefix "if"; reference "RFC 8343: A YANG Data Model for Interface Management"; } import ietf-routing { prefix "rt"; reference "RFC 8349: A YANG Data Model for Routing Management (NMDA version)"; } import ietf-routing-types { prefix "rt-types"; reference "RFC 8294: Common YANG Data Types for the Routing Area"; } import ietf-mpls-ldp { prefix "ldp"; reference "RFC 9070: YANG Data Model for MPLS LDP"; } import ietf-mpls-ldp-extended { prefix "ldp-ext"; reference "RFC 9070: YANG Data Model for MPLS LDP"; } import ietf-mpls-mldp { prefix "mldp"; reference "RFC XXXX: Base YANG Data Model for MPLS mLDP"; // RFC Editor: replace the XXXX with actual mLDP YANG RFC number at // time of publication and remove this note. Raza, et al. Expires 20 May 2027 [Page 37] Internet-Draft A YANG Model for MPLS mLDP November 2026 } import iana-ldp-mp-opaque-value-element-basic-types { prefix "iana-mldp-opaque"; reference "RFC XXX: XXXX"; // RFC editor: replace XXX with the RFC number of this document } organization "IETF MPLS Working Group"; contact "WG Web: WG List: Editor: Kamran Raza Editor: Xufeng Liu Editor: Santosh Easale Editor: Loa Andersson Editor: Jeff Tantsura "; description "This YANG module defines the extended components for the management of Multiprotocol Label Switching (MPLS) Multipoint LDP (mLDP). The types and groupings defined in this module are intended exclusively for use within this module itself or any other module that augments this module. This module is available from the IANA YANG Parameters registry (https://www.iana.org/assignments/yang-parameters). Copyright (c) 2026 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Revised BSD License Raza, et al. Expires 20 May 2027 [Page 38] Internet-Draft A YANG Model for MPLS mLDP November 2026 set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; // RFC Ed: replace 'date-revision' with the module publication date // the format is (YYYY-MM-DD) // replace XXXX with actual RFC number and remove // this note revision 2026-11-16 { description "Initial revision."; reference "RFC XXXX: A YANG Data Model for MPLS mLDP."; // RFC Editor: replace XXXX with actual RFC number and remove // this note } /* * Features */ feature capability-mldp-hsmp { description "This feature indicates that the system allows to configure mLDP hub-and-spoke-multipoint capability."; reference "RFC7140: LDP Extensions for Hub and Spoke Multipoint Label Switched Path"; } feature capability-mldp-node-protection { description "This feature indicates that the system allows to configure mLDP node-protection capability."; reference "RFC7715: Multipoint LDP (mLDP) Node Protection"; } feature mldp-mofrr { description "This feature indicates that the system supports mLDP Multicast only FRR (MoFRR)."; reference "RFC7431: Multicast-Only Fast Reroute"; Raza, et al. Expires 20 May 2027 [Page 39] Internet-Draft A YANG Model for MPLS mLDP November 2026 } feature per-peer-capability { description "This feature indicates that the system allows to configure mLDP capabilities at the per peer level."; } /* * Typedefs */ typedef lsp-mofrr-role { type enumeration { enum none { description "MoFRR is not enabled."; } enum primary { description "This LSP is primary."; } enum backup { description "This LSP is backup."; } } description "This type represents the MoFRR (Multicast-only FRR) role of an LSP."; } /* * Groupings */ grouping mldp-ext-binding-label-peer-state { description "mLDP label binding peer state."; list peer { key "direction peer advertisement-type"; description "List of peers with bindings exchanged (sent and/or received)"; leaf peer { type leafref { path "../../../../../../../../../../../ldp:peers/ldp:peer/" + "ldp:lsr-id"; } description "[m]LDP peer from which this binding is received, or Raza, et al. Expires 20 May 2027 [Page 40] Internet-Draft A YANG Model for MPLS mLDP November 2026 to which this binding is advertised. The referenced node is an item in the peer list of mpls-ldp, with the hierarchy mpls-ldp/peers/peer/lsr-id, in the configuration plus state data datastore."; } uses mldp:mldp-binding-label-peer-state-attributes; leaf mofrr-status { when "../direction = 'upstream'" { description "This leaf is used for MoFRR upstream direction only."; } type lsp-mofrr-role; description "The MoFRR status of this LSP"; } } // peer } // mldp-ext-binding-label-peer-state grouping mldp-ext-capabilities { description "mLDP extended capabilities"; container hub-and-spoke { if-feature capability-mldp-hsmp; description "Configure hub-and-spoke-multipoint capability"; reference "RFC7140: LDP Extensions for Hub and Spoke Multipoint Label Switched Path"; leaf enabled { type boolean; description "Enables the multipoint hub-and-spoke capability when set to 'true'."; } } container node-protection { if-feature capability-mldp-node-protection; description "Configure node-protection capability."; reference "RFC7715: mLDP Node Protection."; leaf plr { type boolean; description "Enables the multipoint node-protection PLR capability when set to 'true'."; } Raza, et al. Expires 20 May 2027 [Page 41] Internet-Draft A YANG Model for MPLS mLDP November 2026 container merge-point { description "Merge Point capable for Multipoint LSP node protection"; leaf enabled { type boolean; description "Enables the multipoint node-protection merge-point capability when set to 'true'."; } leaf targeted-session-teardown-delay { type uint16; units seconds; description "Targeted session teardown delay"; } } // merge-point } // node-protection } // mldp-ext-capabilities grouping mldp-ext-per-af-config-attributes { description "mLDP per address family configuration attributes"; container multicast-only-frr { if-feature mldp-mofrr; description "Multicast-only FRR (MoFRR) policy"; reference "RFC7431: Multicast-Only Fast Reroute"; leaf prefix-list { type ldp-ext:prefix-list-ref; description "Enables Multicast-only FRR (MoFRR) for the specified prefix-list"; } } // multicast-only-frr container recursive-fec { description "Recursive FEC policy"; leaf prefix-list { type ldp-ext:prefix-list-ref; description "Enables recursive FEC for the specified prefix-list"; } } // recursive-fec } // mldp-ext-per-af-config-attributes grouping opaque-value-element-recursive-container { Raza, et al. Expires 20 May 2027 [Page 42] Internet-Draft A YANG Model for MPLS mLDP November 2026 description "Container mLDP recursive opaque elements."; reference "RFC6512: Using Multipoint LDP When the Backbone Has No Route to the Root"; container opaque-value-element-recursive { config false; description "Recursive opaque type"; reference "RFC6512: Using Multipoint LDP When the Backbone Has No Route to the Root"; list fec-label { key "rd opaque-value"; description "List of FEC-label bindings"; leaf rd { type rt-types:route-distinguisher; description "Route Distinguisher"; reference "RFC7246: Multipoint Label Distribution Protocol In-Band Signaling in a Virtual Routing and Forwarding (VRF) Table Context."; } leaf opaque-value { type binary; description "The opaque value that is not interpreted at this device."; } leaf multipoint-type { type mldp:multipoint-type; description "The type of multipoint: p2mp or mp2mp"; } leaf opaque-value-element-type { type identityref { base iana-mldp-opaque:iana-ldp-mp-opaque-value-element-basic-type; } description "Type of Opaque value element"; } uses mldp-ext-binding-label-peer-state; } // fec-label } // opaque-value-element-recursive } // opaque-value-element-recursive-container Raza, et al. Expires 20 May 2027 [Page 43] Internet-Draft A YANG Model for MPLS mLDP November 2026 grouping recursive-fec-base-attributes { description "mLDP recursive FEC base attributes."; reference "RFC6512: Using Multipoint LDP When the Backbone Has No Route to the Root"; leaf recur-root-address { type inet:ip-address; description "Recursive root address"; } } // recursive-fec-base-attributes grouping recursive-fec-attributes { description "mLDP recursive FEC attributes."; reference "RFC6512: Using Multipoint LDP When the Backbone Has No Route to the Root"; uses recursive-fec-base-attributes; leaf recur-rd { type rt-types:route-distinguisher; description "Route Distinguisher in the VPN-Recursive Opaque Value"; } } // recursive-fec-attributes /* * Configuration data and operational state data nodes */ // Global capability augment "/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:global/" + "ldp:capability/mldp:mldp" { description "Augmentation for mLDP global capabilities."; uses mldp-ext-capabilities; } // IPv4 config augment "/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:global/mldp:mldp/" + "mldp:address-families/mldp:ipv4" { description "Augmentation for mLDP IPv4 configuration"; uses mldp-ext-per-af-config-attributes; Raza, et al. Expires 20 May 2027 [Page 44] Internet-Draft A YANG Model for MPLS mLDP November 2026 } // IPv6 config augment "/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:global/mldp:mldp/" + "mldp:address-families/ipv6" { description "Augmentation for mLDP IPv6 configuration"; uses mldp-ext-per-af-config-attributes; } // Global forwarding-nexthop augment "/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:global/" + "ldp-ext:forwarding-nexthop/ldp-ext:interfaces/" + "ldp-ext:interface/ldp-ext:address-family" { description "Augmentation for mLDP nexthop forwarding interface"; leaf mldp-disable { type boolean; description "Disables mLDP forwarding on this interface when set to 'true'."; } } /* * Operational state data nodes */ // IPv4 state for per peer bindings augment "/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:global/mldp:mldp/" + "mldp:address-families/mldp:ipv4/mldp:roots/mldp:root/" + "mldp:bindings/mldp:opaque-value-element-lspid/mldp:fec-label/" + "mldp:peer" { description "Augmentation for mLDP IPv4 state"; leaf mofrr-status { when "../mldp:direction = 'upstream'" { description "This leaf is used for upstream direction only."; } type lsp-mofrr-role; description "The MoFRR status of this LSP"; } } // Peer capability state Raza, et al. Expires 20 May 2027 [Page 45] Internet-Draft A YANG Model for MPLS mLDP November 2026 augment "/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:peers/ldp:peer/" + "ldp:received-peer-state/ldp:capability/mldp:mldp" { description "Augmentation for mLDP received peer state capability."; container hub-and-spoke { description "Operational state information for the peer's hub-and-spoke-multipoint capability."; reference "RFC7140: LDP Extensions for Hub and Spoke Multipoint Label Switched Path"; leaf is-capable { type boolean; description "Set to 'true' when hub-and-spoke-multipoint capability is received from peer"; } } container node-protection { description "Operational state information for the peer's node-protection capability"; reference "RFC7715: mLDP Node Protection."; leaf is-plr-capable { type boolean; description "Set to 'true' when Point of Local Repair (PLR) node-protection capability is received from peer"; } leaf is-merge-point-capable { type boolean; description "Set to 'true' when Merge-point node-protection capability is received from peer"; } // merge-point } // node-protection } // IPv4 bindings state augment "/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:global/mldp:mldp/" + "mldp:address-families/mldp:ipv4/mldp:roots/mldp:root/" + "mldp:bindings" { description "Augmentation for mLDP IPv4 bindings extended type."; container opaque-value-element-transit-source { Raza, et al. Expires 20 May 2027 [Page 46] Internet-Draft A YANG Model for MPLS mLDP November 2026 description "Transit IPv4/VPNv4 Source opaque type"; reference "RFC6826: Multipoint LDP In-Band Signaling for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths."; list fec-label { key "source-address group-address rd"; description "List of FEC-label bindings"; leaf source-address { type inet:ipv4-address; description "Source address (0.0.0.0 refers to wildcard *)"; } leaf group-address { type inet:ipv4-address; description "Group address (0.0.0.0 refers to wildcard *)"; } leaf rd { type rt-types:route-distinguisher; description "Route Distinguisher"; reference "RFC7246: Multipoint Label Distribution Protocol In-Band Signaling in a Virtual Routing and Forwarding (VRF) Table Context."; } leaf multipoint-type { type mldp:multipoint-type; description "The type of multipoint: p2mp or mp2mp"; } leaf opaque-value-element-type { type identityref { base iana-mldp-opaque:iana-ldp-mp-opaque-value-element-basic-type; } description "Type of Opaque value element"; } uses mldp-ext-binding-label-peer-state; } // fec-label } // opaque-value-element-transit-source container opaque-value-element-transit-bidir { description Raza, et al. Expires 20 May 2027 [Page 47] Internet-Draft A YANG Model for MPLS mLDP November 2026 "Transit IPv4/VPNv4 Bidir opaque type"; reference "RFC6826: Multipoint LDP In-Band Signaling for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths."; list fec-label { key "masklen rp group-address rd"; description "List of FEC-label bindings"; leaf masklen { type uint8; description "Mask length for the subnet"; } leaf rp { type inet:ipv4-address; description "Rendezvous Point (RP) address"; } leaf group-address { type inet:ipv4-address; description "Group address"; } leaf rd { type rt-types:route-distinguisher; description "Route Distinguisher"; reference "RFC7246: Multipoint Label Distribution Protocol In-Band Signaling in a Virtual Routing and Forwarding (VRF) Table Context."; } leaf multipoint-type { type mldp:multipoint-type; description "The type of multipoint: p2mp or mp2mp"; } leaf opaque-value-element-type { type identityref { base iana-mldp-opaque:iana-ldp-mp-opaque-value-element-basic-type; } description "Type of Opaque value element"; } uses mldp-ext-binding-label-peer-state; } // fec-label Raza, et al. Expires 20 May 2027 [Page 48] Internet-Draft A YANG Model for MPLS mLDP November 2026 } // opaque-value-element-transit-bidir uses opaque-value-element-recursive-container; } // IPv6 bindings state augment "/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:global/mldp:mldp/" + "mldp:address-families/ipv6/roots/root/bindings" { description "Augmentation for mLDP IPv6 bindings."; container opaque-value-element-transit-source { config false; description "Transit IPv6/VPNv6 Source opaque type"; reference "RFC6826: Multipoint LDP In-Band Signaling for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths."; list fec-label { key "source-address group-address rd"; description "List of FEC-label bindings"; leaf source-address { type inet:ipv6-address; description "Source address (:: refers to wildcard *)"; } leaf group-address { type inet:ipv6-address; description "Group address (:: refers to wildcard *)"; } leaf rd { type rt-types:route-distinguisher; description "Route Distinguisher"; reference "RFC7246: Multipoint Label Distribution Protocol In-Band Signaling in a Virtual Routing and Forwarding (VRF) Table Context."; } leaf multipoint-type { type mldp:multipoint-type; description "The type of multipoint: p2mp or mp2mp"; } Raza, et al. Expires 20 May 2027 [Page 49] Internet-Draft A YANG Model for MPLS mLDP November 2026 leaf opaque-value-element-type { type identityref { base iana-mldp-opaque:iana-ldp-mp-opaque-value-element-basic-type; } description "Type of Opaque value element"; } uses mldp-ext-binding-label-peer-state; } // fec-label } // opaque-value-element-transit-source container opaque-value-element-transit-bidir { config false; description "Transit IPv6/VPNv6 Bidir opaque type"; reference "RFC6826: Multipoint LDP In-Band Signaling for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths."; list fec-label { key "masklen rp group-address rd"; description "List of FEC-label bindings"; leaf masklen { type uint8; description "Mask length for the subnet"; } leaf rp { type inet:ipv6-address; description "Rendezvous Point (RP) address"; } leaf group-address { type inet:ipv6-address; description "Group address"; } leaf rd { type rt-types:route-distinguisher; description "Route Distinguisher"; reference "RFC7246: Multipoint Label Distribution Protocol In-Band Signaling in a Virtual Routing and Forwarding (VRF) Table Context."; Raza, et al. Expires 20 May 2027 [Page 50] Internet-Draft A YANG Model for MPLS mLDP November 2026 } leaf multipoint-type { type mldp:multipoint-type; description "The type of multipoint: p2mp or mp2mp"; } leaf opaque-value-element-type { type identityref { base iana-mldp-opaque:iana-ldp-mp-opaque-value-element-basic-type; } description "Type of Opaque value element"; } uses mldp-ext-binding-label-peer-state; } // fec-label } // opaque-value-element-transit-bidir uses opaque-value-element-recursive-container; } /* * Per AF augmentation */ // IPv6 augmentation augment "/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:global/mldp:mldp/" + "mldp:address-families" { description "Augmentation for mLDP IPv6 address family."; container ipv6 { presence "Enables IPv6 mLDP support unless the 'enabled' leaf is set to 'false'."; description "Containing data related to the IPv6 address family."; leaf enabled { type boolean; default "true"; description "Disables the IPv6 address family when set to 'false'."; } container roots { config false; description "IPv6 multicast LSP roots"; list root { key "root-address"; description "List of roots for configured multicast LSPs"; Raza, et al. Expires 20 May 2027 [Page 51] Internet-Draft A YANG Model for MPLS mLDP November 2026 leaf root-address { type inet:ipv6-address; description "Root address"; } leaf is-self { type boolean; description "Set to 'true' when the node itself is the root node."; } list reachability { key "address interface"; description "Root reachability information in form of a next-hop"; leaf address { type inet:ipv6-address; description "The next-hop address to reach root"; } leaf interface { type if:interface-ref; description "The next-hop interface to reach root"; } leaf peer { type leafref { path "../../../../../../../../ldp:peers/" + "ldp:peer/ldp:lsr-id"; } description "LDP peer associated with the nexthop (address, interface). The referenced node is an item in the peer list of mpls-ldp, with the hierarchy mpls-ldp/peers/peer/lsr-id, in the configuration plus state data datastore."; } } container bindings { description "mLDP FEC-label bindings"; container opaque-value-element-lspid { description Raza, et al. Expires 20 May 2027 [Page 52] Internet-Draft A YANG Model for MPLS mLDP November 2026 "Generic LSP identifier opaque element FEC-label bindings container"; reference "RFC6388: Label Distribution Protocol Extensions for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths."; list fec-label { key "lsp-id"; description "List of FEC-label bindings"; leaf lsp-id { type uint32; description "LSP identifier"; } leaf multipoint-type { type mldp:multipoint-type; description "The type of multipoint: p2mp or mp2mp"; } leaf opaque-value-element-type { type identityref { base iana-mldp-opaque:iana-ldp-mp-opaque-value-element-basic-type; } description "Type of Opaque value element"; } uses mldp-ext-binding-label-peer-state; } // fec-label } // opaque-value-element-lspid } // bindings } // list root } // roots } // ipv6 } /* * Global augmentation */ /* * Notifications */ augment "/mldp:mpls-mldp-fec-event/mldp:opaque-value-element/" + "mldp:opaque-value-element-lspid/" + "mldp:opaque-value-element-lspid" { description "Augmentation for mLDP notification for Raza, et al. Expires 20 May 2027 [Page 53] Internet-Draft A YANG Model for MPLS mLDP November 2026 opaque-value-element-lspid."; container recursive-fec { description "Container of recursive opaque values"; uses recursive-fec-base-attributes; } // recursive-fec } augment "/mldp:mpls-mldp-fec-event/mldp:opaque-value-element" { description "Augmentation for mLDP notification for opaque types other than lspid."; case opaque-value-element-transit-source { container opaque-value-element-transit-source { description "Transit IP/VPN Source opaque type"; reference "RFC6826: Multipoint LDP In-Band Signaling for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths."; leaf root-address { type inet:ip-address; description "Root address"; } leaf source-address { type inet:ip-address; description "Source address"; } leaf group-address { type inet:ip-address; description "Group address"; } leaf rd { type rt-types:route-distinguisher; description "Route Distinguisher"; reference "RFC7246: Multipoint Label Distribution Protocol In-Band Signaling in a Virtual Routing and Forwarding (VRF) Table Context."; } uses recursive-fec-attributes; } // opaque-value-element-transit-source container } // opaque-value-element-transit-source case Raza, et al. Expires 20 May 2027 [Page 54] Internet-Draft A YANG Model for MPLS mLDP November 2026 case opaque-value-element-transit-bidir { container opaque-value-element-transit-bidir { description "Transit IP/VPN Bidir opaque type"; reference "RFC6826: Multipoint LDP In-Band Signaling for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths."; leaf root-address { type inet:ip-address; description "Root address"; } leaf masklen { type uint8; description "Mask length for the subnet"; } leaf rp { type inet:ip-address; description "Rendezvous Point (RP) address"; } leaf group-address { type inet:ip-address; description "Group address"; } leaf rd { type rt-types:route-distinguisher; description "Route Distinguisher"; reference "RFC7246: Multipoint Label Distribution Protocol In-Band Signaling in a Virtual Routing and Forwarding (VRF) Table Context."; } uses recursive-fec-attributes; } // opaque-value-element-transit-bidir container } // opaque-value-element-transit-bidir case } // augment } // module Figure 13: mLDP extended module Raza, et al. Expires 20 May 2027 [Page 55] Internet-Draft A YANG Model for MPLS mLDP November 2026 6. Operational Considerations This section provides operational guidance for deploying, managing, and migrating to the mLDP YANG data model defined in this document, in accordance with the recommendations in [RFC5706]. 6.1. Migration path from LDP YANG (RFC 9070) The mLDP YANG modules defined in this document are designed as an augmentation to LDP YANG modules [RFC9070]. These mLDP YANG modules do not replace or deprecate RFC 9070; rather, they introduces multipoint extensions (P2MP and MP2MP) onto existing LDP instance, peer, interface, and forwarding structures. Operators planning to introduce mLDP into networks already managed using [RFC9070] should consider the following migration sequence: 1. Prerequisite Verification: Ensure that management systems (NMS/ controllers) and network elements support the base "ietf-mpls- ldp" module [RFC9070] and that unicast LDP sessions, targeted sessions, and interface configurations are operational. 2. Functionality Capability Discovery: Network elements advertise their supported mLDP capabilities via YANG feature statements (e.g., "p2mp", "mp2mp", "node-protection", and "recursive-fec"). Management applications MUST inspect the server's capabilities prior to provisioning multipoint structures to avoid semantic or schema validation rejections. 3. Non-Disruptive Incremental Enablement: Enabling mLDP capabilities under an active LDP instance or interface is designed to be non- disruptive to active unicast LDP LSPs. The introduction of the "mldp" container triggers capability negotiation with supported peers via standard LDP Capability Parameter TLVs without tearing down existing unicast LDP transport sessions. 4. Coexistence and Dual-Stack Operations: In heterogeneous deployments where legacy nodes do not implement mLDP or the mLDP YANG data model, the base LDP operational state [RFC9070] continues to reflect peer session state, while mLDP-specific operational state (e.g., Multipoint FEC-to-NHLFE mappings, Upstream LSR selection) is populated only on nodes and sessions where mLDP is active. Raza, et al. Expires 20 May 2027 [Page 56] Internet-Draft A YANG Model for MPLS mLDP November 2026 6.2. Deployment and Feature Modularity The model defines granular YANG features to allow implementations to support subsets of the specification according to hardware and platform constraints: * Point-to-Multipoint ("p2mp") vs. Multipoint-to-Multipoint ("mp2mp"): Platforms supporting only P2MP trees (e.g., for IPTV/ multicast distribution) are not required to implement or expose MP2MP configuration or state containers. * Protection Capabilities: Advanced protection mechanisms, such as Multicast-only Fast Reroute (MoFRR) and node protection, are conditioned under dedicated features. Operators should verify hardware forwarding engine support prior to activating fast- reroute policies. 6.3. Telemetry, Monitoring, and State Synchronization mLDP networks often maintain significant dynamic state driven by multicast group join/prune events, dynamic root failovers, and upstream LSR path re-evaluation: * YANG-Push and Telemetry: Given the high potential rate of state transitions during network reconvergence or root migration, operators SHOULD utilize subscription-based telemetry (YANG-Push, [RFC8639] / [RFC8641]) rather than repetitive SNMP or NETCONF polling. On-change notifications are RECOMMENDED for session state and root-reachability state transitions, whereas periodic subscriptions should be used for forwarding statistics and LSP counters. * Upstream and Downstream Tracking: Operators should monitor the operational containers representing upstream LSR bindings and downstream forwarding replication lists (NHLFE entries) to verify tree branch health and detect split-brain or branch-isolation conditions. 6.4. Scale, Churn, and Resource Management The scale of mLDP state is directly proportional to the number of active (Root, Opaque Value) FEC elements and the number of outgoing interfaces per replication node: Raza, et al. Expires 20 May 2027 [Page 57] Internet-Draft A YANG Model for MPLS mLDP November 2026 * Control-Plane Overhead: Large multicast deployments can result in high memory utilization for mLDP RIB and LIB databases. Operators SHOULD utilize inbound/outbound FEC filtering policies supported in the model to constrain label mapping distribution to authorized multicast distribution trees. * Data-Plane Replication Limits: The creation of extensive P2MP/ MP2MP trees places significant demand on hardware multicast replication tables. Management systems SHOULD track interface and node-level forwarding utilization counters to avoid out-of- resource conditions on branching nodes. 6.5. Fault Handling, Diagnostics, and Notifications * Root Node Unreachability: If an IGP path to the root node fails and no alternate Upstream LSR (via LDP upstream selection or MoFRR) is available, the mLDP tree will transition to an inactive state. The model provides notifications for significant state changes, such as neighbor capability loss or root unreachability. * Opaque Value Interoperability: When provisioning recursive or extended opaque values, operators must ensure that all transit and root nodes within the mLDP domain support matching opaque types (e.g., Generic LSP identifier, Transit IPv4/IPv6 Source) to prevent FEC resolution failures. 7. Security Considerations The YANG modules defined in this document specify data models designed to be accessed via YANG- based management protocols, such as the Network Configuration Protocol (NETCONF) [RFC6241] and RESTCONF [RFC8040]. These YANG-based management protocols (1) have to use a secure transport layer (e.g., Secure Shell (SSH) [RFC4252] [RFC6242], TLS [RFC9846] [RFC9846], and QUIC [RFC9000]) and (2) have to use mutual authentication. The Network Configuration Access Control Model (NACM) [RFC8341] provides the means to restrict access for particular NETCONF or RESTCONF users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. Raza, et al. Expires 20 May 2027 [Page 58] Internet-Draft A YANG Model for MPLS mLDP November 2026 This specification also inherits the security considerations captured in [RFC5920] and the underlying mLDP protocol specifications, namely base mLDP [RFC6388], targeted mLDP [RFC7060], mLDP Recursive FEC [RFC6512], Multicast-only Fast Reroute (MoFRR) [RFC7431], mLDP Node Protection [RFC7715], mLDP In-band Signaling [RFC6826] [RFC7246] [RFC7438], and Hub-and-Spoke Multipoint LSPs [RFC7140]. Furthermore, security considerations defined in the base LDP YANG data model [RFC9070] apply directly to this document. 7.1. Writable Data Nodes There are a number of data nodes defined in the "ietf-mpls-mldp" and "ietf-mpls-mldp-extended" YANG modules that are writable/creatable/ deletable (i.e., "config true", which is the default). All writable data nodes are likely to be sensitive or vulnerable in some network environments. Write operations (e.g., edit-config) and delete operations to these data nodes without proper protection or authentication can have a negative effect on network operations. The following subtrees and data nodes have particular sensitivities/ vulnerabilities: * /rt:routing/control-plane-protocols/control-plane-protocol/ ldp:mpls-ldp/global/mldp: Unauthorized modifications to global mLDP configuration (such as enabling/disabling mLDP capabilities, recursive FEC support, or node protection) can compromise the entire multipoint label switched path (LSP) forwarding domain. An attacker could tear down active multicast distribution trees (MDTs) or force unauthorized capability negotiation, resulting in widespread Denial of Service (DoS) for multicast services (e.g., IPTV, MVPN). * /rt:routing/control-plane-protocols/control-plane-protocol/ ldp:mpls-ldp/global/mldp/address-families/ipv4 and /rt:routing/ control-plane-protocols/control-plane-protocol/ ldp:mpls- ldp/global/mldp/address-families/ipv6: Unauthorized changes to address-family parameters, recursive FEC policies, or MoFRR policies can cause multicast traffic to be diverted, blackholed, or looped, disrupting multicast delivery across the provider backbone. * /rt:routing/control-plane-protocols/control-plane-protocol/ ldp:mpls-ldp/discovery/interfaces/interface/mldp: Modifying or disabling interface-level mLDP configurations can prevent Point- to-Multipoint (P2MP) and Multipoint-to-Multipoint (MP2MP) tree branch establishment on specific physical or logical links, isolating downstream multicast receivers. Raza, et al. Expires 20 May 2027 [Page 59] Internet-Draft A YANG Model for MPLS mLDP November 2026 * Reused LDP Nodes: The subtrees and data nodes inherited from the base LDP module [RFC9070](such as peer Discovery, targeted LDP sessions, and authentication parameters) are equally vulnerable to unauthorized modification, as detailed in Section 10.1.1 of [RFC9070]. 7.2. Readable Data Nodes Some of the readable data nodes in the "ietf-mpls-mldp" and "ietf- mpls-mldp-extended" YANG modules may be considered sensitive or vulnerable in some network environments. It is thus important to control read access (e.g., via get, get-config, or notification) to these data nodes. Specifically, the following subtrees and data nodes have particular sensitivities/vulnerabilities: * /rt:routing/control-plane-protocols/control-plane-protocol/ ldp:mpls-ldp/global/mldp/address-families/ipv4/roots and /rt:routing/control-plane-protocols/control-plane-protocol/ ldp:mpls-ldp/global/mldp/address-families/ipv6/roots: Exposing active mLDP Root addresses, Upstream LSR bindings, and tree operational states reveals the exact topological locations of multicast sources, root routers, and transit paths, which an attacker could use to target high-value infrastructure nodes. * /rt:routing/control-plane-protocols/control-plane-protocol/ ldp:mpls-ldp/global/mldp/address-families/ipv4/roots/root/bindings and /rt:routing/control-plane-protocols/control-plane-protocol/ ldp:mpls-ldp/global/mldp/address-families/ipv6/roots/root/ bindings: Exposing Next Hop Label Forwarding Entry (NHLFE) replication lists, incoming/outgoing labels, and client branch attachment points reveals the subscriber/receiver traffic matrix and multicast group membership patterns. * /rt:routing/control-plane-protocols/control-plane-protocol/ ldp:mpls-ldp/peers/peer/received-peer-state/capability/mldp: Reading negotiated peer capabilities exposes supported feature sets (e.g., node protection, MoFRR), enabling an attacker to identify unprotected or legacy routers for targeted attacks. * Reused LDP Operational State: Exposure of base LDP session states, hello adjacencies, and label databases presents vulnerabilities as described in Section 10.1.2 of [RFC9070]. 7.3. RPC and Action Operations There are no RPC or action operations defined in the "ietf-mpls-mldp" and "ietf-mpls-mldp-extended" YANG modules. Raza, et al. Expires 20 May 2027 [Page 60] Internet-Draft A YANG Model for MPLS mLDP November 2026 7.4. Notifications The "ietf-mpls-mldp" and "ietf-mpls-mldp-extended" YANG modules define notifications (e.g., for peer capability changes, root state transitions, and mLDP FEC events). Implementations MUST rate-limit the generation of these notifications to avoid creating excessive processing load, exhausting network bandwidth, or causing DoS conditions during mass network reconvergence or root failover events. 7.5. IANA Types Modules The "iana-ldp-mp-opaque-value-element-basic-types", "iana-ldp-mp- opaque-value-element-ext-types", and "iana-ldp-mp-status-value- element-types" modules define only identities and types intended for reuse by other YANG modules. It does not define any writable data nodes, read-only state data nodes, RPCs, or notifications. As such, there are no additional security issues related directly to this module. 8. IANA Considerations IANA is requested to register the following URI in the "ns" registry within the "IETF XML Registry" group [RFC3688]: URI: urn:ietf:params:xml:ns:yang:iana-ldp-mp-opaque-value-element- basic-types Registrant Contact: The IESG XML: N/A; the requested URI is an XML namespace. URI: urn:ietf:params:xml:ns:yang:iana-ldp-mp-opaque-value-element- extended-types Registrant Contact: The IESG XML: N/A; the requested URI is an XML namespace. URI: urn:ietf:params:xml:ns:yang:iana-ldp-mp-status-value-element- types Registrant Contact: The IESG XML: N/A; the requested URI is an XML namespace. URI: urn:ietf:params:xml:ns:yang:ietf-mpls-mldp Registrant Contact: The IESG XML: N/A; the requested URI is an XML namespace. URI: urn:ietf:params:xml:ns:yang:ietf-mpls-mldp-extended Registrant Contact: The IESG XML: N/A; the requested URI is an XML namespace. Raza, et al. Expires 20 May 2027 [Page 61] Internet-Draft A YANG Model for MPLS mLDP November 2026 IANA is requested to register the following YANG module in the "YANG Module Names" registry [RFC6020] within the "YANG Parameters" registry group: Name: iana-ldp-mp-opaque-value-element-basic-types Maintained by IANA? Y Namespace: urn:ietf:params:xml:ns:yang:iana-ldp-mp-opaque-value- element-basic-types Prefix: mldp-opaque-value-element-basic Reference: This document Name: iana-ldp-mp-opaque-value-element-ext-types Maintained by IANA? Y Namespace: urn:ietf:params:xml:ns:yang:iana-ldp-mp-opaque-value- element-ext-types Prefix: mldp-opaque-value-element-ext Reference: This document Name: iana-ldp-mp-status-value-element-types Maintained by IANA? Y Namespace: urn:ietf:params:xml:ns:yang:iana-ldp-mp-status-value- element-types Prefix: mldp-status-value-element Reference: This document Name: ietf-mpls-ldp Maintained by IANA? N Namespace: urn:ietf:params:xml:ns:yang:ietf-mpls-mldp Prefix: mldp Reference: This document Name: ietf-mpls-ldp-extended Maintained by IANA? N Namespace: urn:ietf:params:xml:ns:yang:ietf-mpls-mldp-extended Prefix: mldp-ext Reference: This document // RFC Editor: Replace "This document" with the document RFC number // at time of publication and remove this note. 8.1. mLDP Opaque Value Element basic types This document specifies the initial version of the IANA-maintained "iana-ldp-mp-opaque-value-element-basic-types" YANG module. The most recent version of the YANG module is available from the "YANG Parameters" registry group [IANA-YANG-PARAMETERS]. IANA is requested to add this note to the registry: Raza, et al. Expires 20 May 2027 [Page 62] Internet-Draft A YANG Model for MPLS mLDP November 2026 New values must not be directly added to the "iana-ldp-mp-opaque- value-element-basic-types" YANG module. They must instead be added to the "LDP MP Opaque Value Element basic type" registry [IANA-LDP-MP-OPAQUE] registry. IANA is requested to add this note to [IANA-LDP-MP-OPAQUE] registry: When this registry is modified, the YANG module "iana-ldp-mp-opaque- value-element-basic-types" must be updated as defined in RFC XXX. // RFC editor: Replace RFC XXX with the reference to this document. When a value is added to the [IANA-LDP-MP-OPAQUE] registry, a new "identity" statement needs to be added to the "iana-ldp-mp-opaque- value-element-basic-types" YANG module. The name of the "identity" is a lower-case version of the type provided in the description. The "identity" statement should have the following sub-statements defined: "base": Contains 'iana-ldp-mp-opaque-value-element-basic-types'. "description": Replicates the description from the registry. "reference": Replicates the reference from the registry with the title of the document added. Unassigned or reserved values are not present in the module. When the "iana-ldp-mp-opaque-value-element-basic-types" YANG module is updated, a new "revision" statement with a unique revision date must be added in front of the existing revision statements. 8.2. mLDP Opaque Value Element extended types This document specifies the initial version of the IANA-maintained "iana-ldp-mp-opaque-value-element-ext-types" YANG module. The most recent version of the YANG module is available from the "YANG Parameters" registry group [IANA-YANG-PARAMETERS]. IANA is requested to add this note to the registry: New values must not be directly added to the "iana-ldp-mp-opaque- value-element-ext-types" YANG module. They must instead be added to the "LDP MP Opaque Value Element extended type" registry [IANA-LDP-MP-OPAQUE-EXT] registry. IANA is requested to add this note to [IANA-LDP-MP-OPAQUE-EXT] registry: Raza, et al. Expires 20 May 2027 [Page 63] Internet-Draft A YANG Model for MPLS mLDP November 2026 When this registry is modified, the YANG module "iana-ldp-mp-opaque- value-element-ext-types" must be updated as defined in RFC XXX. // RFC editor: Replace RFC XXX with the reference to this document. Currently [IANA-LDP-MP-OPAQUE-EXT] registry does not register any value except reserved value 0. When a value is added to the [IANA-LDP-MP-OPAQUE-EXT] registry, a new "identity" statement needs to be added to the "iana-ldp-mp-opaque- value-element-ext-types" YANG module. The name of the "identity" is a lower-case version of the type provided in the description. The "identity" statement should have the following sub- statements defined: "base": Contains 'iana-ldp-mp-opaque-value-element-ext-types'. "description": Replicates the description from the registry. "reference": Replicates the reference from the registry with the title of the document added. Unassigned or reserved values are not present in the module. When the "iana-ldp-mp-opaque-value-element-ext-types" YANG module is updated, a new "revision" statement with a unique revision date must be added in front of the existing revision statements. 8.3. mLDP Status Value Element types This document specifies the initial version of the IANA-maintained "iana-ldp-mp-status-value-element-types" YANG module. The most recent version of the YANG module is available from the "YANG Parameters" registry group [IANA-YANG-PARAMETERS]. IANA is requested to add this note to the registry: New values must not be directly added to the "iana-ldp-mp-status- value-element-types" YANG module. They must instead be added to the "LDP MP Status Value Element type" registry [IANA-LDP-MP-STATUS] registry. IANA is requested to add this note to [IANA-LDP-MP-STATUS] registry: When this registry is modified, the YANG module "iana-ldp-mp-status- value-element-types" must be updated as defined in RFC XXX. // RFC editor: Replace RFC XXX with the reference to this document. Raza, et al. Expires 20 May 2027 [Page 64] Internet-Draft A YANG Model for MPLS mLDP November 2026 When a value is added to the [IANA-LDP-MP-STATUS] registry, a new "identity" statement needs to be added to the "iana-ldp-mp-status- value-element-types" YANG module. The name of the "identity" is a lower-case version of the type provided in the description. The "identity" statement should have the following sub-statements defined: "base": Contains 'iana-ldp-mp-status-value-element-types'. "description": Replicates the description from the registry. "reference": Replicates the reference from the registry with the title of the document added. Unassigned or reserved values are not present in the module. When the "iana-ldp-mp-status-value-element-types" YANG module is updated, a new "revision" statement with a unique revision date must be added in front of the existing revision statements. 9. References 9.1. Normative References [IANA-LDP] IANA, "LDP Parameters", . [IANA-LDP-MP-OPAQUE] IANA, "LDP MP Opaque Value Element basic type", . [IANA-LDP-MP-OPAQUE-EXT] IANA, "LDP MP Opaque Value Element extended type", . [IANA-LDP-MP-STATUS] IANA, "LDP MP Status Value Element type", . [IANA-YANG-PARAMETERS] IANA, "IANA-YANG-PARAMETERS", . Raza, et al. Expires 20 May 2027 [Page 65] Internet-Draft A YANG Model for MPLS mLDP November 2026 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, . [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, DOI 10.17487/RFC6020, October 2010, . [RFC6388] Wijnands, IJ., Ed., Minei, I., Ed., Kompella, K., and B. Thomas, "Label Distribution Protocol Extensions for Point- to-Multipoint and Multipoint-to-Multipoint Label Switched Paths", RFC 6388, DOI 10.17487/RFC6388, November 2011, . [RFC6389] Aggarwal, R. and JL. Le Roux, "MPLS Upstream Label Assignment for LDP", RFC 6389, DOI 10.17487/RFC6389, November 2011, . [RFC6512] Wijnands, IJ., Rosen, E., Napierala, M., and N. Leymann, "Using Multipoint LDP When the Backbone Has No Route to the Root", RFC 6512, DOI 10.17487/RFC6512, February 2012, . [RFC6826] Wijnands, IJ., Ed., Eckert, T., Leymann, N., and M. Napierala, "Multipoint LDP In-Band Signaling for Point-to- Multipoint and Multipoint-to-Multipoint Label Switched Paths", RFC 6826, DOI 10.17487/RFC6826, January 2013, . [RFC7060] Napierala, M., Rosen, E., and IJ. Wijnands, "Using LDP Multipoint Extensions on Targeted LDP Sessions", RFC 7060, DOI 10.17487/RFC7060, November 2013, . [RFC7140] Jin, L., Jounay, F., Wijnands, IJ., and N. Leymann, "LDP Extensions for Hub and Spoke Multipoint Label Switched Path", RFC 7140, DOI 10.17487/RFC7140, March 2014, . [RFC7246] Wijnands, IJ., Ed., Hitchen, P., Leymann, N., Henderickx, W., Gulko, A., and J. Tantsura, "Multipoint Label Distribution Protocol In-Band Signaling in a Virtual Raza, et al. Expires 20 May 2027 [Page 66] Internet-Draft A YANG Model for MPLS mLDP November 2026 Routing and Forwarding (VRF) Table Context", RFC 7246, DOI 10.17487/RFC7246, June 2014, . [RFC7438] Wijnands, IJ., Ed., Rosen, E., Gulko, A., Joorde, U., and J. Tantsura, "Multipoint LDP (mLDP) In-Band Signaling with Wildcards", RFC 7438, DOI 10.17487/RFC7438, January 2015, . [RFC7442] Rekhter, Y., Aggarwal, R., Leymann, N., Henderickx, W., Zhao, Q., and R. Li, "Carrying Protocol Independent Multicast - Sparse Mode (PIM-SM) in Any-Source Multicast (ASM) Mode Trees over Multipoint LDP (mLDP)", RFC 7442, DOI 10.17487/RFC7442, February 2015, . [RFC7715] Wijnands, IJ., Ed., Raza, K., Atlas, A., Tantsura, J., and Q. Zhao, "Multipoint LDP (mLDP) Node Protection", RFC 7715, DOI 10.17487/RFC7715, January 2016, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . [RFC8294] Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger, "Common YANG Data Types for the Routing Area", RFC 8294, DOI 10.17487/RFC8294, December 2017, . [RFC8338] Boutros, S., Ed. and S. Sivabalan, Ed., "Signaling Root- Initiated Point-to-Multipoint Pseudowire Using LDP", RFC 8338, DOI 10.17487/RFC8338, March 2018, . [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration Access Control Model", STD 91, RFC 8341, DOI 10.17487/RFC8341, March 2018, . [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., and R. Wilton, "Network Management Datastore Architecture (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, . [RFC8343] Bjorklund, M., "A YANG Data Model for Interface Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, . Raza, et al. Expires 20 May 2027 [Page 67] Internet-Draft A YANG Model for MPLS mLDP November 2026 [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for Routing Management (NMDA Version)", RFC 8349, DOI 10.17487/RFC8349, March 2018, . [RFC8529] Berger, L., Hopps, C., Lindem, A., Bogdanovic, D., and X. Liu, "YANG Data Model for Network Instances", RFC 8529, DOI 10.17487/RFC8529, March 2019, . [RFC9070] Raza, K., Ed., Asati, R., Liu, X., Esale, S., Chen, X., and H. Shah, "YANG Data Model for MPLS LDP", RFC 9070, DOI 10.17487/RFC9070, March 2022, . [RFC9911] Schönwälder, J., Ed., "Common YANG Data Types", RFC 9911, DOI 10.17487/RFC9911, December 2025, . 9.2. Informative References [IETF-XML-REGISTRY] IANA, "IETF XML Registry", . [RFC4252] Ylonen, T. and C. Lonvick, Ed., "The Secure Shell (SSH) Authentication Protocol", RFC 4252, DOI 10.17487/RFC4252, January 2006, . [RFC5706] Harrington, D., "Guidelines for Considering Operations and Management of New Protocols and Protocol Extensions", RFC 5706, DOI 10.17487/RFC5706, November 2009, . [RFC5920] Fang, L., Ed., "Security Framework for MPLS and GMPLS Networks", RFC 5920, DOI 10.17487/RFC5920, July 2010, . [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., and A. Bierman, Ed., "Network Configuration Protocol (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, . [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, . Raza, et al. Expires 20 May 2027 [Page 68] Internet-Draft A YANG Model for MPLS mLDP November 2026 [RFC7431] Karan, A., Filsfils, C., Wijnands, IJ., Ed., and B. Decraene, "Multicast-Only Fast Reroute", RFC 7431, DOI 10.17487/RFC7431, August 2015, . [RFC7473] Raza, K. and S. Boutros, "Controlling State Advertisements of Non-negotiated LDP Applications", RFC 7473, DOI 10.17487/RFC7473, March 2015, . [RFC7951] Lhotka, L., "JSON Encoding of Data Modeled with YANG", RFC 7951, DOI 10.17487/RFC7951, August 2016, . [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, . [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, . [RFC8639] Voit, E., Clemm, A., Gonzalez Prieto, A., Nilsen-Nygaard, E., and A. Tripathy, "Subscription to YANG Notifications", RFC 8639, DOI 10.17487/RFC8639, September 2019, . [RFC8641] Clemm, A. and E. Voit, "Subscription to YANG Notifications for Datastore Updates", RFC 8641, DOI 10.17487/RFC8641, September 2019, . [RFC9000] Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based Multiplexed and Secure Transport", RFC 9000, DOI 10.17487/RFC9000, May 2021, . [RFC9846] Rescorla, E., "The Transport Layer Security (TLS) Protocol Version 1.3", RFC 9846, DOI 10.17487/RFC9846, July 2026, . Appendix A. YANG Data Model: Complete tree The following is the complete tree representation of configuration, state, and notification items under mLDP base and extended modules. Since mLDP modules augment LDP module, the mLDP tree view is shown within the LDP tree. In this view, we only show mLDP specific leaves and containers along with their hierarchy; we do not show any leaves or containers that are LDP specific. Raza, et al. Expires 20 May 2027 [Page 69] Internet-Draft A YANG Model for MPLS mLDP November 2026 module: ietf-mpls-mldp augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/ldp:mpls-ldp/ldp:global /ldp:capability: +--rw mldp +--rw p2mp | +--rw enabled? boolean +--rw mp2mp | +--rw enabled? boolean +--rw make-before-break | +--rw enabled? boolean | +--rw switchover-delay? uint16 | +--rw timeout? uint16 +--rw mldp-ext:hub-and-spoke {capability-mldp-hsmp}? | +--rw mldp-ext:enabled? boolean +--rw mldp-ext:node-protection {capability-mldp-node-protection}? +--rw mldp-ext:plr? boolean +--rw mldp-ext:merge-point +--rw mldp-ext:enabled? | boolean +--rw mldp-ext:targeted-session-teardown-delay? uint16 augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/ldp:mpls-ldp/ldp:peers /ldp:peer/ldp:received-peer-state/ldp:capability: +--ro mldp +--ro p2mp | +--ro is-capable? boolean +--ro mp2mp | +--ro is-capable? boolean +--ro make-before-break | +--ro is-capable? boolean +--ro mldp-ext:hub-and-spoke | +--ro mldp-ext:is-capable? boolean +--ro mldp-ext:node-protection +--ro mldp-ext:is-plr-capable? boolean +--ro mldp-ext:is-merge-point-capable? boolean augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/ldp:mpls-ldp/ldp:global: +--rw mldp +--rw enabled? boolean +--rw address-families +--rw ipv4! | +--rw enabled? boolean | +--ro roots | | +--ro root* [root-address] | | +--ro root-address inet:ipv4-address Raza, et al. Expires 20 May 2027 [Page 70] Internet-Draft A YANG Model for MPLS mLDP November 2026 | | +--ro is-self? boolean | | +--ro reachability* [address interface] | | | +--ro address inet:ipv4-address | | | +--ro interface if:interface-ref | | | +--ro peer? leafref | | +--ro bindings | | +--ro opaque-value-element-lspid | | | +--ro fec-label* [lsp-id] | | | +--ro lsp-id uint32 | | | +--ro multipoint-type? | | | | multipoint-type | | | +--ro opaque-value-element-type? | | | | identityref | | | +--ro peer* | | | [direction peer advertisement-type] | | | +--ro peer leafref | | | +--ro direction | | | | ldp:downstream-upstream | | | +--ro advertisement-type | | | | ldp:advertised-received | | | +--ro label? | | | | rt-types:mpls-label | | | +--ro mbb-status? | | | | lsp-mbb-role | | | +--ro mldp-ext:mofrr-status? | | | lsp-mofrr-role | | +--ro mldp-ext:opaque-value-element-transit-source | | | +--ro mldp-ext:fec-label* | | | [source-address group-address rd] | | | +--ro mldp-ext:source-address | | | | inet:ipv4-address | | | +--ro mldp-ext:group-address | | | | inet:ipv4-address | | | +--ro mldp-ext:rd | | | | rt-types:route-distinguisher | | | +--ro mldp-ext:multipoint-type? | | | | mldp:multipoint-type | | | +--ro mldp-ext:opaque-value-element-type? | | | | identityref | | | +--ro mldp-ext:peer* | | | [direction peer advertisement-type] | | | +--ro mldp-ext:peer | | | | leafref | | | +--ro mldp-ext:direction | | | | ldp:downstream-upstream | | | +--ro mldp-ext:advertisement-type | | | | ldp:advertised-received | | | +--ro mldp-ext:label? Raza, et al. Expires 20 May 2027 [Page 71] Internet-Draft A YANG Model for MPLS mLDP November 2026 | | | | rt-types:mpls-label | | | +--ro mldp-ext:mbb-status? | | | | lsp-mbb-role | | | +--ro mldp-ext:mofrr-status? | | | lsp-mofrr-role | | +--ro mldp-ext:opaque-value-element-transit-bidir | | | +--ro mldp-ext:fec-label* | | | [masklen rp group-address rd] | | | +--ro mldp-ext:masklen | | | | uint8 | | | +--ro mldp-ext:rp | | | | inet:ipv4-address | | | +--ro mldp-ext:group-address | | | | inet:ipv4-address | | | +--ro mldp-ext:rd | | | | rt-types:route-distinguisher | | | +--ro mldp-ext:multipoint-type? | | | | mldp:multipoint-type | | | +--ro mldp-ext:opaque-value-element-type? | | | | identityref | | | +--ro mldp-ext:peer* | | | [direction peer advertisement-type] | | | +--ro mldp-ext:peer | | | | leafref | | | +--ro mldp-ext:direction | | | | ldp:downstream-upstream | | | +--ro mldp-ext:advertisement-type | | | | ldp:advertised-received | | | +--ro mldp-ext:label? | | | | rt-types:mpls-label | | | +--ro mldp-ext:mbb-status? | | | | lsp-mbb-role | | | +--ro mldp-ext:mofrr-status? | | | lsp-mofrr-role | | +--ro mldp-ext:opaque-value-element-recursive | | +--ro mldp-ext:fec-label* [rd opaque-value] | | +--ro mldp-ext:rd | | | rt-types:route-distinguisher | | +--ro mldp-ext:opaque-value | | | binary | | +--ro mldp-ext:multipoint-type? | | | mldp:multipoint-type | | +--ro mldp-ext:opaque-value-element-type? | | | identityref | | +--ro mldp-ext:peer* | | [direction peer advertisement-type] | | +--ro mldp-ext:peer | | | leafref Raza, et al. Expires 20 May 2027 [Page 72] Internet-Draft A YANG Model for MPLS mLDP November 2026 | | +--ro mldp-ext:direction | | | ldp:downstream-upstream | | +--ro mldp-ext:advertisement-type | | | ldp:advertised-received | | +--ro mldp-ext:label? | | | rt-types:mpls-label | | +--ro mldp-ext:mbb-status? | | | lsp-mbb-role | | +--ro mldp-ext:mofrr-status? | | lsp-mofrr-role | +--rw mldp-ext:multicast-only-frr {mldp-mofrr}? | | +--rw mldp-ext:prefix-list? ldp-ext:prefix-list-ref | +--rw mldp-ext:recursive-fec | +--rw mldp-ext:prefix-list? ldp-ext:prefix-list-ref +--rw mldp-ext:ipv6! +--rw mldp-ext:enabled? boolean +--ro mldp-ext:roots | +--ro mldp-ext:root* [root-address] | +--ro mldp-ext:root-address inet:ipv6-address | +--ro mldp-ext:is-self? boolean | +--ro mldp-ext:reachability* [address interface] | | +--ro mldp-ext:address inet:ipv6-address | | +--ro mldp-ext:interface if:interface-ref | | +--ro mldp-ext:peer? leafref | +--ro mldp-ext:bindings | +--ro mldp-ext:opaque-value-element-lspid | | +--ro mldp-ext:fec-label* [lsp-id] | | +--ro mldp-ext:lsp-id | | | uint32 | | +--ro mldp-ext:multipoint-type? | | | mldp:multipoint-type | | +--ro mldp-ext:opaque-value-element-type? | | | identityref | | +--ro mldp-ext:peer* | | [direction peer advertisement-type] | | +--ro mldp-ext:peer | | | leafref | | +--ro mldp-ext:direction | | | ldp:downstream-upstream | | +--ro mldp-ext:advertisement-type | | | ldp:advertised-received | | +--ro mldp-ext:label? | | | rt-types:mpls-label | | +--ro mldp-ext:mbb-status? | | | lsp-mbb-role | | +--ro mldp-ext:mofrr-status? | | lsp-mofrr-role | +--ro mldp-ext:opaque-value-element-transit-source Raza, et al. Expires 20 May 2027 [Page 73] Internet-Draft A YANG Model for MPLS mLDP November 2026 | | +--ro mldp-ext:fec-label* | | [source-address group-address rd] | | +--ro mldp-ext:source-address | | | inet:ipv6-address | | +--ro mldp-ext:group-address | | | inet:ipv6-address | | +--ro mldp-ext:rd | | | rt-types:route-distinguisher | | +--ro mldp-ext:multipoint-type? | | | mldp:multipoint-type | | +--ro mldp-ext:opaque-value-element-type? | | | identityref | | +--ro mldp-ext:peer* | | [direction peer advertisement-type] | | +--ro mldp-ext:peer | | | leafref | | +--ro mldp-ext:direction | | | ldp:downstream-upstream | | +--ro mldp-ext:advertisement-type | | | ldp:advertised-received | | +--ro mldp-ext:label? | | | rt-types:mpls-label | | +--ro mldp-ext:mbb-status? | | | lsp-mbb-role | | +--ro mldp-ext:mofrr-status? | | lsp-mofrr-role | +--ro mldp-ext:opaque-value-element-transit-bidir | | +--ro mldp-ext:fec-label* | | [masklen rp group-address rd] | | +--ro mldp-ext:masklen | | | uint8 | | +--ro mldp-ext:rp | | | inet:ipv6-address | | +--ro mldp-ext:group-address | | | inet:ipv6-address | | +--ro mldp-ext:rd | | | rt-types:route-distinguisher | | +--ro mldp-ext:multipoint-type? | | | mldp:multipoint-type | | +--ro mldp-ext:opaque-value-element-type? | | | identityref | | +--ro mldp-ext:peer* | | [direction peer advertisement-type] | | +--ro mldp-ext:peer | | | leafref | | +--ro mldp-ext:direction | | | ldp:downstream-upstream | | +--ro mldp-ext:advertisement-type Raza, et al. Expires 20 May 2027 [Page 74] Internet-Draft A YANG Model for MPLS mLDP November 2026 | | | ldp:advertised-received | | +--ro mldp-ext:label? | | | rt-types:mpls-label | | +--ro mldp-ext:mbb-status? | | | lsp-mbb-role | | +--ro mldp-ext:mofrr-status? | | lsp-mofrr-role | +--ro mldp-ext:opaque-value-element-recursive | +--ro mldp-ext:fec-label* [rd opaque-value] | +--ro mldp-ext:rd | | rt-types:route-distinguisher | +--ro mldp-ext:opaque-value | | binary | +--ro mldp-ext:multipoint-type? | | mldp:multipoint-type | +--ro mldp-ext:opaque-value-element-type? | | identityref | +--ro mldp-ext:peer* | [direction peer advertisement-type] | +--ro mldp-ext:peer | | leafref | +--ro mldp-ext:direction | | ldp:downstream-upstream | +--ro mldp-ext:advertisement-type | | ldp:advertised-received | +--ro mldp-ext:label? | | rt-types:mpls-label | +--ro mldp-ext:mbb-status? | | lsp-mbb-role | +--ro mldp-ext:mofrr-status? | lsp-mofrr-role +--rw mldp-ext:multicast-only-frr {mldp-mofrr}? | +--rw mldp-ext:prefix-list? ldp-ext:prefix-list-ref +--rw mldp-ext:recursive-fec +--rw mldp-ext:prefix-list? ldp-ext:prefix-list-ref notifications: +---n mpls-mldp-fec-event +--ro event-type? | ldp:oper-status-event-type +--ro (opaque-value-element)? +--:(opaque-value-element-lspid) | +--ro opaque-value-element-lspid | +--ro root-address? inet:ip-address | +--ro lsp-id? uint32 | +--ro multipoint-type? multipoint-type | +--ro mldp-ext:recursive-fec | +--ro mldp-ext:recur-root-address? Raza, et al. Expires 20 May 2027 [Page 75] Internet-Draft A YANG Model for MPLS mLDP November 2026 | inet:ip-address +--:(mldp-ext:opaque-value-element-transit-source) | +--ro mldp-ext:opaque-value-element-transit-source | +--ro mldp-ext:root-address? inet:ip-address | +--ro mldp-ext:source-address? inet:ip-address | +--ro mldp-ext:group-address? inet:ip-address | +--ro mldp-ext:rd? | | rt-types:route-distinguisher | +--ro mldp-ext:recur-root-address? inet:ip-address | +--ro mldp-ext:recur-rd? | rt-types:route-distinguisher +--:(mldp-ext:opaque-value-element-transit-bidir) +--ro mldp-ext:opaque-value-element-transit-bidir +--ro mldp-ext:root-address? inet:ip-address +--ro mldp-ext:masklen? uint8 +--ro mldp-ext:rp? inet:ip-address +--ro mldp-ext:group-address? inet:ip-address +--ro mldp-ext:rd? | rt-types:route-distinguisher +--ro mldp-ext:recur-root-address? inet:ip-address +--ro mldp-ext:recur-rd? rt-types:route-distinguisher module: ietf-mpls-mldp-extended augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/ldp:mpls-ldp/ldp:global /ldp-ext:forwarding-nexthop/ldp-ext:interfaces /ldp-ext:interface/ldp-ext:address-family: +--rw mldp-disable? boolean Figure 14: Complete tree Appendix B. Data Tree Example This section contains an example of an instance data tree in the JSON encoding [RFC7951], containing both configuration and state data. Raza, et al. Expires 20 May 2027 [Page 76] Internet-Draft A YANG Model for MPLS mLDP November 2026 lo0: 2001:db8:0:200::1 (Root Address) +-------+ | | Router| | eth21 +---+ R2 +---+ eth23 | | (Root)| | | +-------+ | lo0: 2001:db8:0:300::1 | +-------+ | | +-------+ | | | Router| | | | Router| | eth10 +--+ R1 +---+ eth12 eth32 +---+ R3 +--+ eth30 | | | | | | | | | +-------+ | | +-------+ | lo0: 2001:db8:0:200::1 (Root Address) The configuration instance data tree for Router R3 in the above figure could be as follows: { "ietf-interfaces:interfaces": { "interface": [ { "name": "lo0", "description": "R3 loopback interface.", "type": "iana-if-type:softwareLoopback", "ietf-ip:ipv6": { "address": [ { "ip": "2001:db8:0:300::1", "prefix-length": 64 } ] } }, { "name": "eth30", "description": "An interface connected to client routers.", "type": "iana-if-type:ethernetCsmacd", "ietf-ip:ipv6": { "forwarding": true } }, { "name": "eth32", "description": "An interface connected to root (R2).", "type": "iana-if-type:ethernetCsmacd", "ietf-ip:ipv6": { "forwarding": true } Raza, et al. Expires 20 May 2027 [Page 77] Internet-Draft A YANG Model for MPLS mLDP November 2026 } ] }, "ietf-routing:routing": { "router-id": "203.0.113.3", "control-plane-protocols": { "ietf-mpls-ldp:mpls-ldp": { "global": { "address-families": { "ietf-mpls-ldp-extended:ipv6": { "enable": true } }, "capability": { "ietf-mpls-mldp:mldp": { "mp2mp": { "enable": true } } }, "ietf-mpls-mldp:mldp": { "enable": true, "address-families": { "ietf-mpls-mldp-extended:ipv6": { "roots": { "root": [ { "root-address": "2001:db8:0:200::1" } ] } } } } } }, "discovery": { "interfaces": { "interface": [ { "name": "eth30", "address-families": { "ietf-mpls-ldp-extended:ipv6": { "enable": true } } }, { "name": "eth32", "address-families": { "ietf-mpls-ldp-extended:ipv6": { "enable": true Raza, et al. Expires 20 May 2027 [Page 78] Internet-Draft A YANG Model for MPLS mLDP November 2026 } } } ] } } } } } } The corresponding operational state data for Router R3 could be as follows: { "ietf-interfaces:interfaces": { "interface": [ { "name": "lo0", "description": "R3 loopback interface.", "type": "iana-if-type:softwareLoopback", "phys-address": "00:00:5e:00:53:03", "oper-status": "up", "statistics": { "discontinuity-time": "2018-10-15T12:34:56-05:00" }, "ietf-ip:ipv6": { "mtu": 1500, "address": [ { "ip": "2001:db8:0:300::1", "prefix-length": 64, "origin": "static", "status": "preferred" }, { "ip": "fe80::200:5eff:fe00:5303", "prefix-length": 64, "origin": "link-layer", "status": "preferred" } ], "neighbor": [ ] } }, { "name": "eth30", Raza, et al. Expires 20 May 2027 [Page 79] Internet-Draft A YANG Model for MPLS mLDP November 2026 "description": "An interface connected to client routers.", "type": "iana-if-type:ethernetCsmacd", "phys-address": "00:00:5e:00:53:30", "oper-status": "up", "statistics": { "discontinuity-time": "2018-10-15T12:34:56-05:00" }, "ietf-ip:ipv6": { "forwarding": true, "mtu": 1500, "address": [ { "ip": "fe80::200:5eff:fe00:5330", "prefix-length": 64, "origin": "link-layer", "status": "preferred" } ], "neighbor": [ ] } }, { "name": "eth32", "description": "An interface connected to root (R2).", "type": "iana-if-type:ethernetCsmacd", "phys-address": "00:00:5e:00:53:32", "oper-status": "up", "statistics": { "discontinuity-time": "2018-10-15T12:34:56-05:00" }, "ietf-ip:ipv6": { "forwarding": true, "mtu": 1500, "address": [ { "ip": "fe80::200:5eff:fe00:5332", "prefix-length": 64, "origin": "link-layer", "status": "preferred" } ], "neighbor": [ { "ip": "fe80::200:5eff:fe00:5323", "link-layer-address": "00:00:5e:00:53:23", "origin": "dynamic", "is-router": [null], Raza, et al. Expires 20 May 2027 [Page 80] Internet-Draft A YANG Model for MPLS mLDP November 2026 "state": "reachable" } ] } } ] }, "ietf-routing:routing": { "router-id": "203.0.113.3", "interfaces": { "interface": [ "lo0", "eth30", "eth32" ] }, "control-plane-protocols": { "ietf-mpls-ldp:mpls-ldp": { "global": { "address-families": { "ietf-mpls-ldp-extended:ipv6": { "enable": true } }, "capability": { "ietf-mpls-mldp:mldp": { "mp2mp": { "enable": true } } }, "ietf-mpls-mldp:mldp": { "enable": true, "address-families": { "ietf-mpls-mldp-extended:ipv6": { "roots": { "root": [ { "root-address": "2001:db8:0:200::1", "is-self": false, "reachability": [ { "address": "fe80::200:5eff:fe00:5323", "interface": "eth32", "peer": "203.0.113.2" } ], "bindings": { Raza, et al. Expires 20 May 2027 [Page 81] Internet-Draft A YANG Model for MPLS mLDP November 2026 "opaque-element-lspid": { "fec-label": [ { "lsp-id": 201, "multipoint-type": "mp2mp", "peer": [ { "direction": "upstream", "peer": "203.0.113.2", "advertisement-type": "advertised", "label": 3201 }, { "direction": "upstream", "peer": "203.0.113.2", "advertisement-type": "received", "label": 2301 } ] } ] } } } ] } } } } }, "discovery": { "interfaces": { "interface": [ { "name": "eth30", "address-families": { "ietf-mpls-ldp-extended:ipv6": { "enable": true, "hello-adjacencies": { "hello-adjacency": [ ] } } } }, { "name": "eth32", "address-families": { Raza, et al. Expires 20 May 2027 [Page 82] Internet-Draft A YANG Model for MPLS mLDP November 2026 "ietf-mpls-ldp-extended:ipv6": { "enable": true, "hello-adjacencies": { "hello-adjacency": [ { "adjacent-address": "fe80::200:5eff:fe00:5323", "flag": ["adjacency-flag-active"], "hello-holdtime": { "adjacent": 15, "negotiated": 15, "remaining": 9 }, "next-hello": 3, "statistics": { "discontinuity-time": "2018-10-15T12:34:56-05:00" }, "peer": { "lsr-id": "203.0.113.2", "label-space-id": 0 } } ] } } } } ] } }, "peers": { "peer": [ { "lsr-id": "203.0.113.2", "label-space-id": 0, "label-advertisement-mode": { "local": "downstream-unsolicited", "peer": "downstream-unsolicited", "negotiated": "downstream-unsolicited" }, "next-keep-alive": 5, "session-holdtime": { "peer": 180, "negotiated": 180, "remaining": 78 }, "session-state": "operational", Raza, et al. Expires 20 May 2027 [Page 83] Internet-Draft A YANG Model for MPLS mLDP November 2026 "tcp-connection": { "local-address": "fe80::200:5eff:fe00:5332", "local-port": 646, "remote-address": "fe80::200:5eff:fe00:5323", "remote-port": 646 }, "up-time": "P2H33M5S", "statistics": { "discontinuity-time": "2018-10-15T12:34:56-05:00" }, "received-peer-state": { "capability": { "ietf-mpls-mldp:mldp": { "mp2mp": { "enable": true } } } } } ] } } } } } Appendix C. Acknowledgments The authors would like to acknowledge Ladislav Lhotka, Acee Lindem, and Sowmya Krishnaswamy for their review and comments. Appendix D. Contributors Rajiv Asati Individual Email: Rajiv.ASATI@gmail.com Xia Chen Huawei Technologies Email: xiachen002@outlook.com Raza, et al. Expires 20 May 2027 [Page 84] Internet-Draft A YANG Model for MPLS mLDP November 2026 Himanshu Shah Ciena Corporation Email: hshah@ciena.com Matthew Bocci Nokia Email: matthew.bocci@nokia.com Authors' Addresses Kamran Raza (editor) Cisco Systems Email: skraza@cisco.com Xufeng Liu Individual Email: xufeng.liu.ietf@gmail.com Santosh Easale Juniper Networks Email: santosh_easale@berkeley.edu Loa Andersson Huawei Technologies Email: loa@pi.nu Jeff Tantsura Microsoft Corporation Email: jefftant.ietf@gmail.com Raza, et al. Expires 20 May 2027 [Page 85]