%% You should probably cite draft-rokui-5g-ietf-network-slice instead of this I-D.
@techreport{rokui-5g-transport-slice-00,
    number =    {draft-rokui-5g-transport-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-transport-slice/00/},
    author =    {Reza Rokui and Shunsuke Homma and Diego Lopez and Xavier de Foy and Luis M. Contreras and Jose A. Ordonez-Lucena and Pedro Martinez-Julia and Mohamed Boucadair and Philip Eardley and Kiran Makhijani and Hannu Flinck},
    title =     {{5G Transport Slice Connectivity Interface}},
    pagetotal = 28,
    year =      2019,
    month =     jul,
    day =       2,
    abstract =  {The 5G Network slicing is an approach to provide separate independent E2E logical network from user equipment (UE) to applications where each network slice has different SLA requirements. Each E2E network slice consists of multitude of RAN-slice, Core-slice and Transport- slices, each with its own controller. To provide automation, assurance and optimization of the network slices, an E2E network slice controller is needed which interacts with controller in RAN, Core and Transport slices. The interfaces between the E2E network slice controller and RAN and Core controllers are defined in various 3GPP technical specifications. However, 3GPP has not defined the same interface for transport slices. The aim of this document is to provide the clarification of this interface and to provide the information model of this interface for automation, monitoring and optimization of the transport slices.},
}