TEAS V. P. Beeram Internet-Draft K. Kompella Intended status: Standards Track HPE Expires: 6 May 2027 2 November 2026 A YANG Data Model for Multipath Traffic Engineering Directed Acyclic Graph (MPTED) Tunnels and Junctions draft-beeram-teas-yang-mpted-05 Abstract This document defines a YANG data model for representing, retrieving, and manipulating Multipath Traffic Engineering Directed Acyclic Graph (MPTED) tunnels and junctions. The model includes two YANG modules, one for managing MPTED tunnels on an MPTED tunnel originator node and the other for managing MPTED junctions on an MPTED junction node. 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 6 May 2027. Copyright Notice Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved. 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. Beeram & Kompella Expires 6 May 2027 [Page 1] Internet-Draft MPTED YANG Model November 2026 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.3. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 3 2. MPTED YANG Module . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Model Structure . . . . . . . . . . . . . . . . . . . . . 3 2.2. YANG Code . . . . . . . . . . . . . . . . . . . . . . . . 4 3. MPTED-JCT YANG Module . . . . . . . . . . . . . . . . . . . . 22 3.1. Model Structure . . . . . . . . . . . . . . . . . . . . . 22 3.2. YANG Code . . . . . . . . . . . . . . . . . . . . . . . . 23 4. Security Considerations . . . . . . . . . . . . . . . . . . . 30 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 32 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 32 7.1. Normative References . . . . . . . . . . . . . . . . . . 32 7.2. Informative References . . . . . . . . . . . . . . . . . 33 Appendix A. MPTED YANG Module - Complete Tree Structure . . . . 33 Appendix B. MPTED-JCT YANG Module - Complete Tree Structure . . 35 Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 37 1. Introduction The notions of a Multipath Traffic Engineering Directed Acyclic Graph (MPTED) tunnel and an MPTED junction are introduced in [I-D.draft-kompella-teas-mpte]. An MPTED tunnel is a Traffic Engineering (TE) construct that contains a constrained set of paths representing an optimized Directed Acyclic Graph (DAG) from one or more ingresses to one or more egresses. The paths that make up an MPTED tunnel traverse a set of junction nodes. An MPTED junction refers to the construct associated with the MPTED tunnel at each junction node and constitutes a set of previous-hops and a set of next-hops over which traffic is load-balanced in a weighted fashion. Provisioning an MPTED tunnel in a TE network involves provisioning MPTED junction state at each junction node. An MPTED tunnel is instantiated and managed on a tunnel originator node, while an MPTED junction is instantiated and managed on a junction node. A tunnel originator node may also be a junction node. This document defines a YANG data model for representing, retrieving, and manipulating MPTED tunnels and junctions. The model includes two YANG modules, one for managing MPTED tunnels on a tunnel originator node and the other for managing MPTED junctions on a junction node. Beeram & Kompella Expires 6 May 2027 [Page 2] Internet-Draft MPTED YANG Model November 2026 The YANG modules discussed in this version of the document are scoped to MPLS MPTED tunnels and junctions with signaled label switching. The coverage for other types of MPTED tunnels and junctions will be added in later versions. The provisioning of MPTED tunnels using RSVP-TE is described in [I-D.kbr-teas-mptersvp]. 1.1. Requirements Language 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. 1.2. Terminology The terminology for describing YANG data models is found in [RFC7950]. The reader is expected to be familiar with the terminology used in [I-D.draft-kompella-teas-mpte]. 1.3. Tree Diagram A simplified graphical representation of the data model is used in Appendix A and Appendix B of this document. The meaning of the symbols in these diagrams is defined in [RFC8340]. 2. MPTED YANG Module 2.1. Model Structure The high-level model structure for MPTED tunnels defined by this document is as shown below: Beeram & Kompella Expires 6 May 2027 [Page 3] Internet-Draft MPTED YANG Model November 2026 module: ietf-mpted augment /te:te: +--rw mpted-tunnels +--rw tunnel* [originator identifier] +--rw originator inet:ip-address +--rw identifier uint32 + .. +--ro instances +--ro instance* [instance-id] +--ro instance-id uint32 + .. +--ro junctions +--ro junction* [node-id] +--ro node-id inet:ip-address + .. +--ro phops | +--ro phop* | [hop-address hop-index hop-version] | +--ro hop-address inet:ip-address | +--ro hop-index uint32 | +--ro hop-version uint32 + .. +--ro nhops +--ro nhop* [hop-address hop-index hop-version] +--ro hop-address | inet:ip-address +--ro hop-index uint32 +--ro hop-version uint32 + .. Figure 1: MPTED YANG Structure The top-level 'te' container in [I-D.draft-ietf-teas-yang-te] is augmented with a set of MPTED tunnels. The 'mpted-tunnels' container carries a list of tunnel entries. Each tunnel entry includes the set of parameters required to produce a list of junctions that need to be programmed in the network. Each tunnel entry may have more than one instance associated with it, where a unique instance-id identifies each instance. Each tunnel instance has a list of junctions associated with it. Each junction entry consists of the set of previous-hops ('phops' container) and next-hops ('nhops' container). 2.2. YANG Code Beeram & Kompella Expires 6 May 2027 [Page 4] Internet-Draft MPTED YANG Model November 2026 file "ietf-mpted@2026-11-02.yang" module ietf-mpted { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-mpted"; prefix mpted; import ietf-te { prefix te; reference "draft-ietf-teas-yang-te: A YANG Data Model for Traffic Engineering Tunnels, Label Switched Paths, and Interfaces"; } import ietf-routing-types { prefix rt-types; reference "RFC8294: Common YANG Data Types for the Routing Area"; } import ietf-inet-types { prefix inet; reference "RFC6991: Common YANG Data Types"; } organization "IETF Traffic Engineering Architecture and Signaling (TEAS) Working Group."; contact "WG Web: WG List: Editor: Vishnu Pavan Beeram Editor: Kireeti Kompella "; description "This module defines a YANG data model for Multipath Traffic Engineering Directed Acyclic Graph (MPTED) tunnels. It is intended to be used as part of the IETF TEAS framework to enable the configuration and management of MPTED tunnels on an MPTED tunnel originator. 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 Beeram & Kompella Expires 6 May 2027 [Page 5] Internet-Draft MPTED YANG Model 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 (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself for full legal notices."; revision 2026-11-02 { description "Initial revision. This revision introduces the YANG data model for Multipath Traffic Engineering Directed Acyclic Graph (MPTED) tunnels."; reference "RFC XXXX: A YANG Data Model for Multipath Traffic Engineering Directed Acyclic Graph (MPTED) Tunnels and Junctions"; } identity mpted-tunnel-type { description "Base identity of MPTED tunnel type."; } identity mpted-tunnel-type-mpls-siglab { base mpted-tunnel-type; description "MPLS MPTED tunnel with signaled label switching."; } identity mpted-signaling-type { description "Base identity for MPTED signaling type."; } identity mpted-signaling-rsvp { base mpted-signaling-type; description "MPTED RSVP signaling."; reference "draft-kbr-teas-mptersvp: RSVP-TE Extensions for Multipath Traffic Engineered Directed Acyclic Graph Tunnels"; } identity mpted-signaling-pcep { base mpted-signaling-type; description Beeram & Kompella Expires 6 May 2027 [Page 6] Internet-Draft MPTED YANG Model November 2026 "MPTED PCEP signaling."; } identity mpted-signaling-bgp { base mpted-signaling-type; description "MPTED BGP signaling."; } identity mpted-signaling-grpc { base mpted-signaling-type; description "MPTED gRPC signaling."; } identity mpted-tunnel-status { description "Base identity for MPTED tunnel status."; } identity mpted-tunnel-up { base mpted-tunnel-status; description "MPTED tunnel is up."; } identity mpted-tunnel-down { base mpted-tunnel-status; description "MPTED tunnel is down."; } identity mpted-tunnel-degraded { base mpted-tunnel-status; description "MPTED tunnel is degraded."; } identity mpted-junction-status { description "Base identity for MPTED JUNCTION status."; } identity mpted-junction-up { base mpted-junction-status; description "MPTED JUNCTION Up."; } Beeram & Kompella Expires 6 May 2027 [Page 7] Internet-Draft MPTED YANG Model November 2026 identity mpted-junction-down { base mpted-junction-status; description "MPTED JUNCTION Down."; } identity mpted-junction-degraded { base mpted-junction-status; description "MPTED JUNCTION Degraded."; } identity mpted-jct-phop-status { description "Base identity for MPTED JCT-PHOP status."; } identity mpted-jct-phop-up { base mpted-jct-phop-status; description "MPTED JCT-PHOP Up."; } identity mpted-jct-phop-down { base mpted-jct-phop-status; description "MPTED JCT-PHOP Down."; } identity mpted-jct-nhop-status { description "Base identity for MPTED JCT-NHOP status."; } identity mpted-jct-nhop-up { base mpted-jct-nhop-status; description "MPTED JCT-NHOP Up."; } identity mpted-jct-nhop-down { base mpted-jct-nhop-status; description "MPTED JCT-NHOP Down."; } identity mpted-jct-nhop-degraded { Beeram & Kompella Expires 6 May 2027 [Page 8] Internet-Draft MPTED YANG Model November 2026 base mpted-jct-nhop-status; description "MPTED JCT-NHOP Degraded."; } identity mpted-opt-metric-type { description "Base identity of MPTED optimization metric type."; } identity mpted-opt-metric-te { base mpted-opt-metric-type; description "TE Metric."; } identity mpted-opt-metric-igp { base mpted-opt-metric-type; description "IGP Metric."; } identity mpted-opt-metric-delay { base mpted-opt-metric-type; description "Delay Metric."; } identity mpted-bw-spec-type { description "Base identity for MPTED bandwidth specification type."; } identity mpted-bw-spec-explicit { base mpted-bw-spec-type; description "Explicit MPTED bandwidth specification type."; } identity mpted-bw-spec-auto { base mpted-bw-spec-type; description "Automatic MPTED bandwidth specification type."; } grouping mpted-ingress { description Beeram & Kompella Expires 6 May 2027 [Page 9] Internet-Draft MPTED YANG Model November 2026 "Grouping for MPTED ingress information."; leaf ingress-id { type inet:ip-address; description "IP-address of the ingress node."; } leaf set-bandwidth { when "derived-from-or-self(../../../bandwidth-spec-type, " + "'mpted:mpted-bw-spec-explicit')" { description "Applicable only when bandwidth specification type is explicit."; } type uint64; units "bytes per second"; description "Explicitly specified bandwidth at the ingress of the MPTED tunnel."; } container auto-bandwidth { when "derived-from-or-self(../../../bandwidth-spec-type, " + "'mpted:mpted-bw-spec-auto')" { description "Applicable only when bandwidth specification type is automatic."; } description "Container for auto-bandwidth parameters."; uses mpted-ingress-autobw-config; container overflow { description "Auto-bandwidth overflow parameters."; uses mpted-autobw-overflow-config; } container underflow { description "Auto-bandwidth underflow parameters."; uses mpted-autobw-underflow-config; } } } grouping mpted-ingress-autobw-config { description "MPTED tunnel ingress auto-bandwidth parameters."; leaf min-bw { type uint64; Beeram & Kompella Expires 6 May 2027 [Page 10] Internet-Draft MPTED YANG Model November 2026 units "bytes per second"; description "Minimum bandwidth at the ingress of the auto-bandwidth enabled MPTED tunnel."; } leaf max-bw { type uint64; units "bytes per second"; description "Maximum bandwidth at the ingress of the auto-bandwidth enabled MPTED tunnel."; } leaf adjust-threshold { type rt-types:percentage; description "Bandwidth demand at the ingress for the current bandwidth adjustment interval is compared to the current bandwidth allocation for the ingress of the MPTED tunnel. If the percentage difference in bandwidth is greater than or equal to the percentage specified by this leaf, the bandwidth allocation for the ingress is adjusted to the current bandwidth demand."; } } grouping mpted-autobw-overflow-config { description "MPTED tunnel ingress auto-bandwidth overflow parameters."; leaf enabled { type boolean; default "false"; description "Enables auto-bandwidth overflow adjustment on the MPTED tunnel ingress."; } leaf overflow-threshold { type rt-types:percentage; description "Bandwidth percentage change to trigger an overflow event"; } leaf trigger-event-count { type uint16; description "Number of consecutive overflow sample events needed to trigger an overflow adjustment"; } Beeram & Kompella Expires 6 May 2027 [Page 11] Internet-Draft MPTED YANG Model November 2026 } grouping mpted-autobw-underflow-config { description "MPTED tunnel ingress auto-bandwidth underflow parameters."; leaf enabled { type boolean; default "false"; description "Enables auto-bandwidth underflow adjustment on the MPTED tunnel ingress."; } leaf underflow-threshold { type rt-types:percentage; description "Bandwidth percentage change to trigger an underflow event"; } leaf trigger-event-count { type uint16; description "Number of consecutive underflow sample events needed to trigger an underflow adjustment"; } } grouping tunnel-status-info { description "Grouping for tunnel status information."; leaf current-version { type uint32; config false; description "Current version of the MPTED tunnel."; } leaf status { type identityref { base mpted-tunnel-status; } config false; description "Status of the MPTED tunnel"; } leaf max-flow-throughput { type uint64; units "bytes per second"; config false; description Beeram & Kompella Expires 6 May 2027 [Page 12] Internet-Draft MPTED YANG Model November 2026 "Max-flow throughput of the MPTED DAG of the instance of the tunnel that is currently in use, i.e., the maximum bandwidth that the DAG can carry from the ingress nodes to the egress nodes."; } leaf min-metric { type uint64; config false; description "Metric of the best ingress-to-egress path in the MPTED DAG of the instance of the tunnel that is currently in use. The units are those of the optimization-metric."; } leaf max-metric { type uint64; config false; description "Metric of the worst ingress-to-egress path in the MPTED DAG of the instance of the tunnel that is currently in use. The units are those of the optimization-metric."; } } grouping tunnel-instance-status-info { description "Grouping for tunnel instance status information."; leaf instance-id { type uint32; config false; description "Identifier of the MPTED tunnel instance."; } leaf status { type identityref { base mpted-tunnel-status; } config false; description "Status of the MPTED tunnel instance"; } } grouping junction-info { description "Grouping for junction information."; leaf node-id { type inet:ip-address; Beeram & Kompella Expires 6 May 2027 [Page 13] Internet-Draft MPTED YANG Model November 2026 description "IP-address of the junction node."; } leaf current-jct-instance { type uint32; description "Current instance identifier of the MPTED tunnel junction."; } leaf bandwidth-requested { type uint64; units "bytes per second"; description "Bandwidth to be reserved for the junction. A value of zero means that no bandwidth is reserved."; } } grouping junction-status-info { description "Grouping for junction status information."; uses junction-info; leaf mtu { type uint16; description "MTU at the junction node. This is the smallest MTU value among the MTUs received from all JCT-NHOPs."; } leaf status { type identityref { base mpted-junction-status; } description "Status of the JUNCTION."; } } grouping mpted-jct-hop-info { description "Grouping for junction hop information."; leaf hop-address { type inet:ip-address; description "IP-address of the peer."; } leaf hop-index { type uint32; description "Index of the peer interface."; Beeram & Kompella Expires 6 May 2027 [Page 14] Internet-Draft MPTED YANG Model November 2026 } leaf hop-version { type uint32; description "Version of the Hop."; } } grouping mpted-jct-phop-status-info { description "Grouping for junction phop status information."; uses mpted-jct-hop-info; leaf in-label { type rt-types:mpls-label; description "Label used by incoming packets on the JCT-PHOP."; } leaf status { type identityref { base mpted-jct-phop-status; } description "Status of the JCT-PHOP."; } } grouping mpted-jct-nhop-info { description "Grouping for junction nhop information."; uses mpted-jct-hop-info; leaf backup { type boolean; description "Indicates that the JCT-NHOP is a backup next-hop."; } leaf load-share { type uint16; config false; description "Effective relative load share of the JCT-NHOP. It is derived from the bandwidth-requested values of the JCT-NHOPs of the junction. It is zero for a JCT-NHOP that is not active, and it is the same for all active JCT-NHOPs if their bandwidth-requested values are all zero."; } leaf bandwidth-requested { Beeram & Kompella Expires 6 May 2027 [Page 15] Internet-Draft MPTED YANG Model November 2026 type uint64; units "bytes per second"; description "Bandwidth value of the JCT-NHOP, which determines its load share. Only the ratio of these values across the JCT-NHOPs of a junction is used. It does not by itself cause a bandwidth reservation."; } } grouping mpted-jct-nhop-status-info { description "Grouping for junction nhop status information."; uses mpted-jct-nhop-info; leaf bandwidth-reserved { type uint64; units "bytes per second"; description "Amount of bandwidth reserved on the TE link associated with the JCT-NHOP. It is zero if the bandwidth of the junction is zero. It is also zero for a backup JCT-NHOP, because the RSVP-TE signaling for MPTED tunnels (draft-kbr-teas-mptersvp) does not reserve bandwidth toward backup next-hops."; } leaf out-label { type rt-types:mpls-label; description "Label used by outgoing packets on the JCT-NHOP."; } leaf status { type identityref { base mpted-jct-nhop-status; } description "Status of the JCT-NHOP."; } } grouping dag-span-constraints { description "Grouping for parameters that control the span of the MPTED DAG."; leaf max-jcts { type uint16; description "Maximum number of junctions in the DAG."; } Beeram & Kompella Expires 6 May 2027 [Page 16] Internet-Draft MPTED YANG Model November 2026 leaf min-nhops { type uint16; description "Minimum number of next-hops per junction."; } leaf max-nhops { type uint16; description "Maximum number of next-hops per junction."; } } grouping hop-constraints { description "Grouping for parameters that constrain hops of the MPTED DAG."; leaf minimum-bandwidth { type uint64; units "bytes per second"; description "Minimum bandwidth per hop of the MPTED DAG."; } } augment "/te:te" { description "Augmentation for MPTED tunnels."; container mpted-tunnels { description "Container for MPTED tunnels."; list tunnel { key "originator identifier"; unique "name"; description "MPTED tunnel entry."; leaf originator { type inet:ip-address; description "IP address of the MPTED tunnel originator."; } leaf identifier { type uint32; description "Identifier of the MPTED tunnel."; } leaf name { type string; Beeram & Kompella Expires 6 May 2027 [Page 17] Internet-Draft MPTED YANG Model November 2026 description "Name of the MPTED tunnel."; } leaf description { type string; description "Textual description of the MPTED tunnel."; } container ingresses { description "Container for list of MPTED ingresses."; list ingress { key "ingress-id"; description "MPTED ingress entry."; uses mpted-ingress; } } leaf-list egress { type inet:ip-address; description "List of egress nodes associated with the MPTED tunnel."; } leaf type { type identityref { base mpted-tunnel-type; } description "Type of tunnel."; } leaf setup-priority { type uint8 { range "0..7"; } default "7"; description "The priority of the MPTED tunnel with respect to taking resources, in the range of 0 to 7. The value 0 is the highest priority."; } leaf hold-priority { type uint8 { range "0..7"; } default "7"; description "The priority of the MPTED tunnel with respect to Beeram & Kompella Expires 6 May 2027 [Page 18] Internet-Draft MPTED YANG Model November 2026 holding resources, in the range of 0 to 7. The value 0 is the highest priority."; } leaf optimization-metric { type identityref { base mpted-opt-metric-type; } description "Metric type for which the DAG is optimized."; } leaf metric-margin { type uint32; description "Metric margin for path selection. A path whose metric is within this margin of the optimal metric is considered acceptable."; } uses dag-span-constraints; container resource-affinities { description "Resource-affinity constraints."; leaf-list exclude-any { type string; description "Exclude the link if it has any of these affinities."; } leaf-list include-any { type string; description "Include the link if it has any of these affinities"; } leaf-list include-all { type string; description "Include the link if it has all these affinities"; } } leaf bandwidth-spec-type { type identityref { base mpted-bw-spec-type; } description "The method used for setting the bandwidth on the tunnel, either explicitly specified or automatically derived."; } Beeram & Kompella Expires 6 May 2027 [Page 19] Internet-Draft MPTED YANG Model November 2026 leaf auto-bandwidth-adjust-interval { when "derived-from-or-self(../bandwidth-spec-type, " + "'mpted:mpted-bw-spec-auto')" { description "Applicable only when bandwidth specification type is automatic."; } type uint32; units "seconds"; description "Time in seconds between auto-bandwidth adjustments."; } leaf mpted-computer { type inet:ip-address; description "IP-address of the MPTED computer."; } leaf signaling-type { type identityref { base mpted-signaling-type; } description "MPTED tunnel signaling type."; } leaf signaling-source { type inet:ip-address; description "IP-address of the MPTED tunnel signaling source."; } container hop { description "Hop constraint parameters for the MPTED tunnel."; uses hop-constraints; } leaf compute-only { type boolean; default "false"; description "When set to true, the MPTED DAG is computed but not signaled."; } leaf retry-timer { type uint16; units "seconds"; description "Timer interval for retrying tunnel setup after a failure."; Beeram & Kompella Expires 6 May 2027 [Page 20] Internet-Draft MPTED YANG Model November 2026 } leaf optimize-timer { type uint16; units "seconds"; description "Timer interval for periodic path reoptimization."; } leaf-list exclude-hops { type inet:ip-address; description "List of node addresses to exclude from path computation."; } uses tunnel-status-info; container instances { config false; description "Container for list of instances of the MPTED tunnel."; list instance { key "instance-id"; description "MPTED tunnel instance entry."; uses tunnel-instance-status-info; container junctions { description "Container for list of JUNCTIONs associated with the MPTED tunnel instance."; list junction { key "node-id"; description "JUNCTION entry."; uses junction-status-info; container phops { description "Container for associated JCT-PHOPs."; list phop { key "hop-address hop-index hop-version"; description "JCT-PHOP entry."; uses mpted-jct-phop-status-info; } } container nhops { description "Container for associated JCT-NHOPs."; list nhop { Beeram & Kompella Expires 6 May 2027 [Page 21] Internet-Draft MPTED YANG Model November 2026 key "hop-address hop-index hop-version"; description "JCT-NHOP entry."; uses mpted-jct-nhop-status-info; } } } } } } } } } } Figure 2: MPTED YANG module 3. MPTED-JCT YANG Module 3.1. Model Structure The high-level model structure for MPTED junctions defined by this document is as shown below: Beeram & Kompella Expires 6 May 2027 [Page 22] Internet-Draft MPTED YANG Model November 2026 module: ietf-mpted-jct augment /te:te: +--rw mpted-junctions +--rw junction* [node-id originator tnl-id tnl-instance-id sig-src] +--rw node-id inet:ip-address +--rw originator inet:ip-address +--rw tnl-id uint32 +--rw tnl-instance-id uint32 +--rw sig-src inet:ip-address + .. +--rw phops | +--rw phop* [hop-address hop-index hop-version] | +--rw hop-address inet:ip-address | +--rw hop-index uint32 | +--rw hop-version uint32 | + .. +--rw nhops +--rw nhop* [hop-address hop-index hop-version] +--rw hop-address inet:ip-address +--rw hop-index uint32 +--rw hop-version uint32 + .. Figure 3: MPTED-JCT YANG Structure The top-level 'te' container in [I-D.draft-ietf-teas-yang-te] is augmented with a set of MPTED junctions. The 'mpted-junctions' container carries a list of junction entries. Each junction entry includes information about the associated set of previous-hops ('phops' container) and next-hops ('nhops' container). 3.2. YANG Code file "ietf-mpted-jct@2026-11-02.yang" module ietf-mpted-jct { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-mpted-jct"; prefix mpted-jct; import ietf-te { prefix te; reference "draft-ietf-teas-yang-te: A YANG Data Model for Traffic Engineering Tunnels, Label Switched Paths, and Interfaces"; } import ietf-inet-types { Beeram & Kompella Expires 6 May 2027 [Page 23] Internet-Draft MPTED YANG Model November 2026 prefix inet; reference "RFC6991: Common YANG Data Types"; } import ietf-routing-types { prefix rt-types; reference "RFC8294: Common YANG Data Types for the Routing Area"; } import ietf-mpted { prefix mpted; reference "RFC XXXX: A YANG Data Model for Multipath Traffic Engineering Directed Acyclic Graph (MPTED) Tunnels and Junctions"; } organization "IETF Traffic Engineering Architecture and Signaling (TEAS) Working Group."; contact "WG Web: WG List: Editor: Vishnu Pavan Beeram Editor: Kireeti Kompella "; description "This module defines a YANG data model for Multipath Traffic Engineering Directed Acyclic Graph (MPTED) junctions. It is intended to be used as part of the IETF TEAS framework to enable the configuration and management of MPTED junctions on an MPTED junction node. 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 XXXX Beeram & Kompella Expires 6 May 2027 [Page 24] Internet-Draft MPTED YANG Model November 2026 (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself for full legal notices."; revision 2026-11-02 { description "Initial revision. This revision introduces the YANG data model for Multipath Traffic Engineering Directed Acyclic Graph (MPTED) junctions."; reference "RFC XXXX: A YANG Data Model for Multipath Traffic Engineering Directed Acyclic Graph (MPTED) Tunnels and Junctions"; } grouping mpted-jct-info { description "Grouping for junction information."; leaf current-jct-instance { type uint32; description "Current instance identifier of the MPTED tunnel junction."; } leaf bandwidth-requested { type uint64; units "bytes per second"; description "Bandwidth to be reserved for the junction. A value of zero means that no bandwidth is reserved."; } } grouping mpted-jct-status-info { description "Grouping for junction status information."; uses mpted-jct-info; leaf mtu { type uint16; config false; description "MTU at the junction node. This is the smallest MTU value among the MTUs received from all JCT-NHOPs."; } leaf status { type identityref { base mpted:mpted-junction-status; Beeram & Kompella Expires 6 May 2027 [Page 25] Internet-Draft MPTED YANG Model November 2026 } config false; description "Status of the JUNCTION."; } } grouping mpted-jct-hop-info { description "Grouping for MPTED junction hop information."; leaf hop-address { type inet:ip-address; description "IP-address of the peer."; } leaf hop-index { type uint32; description "Index of the peer interface."; } leaf hop-version { type uint32; description "Version of the Hop."; } } grouping mpted-jct-nhop-info { description "Grouping for MPTED junction next-hop information."; uses mpted-jct-hop-info; leaf backup { type boolean; description "Indicates that the JCT-NHOP is a backup next-hop."; } leaf load-share { type uint16; config false; description "Effective relative load share of the JCT-NHOP. It is derived from the bandwidth-requested values of the JCT-NHOPs of the junction. It is zero for a JCT-NHOP that is not active, and it is the same for all active JCT-NHOPs if their bandwidth-requested values are all zero."; } leaf bandwidth-requested { Beeram & Kompella Expires 6 May 2027 [Page 26] Internet-Draft MPTED YANG Model November 2026 type uint64; units "bytes per second"; description "Bandwidth value of the JCT-NHOP, which determines its load share. Only the ratio of these values across the JCT-NHOPs of a junction is used. It does not by itself cause a bandwidth reservation."; } } augment "/te:te" { description "Augmentation for MPTED junctions."; container mpted-junctions { description "Container for MPTED junctions."; list junction { key "node-id originator tnl-id tnl-instance-id sig-src"; unique "name"; description "MPTED junction entry."; leaf node-id { type inet:ip-address; description "IP-address of the junction node."; } leaf originator { type inet:ip-address; description "IP address of the associated MPTED tunnel originator."; } leaf tnl-id { type uint32; description "Identifier of the associated MPTED tunnel."; } leaf tnl-instance-id { type uint32; description "Instance ID of the associated MPTED tunnel."; } leaf sig-src { type inet:ip-address; description "IP-address of the MPTED tunnel signaling source."; } Beeram & Kompella Expires 6 May 2027 [Page 27] Internet-Draft MPTED YANG Model November 2026 leaf name { type string; description "Name of the associated MPTED tunnel."; } leaf-list ingress { type inet:ip-address; description "List of ingress nodes of the associated MPTED tunnel."; } leaf-list egress { type inet:ip-address; description "List of egress nodes of the associated MPTED tunnel."; } leaf type { type identityref { base mpted:mpted-tunnel-type; } description "Type of associated tunnel."; } leaf setup-priority { type uint8 { range "0..7"; } default "7"; description "The priority of the associated MPTED tunnel with respect to taking resources, in the range of 0 to 7. The value 0 is the highest priority."; } leaf hold-priority { type uint8 { range "0..7"; } default "7"; description "The priority of the associated MPTED tunnel with respect to holding resources, in the range of 0 to 7. The value 0 is the highest priority."; } uses mpted-jct-status-info; container phops { description Beeram & Kompella Expires 6 May 2027 [Page 28] Internet-Draft MPTED YANG Model November 2026 "Container for associated JCT-PHOPs."; list phop { key "hop-address hop-index hop-version"; uses mpted-jct-hop-info; description "JCT-PHOP entry."; leaf in-label { type rt-types:mpls-label; config false; description "Label used by incoming packets on the JCT-PHOP."; } leaf status { type identityref { base mpted:mpted-jct-phop-status; } config false; description "Status of the JCT-PHOP."; } } } container nhops { description "Container for associated JCT-NHOPs."; list nhop { key "hop-address hop-index hop-version"; description "JCT-NHOP entry."; uses mpted-jct-nhop-info; leaf bandwidth-reserved { type uint64; units "bytes per second"; config false; description "Amount of bandwidth reserved on the TE link associated with the JCT-NHOP. It is zero if the bandwidth of the junction is zero. It is also zero for a backup JCT-NHOP, because the RSVP-TE signaling for MPTED tunnels (draft-kbr-teas-mptersvp) does not reserve bandwidth toward backup next-hops."; } leaf out-label { type rt-types:mpls-label; config false; Beeram & Kompella Expires 6 May 2027 [Page 29] Internet-Draft MPTED YANG Model November 2026 description "Label used by outgoing packets on the JCT-NHOP."; } leaf status { type identityref { base mpted:mpted-jct-nhop-status; } config false; description "Status of the JCT-NHOP."; } } } } } } } Figure 4: MPTED JCT YANG module 4. Security Considerations The YANG module specified in this document defines a schema for data that is designed to be accessed via network management protocols such as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS [RFC9846]. 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. The data nodes defined in these YANG modules that are writable/creatable/deletable (i.e., config true, which is the default) may be considered sensitive or vulnerable in some network environments. Write operations (e.g., edit-config) to these data nodes without proper protection can have a negative effect on network operations. These are the subtrees and data nodes and their sensitivity/vulnerability: "/te/mpted-tunnels": Unauthorized access to this list could influence how traffic is forwarded through the network. Beeram & Kompella Expires 6 May 2027 [Page 30] Internet-Draft MPTED YANG Model November 2026 "/te/mpted-junctions": Unauthorized access to this list could influence how traffic is forwarded on a junction node. The readable data nodes in these 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. These are the subtrees and data nodes and their sensitivity/vulnerability: "/te/mpted-tunnels/tunnel/instances/instance/junctions": Unauthorized read access to this list can disclose how traffic is load-balanced on each junction node. "/te/mpted-junctions/junction": Unauthorized read access to this list can disclose how traffic is load-balanced on the junction node. 5. IANA Considerations This document requests IANA to register the following URIs in the "ns" subregistry within the "IETF XML Registry" [RFC3688]. URI: urn:ietf:params:xml:ns:yang:ietf-mpted Registrant Contact: The IESG. XML: N/A; the requested URI is an XML namespace. URI: urn:ietf:params:xml:ns:yang:ietf-mpted-jct Registrant Contact: The IESG. XML: N/A; the requested URI is an XML namespace. This document requests IANA to register the following YANG modules in the "YANG Module Names" subregistry [RFC6020] within the "YANG Parameters" registry. name: ietf-mpted namespace: urn:ietf:params:xml:ns:yang:ietf-mpted prefix: mpted reference: RFC XXXX name: ietf-mpted-jct namespace: urn:ietf:params:xml:ns:yang:ietf-mpted-jct prefix: mpted-jct reference: RFC XXXX RFC Editor: Please replace XXXX with the RFC number assigned to this document. Beeram & Kompella Expires 6 May 2027 [Page 31] Internet-Draft MPTED YANG Model November 2026 6. Acknowledgments The authors would like to thank Sudharsana Venkatraman for her input and discussions. 7. References 7.1. Normative References [I-D.draft-ietf-teas-yang-te] Saad, T., Gandhi, R., Liu, X., Beeram, V. P., and I. Bryskin, "A YANG Data Model for Traffic Engineering Tunnels, Label Switched Paths, and Interfaces", Work in Progress, Internet-Draft, draft-ietf-teas-yang-te-44, March 2026, . [I-D.draft-kompella-teas-mpte] Kompella, K., Jalil, L., Khaddam, M., Geyer, N., and A. J. Smith, "Multipath Traffic Engineering", Work in Progress, Internet-Draft, draft-kompella-teas-mpte-04, October 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, . [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, . Beeram & Kompella Expires 6 May 2027 [Page 32] Internet-Draft MPTED YANG Model November 2026 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", RFC 7950, DOI 10.17487/RFC7950, August 2016, . [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration Access Control Model", STD 91, RFC 8341, DOI 10.17487/RFC8341, March 2018, . [RFC9846] Rescorla, E., "The Transport Layer Security (TLS) Protocol Version 1.3", RFC 9846, DOI 10.17487/RFC9846, July 2026, . 7.2. Informative References [I-D.kbr-teas-mptersvp] Kompella, K., Beeram, V. P., and C. Ramachandran, "RSVP-TE Extensions for Multipath Traffic Engineered Directed Acyclic Graph Tunnels", Work in Progress, Internet-Draft, draft-kbr-teas-mptersvp-05, November 2026, . [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, . Appendix A. MPTED YANG Module - Complete Tree Structure module: ietf-mpted augment /te:te: +--rw mpted-tunnels +--rw tunnel* [originator identifier] +--rw originator inet:ip-address +--rw identifier uint32 +--rw name? string +--rw description? string +--rw ingresses | +--rw ingress* [ingress-id] Beeram & Kompella Expires 6 May 2027 [Page 33] Internet-Draft MPTED YANG Model November 2026 | +--rw ingress-id inet:ip-address | +--rw set-bandwidth? uint64 | +--rw auto-bandwidth | +--rw min-bw? uint64 | +--rw max-bw? uint64 | +--rw adjust-threshold? rt-types:percentage | +--rw overflow | | +--rw enabled? boolean | | +--rw overflow-threshold? | | | rt-types:percentage | | +--rw trigger-event-count? uint16 | +--rw underflow | +--rw enabled? boolean | +--rw underflow-threshold? | | rt-types:percentage | +--rw trigger-event-count? uint16 +--rw egress* inet:ip-address +--rw type? identityref +--rw setup-priority? uint8 +--rw hold-priority? uint8 +--rw optimization-metric? identityref +--rw metric-margin? uint32 +--rw max-jcts? uint16 +--rw min-nhops? uint16 +--rw max-nhops? uint16 +--rw resource-affinities | +--rw exclude-any* string | +--rw include-any* string | +--rw include-all* string +--rw bandwidth-spec-type? identityref +--rw auto-bandwidth-adjust-interval? uint32 +--rw mpted-computer? inet:ip-address +--rw signaling-type? identityref +--rw signaling-source? inet:ip-address +--rw hop | +--rw minimum-bandwidth? uint64 +--rw compute-only? boolean +--rw retry-timer? uint16 +--rw optimize-timer? uint16 +--rw exclude-hops* inet:ip-address +--ro current-version? uint32 +--ro status? identityref +--ro max-flow-throughput? uint64 +--ro min-metric? uint64 +--ro max-metric? uint64 +--ro instances +--ro instance* [instance-id] +--ro instance-id uint32 Beeram & Kompella Expires 6 May 2027 [Page 34] Internet-Draft MPTED YANG Model November 2026 +--ro status? identityref +--ro junctions +--ro junction* [node-id] +--ro node-id inet:ip-address +--ro current-jct-instance? uint32 +--ro bandwidth-requested? uint64 +--ro mtu? uint16 +--ro status? identityref +--ro phops | +--ro phop* | [hop-address hop-index hop-version] | +--ro hop-address inet:ip-address | +--ro hop-index uint32 | +--ro hop-version uint32 | +--ro in-label? rt-types:mpls-label | +--ro status? identityref +--ro nhops +--ro nhop* [hop-address hop-index hop-version] +--ro hop-address | inet:ip-address +--ro hop-index uint32 +--ro hop-version uint32 +--ro backup? boolean +--ro load-share? uint16 +--ro bandwidth-requested? uint64 +--ro bandwidth-reserved? uint64 +--ro out-label? | rt-types:mpls-label +--ro status? identityref Figure 5: MPTED YANG tree Appendix B. MPTED-JCT YANG Module - Complete Tree Structure Beeram & Kompella Expires 6 May 2027 [Page 35] Internet-Draft MPTED YANG Model November 2026 module: ietf-mpted-jct augment /te:te: +--rw mpted-junctions +--rw junction* [node-id originator tnl-id tnl-instance-id sig-src] +--rw node-id inet:ip-address +--rw originator inet:ip-address +--rw tnl-id uint32 +--rw tnl-instance-id uint32 +--rw sig-src inet:ip-address +--rw name? string +--rw ingress* inet:ip-address +--rw egress* inet:ip-address +--rw type? identityref +--rw setup-priority? uint8 +--rw hold-priority? uint8 +--rw current-jct-instance? uint32 +--rw bandwidth-requested? uint64 +--ro mtu? uint16 +--ro status? identityref +--rw phops | +--rw phop* [hop-address hop-index hop-version] | +--rw hop-address inet:ip-address | +--rw hop-index uint32 | +--rw hop-version uint32 | +--ro in-label? rt-types:mpls-label | +--ro status? identityref +--rw nhops +--rw nhop* [hop-address hop-index hop-version] +--rw hop-address inet:ip-address +--rw hop-index uint32 +--rw hop-version uint32 +--rw backup? boolean +--ro load-share? uint16 +--rw bandwidth-requested? uint64 +--ro bandwidth-reserved? uint64 +--ro out-label? rt-types:mpls-label +--ro status? identityref Figure 6: MPTED-JCT YANG tree Contributors Chandrasekar Ramachandran HPE Email: chandrasekar.ramachandran@hpe.com Beeram & Kompella Expires 6 May 2027 [Page 36] Internet-Draft MPTED YANG Model November 2026 Jai Hari M.K HPE Email: jai-hari.m-k@hpe.com Authors' Addresses Vishnu Pavan Beeram HPE Email: vishnupavan.ietf@gmail.com Kireeti Kompella HPE Email: kireeti.ietf@gmail.com Beeram & Kompella Expires 6 May 2027 [Page 37]