Skip to main content

Sub-slicing for SRv6

Document Type Replaced Internet-Draft (individual)
Expired & archived
Author Louis Chan
Last updated 2022-02-09 (Latest revision 2021-08-08)
Replaced by draft-chan-spring-srv6-sub-slice
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-chan-spring-srv6-sub-slice
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


This document describes how to achieve further slicing or traffic engineering interoperability between vendors without the use of SRH. Slicing or traffic engineering information is encapsulated as part of the SRv6 SID. Use of IP longest prefix match approach to identify the further slicing via sub- slice identifier. The traffic engineering from one end to another end is seen as segment by segment approach. This approach could solve the scalability of traffic engineering tunnels required in a huge network, which order of N^2 has be considered.


Louis Chan

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)