Hi Tianji, Thank you for these comments.
On (1), we’ll add the HDLLC as one of the SSTs and note that all the listed are exemplary. On (2), agree that the sentence on 5QI is not necessary and its best to avoid in this draft (references to 3GPP specs are there for those who need it). Will remove. Best Regards, John From: Tianji Jiang <[email protected]> Sent: Tuesday, March 4, 2025 3:31 PM To: [email protected] Subject: [DMM] Re: Working Group Last Call: draft-ietf-dmm-tn-aware-mobility-16 Hi, Reading thru the draft, I do think it is already in good shape. I have only the following minor comments: 1. Section-1, 1st paragraph,: * [quoted]: Slice types defined by the 3GPP include enhanced mobile broadband (eMBB) communications, ultra-reliable low latency communications (URLLC), massive internet of things (MIoT), vehicle-to-X (V2X) and high-performance machine type communications (HMTC). Other types can be defined in the future to include new slice types. * Since your intension here is to list all the standardized SST values, there is a new one ‘HDLLC’ (High Data rate and Low Latency Communications) which you may consider including here. 1. Section-2: GTP-U UDP port with the consideration of 5QI: quoted ‘… The 5G network function takes the 5QI into consideration when selecting the GTP-U (UDP) source port number…” * In addition to standardized 5QI, there are dynamically allocated 5Qis to match the QoS requirements of different data flows. * And, normally the GTP-U (UDP) source port is also dynamic, which could be different across PDU. * So, if a 5QI is in the standard-range, it might make sense to ‘…take the 5QI into consideration when selection the GTP-U (UDP) source port#...’. But, for dynamic 5Qis, this does not make too much sense. * [Suggestion] This sentence is not of importance to the theme of the draft. So, you may consider removing it. BR, -Tianji From: Satoru Matsushima <[email protected]<mailto:[email protected]>> Date: Monday, February 24, 2025 at 6:20 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Cc: "Sri Gundavelli (sgundave)" <[email protected]<mailto:[email protected]>> Subject: [DMM] Re: Working Group Last Call: draft-ietf-dmm-tn-aware-mobility-16 All, The WG LC has been ended for this draft with only one comment. We chairs are concerned that the rest of the dmm community was aware of this WGLC and made enough review. So I suggest next two week for your post WGLC review again. >From my end, when I re-review the draft, I come up some questions as below: 1. status changed to STD from INFO. It might be for some reason, i.e. namespaces allocation request to IANA. But XML NS and YANG parameters don't require STD status RFC. Is STD sufficient status instead of INFO? 2. Assumed information model In Fig.3, "EP_Transport" at gNB-CU includes S-NSSAI. But when I read TS28.549, the EP_Transport class doesn't include attributes regarding S-NSSAI. Does this draft refer to the correct spec in 3GPP to show how the slice mapping be made? Best regards, --satoru On Mon, Jan 20, 2025 at 5:16 PM Lionel Morand <[email protected]<mailto:[email protected]>> wrote: Hi, Since the last IETF meeting, after several rounds of comments and revisions, I think that this draft is now completed and can be moved forward. Regards, Lionel From: Sri Gundavelli (sgundave) <[email protected]<mailto:[email protected]>> Sent: lundi 20 janvier 2025 06:17 To: [email protected]<mailto:[email protected]> Subject: [DMM] Working Group Last Call: draft-ietf-dmm-tn-aware-mobility-16 Folks: This document, draft-ietf-dmm-tn-aware-mobility-16.txt, went through several revisions based on the WG feedback. The authors believe they have addressed all the comments and there are no open issues that they are tracking at this time. We would like to confirm the same from the working group. The following message commences a two-week WGLC for all feedback. Document Link: https://www.ietf.org/archive/id/draft-ietf-dmm-tn-aware-mobility-16.txt Please post any comments/concerns on the draft. Thanks! Satoru & Sri Cisco Confidential _______________________________________________ dmm mailing list -- [email protected]<mailto:[email protected]> To unsubscribe send an email to [email protected]<mailto:[email protected]> _______________________________________________ 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]
