Resource guarantee Slicing over Srv6

1

(% class="row" %)

2

(((

3

(% class="col-xs-12 col-sm-7 test-report-content" %)

(((

----

Link Resource Slicing over SRv6 provides isolation and differentiation of traffic flows across common shared network infrastructures by embedding Network Slice Identifiers (NSIs) within SRv6 headers. Allocating resources to specific slices can guaranteed performance for various services.

8

As part of our interoperability testing for link resource slicing, we validated the ability of SRv6-enabled routers to support Network Resource Partitioning (NRP) using Slice Identifiers (SLIDs), as outlined in draft-cheng-spring-srv6-encoding-network-sliceid-10. The test focused on ensuring that NRP-IDs could be carried in packets and correctly interpreted by routers along the forwarding path. This allowed each node to extract the NRP-ID, associate the packet with its respective Network Resource Partition (NRP), and forward it using the allocated resources.

9

For the SLID assignment, we verified that ingress PEs correctly reserved a portion of the least significant bits (LSBs) of the IPv6 source address for slice identification. Then, slice-specific bandwidth constraints were applied based on the classification of traffic into different slices. As traffic traversed the network, P nodes successfully recognized the SLID, preserved it throughout forwarding, and applied their own slice-specific bandwidth constraints. This allowed us to verify that all participating nodes correctly enforced NRP, ensuring consistent slice-aware forwarding and resource isolation across the entire SRv6 transport domain.

10

11

[[Figure 98: Resource guarantee Slicing>>image:433488182479683585_Resource garaunteed Slicing.png||alt="Figure 98" width="550"]]

12

13

14

(% class="table-bordered" %)

15

|=Egress PE|=Ingress PE|=P node|=Traffic Generator

16

|H3C CR16000-M1A|H3C CR16003E-F|Juniper MX204|Keysight IxNetwork

17