TEAS S. Barguil, Ed. Internet-Draft Nokia Intended status: Informational L.M. Contreras, Ed. Expires: 10 May 2027 Telefonica V. Lopez Nokia O. Gonzalez de Dios Telefonica M. Boucadair Orange 16 November 2026 Applicability of IETF-Defined Service and Network Data Models for Network Slice Service Management draft-ietf-teas-ns-models-applicability-03 Abstract This document describes how IETF-defined YANG data models can be used together to manage RFC 9543 Network Slice Services. It explains how a Network Slice Controller (NSC) translates a customer-facing Network Slice Service request into requests based on network models, such as the L3VPN and L2VPN Network Models, and how these relate to the corresponding service models. The document compares these models against Network Slice Service requirements, identifies gaps, and shows how the models apply in different controller architectures, including multi-domain deployments. 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 10 May 2027. Barguil, et al. Expires 10 May 2027 [Page 1] Internet-Draft Network Models for IETF Network Slices November 2026 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. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 1.2. Key Concepts . . . . . . . . . . . . . . . . . . . . . . 4 2. A Reference Architecture and Main Components . . . . . . . . 6 3. RFC 9543 Network Slice Requirements and Data Models . . . . . 10 4. Operational Considerations . . . . . . . . . . . . . . . . . 12 4.1. Availability . . . . . . . . . . . . . . . . . . . . . . 12 4.2. Downlink Throughput/Uplink Throughput . . . . . . . . . . 12 4.3. Protection Scheme . . . . . . . . . . . . . . . . . . . . 13 4.4. Delay . . . . . . . . . . . . . . . . . . . . . . . . . . 13 4.5. Packet Loss Rate . . . . . . . . . . . . . . . . . . . . 13 5. Relationship Between RFC 9543 Network Slice Service YANG Model Parameters and those in Lx Service and Network Models . . 13 5.1. Relationship Between RFC 9543 Network Slice Service Model Parameters and L3SM and L2SM . . . . . . . . . . . . . . 14 5.1.1. Parameter Mapping . . . . . . . . . . . . . . . . . . 14 5.1.2. Functional and Capability Alignment . . . . . . . . . 18 5.2. Relationship Between RFC 9543 Network Slice Service Model Parameters and the L3NM and L2NM . . . . . . . . . . . . 18 5.2.1. Parameter mapping . . . . . . . . . . . . . . . . . . 19 5.2.2. Functional and Capability Alignment . . . . . . . . . 22 5.3. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 22 6. RFC 9543 Network Slice Procedure . . . . . . . . . . . . . . 23 6.1. RFC 9543 Network Slice Provisioning Workflow . . . . . . 23 6.2. LxVPN Network Models . . . . . . . . . . . . . . . . . . 24 6.3. Traffic Engineering Models . . . . . . . . . . . . . . . 24 6.4. Traffic Engineering Service Mapping . . . . . . . . . . . 25 7. Potential Models Usage in Alternative RFC 9543 NSC Architectures . . . . . . . . . . . . . . . . . . . . . . 25 7.1. RFC 9543 Network Slice Service Requested to Hierarchical Network Controller . . . . . . . . . . . . . . . . . . . 26 Barguil, et al. Expires 10 May 2027 [Page 2] Internet-Draft Network Models for IETF Network Slices November 2026 7.2. RFC 9543 Network Slice Service Requested to Network Slice Controller . . . . . . . . . . . . . . . . . . . . . . . 28 7.3. Network Slice Controller as Part of the Domain Controller . . . . . . . . . . . . . . . . . . . . . . . 29 8. Security Considerations . . . . . . . . . . . . . . . . . . . 30 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31 10. Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . 31 Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 31 References . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Normative References . . . . . . . . . . . . . . . . . . . . . 31 Informative References . . . . . . . . . . . . . . . . . . . . 33 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 35 1. Introduction The IETF has produced several YANG data models for automating the provisioning and delivery of connectivity services. [RFC8969] describes a framework for using these models together. This document applies the same approach to the RFC 9543 Network Slice Service [RFC9543]. A customer requests a Network Slice Service using the Network Slice Service Model (NSSM) [I-D.ietf-teas-ietf-network-slice-nbi-yang], which expresses what the customer needs (e.g., connectivity and Service Level Objectives) rather than how the network delivers it. The Network Slice Controller (NSC) [RFC9543] must translate that request into requests that network controllers understand. Those controllers typically expose service models, such as the L3VPN Service Model (L3SM) [RFC8299] and the L2VPN Service Model (L2SM) [RFC8466], and network models, such as the L3VPN Network Model (L3NM) [RFC9182] and the L2VPN Network Model (L2NM) [RFC9291]. This document: * describes a reference architecture and the interfaces between an NSC and network controllers (Section 2); * lists the data models involved and discusses how they address operational requirements such as availability, bandwidth, and delay (Sections 3 and 4); * maps NSSM parameters and capabilities to the service and network models, and identifies gaps (Section 5); * outlines the provisioning workflow (Section 6); and * shows how the models can be used in different NSC architectures, including multi-domain deployments (Section 7). Barguil, et al. Expires 10 May 2027 [Page 3] Internet-Draft Network Models for IETF Network Slices November 2026 1.1. Terminology 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. This document assumes that the reader is familiar with the contents of [RFC6241], [RFC7950], [RFC8309], and [RFC9543] as it uses terms from those RFCs. This document uses the term "network model" as defined in Section 2.1 of [RFC8969]. 1.2. Key Concepts This section defines key terms used throughout the document to ensure clarity and consistency. * Attachment Circuit (AC): Identifies where to deliver a Network Slice Service. YANG data models for managing Attachment Circuits- as-a-Service (ACaaS) and bearers are specified. A network YANG data model for Attachment Circuits augments the Service Attachment Point (SAP) model. It is defined in [RFC9834]. * Bearer: A component of the underlying delivery setup, managed prior to or during the provisioning of a Network Slice Service. YANG data models for bearers are specified as part of the Attachment Circuit RFC. It is defined in [RFC9834]. * L2VPN Network Model (L2NM): A YANG network data model for Layer 2 VPNs. It exposes network-level data and the parameters needed for service creation. Parameters relevant to Network Slicing include committed and peak bandwidth (CIR, PIR), MTU, QoS profiles, classification policies, and support for broadcast, unknown- unicast, and multicast (BUM) traffic [RFC9291]. * L2VPN Service Model (L2SM): A YANG data model for the delivery of Layer 2 VPN services [RFC8466]. It includes parameters for bandwidth, MTU, QoS, BUM traffic, and availability. * L3VPN Network Model (L3NM): A YANG network data model for Layer 3 VPNs. It exposes network-level data and defines parameters such as l2 and l3 connection, bandwidth, MTU, QoS (profile, classification policy, action), and multicast (mVPN) support [RFC9182]. Barguil, et al. Expires 10 May 2027 [Page 4] Internet-Draft Network Models for IETF Network Slices November 2026 * L3VPN Service Model (L3SM): A YANG data model for the delivery of Layer 3 VPN services [RFC8299]. It includes bandwidth, MTU, QoS, and multicast parameters. * Network Controller(s): Functional entities that interact with a Network Slice Controller (NSC) through the network-facing interface for the realization of RFC 9543 Network Slice Services. These controllers expose network data models such as L3NM, L2NM, and SAPs. * Network-facing Interface (NFI): The interface used by an NSC to interact with one or more Network Controllers for the realization of a Network Slice Service as defined in [RFC9543]. * Network Model: As defined in Section 2.1 of [RFC8969], these models describe a VPN service from the network's point of view. Examples include L3NM and L2NM. Network Controllers expose these models to NSCs. * Network Slice Controller (NSC): A key functional entity responsible for the control and management of RFC 9543 Network Slice Services. It exposes APIs for higher-layer systems to request Network Slice Services. Upon receiving a request, the NSC assesses feasibility, identifies resources, and maps customer- oriented service requests into objectives for the network. It may be implemented as a module of a hierarchical SDN controller, a standalone component, or integrated within a network controller. * Network Slice Service Model (NSSM): The YANG service model that provides a customer-oriented abstraction for requesting RFC 9543 Network Slice Services [I-D.ietf-teas-ietf-network-slice-nbi-yang]. * RFC 9543 Network Slice: A Network Slice built using IETF technologies, as defined in [RFC9543]. This document focuses on the composition of IETF data models to support RFC 9543-compliant services. Use case requirements are specified in [I-D.ietf-teas-ietf-network-slice-use-cases]. * RFC 9543 Network Slice Mapper: A high-level component of an NSC that processes customer requests and contextualizes them within the set of existing RFC 9543 Network Slices. It maps Service Level Objectives (SLOs) into routing and forwarding policies. Barguil, et al. Expires 10 May 2027 [Page 5] Internet-Draft Network Models for IETF Network Slices November 2026 * RFC 9543 Network Slice Realizer: A high-level component of an NSC responsible for processing transport slice views, determining appropriate technologies, and triggering the realization of the RFC 9543 Network Slice. This process may involve generating LxNM network requests. * Service Attachment Points (SAPs): A YANG data model providing an abstracted view of the provider network topology. SAPs indicate where services can be delivered. NSCs may use SAPs to identify available delivery locations for a Network Slice Service [RFC9408]. * Service Model: A model used to request Network Slice Services (e.g., L3SM, L2SM). These provide a customer-facing abstraction of the desired connectivity or service. * Traffic Engineering (TE) Models: A set of YANG models defined by the TEAS working group to support the management and instantiation of TE-enabled paths and tunnels. * Traffic Engineering Service Mapping: A YANG model that defines the procedure for mapping VPN service or network models to TE models. It enables Network Controllers to associate TE resources with specific services. * YANG Data Model: IETF-defined models that support automated provisioning and delivery of connectivity services. These models can be composed and integrated to enable RFC 9543 Network Slice Service delivery. The Network Slice Service YANG model provides a customer-facing abstraction. 2. A Reference Architecture and Main Components The NSC is a key functional entity for the control and management of [RFC9543] Network Slice Services. As shown in Figure 1, an NSC exposes a set of APIs for higher level systems to request an [RFC9543] Network Slice Service. These APIs can be used to manage other connectivity services, such as managing the underlying delivery setup that is required for the delivery of an RFC 9543 Network Slice Service. Such a setup can be managed prior to or during the provisioning of a Network Slice Service. Concretely, the setup includes the management of bearers and attachment circuits that connect Service Demarcation Points (SDPs) to customer premises. In the northbound the NSC customer-facing interface is invoked by a customer for managing an RFC 9543 Network Slice Service (i.e., creation, modification, or deletion). Upon receiving a request via a customer-facing interface, an NSC assesses whether it can satisfy the Barguil, et al. Expires 10 May 2027 [Page 6] Internet-Draft Network Models for IETF Network Slices November 2026 request and then identifies the resources that are needed for realization of the RFC 9543 Network Slice Service. The network- facing interface is used to interact with one or more Network Controllers for the realization of the requested RFC 9543 Network Slice Service. In this customer facing interface, NSC exposes a set of RFC 9543 service data models: mainly, the RFC 9543 Network Slice Service Interface [I-D.ietf-teas-ietf-network-slice-nbi-yang] or the Attachment Circuit-as-a-Service Interface [RFC9834], but it is not restricted to those. Network Controllers expose to NSCs a set of network centric data models, such as the L3NM, the L2NM, or the Service Attachment Points (SAPs) [RFC9408]. Typically, by setting the service type to "network-slice", an NSC can retrieve via the SAPs API where the Slice Services can be delivered to customers. Likewise, SAPs can also be used to retrieve where such services are delivered to customers through the network configuration described in the L3NM [RFC9182] or the L2NM [RFC9291]. These checks can be used as part of feasibility checks, prior to the Network Slice realization. +------------------------------------------+ | A higher level system | | (e.g., E2E Network Slice orchestrator) | +------------------------------------------+ A | NSC Customer-facing APIs V Customer Service Models +------------------------------------------+ | RFC 9543 Network Slice Controller (NSC) | +------------------------------------------+ A | NSC Network-facing APIs V Network Models +------------------------------------------+ | Network Controller(s) | +------------------------------------------+ Figure 1: Network Slice Controller Interfaces. Several architectural definitions have arisen on the IETF to support SDN and network slicing deployments. The architecture defined in [RFC9543] includes a three-level hierarchy. Figure 2 depicts a possible architecture using similar concepts. It starts from a consumer or high-level operational systems. Then, the NSC function might be part of a hierarchical network controller Barguil, et al. Expires 10 May 2027 [Page 7] Internet-Draft Network Models for IETF Network Slices November 2026 (e.g., as the MDSC in the ACTN context [RFC8453]) as a modular function. As an alternative, in Figure 2 at the bottom, multiple network controllers can be orchestrated from the NSC. Each Network controller can handle multiple or single underlay technologies. +------------------------------+ | High-level operation system. | +--------------+---------------+ |RFC 9543 Network Slice | Service Request +-------------------v------------------+ | | | Hierarchical Network | | Controller/Orchestrator | | | | +-------------------------------+ | | | RFC 9543 NSC | | | +-------------------------------+ | | | +-------------------+------------------+ | | +--------------+---------------+ | | v v +-------------+----------+ +-------------+----------+ | Network Controller | | Network Controller | +-------------+----------+ +-------------+----------+ | | | | v v Network Elements Network Elements Figure 2: RFC 9543 Network Slice Controller as a Module of a Hierarchical SDN Controller. In other implementations, an NSC can be a standalone component that directly interacts with a network controller, as depicted in Figure 3. In this scenario, a service request follows a "data- enrichment" path, where each entity adds more information to the service request. Barguil, et al. Expires 10 May 2027 [Page 8] Internet-Draft Network Models for IETF Network Slices November 2026 +-------------------------------+ | High-level operation system | +-------------+-----------------+ |RFC 9543 Network Slice Request | +-------------v-----------------+ | RFC 9543 NSC | +-------------+-----------------+ | | +-------------v-----------------+ | Network Controller | +-------------+-----------------+ | | v Network Elements Figure 3: RFC 9543 Network Slice Controller as a Standalone Component Alternatively, an NSC can be integrated with a network controller and directly realizes the Network Slice Services using device data models to configure the network devices. A sample architecture is depicted in Figure 4. +-------------------------------+ | High-level operation system | +-------------+-----------------+ |RFC 9543 Network Slice Request | +-------------v----------------+ | Network Controller | | | |+----------------------------+| || Network Slice Controller || |+----------------------------+| | | +-------------+----------------+ | | v Network Elements Figure 4: RFC 9543 Network Slice Controller as a Module of a Network Controller. Barguil, et al. Expires 10 May 2027 [Page 9] Internet-Draft Network Models for IETF Network Slices November 2026 3. RFC 9543 Network Slice Requirements and Data Models The main requirements for an RFC 9543 Network Slice Service, based on the high-level slice requirements from multiple organizations and use cases are compiled in [I-D.ietf-teas-ietf-network-slice-use-cases]. To accomplish those requirements, a set of YANG data models have been proposed: * [I-D.ietf-teas-ietf-network-slice-nbi-yang]: specifies the YANG data model for the RFC 9543 Network Slice Service (NSSM). * [RFC9181]: specifies a set of reusable types and groupings to manage VPN services; VPN is used to realize slices. * [RFC9833]: specifies a set of reusable types and groupings to manage Attachment Circuits (ACs). * [RFC9834]: specifies YANG data models for managing 'Attachment Circuits'-as-a-Service (ACaaS) and also bearers. These ACs and bearers are used to identify where to deliver a Network Slice Service. * [RFC9408]: defines a YANG data model for representing an abstract view of the provider network topology that contains the points from which its services can be attached (e.g., Network Slices). A SAP network topology can be used for one or multiple service types ('service-type'). Setting this data node to 'network-slice' allows a controller to expose where RFC 9543 Network Slices services are being delivered. It can also be used to check where RFC 9543 Network Slice services can be delivered. * [RFC9835] augments the SAP model with more details for managing ACs at the network level. * [I-D.dhody-teas-ietf-network-slice-mapping] specifies an RFC 9543 Network Slice Service mapping YANG model. Barguil, et al. Expires 10 May 2027 [Page 10] Internet-Draft Network Models for IETF Network Slices November 2026 +---------------+ | Customer | +-------+-------+ Customer Service Model | e.g., slice-svc, ac-svc,| bearer-svc l3vpn-svc and | l2vpn-svc +-------+-------+ | Service | | Orchestration | +-------+-------+ Network Model | e.g., l2vpn-ntw, l3vpn-ntw, sap, and | ac-ntw +-------+-------+ | Network | | Orchestration | +-------+-------+ Network Configuration Model | +-----------+-----------+ | | +--------+------+ +--------+------+ | Domain | | Domain | | Orchestration | | Orchestration | +---+-----------+ +--------+------+ Device | | | Configuration | | | Model | | | +----+----+ | | | Config | | | | Manager | | | +----+----+ | | | | | | NETCONF/CLI.................. | | | +--------------------------------+ +----+ Bearer | | Bearer +----+ |CE#1+--------+ Network +--------+CE#2| +----+ AC | | AC +----+ +--------------------------------+ Site A Site B Figure 5: Overview of Data Models used for Network Slicing Barguil, et al. Expires 10 May 2027 [Page 11] Internet-Draft Network Models for IETF Network Slices November 2026 4. Operational Considerations This section outlines the compliance and operational aspects of Network Controller models with Network Slice requirements. The previous section presented the requirements of the RFC 9543 Network Slice. This section analyzes how the YANG models available to a Network Controller can satisfy those requirements and identifies gaps. 4.1. Availability As per [I-D.ietf-teas-te-service-mapping-yang], availability is a probabilistic measure of the length of time that a VPN/VN instance functions without a network failure. As per RFC 8330, the parameter "availability", as described in [G.827], [F.1703], and [P.530], is often used to describe the link capacity. The availability is a time scale, representing a proportion of the operating time that the requested bandwidth is ensured. The calculation of the availability is not trivial and would need to be clearly scoped to avoid misunderstandings. The set of YANG models proposed today allow to request tunnels/paths with different resiliency requirements in terms of protection and restoration. However, none of them include the possibility of requesting a specific availability (e.g. 99.9999%). 4.2. Downlink Throughput/Uplink Throughput The LxNMs ([RFC9182] and [RFC9291]) allow to specify the bandwidth at the interface level between the slice and the customer. In addition, the Service Mapping model [I-D.ietf-teas-te-service-mapping-yang] allows to bind a VPN to a given LSP, which have its bandwidth requirements. Additionally, TE models can force a give bandwidth in the connection between Provider Edges. Previous comment applies to the incoming and outgoing bandwidth parameters required for the NFV-based services use case in [I-D.ietf-teas-ietf-network-slice-use-cases]. The Network sharing use case has Maximum and Guaranteed Bit Rate parameters. These parameters can be mapped to the TE tunnel models when setting up LSPs [I-D.ietf-teas-yang-te]. Barguil, et al. Expires 10 May 2027 [Page 12] Internet-Draft Network Models for IETF Network Slices November 2026 4.3. Protection Scheme Protection schemes are mechanisms to define how to setup resources for a given connection. TE tunnel models [I-D.ietf-teas-yang-te] includes protection and restoration as two main attributes. The parameters included in the containers for protection and restoration cover the requirements of the RFC 9543 NS related with protection schemes. Similarly, TE models cover the parameter 'recovery time' for the network sharing use case. 4.4. Delay Delay is a critical parameter for several RFC 9543 NS types. Every use-case defined in [I-D.ietf-teas-ietf-network-slice-use-cases] contains delay constraints. 5G use cases require 'delay tolerance', NFV-based services have the delay information within 'QoS metrics' and 'Bounded latency' in the network sharing use case. During the realization of the RFC 9543 Network Slice, these parameters are part of the requirements of a TE tunnel configuration [I-D.ietf-teas-yang-te]. They can be included within the 'path- metric-bounds' parameter, so the created LSP fulfils the given metrics bounds like 'path-metric-delay-average' or 'path-metric- delay-minimum'. 4.5. Packet Loss Rate The packet loss rate indicates the maximum rate for lost packets that the service tolerates in the link. During the realization of the RFC 9543 Network Slice, this attribute will influence the tunnel selection and the value is included in the [I-D.ietf-teas-yang-te] document as the 'path-metric-loss". The 'path-metric-loss' is a metric type, which measures the percentage of packet loss of all links traversed by a P2P path. This parameter is required for 5G services and network sharing use-case, while it is part of the 'QoS metrics' for the NFV-based services. 5. Relationship Between RFC 9543 Network Slice Service YANG Model Parameters and those in Lx Service and Network Models The following sections distinguish between parameter mappings and functional or procedural capabilities. Parameters are data elements that can be directly or partially mapped between the Network Slice Service Model (NSSM) and the L3SM/L2SM or L3NM/L2NM models. Barguil, et al. Expires 10 May 2027 [Page 13] Internet-Draft Network Models for IETF Network Slices November 2026 In contrast, capabilities (e.g., feasibility checks, reusable SLO/SLE templates, or policy inheritance semantics) are not direct parameter mappings. These capabilities typically rely on Network Slice Controller (NSC) behavior, orchestration logic, or additional models, and are therefore identified separately as partial mappings or gaps. 5.1. Relationship Between RFC 9543 Network Slice Service Model Parameters and L3SM and L2SM For L3SM and L2SM, the mapping is primarily service-oriented. Network Slice Service Model (NSSM) constructs such as SDPs and Connectivity Constructs may be mapped to service sites, access points, or VPN service topology abstractions. Service-level parameters such as MTU, bandwidth, QoS, classification, and multicast/BUM support may have direct or partial equivalents. However, NSSM capabilities such as reusable SLO/SLE templates, connection-group-level policy inheritance, feasibility checks, and test-only behavior are not service parameters and should be treated separately. 5.1.1. Parameter Mapping This section presents an initial analysis of the relationship between the RFC 9543 Network Slice Service model parameters and the L3SM and L2SM service model parameters. The L3SM service parameters are defined in Section 6.2 of [RFC8299]. The following parameters are considered, so far: Bandwidth: This parameter indicates the bandwidth requirement between each CE and PE participating in the service, then referring essentially to the required WAN link bandwidth. It is expressed in terms of bits per second and individually specified for both input and output. Despite it is not stated in RFC 8299, this parameter can be interpreted as the CIR/PIR expected for the CE - PE connection. MTU: This parameter indicates the maximum PDU size expected for the layer-3 service. It is relevant since packets could be discarded in case the customer sends packets with longer MTU than the one expressed by this parameter. QoS: Regarding QoS, two different kind of parameters are detailed. * QoS classification policy:This policy is used to classify the traffic received from the customer, and it is expressed as a set of ordered rules. It is used for marking the input traffic Barguil, et al. Expires 10 May 2027 [Page 14] Internet-Draft Network Models for IETF Network Slices November 2026 (from CE to PE) when the customer flows match any of the rules in the list, setting the appropriate target class of service (target-class-id). * QoS profile:This profile defines the traffic-scheduling to be applied to the flows for either Site-to-WAN, WAN-to-Site, or both directions. It contains the following information per class of service: rate-limit, latency, jitter and guaranteed bandwidth. Multicast: This parameter identifies if the service is multicast, and if so, what is the role of the site in the customer multicast service topology (i.e., source, receiver, or both). It also defines the kind of multicast relationship with the customer (i.e., as a router requiring PIM, host requiring either Internet Group Management Protocol (IGMP) or Multicast Label Distribution Protocol (MLDP), or both), as well as the support of IPv4, IPv6 or both. Similarly, the L2SMs parameters are described in Sections 5.9 and 5.10 of [RFC8466]. Bandwidth: This parameter is related to the bandwidth between both CE and PE and can be expressed as CIR/EIR/PIR, in the ingress or egress direction, taking the CE as the point of reference. MTU: This parameter refers to the maximum layer-2 PDU frame size. QoS: The specification of the QoS follows a similar structure to the one described in the case of L3SM. Some differences apply, for instance, at the time of QoS classification, which is performed on top of layer-2 parameters (e.g., MAC addresses). Broadcast, unknown-unicast and multicast (BUM) traffic: This parameter allows to determine if a site acts as source, receiver, or both. Availability: This parameter in the L2SM model relates to the capability of supporting multi-homing. On the other hand, the RFC 9543 Network Slice Service YANG module supports a number of SLOs and SLEs in the form of Network Slice Service policy attributes. Such policy can apply to per-Network Slice, per-connection group or per-connection individually (overriding of attributes is allowed as more granular information is provided). The following SLO attributes are detailed: * One-way/Two-way bandwidth, indicating the guaranteed minimum bandwidth between any two NSEs (unidirectional / bidirectional). * One-way/Two-way latency, indicating the guaranteed minimum latency between any two NSEs (unidirectional / bidirectional). Barguil, et al. Expires 10 May 2027 [Page 15] Internet-Draft Network Models for IETF Network Slices November 2026 * One-way/Two-way delay variation, indicating the maximum permissible delay variation of the slice (unidirectional / bidirectional). * One-way/Two-way packet loss, indicating the maximum permissible packet loss rate between endpoints (unidirectional / bidirectional). Additionally, the following SLEs are defined: * MTU, referring to the maximum Protocol data unit (PDU) size that the customer may use. * Security, indicating if encryption or other security measures are required between two endpoints. * Isolation, as a way of indicating the isolation level expected by the customer in the allocation of network resources. * Maximum occupancy level, to express the amount of flows to be admitted (and optionally a maximum number of countable resource units such as IP or MAC addresses). Thus, an initial mapping between the L3SM, L2SM, and RFC 9543 Network Slice Service model can be performed as indicated in the following table. +-------------------+-----------------------+--------------------------+ | L3SM (RFC 8299) | L2SM (RFC 8466) | RFC 9543 NSS YANG Model | +-------------------+-----------------------+--------------------------+ | Bandwidth | Bandwidth (CIR, PIR) | Sum of bandwidth SLO per | | | | SDP counting all | | | | connections | +-------------------+-----------------------+--------------------------+ | MTU | MTU | | | (Layer 3 Service) | (Layer 2 Service) | MTU attribute of the | | | | attachment circuit | | | | supporting the SDP | | | | | +-------------------+-----------------------+--------------------------+ | QoS | QoS | QoS | +-------------------+-----------------------+--------------------------+ | QoS | QoS | Defined in the model as | | classification | classification | incomming-qos-policy and | | Policy | Policy | outgoing-qos-policy | | | | to be applied per | | | | SDP | +-------------------+-----------------------+--------------------------+ Barguil, et al. Expires 10 May 2027 [Page 16] Internet-Draft Network Models for IETF Network Slices November 2026 | QoS Profile | QoS Profile | | | - rate-limit | - rate-limit | Defined in the model as | | | | rate-limits of the | | | | attachment-circuit | | | | supporting the SDP | +-------------------+-----------------------+--------------------------+ | QoS Profile | QoS Profile | One-way / Two-way | | - latency | - latency | latency SLO | | | | | +-------------------+-----------------------+--------------------------+ | QoS Profile | QoS Profile | One-way / Two-way | | - jitter | - jitter | delay variation SLO | | | | | +-------------------+-----------------------+--------------------------+ | QoS Profile | QoS Profile | One-way / Two-way | | - bandwidth | - bandwidth | bandwidth SLO | | | | | +-------------------+-----------------------+--------------------------+ | Multicast | Broadcast, Unknown, | The need of replication | | | Unicast and Multicast | can be inferred from | | | (BUM) | connectivity-type. | | | | Further | | | | details are not | | | | available (e.g. | | | | source or receiver role)| +-------------------+-----------------------+--------------------------+ | | Availability as dual | Availability as the ratio| | | homing | of up-time to total_time | | | | (up-time+ down-time). | +-------------------+-----------------------+--------------------------+ Table 1: "Mapping of RFC 9543 Network Slice Service and The LxSM Service Attribute" The following considerations can be made: * While the QoS profile in the L3SM and the L2SM applies per service class, the parameters in the RFC 9543 Network Slice Service Interface apply per connection. So if per- class granularity is required in an RFC 9543 Network Slice, then different connections have to be defined between the same end- points, one per service class. Barguil, et al. Expires 10 May 2027 [Page 17] Internet-Draft Network Models for IETF Network Slices November 2026 * A number of attributes are not defined in the L3SM nor the L2SM, such as packet loss, isolation, or security. Then, the L3SM and L2SM could not be sufficient to realize RFC 9543 Network Slice Services with such specific needs, unless those other objectives and expectations are provided by other means (e.g., realizing the L3SM through technologies guaranteeing dedicated resource allocation such as OTN). 5.1.2. Functional and Capability Alignment An initial analysis of the functional and capability alignment between RFC 9543 Network Slice Service and The LxSM Services is summarized in Table 2. +--------------------+--------------------+--------------------+------------------------------+ | NSSM Capability | L3SM | L2SM | Comments / Status | +--------------------+--------------------+--------------------+------------------------------+ | - SLO/SLE templates| Not supported | Not supported | Gap: no reusable templates | | - SLO/SLE hierarchy| Not supported | Not supported | Gap: no inheritance model | | - Connection groups| No direct | No direct | Partial | | | equivalent | equivalent | | | - Custom topology | Limited | Limited | Partial / Gap | | - Performance | Limited service | Limited service | Partial | | monitoring | state | state | | | - Feasibility check| N/A | N/A | NSC capability | | - Test-only | N/A | N/A | NSC capability | +--------------------+--------------------+--------------------+------------------------------+ Table 2: "Alignment of RFC 9543 Network Slice Service and The LxSM Service Models" 5.2. Relationship Between RFC 9543 Network Slice Service Model Parameters and the L3NM and L2NM For L3NM and L2NM, the mapping is network-realization-oriented. NSSM SDPs may be mapped to SAPs, Attachment Circuits, bearers, or network access constructs, while Connectivity Constructs may be mapped to VPN/network topology and connectivity parameters. Parameters such as MTU, bandwidth, CIR/PIR, QoS profile, classification policy, QoS action, and multicast/BUM support can be mapped directly or partially. Capabilities such as feasibility checks, performance monitoring, custom topology processing, and SLO/SLE inheritance/ override are better described as controller or orchestration capabilities rather than as direct LxNM parameters. Barguil, et al. Expires 10 May 2027 [Page 18] Internet-Draft Network Models for IETF Network Slices November 2026 5.2.1. Parameter mapping This section presents an initial analysis of the relationship between RFC 9543 Network Slice Service model parameters and the L3NM and the L2NM parameters. The L3NM service parameters are defined in Section 7.6.6 of [RFC9182]. As made in the previous section, some basic parameters are considered: * Bandwidth: The L3NM defines bandwidth in terms of the 'pe-to-ce- bandwidth' and 'ce-to-pe-bandwidth'. Both values are defined in absolute value in bps per interface. The model supports the usage of QoS policies to include inbound and outbound Rate limits. * MTU: The L3NM only supports the definition at the 'vpn-network- access' level. * QoS: The quality of service is differentiated in three-levels: - QoS Profile: Allows the reference of an existing profile. The profile creation is out of scope of the model. - QoS classification: Defines a set of classification rules. Each rule has an identifier ('id'), match criteria based on Layer 3 and Layer 4 fields (e.g., lower and upper port ranges) or on the application, and a target class of service ('target- class-id'). - QoS Action: Defines rules that apply inbound and outbound rate limits to a given class of service ('target-class-id'). * Multicast: mVPN is supported at vpn-node and vpn-network-access; Each level includes Rendezvous Point (RP), IGMP, PIM, and MLD definitions. Similarly, the L2NM parameters are described in Section 7.6.6 of [RFC9291]: * Bandwidth: The L2NM considers the same parameters 'pe-to-ce- bandwidth' and 'ce-to-pe-bandwidth'. However, per definition, the L2NM supports the differentiation of CIR, PIR values. It includes the same set of values described for the L2SM. Barguil, et al. Expires 10 May 2027 [Page 19] Internet-Draft Network Models for IETF Network Slices November 2026 * MTU: The L2NM differentiates among Service MTU and interface MTU. The MTU mismatch configuration is also supported as part of the 'vpn-service' configuration. * QoS: The quality of service is differentiated in two-levels: - QoS Profile: Reference an existing profile. Creation is out of scope of the model. - QoS Classification: Defines a set of classification rules. Each rule has an identifier ('id'), match criteria based on the flow (e.g., source and destination MAC addresses, VLAN ID (dot1q), PCP, DSCP, or color type) or on the application, and a target class of service ('target-class-id'). * Multicast: Discard options are available for unknown Broadcast, Unicast or Multicast (BUM). Thus, an initial mapping between the L3NM, L2NM, and RFC 9543 Network Slice Service model can be performed as indicated in the following table: Barguil, et al. Expires 10 May 2027 [Page 20] Internet-Draft Network Models for IETF Network Slices November 2026 +-------------------+-----------------------+--------------------------+ | L3NM (RFC 9182) | L2NM (RFC 9291) | RFC 9543 NSS YANG Model | +-------------------+-----------------------+--------------------------+ | Bandwidth | Different types: | Sum of bandwidth SLO per | | between | per CoS, per VPN net- | SDP counting all | | Ce-PE | work-access, per site | connections | +-------------------+-----------------------+--------------------------+ | MTU | MTU | | | (Layer 3 Service) | (Layer 2 Service) | MTU attribute of the | | | | attachment circuit | | | | supporting the SDP | | | | | +-------------------+-----------------------+--------------------------+ | QoS | QoS | QoS | +-------------------+-----------------------+--------------------------+ | QoS | QoS | Defined in the model as | | classification | classification | network-access-qos- | | Policy | Policy | policy-name | | Based on layer 3 | Based on layer 2 | to be applied per | | and 4 details | details | access-point. | +-------------------+-----------------------+--------------------------+ | QoS Profile | QoS Profile | | | - rate-limit | - rate-limit | Defined in the model as | | | | rate-limit of the | | | | attachment-circuit | | | | supporting the SDP. | +-------------------+-----------------------+--------------------------+ | QoS Profile | QoS Profile | One-way / Two-way | | - Not Defined | - Not Defined | latency SLO | | | | | +-------------------+-----------------------+--------------------------+ | Multicast | Broadcast, Unknown, | The need of replication | | | Unicast and Multicast | can be inferred from | | | (BUM) | connectivity-type. | | | | Further | | | | details are not | | | | available (e.g. | | | | source or receiver role)| +-------------------+-----------------------+--------------------------+ | | | Availability as the ratio| | | | of up-time to total_time | | | | (up-time + down-time). | +-------------------+-----------------------+--------------------------+ Table 3: Mapping of RFC 9543 Network Slice Service and The LxNM Service Attribute Barguil, et al. Expires 10 May 2027 [Page 21] Internet-Draft Network Models for IETF Network Slices November 2026 5.2.2. Functional and Capability Alignment An initial analysis of the functional and capability alignment between RFC 9543 Network Slice Service and The LxNM Services is summarized in Table 4. +--------------------+--------------------+--------------------+------------------------------+ | NSSM Capability | L3NM | L2NM | Comments / Status | +--------------------+--------------------+--------------------+------------------------------+ | - SLO/SLE templates| No direct | No direct | Gap / Partial | | | equivalent | equivalent | | | - SLO/SLE hierarchy| Not supported | Not supported | Gap: controller logic needed | | - Connection groups| Not explicit | Not explicit | Partial | | - Custom topology | Requires extra | Requires extra | Partial / Gap | | | models | models | | | - Performance | Telemetry/state | Telemetry/state | Partial | | monitoring | | | | | - Feasibility check| Uses network data | Uses network data | NSC capability | | - Test-only | N/A | N/A | NSC capability | | - Recursive slice | Not supported | Not supported | Architecture capability | | usage | | | | +--------------------+--------------------+--------------------+------------------------------+ Table 4: "Alignment of RFC 9543 Network Slice Service and The LxNM Network Models" 5.3. Summary The analysis highlights a set of functional gaps between the NSSM and the L3SM/L2SM and L3NM/L2NM models. These gaps are not necessarily limitations of the LxSM/LxNM models, but rather reflect differences in abstraction level and scope. In particular, the NSSM introduces capabilities that go beyond traditional service and network parameterization, including: * Reusable SLO/SLE templates that allow policy reuse across multiple slice services * Hierarchical policy application with inheritance and override at slice-service, connection-group, and connectivity-construct levels * Grouping constructs (connection-groups) that enable coordinated control across multiple connectivity constructs * Explicit support for customer-driven topology constraints * Integrated service monitoring and performance observation at slice level * Feasibility check and "test-only" capabilities to validate service requests prior to instantiation Barguil, et al. Expires 10 May 2027 [Page 22] Internet-Draft Network Models for IETF Network Slices November 2026 These capabilities are typically not modeled as native parameters in L3SM/L2SM or L3NM/L2NM. Instead, they rely on the behavior of the Network Slice Controller (NSC), orchestration systems, or additional models (e.g., topology or telemetry models). Therefore, such aspects should be interpreted as controller-level or architecture-level capabilities, rather than as direct parameter mappings. When translating NSSM constructs into LxSM/LxNM models, these capabilities may require: * decomposition into multiple lower-level parameters, * use of additional YANG models, * or implementation-specific logic in the NSC. 6. RFC 9543 Network Slice Procedure 6.1. RFC 9543 Network Slice Provisioning Workflow An RFC 9543 Network Slice may use several underlying technologies. A new [RFC9543] Network Slice may be initiated following these steps: 1. A higher level system requests services with specific characteristics via the customer-facing APIs 2. This request is processed by an NSC which specifies a mapping between service request to any services, tunnels, and paths models. 3. A series of requests for creation of services, tunnels and paths will be sent to the network to realize the transport slice. Variations of this flow can be considered: * The customer requests bearers and attachment circuits, independent of any service that will be delivered over them. * The customer places a service-specific request with references to ACs. * The customer may update the bearers/AC/service delivery points during the lifetime of a service. As a functional entity responsible for managing a network domain, a network controller can expose a set of YANG models to an NSC. An NSC can invoke these models during the realization of an [RFC9543] Network Slice Service. The following network models can be used for realization of [RFC9543] Network slices: * LxVPN network models: These models describe a VPN service from the network point of view. It supports the creation of Layer 3 and Layer 2 services using several control planes. Barguil, et al. Expires 10 May 2027 [Page 23] Internet-Draft Network Models for IETF Network Slices November 2026 * Traffic Engineering models: These models allow to manipulate Traffic Engineering tunnels within the network segment. Technology-specific extensions allow to work with a desired technology (e.g. MPLS RSVP-TE tunnels, Segment Routing paths, OTN tunnels, etc.) * TE Service Mapping extensions: These extensions allow to specify for LxVPN the details of an underlay based on TE. * ACLs and routing policies models: Even though ACLs and routing policies are device models, its exposure in the Network Slice Service of a domain controller allows to provide an additional granularity that the network domain controller is not able to infer on its own. 6.2. LxVPN Network Models The framework defined in [RFC8969] compiles a set of YANG data models for automating network services. The data models can be used during the service and network management life cycle (e.g., service instantiation, service provisioning, service optimization, service monitoring, service diagnosing, and service assurance). The so called Network models could be reused for the realization of Network slice requests. The following models are examples of Network models that describe services. * [RFC9182]: A Layer 3 VPN Network YANG Model * [RFC9291]: A Layer 2 VPN Network YANG Model 6.3. Traffic Engineering Models TEAS has defined a collection of models to allow the management of Traffic Engineering tunnels: * [I-D.ietf-teas-yang-te]: A YANG Data Model for Traffic Engineering Tunnels, Label Switched Paths and Interfaces. The model allows to instantiate paths in a TE enabled network. Note that technology augmented models are required for specific per-technology instantiations. Barguil, et al. Expires 10 May 2027 [Page 24] Internet-Draft Network Models for IETF Network Slices November 2026 6.4. Traffic Engineering Service Mapping The IETF has defined a YANG model to set up the procedure to map VPN service/network models to the TE models. This model, known as service mapping, allows the network controller to assign/retrieve transport resources allocated to specific services. At the moment there is one service mapping model [I-D.ietf-teas-te-service-mapping-yang]. The "Traffic Engineering (TE) and Service Mapping Yang Model" augments the VPN service and network models. 7. Potential Models Usage in Alternative RFC 9543 NSC Architectures This section does not intend to be prescriptive but descriptive about the potential usage of existing and proposed models for the provision of an RFC 9543 Network Slice Service. [I-D.ietf-teas-ns-controller-models] shows a potential internal structure of an RFC 9543 Network Slice Controller which can be divided into two components: * RFC 9543 Network Slice Mapper: This high-level component processes the customer request, putting it into the context of the overall RFC 9543 Network Slices in the network. * RFC 9543 Network Slice Realizer: This high-level component processes the complete view of transport slices including the one requested by the customer, decides the proper technologies for realizing the RFC 9543 Network Slice and triggers its realization. Note that this division in functional components of an RFC 9543 NSC is provided as an implementation option, not constraining any other implementation of functional structure. Barguil, et al. Expires 10 May 2027 [Page 25] Internet-Draft Network Models for IETF Network Slices November 2026 Higher Level System | | NSC Network Slice Service +-------------------------+ | NSC | | | v | | +-----------------+ | | | | | | | NS Mapper | | | | | | | +-----------------+ | | | | | v | | +-----------------+ | | | | | | | NS Realizer | | | | | | | +-----------------+ | | | | +-------------------------+ | NSC SBI v Network Controllers Figure 6: RFC 9543 Network Slice Controller Structure The details of the RFC 9543 Network Slice Mapper and Realizer are provided below for various NSC implementations. 7.1. RFC 9543 Network Slice Service Requested to Hierarchical Network Controller Referring to Figure 2, in an integrated architecture where an NSC is part of a Hierarchical SDN controller, the NSC and the Hierarchical Network Controller should share the same internal data and the same Network Slice Service interface. Thus, the H-SDN module must be able to: * Map: The NSC should process the customer request received through [I-D.ietf-teas-ietf-network-slice-nbi-yang]. The mapping process takes the network-slice SLOs selected by the customer selecting available Routing Policies and Forwarding policies for accomplishing those SLOs. * Realize: Create necessary network requests. The slice's realization can be translated into one or several LxNM Network requests, depending on the number of underlay controllers. Thus, the NSC must have a complete view of the network to map the orders Barguil, et al. Expires 10 May 2027 [Page 26] Internet-Draft Network Models for IETF Network Slices November 2026 and distribute them across domains. The realization should include the expansion/selection of Forwarding Policies, Routing Policies, VPN policies, and Underlay transport preference. To maintain the data coherence between the control layers, the RFC 9543 Network Slice Service identifier (the 'id' of the 'slice- service' list in [I-D.ietf-teas-ietf-network-slice-nbi-yang]) must be directly mapped to the transport-instance-id at the VPN-Node level. + | | RFC 9543 Network Slice Request: draft-ietf-teas-ietf-network-slice-nbi-yang | * slice-service id | +-------------------v------------------+ | | | Hierarchical Network | | Controller/Orchestrator | | | | +-------------------------------+ | | | RFC 9543 NSC | | | +-------------------------------+ | | | +-------------------+------------------+ RFC 9543 Network Slice Realizer: LxNM VPN-id | * transport-instance-id | | +--------------+---------------+ | | v v +-------------+----------+ +-------------+----------+ | Network Controller | | Network Controller | +-------------+----------+ +-------------+----------+ | | | | v v Network Elements Network Elements Figure 7: Workflow for the Slice Request in an Integrated Architecture. Barguil, et al. Expires 10 May 2027 [Page 27] Internet-Draft Network Models for IETF Network Slices November 2026 7.2. RFC 9543 Network Slice Service Requested to Network Slice Controller Referring to Figure 3, when the Network Slice Controller is a standalone controller module, the NSC should perform the same two tasks (Map and Realize) described at the beginning of this section: * Map: Process the customer request. The customer request can be sent using [I-D.ietf-teas-ietf-network-slice-nbi-yang]. The customer can also perform the Network Slice request using customized topologies. * Realize: Create necessary network requests. The slice's realization will be translated into one LxNM Network request. As the NSC has a topological view of the network, the realization can include the customer's traffic engineering transport preferences and policies. + |RFC 9543 Network Slice Request draft-ietf-teas-ietf-network-slice-nbi-yang * slice-service id | +-------------v---------------------+ | RFC 9543 Network Slice Controller | +-------------+---------------------+ | RFC 9543 Network Slice Realizer: LxNM VPN-id | * Underlay-transport * transport-instance-id | +-------------v----------------+ | Network Controller | +-------------+----------------+ | | v Network Elements Figure 8: Workflow for the Slice Request in a Standalone Architecture. Barguil, et al. Expires 10 May 2027 [Page 28] Internet-Draft Network Models for IETF Network Slices November 2026 7.3. Network Slice Controller as Part of the Domain Controller The Network Slice Controller can be a module of the network controller. In that case, two options are available. One is to share the same device data model in the customer-facing and network- facing interfaces of the network controller. The direct translation would reduce the service logic implemented at the network controller level, grouping the mapping and translation into a single task: * Realize: As the device models are part of the network controller's customer-facing interface thus, the realization can be done by the network controller applying a simple service logic to send the Network elements. + | Slice Request based on | Device Models | | +------------------v------------------+ | | | Network | | Controller | | | | +------------------------------+ | | | Network Slice Controller | | | +------------------------------+ | | | +------------------+------------------+ | Device Models | v Network Elements Figure 9: Workflow for the Slice Request when the NSC is Part of the Network Controller (Device Models). A second option introduces a more complex logic in the network controller and creates an abstraction layer to process the transport slices. In that case, the controller should receive Network Slices creation requests and maintain the whole set of implemented slices: * Map & Realize: The mapping and realization can be done by the Domain controller applying the service logic to create policies directly on the Network elements. Barguil, et al. Expires 10 May 2027 [Page 29] Internet-Draft Network Models for IETF Network Slices November 2026 + |Slice Request draft-ietf-teas-ietf-network-slice-nbi-yang * slice-service id | | +------------------v------------------+ | | | Network | | Controller | | | | +------------------------------+ | | | Network Slice Controller | | | +------------------------------+ | | | +------------------+------------------+ | | v Network Elements Figure 10: Workflow for the Slice Request when the NSC is Part of the Network Controller (Slice Abstraction). 8. Security Considerations There are two main aspects to consider. On the one hand, [RFC9543] Network Slice has a set of security-related requirements, such as hard isolation of the slice, or encryption of the communications through the slice. All those requirements need to be analyzed in detail and clearly mapped to the Network Controller and device interfaces. On the other hand, the communication between the [RFC9543] Network Slice Controller and the network controller (or controllers or hierarchy of controllers) needs to follow the same security considerations as with the network models. The network YANG modules define schemas for data that is designed to be accessed via network management protocols such as NETCONF [RFC6241] or RESTCONF [RFC8040]. YANG-based management protocols (1) have to use a secure transport layer (e.g., Secure Shell (SSH) [RFC4252], TLS [RFC9846], and QUIC [RFC9000]) and (2) have to use mutual authentication. Barguil, et al. Expires 10 May 2027 [Page 30] Internet-Draft Network Models for IETF Network Slices November 2026 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 following summarizes the foreseen risks of using the Network Models to instantiate [RFC9543] Network Slices: * Malicious clients attempting to delete or modify VPN services that implement an [RFC9543] Network Slice. The malicious client could manipulate security-related aspects of the network configuration that impact the requirements of the slice, failing to satisfy the customer requirement. * Unauthorized clients attempting to create/modify/delete a VPN that implements an [RFC9543] Network Slice service. * Unauthorized clients attempting to read VPN services related information for VPN services that implement an [RFC9543] Network Slice. * Malicious clients attempting to leak traffic of the slice. 9. IANA Considerations This document is informational and does not require IANA allocations. 10. Conclusions A wide variety of YANG models are currently under definition in IETF that can be used by Network Controllers to instantiate RFC 9543 Network Slices. Some of the [RFC9543] Network Slice requirements can be satisfied by multiple means, as there are multiple choices available. However, other requirements are still not covered by the existing models. A more detailed definition of those uncovered requirements would be needed. Finally a consensus on the set of models to be exposed by Network Controllers would facilitate the deployment of [RFC9543] Network Slices. Contributors The following people (in alphabetical order) also contributed to the document: Daniel King, Old Dog Consulting (daniel@olddog.co.uk) Reza Rokui, Ciena (rrokui@ciena.com) References Normative References Barguil, et al. Expires 10 May 2027 [Page 31] Internet-Draft Network Models for IETF Network Slices November 2026 [I-D.ietf-teas-ietf-network-slice-nbi-yang] Wu, B., Dhody, D., Rokui, R., Saad, T., and J. Mullooly, "A YANG Data Model for the RFC 9543 Network Slice Service", Work in Progress, Internet-Draft, draft-ietf- teas-ietf-network-slice-nbi-yang-26, 26 May 2026, . [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", RFC 7950, DOI 10.17487/RFC7950, August 2016, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . [RFC8299] Wu, Q., Ed., Litkowski, S., Tomotaki, L., and K. Ogaki, "YANG Data Model for L3VPN Service Delivery", RFC 8299, DOI 10.17487/RFC8299, January 2018, . [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration Access Control Model", STD 91, RFC 8341, DOI 10.17487/RFC8341, March 2018, . [RFC8466] Wen, B., Fioccola, G., Ed., Xie, C., and L. Jalil, "A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service Delivery", RFC 8466, DOI 10.17487/RFC8466, October 2018, . [RFC9181] Barguil, S., Gonzalez de Dios, O., Ed., Boucadair, M., Ed., and Q. Wu, "A Common YANG Data Model for Layer 2 and Layer 3 VPNs", RFC 9181, DOI 10.17487/RFC9181, February 2022, . [RFC9182] Barguil, S., Gonzalez de Dios, O., Ed., Boucadair, M., Ed., Munoz, L., and A. Aguado, "A YANG Network Data Model for Layer 3 VPNs", RFC 9182, DOI 10.17487/RFC9182, February 2022, . Barguil, et al. Expires 10 May 2027 [Page 32] Internet-Draft Network Models for IETF Network Slices November 2026 [RFC9291] Boucadair, M., Ed., Gonzalez de Dios, O., Ed., Barguil, S., and L. Munoz, "A YANG Network Data Model for Layer 2 VPNs", RFC 9291, DOI 10.17487/RFC9291, September 2022, . [RFC9408] Boucadair, M., Ed., Gonzalez de Dios, O., Barguil, S., Wu, Q., and V. Lopez, "A YANG Network Data Model for Service Attachment Points (SAPs)", RFC 9408, DOI 10.17487/RFC9408, June 2023, . [RFC9543] Farrel, A., Ed., Drake, J., Ed., Rokui, R., Homma, S., Makhijani, K., Contreras, L., and J. Tantsura, "A Framework for Network Slices in Networks Built from IETF Technologies", RFC 9543, DOI 10.17487/RFC9543, March 2024, . Informative References [I-D.dhody-teas-ietf-network-slice-mapping] Dhody, D. and B. Wu, "IETF Network Slice Service Mapping YANG Model", Work in Progress, Internet-Draft, draft- dhody-teas-ietf-network-slice-mapping-08, 4 July 2026, . [I-D.ietf-teas-ietf-network-slice-use-cases] Contreras, L. M., Homma, S., Ordonez-Lucena, J. A., Tantsura, J., and H. Nishihara, "IETF Network Slice Use Cases and Attributes for the Slice Service Interface of IETF Network Slice Controllers", Work in Progress, Internet-Draft, draft-ietf-teas-ietf-network-slice-use- cases-01, 24 October 2022, . [I-D.ietf-teas-ns-controller-models] Contreras, L. M., Rokui, R., Tantsura, J., Wu, B., and X. Liu, "IETF Network Slice Controller and its Associated Data Models", Work in Progress, Internet-Draft, draft- ietf-teas-ns-controller-models-08, 31 July 2026, . Barguil, et al. Expires 10 May 2027 [Page 33] Internet-Draft Network Models for IETF Network Slices November 2026 [I-D.ietf-teas-te-service-mapping-yang] Lee, Y., Dhody, D., Fioccola, G., Wu, Q., Ceccarelli, D., and J. Tantsura, "Traffic Engineering (TE) and Service Mapping YANG Data Model", Work in Progress, Internet- Draft, draft-ietf-teas-te-service-mapping-yang-19, 4 July 2026, . [I-D.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, 26 March 2026, . [RFC4252] Ylonen, T. and C. Lonvick, Ed., "The Secure Shell (SSH) Authentication Protocol", RFC 4252, DOI 10.17487/RFC4252, January 2006, . [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, . [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, . [RFC8309] Wu, Q., Liu, W., and A. Farrel, "Service Models Explained", RFC 8309, DOI 10.17487/RFC8309, January 2018, . [RFC8453] Ceccarelli, D., Ed. and Y. Lee, Ed., "Framework for Abstraction and Control of TE Networks (ACTN)", RFC 8453, DOI 10.17487/RFC8453, August 2018, . [RFC8969] Wu, Q., Ed., Boucadair, M., Ed., Lopez, D., Xie, C., and L. Geng, "A Framework for Automating Service and Network Management with YANG", RFC 8969, DOI 10.17487/RFC8969, January 2021, . [RFC9000] Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based Multiplexed and Secure Transport", RFC 9000, DOI 10.17487/RFC9000, May 2021, . Barguil, et al. Expires 10 May 2027 [Page 34] Internet-Draft Network Models for IETF Network Slices November 2026 [RFC9833] Boucadair, M., Ed., Roberts, R., Ed., Gonzalez de Dios, O., Barguil, S., and B. Wu, "A Common YANG Data Model for Attachment Circuits", RFC 9833, DOI 10.17487/RFC9833, September 2025, . [RFC9834] Boucadair, M., Ed., Roberts, R., Ed., Gonzalez de Dios, O., Barguil, S., and B. Wu, "YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS)", RFC 9834, DOI 10.17487/RFC9834, September 2025, . [RFC9835] Boucadair, M., Ed., Roberts, R., Gonzalez de Dios, O., Barguil, S., and B. Wu, "A Network YANG Data Model for Attachment Circuits", RFC 9835, DOI 10.17487/RFC9835, September 2025, . [RFC9846] Rescorla, E., "The Transport Layer Security (TLS) Protocol Version 1.3", RFC 9846, DOI 10.17487/RFC9846, July 2026, . Authors' Addresses Samier Barguil (editor) Nokia Calle de María Tubau, 9 28050 Madrid Spain Email: samier.barguil@nokia.com Luis Miguel Contreras (editor) Telefonica Distrito T 28050 Madrid Spain Email: luismiguel.contrerasmurillo@telefonica.com Victor Lopez Nokia Calle de María Tubau, 9 28050 Madrid Spain Email: victor.lopez@nokia.com Barguil, et al. Expires 10 May 2027 [Page 35] Internet-Draft Network Models for IETF Network Slices November 2026 Oscar Gonzalez de Dios Telefonica Distrito T 28050 Madrid Spain Email: oscar.gonzalezdedios@telefonica.com Mohamed Boucadair Orange Email: mohamed.boucadair@orange.com Barguil, et al. Expires 10 May 2027 [Page 36]