%% You should probably cite draft-ietf-teas-ns-ip-mpls-03 instead of this revision.
@techreport{ietf-teas-ns-ip-mpls-01,
    number =    {draft-ietf-teas-ns-ip-mpls-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-ns-ip-mpls/01/},
    author =    {Tarek Saad and Vishnu Pavan Beeram and Jie Dong and Bin Wen and Daniele Ceccarelli and Joel M. Halpern and Shaofu Peng and Ran Chen and Xufeng Liu and Luis M. Contreras and Reza Rokui and Luay Jalil},
    title =     {{Realizing Network Slices in IP/MPLS Networks}},
    pagetotal = 31,
    year =      2022,
    month =     oct,
    day =       24,
    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.},
}