Skip to main content

Scalability Considerations for Network Resource Partition
draft-dong-teas-nrp-scalability-02

Document Type Replaced Internet-Draft (candidate for teas WG)
Expired & archived
Authors Jie Dong , Zhenbin Li , Liyan Gong , Guangming Yang , Jim Guichard , Gyan Mishra , Fengwei Qin , Tarek Saad , Vishnu Pavan Beeram
Last updated 2022-06-16 (Latest revision 2022-05-16)
Replaces draft-dong-teas-enhanced-vpn-vtn-scalability
Replaced by draft-ietf-teas-nrp-scalability
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Additional resources Mailing list discussion
Stream WG state Call For Adoption By WG Issued
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-teas-nrp-scalability
Consensus boilerplate Unknown
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

The IETF Network Slice service aims to meet the connectivity demands of a network slice customer with specific Service Level Objectives (SLOs) and Service Level Expectations (SLEs) over a common underlay network. A Network Resource Partition (NRP) is a set of network resources that are allocated from the underlay network to carry a specific set of network traffic and meet the required SLOs and SLEs. One or multiple IETF Network Slice services can be mapped to one NRP. As the demand for IETF Network Slice services increases, scalability would become an important factor for the large scale deployment of IETF Network Slices. Although the scalability of IETF Network Slices can be improved by mapping a group of IETF Network Slices to one NRP, there are concerns about the scalability of NRPs. This document describes the scalability considerations about NRPs in the network control plane and data plane, and some optimization mechanisms are proposed.

Authors

Jie Dong
Zhenbin Li
Liyan Gong
Guangming Yang
Jim Guichard
Gyan Mishra
Fengwei Qin
Tarek Saad
Vishnu Pavan Beeram

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