Dear DMM experts, This version is a refresh but all comments received (offline and during the presentation at IETF106) were addressed.
Any further comments/suggestions are most welcome. -- Uma C. On Mon, Sep 28, 2020 at 4:44 PM <internet-dra...@ietf.org> wrote: > > A new version of I-D, draft-clt-dmm-tn-aware-mobility-07.txt > has been successfully submitted by Uma Chunduri and posted to the > IETF repository. > > Name: draft-clt-dmm-tn-aware-mobility > Revision: 07 > Title: Transport Network aware Mobility for 5G > Document date: 2020-09-28 > Group: Individual Submission > Pages: 28 > URL: > https://www.ietf.org/id/draft-clt-dmm-tn-aware-mobility-07.txt > Status: > https://datatracker.ietf.org/doc/draft-clt-dmm-tn-aware-mobility/ > Htmlized: > https://datatracker.ietf.org/doc/html/draft-clt-dmm-tn-aware-mobility > Htmlized: > https://tools.ietf.org/html/draft-clt-dmm-tn-aware-mobility-07 > Diff: > https://www.ietf.org/rfcdiff?url2=draft-clt-dmm-tn-aware-mobility-07 > > Abstract: > This document specifies a framework and mapping from slices in 5G > mobile systems to transport slices in IP and Layer 2 transport > networks. Slices in 5G systems are characterized by latency bounds, > reservation guarantees, jitter, data rates, availability, mobility > speed, usage density, criticality and priority should be mapped to > transport slice characteristics that include bandwidth, latency and > criteria such as isolation, directionality and disjoint routes. > Mobile slice criteria need to be mapped to the appropriate transport > slice and capabilities offered in backhaul, midhaul and fronthaul > connectivity segments between radio side network functions and user > plane function (gateway). > > This document describes how mobile network functions map its slice > criteria to identifiers in IP packets that transport segments use to > grant transport layer services. This is based on mapping between > mobile and IP transport underlays (IPv6, MPLS, IPv4, Segment > Routing). Applicability of this framework and a new transport > network underlay routing mechanism, Preferred Path Routing (PPR), > which brings slice properties and works with any underlying transport > (L2, IPv4, SR and MPLS) is also discussed. > > > > > > Please note that it may take a couple of minutes from the time of > submission > until the htmlized version and diff are available at tools.ietf.org. > > The IETF Secretariat > > >
_______________________________________________ dmm mailing list dmm@ietf.org https://www.ietf.org/mailman/listinfo/dmm