%% You should probably cite draft-ietf-teas-nrp-scalability-04 instead of this revision.
@techreport{ietf-teas-nrp-scalability-01,
    number =    {draft-ietf-teas-nrp-scalability-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-teas-nrp-scalability/01/},
    author =    {Jie Dong and Zhenbin Li and Liyan Gong and Guangming Yang and Jim Guichard and Gyan Mishra and Fengwei Qin and Tarek Saad and Vishnu Pavan Beeram},
    title =     {{Scalability Considerations for Network Resource Partition}},
    pagetotal = 18,
    year =      2022,
    month =     oct,
    day =       24,
    abstract =  {The IETF Network Slice aims to offer a connectivity service to 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 slice service traffic and meet specific SLOs and SLEs. As the demand for IETF Network Slice increases, scalability would become an important factor for the 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, that design may not be suitable or possible for all deployments, thus there are concerns about the scalability of NRPs. This document discusses some scalability considerations about NRPs in the network control and data plane. It also investigates a set of optimization mechanisms.},
}