%% You should probably cite draft-ietf-dmm-tn-aware-mobility-10 instead of this revision. @techreport{ietf-dmm-tn-aware-mobility-09, number = {draft-ietf-dmm-tn-aware-mobility-09}, 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/09/}, author = {Uma Chunduri and John Kaippallimalil and Sridhar Bhaskaran and Jeff Tantsura and Praveen Muley}, title = {{Mobility aware Transport Network Slicing for 5G}}, pagetotal = 20, year = , month = , day = , abstract = {Network slicing in 5G supports 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 services, user's data plane packets over the radio access network (RAN) and mobile core network (5GC) use IP transport in many segments of the end-to-end 5G slice. When end-to- end slices in a 5G system use IP network resources, they are mapped to corresponding IP transport network slice(s) which in turn provide the bandwidth, latency, isolation and other criteria requested by the 5G slice. This document describes mapping of 5G slices to IP or Layer 2 transport network slices when the IP transport network (slice provider) is separated from the networks in which the 5G network functions are deployed, for example, 5G functions that are distributed across data centers. The slice mapping proposed here is supported transparently when a 5G user device moves across 5G attachment points and session anchors.}, }