Skip to main content

Realizing Network Slices in IP/MPLS Networks
draft-bestbar-teas-ns-packet-10

Document Type Replaced Internet-Draft (teas WG)
Expired & archived
Authors Tarek Saad , Vishnu Pavan Beeram , Jie Dong , Bin Wen , Daniele Ceccarelli , Joel M. Halpern , Shaofu Peng , Ran Chen , Xufeng Liu , Luis M. Contreras , Reza Rokui , Luay Jalil
Last updated 2022-06-16 (Latest revision 2022-05-05)
Replaced by draft-ietf-teas-ns-ip-mpls
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Additional resources Mailing list discussion
Stream WG state Adopted by a WG
Document shepherd Lou Berger
IESG IESG state Replaced by draft-ietf-teas-ns-ip-mpls
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
Bin Wen
Daniele Ceccarelli
Joel M. Halpern
Shaofu Peng
Ran Chen
Xufeng Liu
Luis M. Contreras
Reza Rokui
Luay Jalil

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