%% You should probably cite draft-li-spring-sr-e2e-ietf-network-slicing-06 instead of this revision.
@techreport{li-spring-sr-e2e-ietf-network-slicing-00,
    number =    {draft-li-spring-sr-e2e-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-spring-sr-e2e-ietf-network-slicing/00/},
    author =    {Zhenbin Li and Jie Dong},
    title =     {{Segment Routing for End-to-End IETF Network Slicing}},
    pagetotal = 11,
    year =      2021,
    month =     apr,
    day =       22,
    abstract =  {Network slicing can be used to meet the connectivity and performance requirement of different services or customers in a shared network. An IETF network slice can be realized as enhanced VPNs (VPN+), which is delivered by integrating the overlay VPN service with a Virtual Transport Network (VTN) as the underlay. An end-to-end IETF network slice may span multiple network domains. Within each domain, traffic of the end-to-end network slice service is mapped to a local VTN. When segment routing (SR) is used to build a multi-domain IETF network slice, information of the local network slices in each domain can be specified using special SR binding segments called VTN binding segments (VTN BSID). The multi-domain IETF network slice can be specified using a list of VTN BSIDs in the packet, each of which can be used by the corresponding domain edge nodes to steer the traffic of end-to-end IETF network slice into the specific VTN in the local domain. This document describes the functionality of VTN binding segment and its instantiation in SR-MPLS and SRv6.},
}