%% You should probably cite draft-ietf-dmm-tn-aware-mobility-32 instead of this revision.
@techreport{ietf-dmm-tn-aware-mobility-29,
    number =    {draft-ietf-dmm-tn-aware-mobility-29},
    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-dmm-tn-aware-mobility/29/},
    author =    {Uma Chunduri and John Kaippallimalil and Sridhar Bhaskaran and Jeff Tantsura and Luis M. Contreras},
    title =     {{Mapping 5G slice to Transport Network slice with UDP Source Ports}},
    pagetotal = 21,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {Network slicing in 5G enables logical networks for communication services of multiple 5G customers to be multiplexed over the same infrastructure. While 5G slicing covers logical separation of various aspects of 5G infrastructure and services, user's data plane packets over the Radio Access Network (RAN) and Core Network (5GC) use IP in many segments of an end-to-end 5G slice. When end-to-end slices in a 5G System use network resources, they are mapped to corresponding Transport Network (TN) slice(s) which in turn provide the bandwidth, latency, isolation, and other criteria required for the realization of a 5G slice. This document describes mapping of 5G slices to TN slices using UDP source port number of the GTP-U bearer when the TN slice provider is separated by an "attachment circuit" from the networks in which the 5G network functions are deployed, for example, 5G functions that are distributed across data centers. The slice mapping defined here is supported transparently when a 5G user device moves across 5G attachment points and session anchors.},
}