Hi Jon, Wassim, all, Thank you for all the time spent to review and provide detailed and valuable feedback on this draft. Revisions 27 and 28 attempt to address the comments from the security and int areas.
Updates related to the security review: =============================== - clarified in sections 1, 2 that TN slices are configured and source port sent within a limited domain consisting of 3GPP (Client) and transport slice (provider). - in section 6, detailed revision with updates recommended in the review (thanks, Jon!) including consequence of leakage of info (source port), ingress filtering at PE re: forgeability, injecting/rewriting, etc. - section 3 and 6 updates re: ESP-in-UDP and reference to RFC3948 with fixed src/dst port of 4500. Plus, clarification that source ports should be configurable in this solution for slice selection and entropy. (and suggested a high-level, non-standard workaround in section 3 to inform the implementer of the issue). - updates between rev 27 and 28 based on reviews among the authors to address the ESP/IPsec aspects. - security section 6 developed fully to address the comments in the review. - fixes for other minor issues and nits. Attaching diff between rev 26-28 for easy reference. Updates related to the int review: =========================== - Attempted to address reducing the text in sections 1-2. Between revision 27 and 28, removed some duplicated text. Some of the text remaining in sections 1 and 2 were kept as they clarify earlier comments from the WG reviews (e.g., relation between CP and UP slices, management vs. control vs. data plane actions which are in different 3GPP standards documents but play a part in this solution). - revised section 4 to with proper references to each of the figures. Link: https://datatracker.ietf.org/doc/draft-ietf-dmm-tn-aware-mobility/ Diff: (rev 27 -> 28): https://author-tools.ietf.org/iddiff?url2=draft-ietf-dmm-tn-aware-mobility-28 Best Regards, John > -----Original Message----- > From: Wassim Haddad via Datatracker <[email protected]> > Sent: Monday, July 6, 2026 8:27 PM > To: [email protected] > Cc: [email protected]; [email protected]; last- > [email protected] > Subject: draft-ietf-dmm-tn-aware-mobility-27 telechat Intdir review > > Document: draft-ietf-dmm-tn-aware-mobility > Title: Mobility-aware Transport Network Slicing for 5G > Reviewer: Wassim Haddad > Review result: Ready with Nits > > Summary: The draft describes using the GTP-U bearer outer UDP header > source port as the slice selector on F1-U/N3/N9 interfaces, since the S-NSSAI > is invisible to the transport network. Although the document core idea is well > described, it takes "a while" to get there making the draft a bit "heavy" to > go > through until section 3.3. IMHO, the draft can/should be shortened till > section > 3.3. > > Nits: Section 4 says: > "An example with different user plane slice types and transport paths is shown > in the figure." AND "The figure shows UDP port ranges, SST, transport path (in > this example pseudowire/VPN) and transport path characteristics." > > => Would be useful to mention which figure you're referring to. > > Thanks! >
<<< text/html; name="draft-ietf-dmm-tn-aware-mobility-28-26.diff.html": Unrecognized >>>
_______________________________________________ dmm mailing list -- [email protected] To unsubscribe send an email to [email protected]
