A YANG Data Model for Multipath Traffic Engineering Directed Acyclic Graph (MPTED) Tunnels and Junctions
draft-beeram-teas-yang-mpted-00
This document is an Internet-Draft (I-D).
Anyone may submit an I-D to the IETF.
This I-D is not endorsed by the IETF and has no formal standing in the
IETF standards process.
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
|
|
|---|---|---|---|
| Authors | Vishnu Pavan Beeram , Kireeti Kompella | ||
| Last updated | 2025-07-07 | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | I-D Exists | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-beeram-teas-yang-mpted-00
TEAS Working Group V. P. Beeram
Internet-Draft K. Kompella
Intended status: Standards Track Juniper Networks
Expires: 8 January 2026 7 July 2025
A YANG Data Model for Multipath Traffic Engineering Directed Acyclic
Graph (MPTED) Tunnels and Junctions
draft-beeram-teas-yang-mpted-00
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 8 January 2026.
Copyright Notice
Copyright (c) 2025 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 8 January 2026 [Page 1]
Internet-Draft MPTED YANG Model July 2025
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 . . . . . . . . . . . . . . . . . . . . 5
3.1. Model Structure . . . . . . . . . . . . . . . . . . . . . 5
3.2. YANG Code . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . 6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.1. Normative References . . . . . . . . . . . . . . . . . . 7
6.2. Informative References . . . . . . . . . . . . . . . . . 8
Appendix A. MPTED YANG Module - Complete Tree Structure . . . . 8
Appendix B. MPTED-JCT YANG Module - Complete Tree Structure . . 10
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 11
Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
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 Multipath Traffic Engineering Directed Acyclic Graph
(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 8 January 2026 [Page 2]
Internet-Draft MPTED YANG Model July 2025
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.
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 8 January 2026 [Page 3]
Internet-Draft MPTED YANG Model July 2025
module: ietf-mpted
augment /te:te:
+--rw mpted-tunnels
+--rw tunnel* [originator identifier]
+--rw originator inet:ip-address
+--rw identifier uint32
+ ..
+--ro junctions
+--ro junction* [node-id]
+--ro node-id inet:ip-address
+ ..
+--ro phops
| +--ro phop* [hop-address hop-index]
| +--ro hop-address inet:ip-address
| +--ro hop-index uint32
| + ..
+--ro nhops
| +--ro nhop* [hop-address hop-index]
| +--ro hop-address inet:ip-address
| +--ro hop-index uint32
| + ..
+--ro phops-pending-deletion
| +--ro phop* [hop-address hop-index]
| +--ro hop-address inet:ip-address
| +--ro hop-index uint32
| + ..
+--ro nhops-pending-deletion
+--ro nhop* [hop-address hop-index]
+--ro hop-address inet:ip-address
+--ro hop-index uint32
+ ..
Figure 1: MPTED YANG Structure
The top-level 'te' container is [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
programmed in the network. The state for each junction entry
consists of the set of previous-hops ('phops' container) and next-
hops ('nhops' container) associated with the current version, as well
as those that are pending deletion ('phops-pending-deletion' and
'nhops-pending-deletion' containers).
2.2. YANG Code
Beeram & Kompella Expires 8 January 2026 [Page 4]
Internet-Draft MPTED YANG Model July 2025
<CODE BEGINS> file "ietf-mpted@2025-07-07.yang"
(Artwork only available as YANG: see
https://www.ietf.org/archive/id/draft-beeram-teas-yang-mpted-00.html)
<CODE ENDS>
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:
module: ietf-mpted-jct
augment /te:te:
+--rw mpted-junctions
+--rw junction* [node-id originator identifier]
+--rw node-id inet:ip-address
+--rw originator inet:ip-address
+--rw identifier uint32
+ ..
+--rw phops
| +--rw phop* [hop-address hop-index]
| +--rw hop-address inet:ip-address
| +--rw hop-index uint32
| + ..
+--rw nhops
+--rw nhop* [hop-address hop-index]
+--rw hop-address inet:ip-address
+--rw hop-index uint32
+ ..
Figure 3: MPTED-JCT YANG Structure
The top-level 'te' container is [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
<CODE BEGINS> file "ietf-mpted-jct@2025-07-07.yang"
(Artwork only available as YANG: see
https://www.ietf.org/archive/id/draft-beeram-teas-yang-mpted-00.html)
<CODE ENDS>
Beeram & Kompella Expires 8 January 2026 [Page 5]
Internet-Draft MPTED YANG Model July 2025
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
[RFC8446].
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.
"/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 module 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/junctions": Unauthorized read access to
this list can disclose how traffic is load-balanced on each junction
node.
5. IANA Considerations
This document requests IANA to register the following URIs in the
"ns" subregistry within the "IETF XML Registry" [RFC3688].
Beeram & Kompella Expires 8 January 2026 [Page 6]
Internet-Draft MPTED YANG Model July 2025
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.
6. References
6.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-38, 29
May 2025, <https://datatracker.ietf.org/doc/html/draft-
ietf-teas-yang-te-38>.
[I-D.draft-kompella-teas-mpte]
Kompella, K., Jalil, L., Khaddam, M., and A. Smith,
"Multipath Traffic Engineering", Work in Progress,
Internet-Draft, draft-kompella-teas-mpte-01, 7 July 2025,
<https://datatracker.ietf.org/doc/html/draft-kompella-
teas-mpte-01>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/rfc/rfc2119>.
Beeram & Kompella Expires 8 January 2026 [Page 7]
Internet-Draft MPTED YANG Model July 2025
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/rfc/rfc3688>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010,
<https://www.rfc-editor.org/rfc/rfc6020>.
[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,
<https://www.rfc-editor.org/rfc/rfc6241>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<https://www.rfc-editor.org/rfc/rfc6242>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/rfc/rfc7950>.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<https://www.rfc-editor.org/rfc/rfc8040>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/rfc/rfc8174>.
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Model", STD 91, RFC 8341,
DOI 10.17487/RFC8341, March 2018,
<https://www.rfc-editor.org/rfc/rfc8341>.
[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
<https://www.rfc-editor.org/rfc/rfc8446>.
6.2. Informative References
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
<https://www.rfc-editor.org/rfc/rfc8340>.
Appendix A. MPTED YANG Module - Complete Tree Structure
Beeram & Kompella Expires 8 January 2026 [Page 8]
Internet-Draft MPTED YANG Model July 2025
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 ingress* inet:ip-address
+--rw egress* inet:ip-address
+--rw version? uint16
+--rw type? identityref
+--rw setup-priority? uint8
+--rw hold-priority? uint8
+--rw optimization-metric? identityref
+--rw resource-affinities
| +--rw exclude-any* string
| +--rw include-any* string
| +--rw include-all* string
+--rw bandwidth-specification-type? identityref
+--rw set-bandwidth? uint64
+--rw auto-bandwidth
| +--rw enabled? boolean
| +--rw min-bw? uint64
| +--rw max-bw? uint64
| +--rw adjust-interval? uint32
| +--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 mpted-computer? inet:ip-address
+--rw signaling-type? identityref
+--rw signaling-source? inet:ip-address
+--ro status? identityref
+--ro junctions
+--ro junction* [node-id]
+--ro node-id inet:ip-address
+--ro version? uint16
+--ro bandwidth-requested? uint64
+--ro mtu? uint16
+--ro status? identityref
+--ro phops
| +--ro phop* [hop-address hop-index]
Beeram & Kompella Expires 8 January 2026 [Page 9]
Internet-Draft MPTED YANG Model July 2025
| +--ro hop-address inet:ip-address
| +--ro hop-index uint32
| +--ro in-label? rt-types:mpls-label
| +--ro status? identityref
+--ro nhops
| +--ro nhop* [hop-address hop-index]
| +--ro hop-address inet:ip-address
| +--ro hop-index uint32
| +--ro load-share? uint16
| +--ro bandwidth-reserved? uint64
| +--ro out-label? rt-types:mpls-label
| +--ro status? identityref
+--ro phops-pending-deletion
| +--ro phop* [hop-address hop-index]
| +--ro hop-address inet:ip-address
| +--ro hop-index uint32
| +--ro version? uint16
+--ro nhops-pending-deletion
+--ro nhop* [hop-address hop-index]
+--ro hop-address inet:ip-address
+--ro hop-index uint32
+--ro version? uint16
Figure 5: MPTED YANG tree
Appendix B. MPTED-JCT YANG Module - Complete Tree Structure
Beeram & Kompella Expires 8 January 2026 [Page 10]
Internet-Draft MPTED YANG Model July 2025
module: ietf-mpted-jct
augment /te:te:
+--rw mpted-junctions
+--rw junction* [node-id originator identifier]
+--rw node-id inet:ip-address
+--rw originator inet:ip-address
+--rw identifier uint32
+--rw name? string
+--rw ingress* inet:ip-address
+--rw egress* inet:ip-address
+--rw version? uint16
+--rw type? identityref
+--rw setup-priority? uint8
+--rw hold-priority? uint8
+--rw bandwidth-requested? uint64
+--ro mtu? uint16
+--ro status? identityref
+--rw phops
| +--rw phop* [hop-address hop-index]
| +--rw hop-address inet:ip-address
| +--rw hop-index uint32
| +--ro in-label? rt-types:mpls-label
| +--ro status? identityref
+--rw nhops
+--rw nhop* [hop-address hop-index]
+--rw hop-address inet:ip-address
+--rw hop-index uint32
+--rw load-share? uint16
+--ro bandwidth-reserved? uint64
+--ro out-label? rt-types:mpls-label
+--ro status? identityref
Figure 6: MPTED-JCT YANG tree
Acknowledgments
The authors would like to thank Sudharsana Venkatraman for her input
from discussions.
This document was prepared using kramdown.
Contributors
Chandrasekar Ramachandran
Juniper Networks
Email: csekar@juniper.net
Beeram & Kompella Expires 8 January 2026 [Page 11]
Internet-Draft MPTED YANG Model July 2025
Authors' Addresses
Vishnu Pavan Beeram
Juniper Networks
Email: vbeeram@juniper.net
Kireeti Kompella
Juniper Networks
Email: kireeti@juniper.net
Beeram & Kompella Expires 8 January 2026 [Page 12]