Network Slicing Use Cases: Network Customization and Differentiated Services
draft-netslices-usecases-02
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Kiran Makhijani , Jun Qin , Ravi Ravindran , Liang Geng , Li Qiang , Shuping Peng , Xavier de Foy , Akbar Rahman , Alex Galis , Giuseppe Fioccola | ||
Last updated | 2018-04-21 (Latest revision 2017-10-18) | ||
Replaces | draft-qin-netslices-use-cases | ||
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 is meant to enable creating (end-to-end) partitioned network infrastructure that may include the user equipment, access/ core transport networks, edge and central data center resources to provide differentiated connectivity behaviors to fulfill the requirements of distinct services, applications and customers. In this context, connectivity is not restricted to differentiated forwarding capabilities but it covers also advanced service functions that will be invoked when transferring data within a given domain. The purpose of this document is to focus on use cases that benefit from the use of network slicing.
Authors
Kiran Makhijani
Jun Qin
Ravi Ravindran
Liang Geng
Li Qiang
Shuping Peng
Xavier de Foy
Akbar Rahman
Alex Galis
Giuseppe Fioccola
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)