RFC 9702: YANG Data Model for Maximum Segment Identifier (SID) Depth (MSD) Types and MPLS MSD
- Y. Qu,
- A. Lindem,
- S. Litkowski,
- J. Tantsura
Abstract
This document defines two YANG modules. The first module is the initial version of the IANA-maintained YANG module for Maximum Segment Identifier (SID) Depth (MSD) Types, which includes identities for both the MPLS data plane and Segment Routing over IPv6 (SRv6) data plane. The second module augments the IETF MPLS YANG data model to provide support for MPLS MSDs as defined in RFCs 8476 and 8491.¶
Status of This Memo
This is an Internet Standards Track document.¶
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841.¶
Information about the current status of this document, any
errata, and how to provide feedback on it may be obtained at
https://
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://
1. Overview
There are two YANG modules [RFC7950] defined in this
document. Module iana-msd-types defines the identities for Maximum SID
Depth (MSD) Types as per the "IGP MSD-Types" IANA registry [IANA
The YANG modules in this document conform to the Network Management Datastore Architecture (NMDA) [RFC8342].¶
2. Design of the Model
2.1. IANA MSD Types Module
IANA has created a registry titled "IGP MSD-Types" under the "Interior Gateway Protocol (IGP) Parameters" registry group to identify MSD-Types. Module iana-msd-types is an IANA-maintained module, which defines the identities for the MSD-Types as in the IANA "IGP MSD-Types" registry. This module references [RFC8476], [RFC8491], [RFC8662], [RFC8664], [RFC8814], [RFC9088], and [RFC9352].¶
On top of the base identity "msd-base", identity "msd-base-mpls" is defined to serve as the base for MSD types for the MPLS data plane, and identity "msd-base-srh" is defined to serve as the base for MSD types for the Segment Routing Header (SRH) in the IPv6 data plane.¶
This module is maintained by IANA and will be updated if and when there is any change to the registry.¶
2.2. IETF MPLS MSD Module
Module ietf-mpls-msd augments the base MPLS model [RFC8960], and it provides support of different types of MSDs in the MPLS data plane.¶
As defined in [RFC8491], a Link MSD is the number of SIDs supported by a node's link, while a Node MSD is the smallest MSD supported by the node across all its links. The module defines lists of MSDs and their MSD Types for a node and its links. Please note that these are read-only data nodes exposing a node's hardware capability.¶
3. Tree for IETF MPLS MSD Types YANG Module
This document uses the graphical representation of data models per [RFC8340].¶
4. YANG Modules
There are two YANG modules defined in this document.¶
4.1. IANA-Maintained Module for MSD-Types
This document defines the initial version of the IANA-maintained YANG
module for MSD Types that mirrors the IANA "IGP MSD-Types"
registry [IANA
4.2. MPLS MSD YANG
This document also defines a YANG module for MSD extensions [RFC8476] [RFC8491] to the MPLS base model as defined in [RFC8960].¶
5. Security Considerations
The YANG modules specified in this document define 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
The Network Configuration Access Control Model (NACM) [RFC8341] provides the means to restrict access for particular NETCONF or RESTCONF users to a pre-configured subset of all available NETCONF or RESTCONF protocol operations and content.¶
Some of the readable data nodes in the ietf-mpls-msd 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
/rt
/rt
Exposure of the node's maximum SID depth may be useful in mounting a
Denial
The iana-msd-types YANG module defines a set of identities that mirror the IANA "IGP MSD-Types" registry. These identities are intended to be reused by other YANG modules. The module by itself does not expose any data nodes that are writable or readable. As such, there are no additional security issues related to this YANG module that need to be considered.¶
6. IANA Considerations
6.1. Registering YANG Modules
This document registers URIs in the IETF XML registry as defined in [RFC3688]. The following registrations have been made:¶
- URI:
- urn
:ietf :params :xml :ns :yang :iana -msd -types¶ - Registrant Contact:
- The IESG.¶
- XML:
- N/A; the requested URI is an XML namespace.¶
- URI:
- urn
:ietf :params :xml :ns :yang :ietf -mpls -msd¶ - Registrant Contact:
- The IESG.¶
- XML:
- N/A; the requested URI is an XML namespace.¶
This document registers the YANG modules in the "YANG Module Names" registry as defined in [RFC6020].¶
6.2. IANA MSD-Types Module
This document defines the initial version of the IANA-maintained
"iana
IANA has added this note to the "YANG Module Names" registry:¶
New values must not be directly added to the "iana
-msd -types" YANG module. They must instead be added to the "IGP MSD-Types" registry in the "Interior Gateway Protocol (IGP) Parameters" registry group [IANA -IGP ].¶-MSD -Types
The identities defined in the iana-msd-types YANG module are organized hierarchically
based on the data plane. In this initial version, only MPLS and SRv6 data
planes are supported, hence "msd-base-mpls" and "msd-base-srh" are defined.
When a new data plane is added to the "IGP MSD-Types" registry, a new "identity"
statement should be added to the "iana
- "base":
- Contains 'msd-base'.¶
- "description":
- Replicates the description from "msd-base-mpls" and changes the corresponding data plane name.¶
- "reference":
- Replicates the reference from the registry with the title of the document added.¶
When an MSD type is added to the "IGP MSD-Types" registry, a new "identity"
statement must be added to the "iana
- "base":
- Contains the base name of the corresponding data plane.¶
- "description":
- Replicates the name 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
IANA has added a "Data Plane" column to the "IGP MSD-Types" registry. This will unequivocally identify the base identity for MSD-Types. The values for the "Data Plane" column for existing MSD-Types are:¶
IANA has added this note to [IANA
When this registry is modified, the YANG module "iana
-msd -types" must be updated as defined in RFC 9702.¶
7. References
7.1. Normative References
- [IANA
-IGP -MSD -Types] -
IANA, "IGP MSD-Types", <https://
www >..iana .org /assignments /igp -parameters - [IANA
-YANG -Parameters] -
IANA, "YANG Module Names", <https://
www >..iana .org /assignments /yang -parameters - [RFC3688]
-
Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10
.17487 , , <https:///RFC3688 www >..rfc -editor .org /info /rfc3688 - [RFC6020]
-
Bjorklund, M., Ed., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, DOI 10
.17487 , , <https:///RFC6020 www >..rfc -editor .org /info /rfc6020 - [RFC6241]
-
Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., and A. Bierman, Ed., "Network Configuration Protocol (NETCONF)", RFC 6241, DOI 10
.17487 , , <https:///RFC6241 www >..rfc -editor .org /info /rfc6241 - [RFC6242]
-
Wasserman, M., "Using the NETCONF Protocol over Secure Shell (SSH)", RFC 6242, DOI 10
.17487 , , <https:///RFC6242 www >..rfc -editor .org /info /rfc6242 - [RFC7950]
-
Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", RFC 7950, DOI 10
.17487 , , <https:///RFC7950 www >..rfc -editor .org /info /rfc7950 - [RFC8040]
-
Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF Protocol", RFC 8040, DOI 10
.17487 , , <https:///RFC8040 www >..rfc -editor .org /info /rfc8040 - [RFC8341]
-
Bierman, A. and M. Bjorklund, "Network Configuration Access Control Model", STD 91, RFC 8341, DOI 10
.17487 , , <https:///RFC8341 www >..rfc -editor .org /info /rfc8341 - [RFC8342]
-
Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., and R. Wilton, "Network Management Datastore Architecture (NMDA)", RFC 8342, DOI 10
.17487 , , <https:///RFC8342 www >..rfc -editor .org /info /rfc8342 - [RFC8349]
-
Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for Routing Management (NMDA Version)", RFC 8349, DOI 10
.17487 , , <https:///RFC8349 www >..rfc -editor .org /info /rfc8349 - [RFC8446]
-
Rescorla, E., "The Transport Layer Security (TLS) Protocol Version 1.3", RFC 8446, DOI 10
.17487 , , <https:///RFC8446 www >..rfc -editor .org /info /rfc8446 - [RFC8476]
-
Tantsura, J., Chunduri, U., Aldrin, S., and P. Psenak, "Signaling Maximum SID Depth (MSD) Using OSPF", RFC 8476, DOI 10
.17487 , , <https:///RFC8476 www >..rfc -editor .org /info /rfc8476 - [RFC8491]
-
Tantsura, J., Chunduri, U., Aldrin, S., and L. Ginsberg, "Signaling Maximum SID Depth (MSD) Using IS-IS", RFC 8491, DOI 10
.17487 , , <https:///RFC8491 www >..rfc -editor .org /info /rfc8491 - [RFC8960]
-
Saad, T., Raza, K., Gandhi, R., Liu, X., and V. Beeram, "A YANG Data Model for MPLS Base", RFC 8960, DOI 10
.17487 , , <https:///RFC8960 www >..rfc -editor .org /info /rfc8960 - [RFC9088]
-
Xu, X., Kini, S., Psenak, P., Filsfils, C., Litkowski, S., and M. Bocci, "Signaling Entropy Label Capability and Entropy Readable Label Depth Using IS-IS", RFC 9088, DOI 10
.17487 , , <https:///RFC9088 www >..rfc -editor .org /info /rfc9088 - [RFC9352]
-
Psenak, P., Ed., Filsfils, C., Bashandy, A., Decraene, B., and Z. Hu, "IS-IS Extensions to Support Segment Routing over the IPv6 Data Plane", RFC 9352, DOI 10
.17487 , , <https:///RFC9352 www >..rfc -editor .org /info /rfc9352
7.2. Informative References
- [RFC8340]
-
Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", BCP 215, RFC 8340, DOI 10
.17487 , , <https:///RFC8340 www >..rfc -editor .org /info /rfc8340 - [RFC8662]
-
Kini, S., Kompella, K., Sivabalan, S., Litkowski, S., Shakir, R., and J. Tantsura, "Entropy Label for Source Packet Routing in Networking (SPRING) Tunnels", RFC 8662, DOI 10
.17487 , , <https:///RFC8662 www >..rfc -editor .org /info /rfc8662 - [RFC8664]
-
Sivabalan, S., Filsfils, C., Tantsura, J., Henderickx, W., and J. Hardwick, "Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing", RFC 8664, DOI 10
.17487 , , <https:///RFC8664 www >..rfc -editor .org /info /rfc8664 - [RFC8814]
-
Tantsura, J., Chunduri, U., Talaulikar, K., Mirsky, G., and N. Triantafillis, "Signaling Maximum SID Depth (MSD) Using the Border Gateway Protocol - Link State", RFC 8814, DOI 10
.17487 , , <https:///RFC8814 www >..rfc -editor .org /info /rfc8814
Acknowledgements
The YANG data model was developed using the suite of YANG tools written and maintained by numerous authors.¶
We would like to thank Jan Lindblad, Tom Petch, Dhruv Dhody, Mohamed Boucadair, and Susan Hares for their reviews and comments.¶