%% You should probably cite draft-gcdrb-teas-5g-network-slice-application instead of this I-D.
@techreport{rokui-5g-ietf-network-slice-00,
    number =    {draft-rokui-5g-ietf-network-slice-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-rokui-5g-ietf-network-slice/00/},
    author =    {Reza Rokui and Shunsuke Homma and Xavier de Foy and Luis M. Contreras and Philip Eardley and Kiran Makhijani and Hannu Flinck and Rainer Schatzmayr and Ali Tizghadam and Christopher Janz and Henry Yu},
    title =     {{IETF Network Slice for 5G and its characteristics}},
    pagetotal = 27,
    year =      2020,
    month =     nov,
    day =       2,
    abstract =  {5G Network slicing is an approach to provide separate independent end-to-end logical network from User Equipment (UE) to various mobile applications where each network slice has its own Service Level Agreement (SLA) and Objectives (SLO) requirements. Each end-to-end network slice consists of a multitude of contexts across RAN, Core and transport domains each with its own controller. To provide automation, assurance and optimization of the 5G the network slices, a 5G E2E network slice orchestrator is needed which interacts with controllers in RAN, Core and Transport network domains. The interfaces between the 5G E2E network slice orchestrator and RAN and Core controllers are defined in various 3GPP technical specifications. However, 3GPP has not defined a similar interface for transport network. The aim of this document is to describe E2E network slicing and its relation to "IETF network slice" for 5G use-case. It also provides an information model for control and mangement of IETF network slices for 5G.},
}