A YANG Data Model for Network Resource Partition (NRP)

defines IETF network slice services that provide connectivity coupled with network resources commitment between a number of endpoints over a shared network infrastructure and, for scalability concerns, defines network resource partition (NRP) to host one or a group of network slice services according to characteristics including SLOs and SLEs. analyzes the scalability issues of network slice services in detail and suggests candidate technologies of control and forwarding planes of the NRP. This document defines a YANG model of NRP that the IETF NSC (Network Slice controller) can use to manage NRP instances to realize the network slicing services. According to the YANG model classification of , the NRP model is a network configuration model.

The following terms are defined in and are used in this specification: configuration data state data The following terms are defined in and are used in this specification: augment data model data node The terminology for describing YANG data models is found in .

The tree diagram used in this document follows the notation defined in .

As specified in , an NRP is a subset of dedicated or shared nodes and links in a network, and includes associated control plane and forwarding plane technologies so that the traffic received from NRP edge nodes that is characterized to match the NRP traffic classification rule is constrained to the NRP exclusive topology and resource allocation. The NRP allows network operators to manage the resources of IETF network slices which are used to provide network slice service traffic with specific SLOs and SLEs. An NRP is a subset of resources allocated from a physical network or logical network. Depending on the SLO and SLE requirements of the slicing service and also the available resources of the operator's network, there are several options of creating an NRP. One option is that each physical link is allocated to only one specific NRP, and different NRPs do not share any physical link. One more typical option is that multiple NRPs share the same physical links, and each NRP is built with virtual links with a certain subset of the bandwidth available on the physical links to provide network resource isolation. To constrain the traffic that matches NRP traffic classification to be forwarded based on the NRP topology and resources, an NRP also includes the control and forwarding plane functions. As defined in , the draft discusses NRP control plane and data plane requirements in different provisioning scenarios, and describes that the NRP control plane is used to exchange network resource attributes and associated logical topology information between nodes of the NRP so that NRP-specific routing and forwarding tables could be generated. For the NRP control plane, distributed control plane mechanism, such as Multi-topology, Flex-Algo or centralized SDN or hybrid combination could be defined. To help with forwarding entries, several data-plane encapsulation options are also discussed to carry NRP information in the NRP traffic packets. The example NRP data plane identifier could be the IPv6 addresses or the MPLS forwarding labels or dedicated NRP data-plane identifiers. An example of NRP instances and a physical network is illustrated in . In the example, each NRP instance has a customized network topology comprised of a set of links and nodes in the physical network. In control plane, each NRP could be associated with a multi-topology or a Flex-Algo. And it also has its own forwarding plane resources and identifiers which provide NRP-specific packet forwarding.

also describes the management of the NRP. After an NRP created, the NRP may need to be refined and modified as the network status and slice services change, and could be extended if necessary to meet the customers' demands. In addition to configuration management, the NRP should also provide detailed monitoring information about underlying resources to further provide monitoring for the hosted slice services.

One major application of network slices is 5G services. shows the use of the NRP model to realize the IETF Network Slice for the 5G use case, based on the reference framework defined in . The figure shows that the NSC uses the L3VPN network model to map to an IETF Network Slice service and uses the NRP model to map VPN traffic to underlying network resources, so that the SLO and SLE required by the IETF network slice service are ensured when the VPN service traverses the underlying network.

In the process of realizing an IETF network slice service, the NSC can use a static NRP instance or dynamically create one as one or a group of VPNs underlay construct. Compared with existing VPN underlying built with full mesh tunneling mechanisms, the NRP could provide resource isolation, topology constraints, and simplified configuration. Additionally, specific service flows of a VPN can be further optimized using SR policies defined in .

An NRP is modeled as network topology defined in with augmentations. A new network type "nrp" is defined. A network topology data instance containing the nrp network type, indicates an NRP instance. As discussed in , an NRP could have multiple control plane implementation options. For a better network scalability, an NRP does not require an independent Layer 3 topology, that is, multiple NRPs can share a same Layer 3 topology or TE topology. Thus, an NRP can use a predefined basic TE topology by referring to the TE network instance or a predefined basic Layer3 TE topology by referring to the network instance with both TE and Layer3 type enabled or other topology combination. The shows the example references between this module and other YANG modules.

|| network-id (key) || +-------------------------------+ | || network-types: { || | ietf-nrp: | | || te-topology || | +---------------------------+ | | || } || | | ietf-network-topology: | | | || || | | network-id (key) | | | |+------------------------+| | | network-types: { | | | | | | | nrp: | |--+ +--------------------------+ | | } | | | | | | | | +-----------------------------+ | +---------------------------+ | | | ietf-l3-te-topology: | | network-ref | | |+---------------------------+| | | | || ietf-network-topology: || +-------------------------------+ | || network-id (key) || | || network-types: { || +-->|| l3-unicast-topology || || te-topology || || } || || || |+---------------------------+| | | | | +-----------------------------+ ]]> But in some situations, an NRP may need its own Layer 3 topology or Traffic Engineering (TE) topology to support route forwarding or TE forwarding capability. Inheriting the extensibility from , an NRP can have several types of networks simultaneously. The Layer 3 Topologies model defined in can be used to enable an NRP unicast capable. And the TE Topology model defined in can be used to make an NRP TE capable. The shows the relationship between this module and other YANG modules.

The container "nrp" under 'network' of defines global parameters for an NRP, which defines the specific control plane and data plane mechanisms of an NRP. And also, the traffic steering policy of the NRP may include a dynamic color based policies or an ACL-based static ones. Each NRP instance consists of a set of nodes and a set of links. Each node and link have different attributes that represent the allocated resources or the operational status of the NRP. An NRP could support several resource partition methods, which are defined by 'link-partition-type'' under an NRP link, which can further be supported by FlexE or independent queue techniques. There are multiple modes of NRP operations to be supported as follows: NRP instantiation: Depending on the slice services types and also network status, there can be two types of approaches. One method is to create an NRP instance before the network controller processes the IETF network slice service request. Another one is that the network controller may start creating an NRP instance while configuring the IETF network slice service request. NRP modification: When the capacity of an existing NPR link is close to capacity, the bandwidth of the link could be increased. And when the NRP link or node resources are insufficient, new NRP links and nodes could be added. NRP Deletion: If the NSC determines that no slice service is using an NRP, the NSC can delete the NRP instance. NRP Monitoring: The NSC can use the NRP model to track and monitor NRP resource status and usage.

The description of the NRP data nodes are as follows: "nrp-id": Is an identifier that is used to uniquely identify an NRP instance within the network scope. NRP resources reservation: The nodes and links represent the network resource allocated for an NRP instance. 'bandwidth-reservation' specifies the bandwidth allocated to an NRP instance, or is overridden by the configuration of the NRP link. 'link-partition-type' specifies the resource partition types of the physical interfaces associated with an NRP link. NRP control plane: When an NRP shares an IGP topology or TE topology with other NRPs, "network-ref" or "te-topology-identifier“ is used to refer to the existing IGP network instance or TE topology instance. And an NRP can further use Multi-Topology Routing (MTR) or Flex-algo to refer to the IGP instance to generate its own NRP-specific forwarding tables. Multi-Topology Routing (MTR) is defined in , , and or Flex-algo is defined in . NRP data plane: Defines the data plane mechanism and the NRP identifier of the network domain managed by the network controller. The data plane mechanism could be based on MPLS or IPv6 forwarding. The container "data plane" is used to specify the NRP data plane encapsulation types and values that are used to identify NRP-specific network resources. The NRP data plane identifier is defined in and. NRP steering policy: The leaf-list "color-id" is used for dynamic traffic steering based on SR policy of an NRP and The leaf-list "acl-ref" is used for common traffic steering.

/nw:networks/network/network-id | | +--rw multi-topology-id? uint32 | | +--rw flex-algo-id? uint32 | +--rw te-topology-identifier | +--rw provider-id? te-global-id | +--rw client-id? te-global-id | +--rw topology-id? te-topology-id +--rw data-plane | +--rw global-resource-identifier | | +--rw nrp-dataplane-ipv6-type | | | +--rw nrp-dp-value? inet:ipv6-address | | +--rw nrp-dataplane-mpls-type | | +--rw nrp-dp-value? uint32 | +--rw nrp-aware-dp | +--rw nrp-aware-srv6-type! | +--rw nrp-aware-sr-mpls-type! +--rw steering-policy +--rw color-id* uint32 +--rw acl-ref* -> /acl:acls/acl/name augment /nw:networks/nw:network/nw:node: +--rw nrp +--rw nrp-aware-srv6 | +--rw nrp-dp-value? srv6-types:srv6-sid +--rw nrp-aware-sr-mpls +--rw nrp-dp-value? rt-types:mpls-label augment /nw:networks/nw:network/nt:link: +--rw nrp | +--rw link-partition-type? identityref | +--rw bandwidth-reservation | | +--rw (bandwidth-type)? | | +--:(bandwidth-value) | | | +--rw bandwidth-value? uint64 | | +--:(bandwidth-percentage) | | +--rw bandwidth-percent? rt-types:percentage | +--rw nrp-aware-srv6 | | +--rw nrp-dp-value? srv6-types:srv6-sid | +--rw nrp-aware-sr-mpls | +--rw nrp-dp-value? rt-types:mpls-label +--ro statistics +--ro admin-status? te-types:te-admin-status +--ro oper-status? te-types:te-oper-status +--ro one-way-available-bandwidth? | rt-types:bandwidth-ieee-float32 +--ro one-way-utilized-bandwidth? | rt-types:bandwidth-ieee-float32 +--ro one-way-min-delay? uint32 +--ro one-way-max-delay? uint32 +--ro one-way-delay-variation? uint32 +--ro one-way-packet-loss? decimal64 ]]>

<CODE BEGINS> file "ietf-nrp@2022-01-29.yang"

WG List: Editor: Bo Wu : Dhruv Dhody "; description "This YANG module defines a network data module for NRP(Network Resource Partition). Copyright (c) 2022 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself for full legal notices."; revision 2022-01-29 { description "This is the initial version of NRP YANG model."; reference "RFC XXX: A YANG Data Model for Network Resource Partition"; } identity link-partition-type { description "Base identity for interface partition type."; } identity virtual-sub-interface-partition { base link-partition-type; description "Identity for virtual interface or sub-interface, e.g. FlexE."; } identity queue-partition { base link-partition-type; description "Identity for queue partition type."; } identity nrp-dataplane-type { description "Base identity for NRP data plane type."; } identity nrp-dataplane-ipv6 { base nrp-dataplane-type; description "Identity for NRP specific packet forwarding of IPv6."; } identity nrp-dataplane-mpls { base nrp-dataplane-type; description "Identity for NRP specific packet forwarding of MPLS."; } identity nrp-dataplane-sr-mpls { base nrp-dataplane-type; description "Identity for NRP specific packet forwarding of SR MPLS."; } identity nrp-dataplane-srv6 { base nrp-dataplane-type; description "Identity for NRP specific packet forwarding of SRv6."; } /* * Groupings */ grouping nrp-bandwidth-reservation { description "Grouping for NRP bandwidth reservation."; container bandwidth-reservation { description "Container for NRP bandwidth reservation."; choice bandwidth-type { description "Choice of bandwidth reservation type."; case bandwidth-value { leaf bandwidth-value { type uint64; units "bps"; description "Bandwidth allocation for the NRP as absolute value."; } } case bandwidth-percentage { leaf bandwidth-percent { type rt-types:percentage; description "Bandwidth allocation for the NRP as a percentage of a link."; } } } } } grouping nrp-control-plane-attributes { description "Grouping for NRP control plane attributes."; container control-plane { description "The container of NRP control plane mechanisms."; container topology-ref { description "Container for topology reference."; container igp-topology-ref { description "Container for IGP topology reference."; uses nw:network-ref; leaf multi-topology-id { type uint32; description "The MT-id of an NRP."; } leaf flex-algo-id { type uint32; description "The flex-algo-id of an NRP."; } } uses te-types:te-topology-identifier; } } } grouping nrp-data-plane-attributes { description "Grouping for NRP data plane attributes."; container data-plane { description "The data plane mechanisms of an NRP. The forwarding plane could be MPLS, IPv6, SRv6, or SR-MPLS."; container global-resource-identifier { description "The container of global NRP data-plane ID."; container nrp-dataplane-ipv6-type { description "The container of IPv6 based NRP data-plane identifier."; leaf nrp-dp-value { type inet:ipv6-address; description "Indicates the IPv6 NRP data-plane identifier."; } } container nrp-dataplane-mpls-type { description "The container of MPLS based NRP data-plane identifier."; leaf nrp-dp-value { type uint32; description "Indicates MPLS metadata values to identify MPLS NRP data plane identifier, e.g. Ancillary data."; } } } container nrp-aware-dp { description "The container of SR based NRP data-plane identifier."; container nrp-aware-srv6-type { presence "Enables SRv6 data plane type."; description "The container of SRv6 based NRP data-plane identifier."; } container nrp-aware-sr-mpls-type { presence "Enables SR MPLS data plane type."; description "The container of SR MPLS based NRP data-plane identifier."; } } } } grouping nrp-traffic-steering-policy { description "The grouping of the NRP traffic steering policy."; container steering-policy { description "The container of a policy set matching an NRP traffic classifier."; leaf-list color-id { type uint32; description "A list of color ID for NRP traffic steering based on SR policy."; } leaf-list acl-ref { type leafref { path "/acl:acls/acl:acl/acl:name"; } description "A list of ACL for NRP traffic classification."; } } } grouping nrp-aware-id { description "The grouping of NRP aware SR ID."; container nrp-aware-srv6 { description "The container of SRv6 based NRP data plane identifier."; leaf nrp-dp-value { type srv6-types:srv6-sid; description "Indicates the SRv6 SID value as the NRP data plane identifier."; } } container nrp-aware-sr-mpls { description "The container of SR MPLS based NRP data plane identifier."; leaf nrp-dp-value { type rt-types:mpls-label; description "Indicates the SR MPLS ID value as the NRP data plane identifier."; } } } grouping nrp-topology-attributes { description "NRP global attributes."; container nrp { description "Containing NRP topology attributes."; leaf nrp-id { type uint32; description "NRP identifier."; } leaf nrp-name { type string; description "NRP Name."; } uses nrp-bandwidth-reservation; uses nrp-control-plane-attributes; uses nrp-data-plane-attributes; uses nrp-traffic-steering-policy; } // nrp } // nrp-node-attributes grouping nrp-node-attributes { description "NRP node scope attributes."; container nrp { description "Containing NRP attributes."; uses nrp-aware-id; } } // nrp-node-attributes grouping nrp-link-attributes { description "NRP link scope attributes."; container nrp { description "Containing NRP attributes."; leaf link-partition-type { type identityref { base link-partition-type; } description "Indicates the resource partition type of a link."; } uses nrp-bandwidth-reservation; uses nrp-aware-id; } } // nrp-statistics grouping statistics-per-nrp { description "Statistics attributes per NRP."; } // nrp-node-statistics grouping statistics-per-node { description "Statistics attributes per NRP node."; } // one-way-performance-metrics grouping one-way-performance-bandwidth { description "Grouping for one-way performance bandwidth."; leaf one-way-available-bandwidth { type rt-types:bandwidth-ieee-float32; units "bytes per second"; default "0x0p0"; description "Available bandwidth that is defined to be NRP link bandwidth minus bandwidth utilization. For a bundled link, available bandwidth is defined to be the sum of the component link available bandwidths."; } leaf one-way-utilized-bandwidth { type rt-types:bandwidth-ieee-float32; units "bytes per second"; default "0x0p0"; description "Bandwidth utilization that represents the actual utilization of the link (i.e. as measured in the router). For a bundled link, bandwidth utilization is defined to be the sum of the component link bandwidth utilizations."; } } // nrp-link-statistics grouping nrp-statistics-per-link { description "Statistics attributes per NRP link."; container statistics { config false; description "Statistics for NRP link."; leaf admin-status { type te-types:te-admin-status; description "The administrative state of the link."; } leaf oper-status { type te-types:te-oper-status; description "The current operational state of the link."; } uses one-way-performance-bandwidth; uses te-packet-types:one-way-performance-metrics-packet; } } augment "/nw:networks/nw:network/nw:network-types" { description "Defines the NRP topology type."; container nrp { presence "Indicates NRP topology"; description "The presence identifies the NRP type."; } } augment "/nw:networks/nw:network" { when 'nw:network-types/nrp:nrp' { description "Augment only for NRP topology."; } description "Augment NRP configuration and state."; uses nrp-topology-attributes; } augment "/nw:networks/nw:network/nw:node" { when '../nw:network-types/nrp:nrp' { description "Augment only for NRP topology."; } description "Augment node configuration and state."; uses nrp-node-attributes; } augment "/nw:networks/nw:network/nt:link" { when '../nw:network-types/nrp:nrp' { description "Augment only for NRP topology."; } description "Augment link configuration and state."; uses nrp-link-attributes; uses nrp-statistics-per-link; } } ]]> <CODE ENDS>

The YANG module defined in this document is designed to be accessed via network management protocols such as NETCONF or RESTCONF . The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) . The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS . The NETCONF access control model 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. There are a number of data nodes defined in this YANG module that are writable/creatable/deletable (i.e., config true, which is the default). These data nodes 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. nrp-link: A malicious client could attempt to remove a link from a topology, add a new link. In each case, the structure of the topology would be sabotaged, and this scenario could, for example, result in an NRP topology that is less than optimal. The entries in the nodes above include the whole network configurations corresponding with the NRP, and indirectly create or modify the PE or P device configurations. Unexpected changes to these entries could lead to service disruption and/or network misbehavior.

This document registers a URI in the IETF XML registry . Following the format in , the following registration is requested to be made:

This document requests to register a YANG module in the YANG Module Names registry .

This section contains an example of an instance data tree in JSON encoding . The example instantiates ietf-nrp for the topology that is depicted in the following diagram. There are three nodes, D1, D2, and D3. D1 has three termination points, 1-0-1, 1-2-1, and 1-3-1. D2 has three termination points as well, 2-1-1, 2-0-1, and 2-3-1. D3 has two termination points, 3-1-1 and 3-2-1. In addition there are six links, two between each pair of nodes with one going in each direction.

| | 2-1-1 | | | | 1-2-1 | |<----------------| | 2-0-1 | | \-/ 1-3-1 \-/ \-/ 2-3-1 \-/ | /----\ | | /----\ | +---| |---+ +---| |---+ \----/ \----/ | | | | | | | | | | | | | | +------------+ | | | | | D3 | | | | | /-\ /-\ | | | +----->| | 3-1-1 | |-------+ | +---------| | 3-2-1 | |<---------+ \-/ \-/ | | +------------+ ]]> The corresponding NRP instance data tree is depicted below: