Hi Tianji, Thanks for the comments and support.
The suggested changes in comments below in 1, 2 and 4 have been implemented in this new revision. RE: 3, the slice mapping is supported for N3 (to anchor UPF) but also for N9 and F1-U as these are all user plane entities. The draft now only has Informational references as was discussed during the DMM session on Monday. Please see new version/diff: https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fauthor-tools.ietf.org%2Fiddiff%3Furl2%3Ddraft-ietf-dmm-tn-aware-mobility-23&data=05%7C02%7Cjohn.kaippallimalil%40futurewei.com%7Ca53923a3718f4b44e9b608de1bad41bc%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C638978628121984873%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=rRuK6uT3gVgtpAK0YvjXQ5IuG%2FC8YnGdGIZI1BQfvXg%3D&reserved=0<https://author-tools.ietf.org/iddiff?url2=draft-ietf-dmm-tn-aware-mobility-23> Best Regards, John From: Tianji Jiang <[email protected]> Sent: Tuesday, October 28, 2025 8:38 AM To: Satoru Matsushima <[email protected]> Cc: [email protected]; [email protected]; [email protected] Subject: Re: [DMM] Re: WG Last Call: draft-ietf-dmm-tn-aware-mobility-22 (Ends 2025-10-30) Hi, Fundamentally, I think this draft is sufficiently mature and I support its WGLC. With some comments: 1. [quoted from section#1] However, 3GPP standards do not specify the capabilities of transport network (TN) slices or slice characteristics for QoS, hard /soft isolation, protection and other aspects. * Either 3GPP standards do ‘not specify’ or ‘consider this is actually out of scope of 3GPP’? if later, please clarify it. 1. [quoted from section#1] TN slices in this document can be used to realize slices between 3GPP control plane NFs or for a UE's user plane. For realizing control plane slicing, the TN slice is deployed along the interface between two 3GPP NFs. User plane 5G slice for each user's PDU session is mapped to corresponding TN slices and is the focus of this document. * From reading these couple of sentences, my understanding is that it implies the TN-slice mapping scheme as specified in the draft is applicable to both 3GPP CP and UP. However, the mapping of the scheme goes thru the source UDP port (of GTP-U), which is not applicable to CP. – suggest clarifying it. 1. [quoted from section#1] Mapping a 3GPP slice to a TN slice using GTP-U (UDP) source port number is useful when the 3GPP network function and PE for TN slice are in different IP subnets * 3GPP network functions include both CP and UP NFs. This draft is focusing on UP and the mapping (via source UDP-port) is applicable to UP (F1-U, N3, N9). So, a little ambiguous and suggest replacing with ‘3GPP UP NF (e.g., anchor-UPF)’ 1. [quoted from section #2] …the N3 interface between the gNB-CU-CP and the UPF… * Should be ‘gNB-CU-UP’ Also, the draft is referencing a couple of documents which are not yet WG-adopted. Not sure what will be the criteria for this kind of reference. Maybe the DMM chairs could shed some light & guidance. Thank you. BR, -Tianji From: Satoru Matsushima <[email protected]<mailto:[email protected]>> Sent: Friday, October 24, 2025 2:52 PM To: Satoru Matsushima <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Subject: [DMM] Re: WG Last Call: draft-ietf-dmm-tn-aware-mobility-22 (Ends 2025-10-30) DMMer, Let me remind you that the mobility-aware transport draft is now in WGLC. It will end on Oct. 30, so please review the draft. You can use this thread to send your feedback. Cheers, --satoru On Thu, Oct 16, 2025 at 9:09 PM Satoru Matsushima via Datatracker <[email protected]<mailto:[email protected]>> wrote: Subject: WG Last Call: draft-ietf-dmm-tn-aware-mobility-22 (Ends 2025-10-30) This message starts a 2-week WG Last Call for this document. 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 IP transport network 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 transport network slices using UDP source port number of the GTP-U bearer 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 defined here is supported transparently when a 5G user device moves across 5G attachment points and session anchors. File can be retrieved from: https://datatracker.ietf.org/doc/draft-ietf-dmm-tn-aware-mobility/ Please review and indicate your support or objection to proceed with the publication of this document by replying to this email keeping [email protected]<mailto:[email protected]> in copy. Objections should be motivated and suggestions to resolve them are highly appreciated. Authors, and WG participants in general, are reminded again of the Intellectual Property Rights (IPR) disclosure obligations described in BCP 79 [1]. Appropriate IPR disclosures required for full conformance with the provisions of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any. Sanctions available for application to violators of IETF IPR Policy can be found at [3]. Thank you. [1] https://datatracker.ietf.org/doc/bcp78/ [2] https://datatracker.ietf.org/doc/bcp79/ [3] https://datatracker.ietf.org/doc/rfc6701/
_______________________________________________ dmm mailing list -- [email protected] To unsubscribe send an email to [email protected]
