Skip to main content

Segment Routing for End-to-End IETF Network Slicing

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Zhenbin Li , Jie Dong , Ran Pang , Yongqing Zhu
Last updated 2023-09-14 (Latest revision 2023-03-13)
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
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:


IETF network slices can be used to meet the connectivity and performance requirements of different services or customers in a shared network. An IETF network slice can be realized by mapping a set of connectivity constructs to a network resource partition (NRP). In some network scenarios, an end-to-end IETF network slice may span multiple network domains. Within each domain, traffic of the end-to- end network slice service is mapped to an intra-domain NRP. When segment routing (SR) is used to provide multi-domain IETF network slices, information of the intra-domain NRP can be specified using special SR binding segments which are called NRP binding segments (NRP BSID). Then a multi-domain IETF network slice can be specified using a list of NRP BSIDs in the packet, each of which is used by the corresponding domain edge nodes to steer the traffic of the end-to-end IETF network slice into the specific intra-domain NRP. This document describes the functionality of the NRP binding segment and its instantiation in SR-MPLS and SRv6 data planes.


Zhenbin Li
Jie Dong
Ran Pang
Yongqing Zhu

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