Realizing Network Slices in IP/MPLS Networks
draft-ietf-teas-ns-ip-mpls-05
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Tarek Saad , Vishnu Pavan Beeram , Jie Dong , Joel M. Halpern , Shaofu Peng | ||
| Last updated | 2025-09-03 (Latest revision 2025-03-02) | ||
| Replaces | draft-bestbar-teas-ns-packet | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | Lou Berger | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | lberger@labn.net |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Realizing network slices may require the Service Provider to have the ability to partition a physical network into multiple logical networks of varying sizes, structures, and functions so that each slice can be dedicated to specific services or customers. Multiple network slices can be realized on the same network while ensuring slice elasticity in terms of network resource allocation. This document describes a scalable solution to realize network slicing in IP/MPLS networks by supporting multiple services on top of a single physical network by relying on compliant domains and nodes to provide forwarding treatment (scheduling, drop policy, resource usage) on to packets that carry identifiers that indicate the slicing service that is to be applied to the packets.
Authors
Tarek Saad
Vishnu Pavan Beeram
Jie Dong
Joel M. Halpern
Shaofu Peng
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)