%% 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-05,
    number =    {draft-li-spring-sr-e2e-ietf-network-slicing-05},
    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/05/},
    author =    {Zhenbin Li and Jie Dong and Ran Pang and Yongqing Zhu},
    title =     {{Segment Routing for End-to-End IETF Network Slicing}},
    pagetotal = 13,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {IETF network slices can be used to meet the connectivity and performance requirements of different services or customers in a shared network. An IETF network slice can be realized by mapping a set of connectivity constructs to a network resource partition (NRP). In some network scenarios, 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 an intra-domain NRP. When segment routing (SR) is used to provide multi-domain IETF network slices, information of the intra-domain NRP can be specified using special SR binding segments which are called NRP binding segments (NRP BSID). Then a multi-domain IETF network slice can be specified using a list of NRP BSIDs in the packet, each of which is used by the corresponding domain edge nodes to steer the traffic of the end-to-end IETF network slice into the specific intra-domain NRP. This document describes the functionality of the NRP binding segment and its instantiation in SR-MPLS and SRv6 data planes.},
}