Encapsulation of End-to-End IETF Network Slice Information in IPv6
draft-li-6man-e2e-ietf-network-slicing-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Zhenbin Li , Jie Dong | ||
Last updated | 2021-10-16 (Latest revision 2021-04-14) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
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:
Abstract
Network slicing can be used to meet the connectivity and performance requirement of different services or customers in a shared network. An IETF network slice may span multiple network domains. In the context of 5G, the 5G end-to-end network slices consist of three major types of network segments: Radio Access Network (RAN), Transport Network (TN) and Core Network (CN). In order to facilitate the mapping between network slices in different network segments and network domains, it is beneficial to carry the identifiers of the 5G end-to-end network slice, the multi- domain IETF network slice together with the intra-domain network slice identifier in the data packet. This document defines the mechanism of encapsulating the end-to-end network slice related information in IPv6 data plane.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)