[DMM] Mohamed Boucadair's Discuss on draft-ietf-dmm-tn-aware -mobility-26: (with DISCUSS and COMMENT)
Kaippallimalil John <[email protected]> Wed, 29 Jul 2026 14:47:21 +0000
| Newsgroups | gmane.ietf.nemo |
|---|---|
| Message-ID | <SN4PR13MB531176EBFA3286BDA2DDD42FE8CA2@SN4PR13MB5311.namprd13.prod.outlook.com> |
--===============5799863884458315110== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_SN4PR13MB531176EBFA3286BDA2DDD42FE8CA2SN4PR13MB5311namp_" --_000_SN4PR13MB531176EBFA3286BDA2DDD42FE8CA2SN4PR13MB5311namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Med, all, (For some reason, I did not receive the e-mail, and I'm using a copy forwar= ded to me by Luis) The authors have revised the draft to address /resolve the DISCUSS comments= : * Revised title of draft to: Mapping 5G slice to Transport Network slic= e with UDP Source Ports References to "mobility awareness" is removed in both occurrences in the dr= aft. * Revised to add Normative References section. Moved RFC9543, RFC9834, RFC9889 and TS28.541 to normative references. There are a few other changes to address comments from tsv-art and I'm repl= ying separately on that. Links: URL: https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F= %2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-ietf-dmm-tn-aware-mobility-29.txt&da= ta=3D05%7C02%7Cjohn.kaippallimalil%40futurewei.com%7C5b0ddc0f5eab41ca9e1c08= deed7d63e9%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C639209320014944035%= 7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJ= XaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=3D9LN9rlfkn%2B= tNjd7vRo1P1gcwvZac780gVBFOjFkDFF4%3D&reserved=3D0<https://www.ietf.org/arch= ive/id/draft-ietf-dmm-tn-aware-mobility-29.txt> Diff: https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F= %2Fauthor-tools.ietf.org%2Fiddiff%3Furl2%3Ddraft-ietf-dmm-tn-aware-mobility= -29&data=3D05%7C02%7Cjohn.kaippallimalil%40futurewei.com%7C5b0ddc0f5eab41ca= 9e1c08deed7d63e9%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C6392093200155= 61443%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsI= lAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=3DuT%2B8= Q%2B3SU49A9MdvFpZ2Vk4UHWs3bXp4P8aM74CuxLA%3D&reserved=3D0<https://author-to= ols.ietf.org/iddiff?url2=3Ddraft-ietf-dmm-tn-aware-mobility-29> Best Regards, John From: Mohamed Boucadair via Datatracker <[email protected]<mailto:noreply@ie= tf.org>> Sent: Thursday, 02 July 2026 10:02:10 To: The IESG <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> <[email protected]<ma= ilto:[email protected]>>; [email protected]<mailto:[email protected]> <[email protected]= <mailto:[email protected]>>; [email protected]<mailto:dr= [email protected]> <draft-ietf-dmm-tn-aware-mobility@= ietf.org<mailto:[email protected]>>; satoru.matsush= [email protected]<mailto:[email protected]> <satoru.matsushima@gmail.= com<mailto:[email protected]>> Subject: Mohamed Boucadair's Discuss on draft-ietf-dmm-tn-aware-mobility-26= : (with DISCUSS and COMMENT) Mohamed Boucadair has entered the following ballot position for draft-ietf-dmm-tn-aware-mobility-26: Discuss When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-= ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-dmm-tn-aware-mobility/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- Hi Uma, John, Sridhar, Jeff, and Luis, Thank you for the effort put into this specification. Please find below some pints for DISCUSSion: # Mobility-awareness & Key technical contribution CURRENT: Following UE handover, the S-NSSAI is mapped seamlessly to the corresponding GTP-U (or UDP encapsulated GTP) source port number of the newly attached network and can be considered to be "mobility aware". The reasoning above applies for all schemes that map S-NSSAIs to transport identifiers, such as already those described in RFC 9889. I'm concerned that the document may be interpreted as if the IETF is recommending this approach compared to other approaches. It would be weird = to make such recommendation anyway because that is up to operators to decide t= he approach that fits their needs and aligned with the capabilities they deplo= y. So, instead of tagging this option as the only one which is "mobility aware= ", I suggest to position this work as a realization model based on tunnel transp= ort source port/ranges. That is, this is an applicability of the RFC9834 extens= ion defined in I-D.ietf-dmm-udp-tunnel-acaas-extn (3.3 is the main contribution here). I suggest that the title is also updated accordingly. This approach is consistent with Section 6.5 of draft-ietf-teas-5g-network-slice-application The details of this solution is described in [I-D.ietf-dmm-tn-aware-mobility]. # Normative references At least [RFC9543], [I-D.ietf-dmm-udp-tunnel-acaas-extn], [RFC9834], [RFC98= 89], and NRM should be normative. Please check the classification of other references and fix as appropriate. Thanks. ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- # For Chairs/AD: As this is a document covering an architecture owned by another SDO, I wonder whether there was an LS sent to the 3GPP about this d= oc? # Leverage Existing RFCs & Consistency RFC9889 already clarifies the concept of slicing in 3GPP, the concept of TN= , relationship between TN slicing and IETF Network Slicing, mapping considerations, realization of TN slicing beyond identification matters, various deployment options for the location of SDP, the attachment circuits= , etc. I suggest that this draft builds on RFC9889 rather than repeating some matt= ers. For example, Sections 2 and 4 can be removed, IMO. rfc9889#section-3 has already all these details. Moreover, the document should be updated to use a terminology that is consistent with existing RFCs. For example, "end-to-end 5G slice" should be= "5G end-to-end slice", etc. Cheers, Med --_000_SN4PR13MB531176EBFA3286BDA2DDD42FE8CA2SN4PR13MB5311namp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)"> <style><!-- /* Font Definitions */ @font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0;} @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} @font-face {font-family:Aptos;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; font-size:12.0pt; font-family:"Aptos",sans-serif; mso-ligatures:standardcontextual;} a:link, span.MsoHyperlink {mso-style-priority:99; color:#467886; text-decoration:underline;} p.MsoPlainText, li.MsoPlainText, div.MsoPlainText {mso-style-priority:99; mso-style-link:"Plain Text Char"; margin:0in; font-size:11.0pt; font-family:"Calibri",sans-serif; mso-ligatures:standardcontextual;} p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph {mso-style-priority:34; margin-top:0in; margin-right:0in; margin-bottom:0in; margin-left:.5in; font-size:12.0pt; font-family:"Aptos",sans-serif; mso-ligatures:standardcontextual;} span.EmailStyle17 {mso-style-type:personal-compose; font-family:"Aptos",sans-serif; color:windowtext;} span.PlainTextChar {mso-style-name:"Plain Text Char"; mso-style-priority:99; mso-style-link:"Plain Text"; font-family:"Calibri",sans-serif;} .MsoChpDefault {mso-style-type:export-only;} @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.WordSection1 {page:WordSection1;} /* List Definitions */ @list l0 {mso-list-id:1536501870; mso-list-type:hybrid; mso-list-template-ids:1482437518 502331202 67698691 67698693 67698689 6769= 8691 67698693 67698689 67698691 67698693;} @list l0:level1 {mso-level-number-format:bullet; mso-level-text:-; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in; font-family:"Aptos",sans-serif; mso-fareast-font-family:Aptos; mso-bidi-font-family:"Times New Roman";} @list l0:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in; font-family:"Courier New";} @list l0:level3 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in; font-family:Wingdings;} @list l0:level4 {mso-level-number-format:bullet; mso-level-text:\F0B7; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in; font-family:Symbol;} @list l0:level5 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in; font-family:"Courier New";} @list l0:level6 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in; font-family:Wingdings;} @list l0:level7 {mso-level-number-format:bullet; mso-level-text:\F0B7; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in; font-family:Symbol;} @list l0:level8 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in; font-family:"Courier New";} @list l0:level9 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in; font-family:Wingdings;} ol {margin-bottom:0in;} ul {margin-bottom:0in;} --></style><!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--> </head> <body lang=3D"EN-US" link=3D"#467886" vlink=3D"#96607D" style=3D"word-wrap:= break-word"> <div class=3D"WordSection1"> <p class=3D"MsoNormal">Hi Med, all,<o:p></o:p></p> <p class=3D"MsoNormal">(For some reason, I did not receive the e-mail, and = I’m using a copy forwarded to me by Luis)<o:p></o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">The authors have revised the draft to address /resol= ve the DISCUSS comments:<o:p></o:p></p> <ul style=3D"margin-top:0in" type=3D"disc"> <li class=3D"MsoListParagraph" style=3D"margin-left:0in;mso-list:l0 level1 = lfo1">Revised title of draft to: Mapping 5G slice to Transport Network slic= e with UDP Source Ports<br> References to “mobility awareness” is removed in both occurrenc= es in the draft.<br> <br> <o:p></o:p></li><li class=3D"MsoListParagraph" style=3D"margin-left:0in;mso= -list:l0 level1 lfo1">Revised to add Normative References section.<br> Moved RFC9543, RFC9834, RFC9889 and TS28.541 to normative references.<o:p><= /o:p></li></ul> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">There are a few other changes to address comments fr= om tsv-art and I’m replying separately on that.<br> <br> <o:p></o:p></p> <p class=3D"MsoNormal">Links:<o:p></o:p></p> <p class=3D"MsoPlainText">URL: <a href=3D"htt= ps://www.ietf.org/archive/id/draft-ietf-dmm-tn-aware-mobility-29.txt"> https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.iet= f.org%2Farchive%2Fid%2Fdraft-ietf-dmm-tn-aware-mobility-29.txt&data=3D0= 5%7C02%7Cjohn.kaippallimalil%40futurewei.com%7C5b0ddc0f5eab41ca9e1c08deed7d= 63e9%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C639209320014944035%7CUnkn= own%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zM= iIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=3D9LN9rlfkn%2BtN= jd7vRo1P1gcwvZac780gVBFOjFkDFF4%3D&reserved=3D0</a><o:p></o:p></p> <p class=3D"MsoPlainText"><o:p> </o:p></p> <p class=3D"MsoPlainText">Diff: <a href=3D"https://= author-tools.ietf.org/iddiff?url2=3Ddraft-ietf-dmm-tn-aware-mobility-29"> https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fauthor-= tools.ietf.org%2Fiddiff%3Furl2%3Ddraft-ietf-dmm-tn-aware-mobility-29&da= ta=3D05%7C02%7Cjohn.kaippallimalil%40futurewei.com%7C5b0ddc0f5eab41ca9e1c08= deed7d63e9%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C639209320015561443%= 7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJ= XaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=3DuT%2B8Q%= 2B3SU49A9MdvFpZ2Vk4UHWs3bXp4P8aM74CuxLA%3D&reserved=3D0</a><o:p></o:p><= /p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">Best Regards,<o:p></o:p></p> <p class=3D"MsoNormal">John<o:p></o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <div style=3D"mso-element:para-border-div;border:none;border-bottom:solid w= indowtext 1.0pt;padding:0in 0in 1.0pt 0in"> <p class=3D"MsoNormal" style=3D"border:none;padding:0in"><o:p> </o:p><= /p> </div> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a= lt:auto"><b><span style=3D"font-size:11.0pt;font-family:"Calibri"= ,sans-serif;color:black">From:</span></b><span style=3D"font-size:11.0pt;fo= nt-family:"Calibri",sans-serif;color:black"> Mohamed Boucadair via Datatracker <<a href=3D"mailto:[email protected]" target= =3D"_blank">[email protected]</a>><br> <b>Sent:</b> Thursday, 02 July 2026 10:02:10<br> <b>To:</b> The IESG <<a href=3D"mailto:[email protected]" target=3D"_blank">= [email protected]</a>><br> <b>Cc:</b> <a href=3D"mailto:[email protected]" target=3D"_blank">dmm-cha= [email protected]</a> <<a href=3D"mailto:[email protected]" target=3D"_blan= k">[email protected]</a>>; <a href=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a> <<a h= ref=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a>>; <a href=3D"mailto:[email protected]" target=3D"_bla= nk">[email protected]</a> <<a href=3D"mailto:dra= [email protected]" target=3D"_blank">draft-ietf-dmm-tn= [email protected]</a>>; <a href=3D"mailto:[email protected]" target=3D"_blank">satoru.mat= [email protected]</a> <<a href=3D"mailto:[email protected]" ta= rget=3D"_blank">[email protected]</a>><br> <b>Subject:</b> Mohamed Boucadair's Discuss on draft-ietf-dmm-tn-aware-mobi= lity-26: (with DISCUSS and COMMENT)</span> <o:p></o:p></p> <p class=3D"MsoNormal"> <span style=3D"font-size:11.0pt"><br> Mohamed Boucadair has entered the following ballot position for<br> draft-ietf-dmm-tn-aware-mobility-26: Discuss<br> <br> When responding, please keep the subject line intact and reply to all<br> email addresses included in the To and CC lines. (Feel free to cut this<br> introductory paragraph, however.)<br> <br> <br> Please refer to <a href=3D"https://www.ietf.org/about/groups/iesg/statement= s/handling-ballot-positions/" target=3D"_blank"> https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions= /</a><br> for more information about how to handle DISCUSS and COMMENT positions.<br> <br> <br> The document, along with other ballot positions, can be found here:<br> <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-dmm-tn-aware-mobilit= y/" target=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-dmm-tn-aw= are-mobility/</a><br> <br> <br> <br> ----------------------------------------------------------------------<br> DISCUSS:<br> ----------------------------------------------------------------------<br> <br> Hi Uma, John, Sridhar, Jeff, and Luis,<br> <br> Thank you for the effort put into this specification.<br> <br> Please find below some pints for DISCUSSion:<br> <br> # Mobility-awareness & Key technical contribution<br> <br> CURRENT:<br> Following UE handover, the S-NSSAI is mapped seamlessly to<br> the corresponding GTP-U (or UDP encapsulated GTP) source port = number<br> of the newly attached network and can be considered to be &quo= t;mobility<br> aware".<br> <br> The reasoning above applies for all schemes that map S-NSSAIs to transport<= br> identifiers, such as already those described in RFC 9889.<br> <br> I’m concerned that the document may be interpreted as if the IETF is<= br> recommending this approach compared to other approaches. It would be weird = to<br> make such recommendation anyway because that is up to operators to decide t= he<br> approach that fits their needs and aligned with the capabilities they deplo= y.<br> <br> So, instead of tagging this option as the only one which is “mobility= aware”, I<br> suggest to position this work as a realization model based on tunnel transp= ort<br> source port/ranges. That is, this is an applicability of the RFC9834 extens= ion<br> defined in I-D.ietf-dmm-udp-tunnel-acaas-extn (3.3 is the main contribution= <br> here). I suggest that the title is also updated accordingly.<br> <br> This approach is consistent with Section 6.5 of<br> draft-ietf-teas-5g-network-slice-application<br> <br> The details of this solution is described in<br> [I-D.ietf-dmm-tn-aware-mobility].<br> <br> # Normative references<br> <br> At least [RFC9543], [I-D.ietf-dmm-udp-tunnel-acaas-extn], [RFC9834], [RFC98= 89],<br> and NRM should be normative.<br> <br> Please check the classification of other references and fix as appropriate.= <br> Thanks.<br> <br> <br> ----------------------------------------------------------------------<br> COMMENT:<br> ----------------------------------------------------------------------<br> <br> # For Chairs/AD: As this is a document covering an architecture owned by<br= > another SDO, I wonder whether there was an LS sent to the 3GPP about this d= oc?<br> <br> # Leverage Existing RFCs & Consistency<br> <br> RFC9889 already clarifies the concept of slicing in 3GPP, the concept of TN= ,<br> relationship between TN slicing and IETF Network Slicing, mapping<br> considerations, realization of TN slicing beyond identification matters,<br= > various deployment options for the location of SDP, the attachment circuits= ,<br> etc.<br> <br> I suggest that this draft builds on RFC9889 rather than repeating some matt= ers.<br> For example, Sections 2 and 4 can be removed, IMO. rfc9889#section-3 has<br= > already all these details.<br> <br> Moreover, the document should be updated to use a terminology that is<br> consistent with existing RFCs. For example, “end-to-end 5G slice̶= 1; should be “5G<br> end-to-end slice”, etc.<br> <br> Cheers,<br> Med</span><o:p></o:p></p> </div> </body> </html> --_000_SN4PR13MB531176EBFA3286BDA2DDD42FE8CA2SN4PR13MB5311namp_-- --===============5799863884458315110== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZG1tIG1haWxp bmcgbGlzdCAtLSBkbW1AaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFpbCB0byBk bW0tbGVhdmVAaWV0Zi5vcmcK --===============5799863884458315110==--