%% You should probably cite draft-li-teas-generalized-ietf-network-slicing-01 instead of this revision.
@techreport{li-teas-generalized-ietf-network-slicing-00,
    number =    {draft-li-teas-generalized-ietf-network-slicing-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-li-teas-generalized-ietf-network-slicing/00/},
    author =    {Zhenbin Li and Jie Dong},
    title =     {{Considerations about Generalized IETF Network Slicing}},
    pagetotal = 8,
    year =      2022,
    month =     jul,
    day =       10,
    abstract =  {IETF network slice has been introduced to meet specific service requirements, such as the connectivity requirements and the associated network capabilities such as bandwidth, latency, jitter and network functions with the resource behaviors such as computing and storage availability. For the realization of IETF network slices, one or more network resource partitions (NRPs) can be created in the network. Each NRP is a collection of network resources (buffer, queuing, scheduling, etc.) allocated in the underlay network. The connectivity constructs from one or more IETF network slices can be mapped to an NRP. NRP specific identifiers could be carried in the IETF network slice packets, which could be used to determine the set of network resources to be used for the processing and forwarding of the packets in the corresponding NRP. With the development of IETF network slicing technologies and the deployment of IETF network slices in different types of networks, there are emerging requirements about the new capability and functionality of IETF network slices. To meet those requirements, it is expected that the concept IETF network slice and NRP needs be generalized. This document describes the considerations about possible generalization of IETF network slice and NRP.},
}