Hi,
We just posted a new version of dmm-tn-aware-mobility (see links below).
The major change in this revision is to define an extension to ACaaS
(Attachment Circuit as a Service) for using GTP addr/port as an attachment
circuit to a PE.
Most significantly, this removes the need to have further 3GPP specification
(in 28.541, EP_Transport) to provision such a slice.
The extension to ACaaS is below:
| ...
+--rw ac* [name]
...
+--rw ip-connection {ac-common:layer3-ac}?
| |...
| +--rw (l3-service)?
| +--: (l3-tunnel-service)
< IPv4 addr, IPv6 prefix and ports for source,
destination >
The "l3-service" structure may be relevant to other services than just this
draft and the authors will request teas and opsawg to review and see how this
fits.
Your reviews are greatly appreciated.
BR,
John
> -----Original Message-----
> From: [email protected] <[email protected]>
> Sent: Tuesday, October 15, 2024 2:58 AM
> To: [email protected]
> Cc: [email protected]
> Subject: [DMM] I-D Action: draft-ietf-dmm-tn-aware-mobility-11.txt
>
> Internet-Draft draft-ietf-dmm-tn-aware-mobility-11.txt is now available. It
> is a
> work item of the Distributed Mobility Management (DMM) WG of the IETF.
>
> Title: Mobility aware Transport Network Slicing for 5G
> Authors: Uma Chunduri
> John Kaippallimalil
> Sridhar Bhaskaran
> Jeff Tantsura
> Luis M. Contreras
> Name: draft-ietf-dmm-tn-aware-mobility-11.txt
> Pages: 25
> Dates: 2024-10-15
>
> 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 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 proposed here is supported transparently when a 5G user
> device moves across 5G attachment points and session anchors.
>
> The IETF datatracker status page for this Internet-Draft is:
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdata<https://datatracker.ietf.org/doc/draft-ietf-dmm-tn-aware-mobility/>
> tracker.ietf.org%2Fdoc%2Fdraft-ietf-dmm-tn-aware-<https://datatracker.ietf.org/doc/draft-ietf-dmm-tn-aware-mobility/>
> mobility%2F&data=05%7C02%7Cjohn.kaippallimalil%40futurewei.com%7C6<https://datatracker.ietf.org/doc/draft-ietf-dmm-tn-aware-mobility/>
> b5939a219504232d51608dcecef7311%7C0fee8ff2a3b240189c753a1d559<https://datatracker.ietf.org/doc/draft-ietf-dmm-tn-aware-mobility/>
> 1fedc%7C1%7C0%7C638645760398257636%7CUnknown%7CTWFpbGZsb3<https://datatracker.ietf.org/doc/draft-ietf-dmm-tn-aware-mobility/>
> d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0<https://datatracker.ietf.org/doc/draft-ietf-dmm-tn-aware-mobility/>
> %3D%7C0%7C%7C%7C&sdata=IZHwz5M21EGhaP8IA3NvTiI7waxcpYqAYg78<https://datatracker.ietf.org/doc/draft-ietf-dmm-tn-aware-mobility/>
> 0m5vAZ8%3D&reserved=0<https://datatracker.ietf.org/doc/draft-ietf-dmm-tn-aware-mobility/>
>
> There is also an HTMLized version available at:
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdata<https://datatracker.ietf.org/doc/html/draft-ietf-dmm-tn-aware-mobility-11>
> tracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-dmm-tn-aware-mobility-<https://datatracker.ietf.org/doc/html/draft-ietf-dmm-tn-aware-mobility-11>
> 11&data=05%7C02%7Cjohn.kaippallimalil%40futurewei.com%7C6b5939a21<https://datatracker.ietf.org/doc/html/draft-ietf-dmm-tn-aware-mobility-11>
> 9504232d51608dcecef7311%7C0fee8ff2a3b240189c753a1d5591fedc%7C1<https://datatracker.ietf.org/doc/html/draft-ietf-dmm-tn-aware-mobility-11>
> %7C0%7C638645760398279674%7CUnknown%7CTWFpbGZsb3d8eyJWIjoi<https://datatracker.ietf.org/doc/html/draft-ietf-dmm-tn-aware-mobility-11>
> MC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0<https://datatracker.ietf.org/doc/html/draft-ietf-dmm-tn-aware-mobility-11>
> %7C%7C%7C&sdata=eKPT%2FYt6fewNJLYVd2NMWXMblK%2FLWUm5%2FW<https://datatracker.ietf.org/doc/html/draft-ietf-dmm-tn-aware-mobility-11>
> LbJ53tL3s%3D&reserved=0<https://datatracker.ietf.org/doc/html/draft-ietf-dmm-tn-aware-mobility-11>
>
> A diff from the previous version is available at:
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fauth<https://author-tools.ietf.org/iddiff?url2=draft-ietf-dmm-tn-aware-mobility-11>
> or-tools.ietf.org%2Fiddiff%3Furl2%3Ddraft-ietf-dmm-tn-aware-mobility-<https://author-tools.ietf.org/iddiff?url2=draft-ietf-dmm-tn-aware-mobility-11>
> 11&data=05%7C02%7Cjohn.kaippallimalil%40futurewei.com%7C6b5939a21<https://author-tools.ietf.org/iddiff?url2=draft-ietf-dmm-tn-aware-mobility-11>
> 9504232d51608dcecef7311%7C0fee8ff2a3b240189c753a1d5591fedc%7C1<https://author-tools.ietf.org/iddiff?url2=draft-ietf-dmm-tn-aware-mobility-11>
> %7C0%7C638645760398291845%7CUnknown%7CTWFpbGZsb3d8eyJWIjoi<https://author-tools.ietf.org/iddiff?url2=draft-ietf-dmm-tn-aware-mobility-11>
> MC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0<https://author-tools.ietf.org/iddiff?url2=draft-ietf-dmm-tn-aware-mobility-11>
> %7C%7C%7C&sdata=068Axl%2BIoPhjpkLc%2BnVbcbXMByOnGXUW2uPY0k<https://author-tools.ietf.org/iddiff?url2=draft-ietf-dmm-tn-aware-mobility-11>
> 8Dtzs%3D&reserved=0<https://author-tools.ietf.org/iddiff?url2=draft-ietf-dmm-tn-aware-mobility-11>
>
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
>
>
> _______________________________________________
> dmm mailing list -- [email protected]<mailto:[email protected]>
> To unsubscribe send an email to [email protected]<mailto:[email protected]>
_______________________________________________
dmm mailing list -- [email protected]
To unsubscribe send an email to [email protected]
