[DMM] Re: WG Last Call: draft-ietf-dmm-tn-aware-mobility-2 2 (Ends 2025-10-30)
Xavier de Foy <[email protected]> Wed, 29 Oct 2025 12:34:32 -0400
| Newsgroups | gmane.ietf.nemo |
|---|---|
| Message-ID | <CAHYjOTZQqSbgDFrkx1Gg0dvnT=1jRLLqC23ePsXqLB0=mnZyPw@mail.gmail.com> |
--===============2525437495146885289== Content-Type: multipart/alternative; boundary="00000000000021140906424eb605" --00000000000021140906424eb605 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I support the publication of draft-ietf-dmm-tn-aware-mobility and provide a few minor comments below, for the authors' consideration. - #1: /map a 3GPP slice to a slice in an IP transport network provider/map a 3GPP slice to a slice in an IP transport network/ -OR- /map a 3GPP slice to an IP transport network slice at a provider edge/ - #3.1: /end-user (UE) sessions/PDU sessions/, because the term PDU session is used multiple times in the document already. - Note: consider expanding the term UE as User Equipment in the first occurence of the term in the draft. - Note: consider describing the meaning of PDU session at the first occurence of the term. - #3.3: consider adding text to define what EP_transport is. E.g., /3GPP user plane nodes (gNB, UPF) are provisioned with GTP transport interface information parameters in [TS.28.541-3GPP]./3GPP user plane nodes (gNB, UPF) are provisioned with GTP end point transport (EP_transport) interface information parameters in [TS.28.541-3GPP]./ - #3.3: a few sentences could be clarified a bit,I try illustrating below a few points. - "Each EP_Transport is configured with ATTACHMENT_CIRCUIT containing UDP source port number/range for each of the slices (S-NSSAI) supported by the 3GPP user plane node." Maybe: "Each EP_Transport is configured with an ATTACHMENT_CIRCUIT containing UDP source port number/range corresponding to a slice (S-NSSAI) supported by the 3GPP user plane node." - "This S-NSSAI in the user plane setup can be used to associate with the previously configured EP_Transport information per S-NSSAI." Maybe: "This S-NSSAI in the user plane setup can be associated with one of the previously configured per-S-NSSAI EP_Transport information." - /to that signaled for the PDU session/to the S-NSSAI signaled for the PDU session/ - #4: About the paragraph "In some E2E scenarios, security is desired granularly...", I was wondering if the text could cover something more general than security, e.g., "In some E2E scenarios, additional path characteristics may be desired in the underlying transport network, such as security characteristics.". The rest of the paragraph may be adapted correspondingly, if you agree with this comment. One example of non-security characteristic that comes to mind is regulatory/legal, e.g., the physical location of the path (and this does not need to be spelled out in the text, this is just for illustrating where my comment comes from). - #6: /authenticaiton/authentication/ Best Regards, Xavier On Wed, Oct 29, 2025 at 7:23=E2=80=AFAM Kaippallimalil John < [email protected]> wrote: > draft-ietf-dmm-tn-aware-mobility provides a solution to support the > capabilities offered by 5G slices across IP transport networks that > backhaul the traffic. > > As an author, I believe this draft is ready for publication. > > > > Best Regards, > > John > > > > *From:* Satoru Matsushima <[email protected]> > *Sent:* Friday, October 24, 2025 4:52 PM > *To:* Satoru Matsushima <[email protected]> > *Cc:* [email protected]; [email protected]; > [email protected] > *Subject:* 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=E2=80=AFPM Satoru Matsushima via Datatracker= < > [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] > in copy. Objections should be motivated and suggestions to resolve them a= re > highly appreciated. > > Authors, and WG participants in general, are reminded again of the > Intellectual Property Rights (IPR) disclosure obligations described in BC= P > 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 o= f > 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] > --00000000000021140906424eb605 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">I support the publication of draft-ietf-dmm-tn-aware-mobil= ity and provide a few minor comments below, for the authors' considerat= ion. =C2=A0<br><div><br></div><div><br></div>- #1: /map a 3GPP slice to a s= lice in an IP transport network provider/map a 3GPP slice to a slice in an = IP transport network/ -OR- /map a 3GPP slice to an=C2=A0 IP transport netwo= rk slice at a provider edge/<br><br>- #3.1: /end-user (UE) sessions/PDU ses= sions/, because the term PDU session is used multiple times in the document= already.<br>=C2=A0 - Note: consider expanding the term UE as User Equipmen= t in the first occurence of the term in the draft.<br>=C2=A0 - Note: consid= er describing the meaning of PDU session at the first occurence of the term= .<br>=C2=A0 <br>- #3.3: consider adding text to define what EP_transport is= . E.g., /3GPP user plane nodes (gNB, UPF) are provisioned with GTP transpor= t interface information parameters in [TS.28.541-3GPP]./3GPP user plane nod= es (gNB, UPF) are provisioned with GTP end point transport (EP_transport) i= nterface information parameters in [TS.28.541-3GPP]./<br>- #3.3: a few sent= ences could be clarified a bit,I try illustrating below a few points.<br>= =C2=A0 - "Each EP_Transport is configured with ATTACHMENT_CIRCUIT cont= aining UDP source port number/range for each of the slices (S-NSSAI) suppor= ted by the 3GPP user plane node." Maybe: "Each EP_Transport is co= nfigured with an ATTACHMENT_CIRCUIT containing UDP source port number/range= corresponding to a slice (S-NSSAI) supported by the 3GPP user plane node.&= quot;<br>=C2=A0 - "This S-NSSAI in the user plane setup can be used to= associate with the previously configured EP_Transport information per S-NS= SAI." Maybe: "This S-NSSAI in the user plane setup can be associa= ted with one of the previously configured per-S-NSSAI EP_Transport informat= ion."<br>=C2=A0 - /to that signaled for the PDU session/to the S-NSSAI= signaled for the PDU session/<br><br>- #4: About the paragraph "In so= me E2E scenarios, security is desired granularly...", I was wondering = if the text could cover something more general than security, e.g., "I= n some E2E scenarios, additional path characteristics may be desired in the= underlying transport network, such as security characteristics.". The= rest of the paragraph may be adapted correspondingly, if you agree with th= is comment. One example of non-security characteristic that comes to mind i= s regulatory/legal, e.g., the physical location of the path (and this does = not need to be spelled out in the text, this is just for illustrating where= my comment comes from).<br><br><div>- #6: /authenticaiton/authentication/<= /div><div><br></div><div>Best Regards,</div><div>Xavier</div></div><br><div= class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmai= l_attr">On Wed, Oct 29, 2025 at 7:23=E2=80=AFAM Kaippallimalil John <<a = href=3D"mailto:[email protected]">john.kaippallimalil@futur= ewei.com</a>> wrote:<br></div><blockquote class=3D"gmail_quote" style=3D= "margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le= ft:1ex"><div class=3D"msg2154808513756961442"> <div lang=3D"EN-US" style=3D"overflow-wrap: break-word;"> <div class=3D"m_2154808513756961442WordSection1"> <p class=3D"MsoNormal">draft-ietf-dmm-tn-aware-mobility provides a solution= to support the capabilities offered by 5G slices across IP transport netwo= rks that backhaul the traffic.<u></u><u></u></p> <p class=3D"MsoNormal">As an author, I believe this draft is ready for publ= ication.<u></u><u></u></p> <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p> <p class=3D"MsoNormal">Best Regards,<u></u><u></u></p> <p class=3D"MsoNormal">John<u></u><u></u></p> <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p> <div style=3D"border-width:medium medium medium 1.5pt;border-style:none non= e none solid;border-color:currentcolor currentcolor currentcolor blue;paddi= ng:0in 0in 0in 4pt"> <div> <div style=3D"border-width:1pt medium medium;border-style:solid none none;b= order-color:rgb(225,225,225) currentcolor currentcolor;padding:3pt 0in 0in"= > <p class=3D"MsoNormal"><b><span style=3D"font-size:11pt;font-family:"C= alibri",sans-serif">From:</span></b><span style=3D"font-size:11pt;font= -family:"Calibri",sans-serif"> Satoru Matsushima <<a href=3D"m= ailto:[email protected]" target=3D"_blank">satoru.matsushima@gmai= l.com</a>> <br> <b>Sent:</b> Friday, October 24, 2025 4:52 PM<br> <b>To:</b> Satoru Matsushima <<a href=3D"mailto:satoru.matsushima@gmail.= com" 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"_blank">dmm@iet= f.org</a>; <a href=3D"mailto:[email protected]" tar= get=3D"_blank">[email protected]</a><br> <b>Subject:</b> Re: WG Last Call: draft-ietf-dmm-tn-aware-mobility-22 (Ends= 2025-10-30)<u></u><u></u></span></p> </div> </div> <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p> <div> <p class=3D"MsoNormal">DMMer,<u></u><u></u></p> <div> <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p> </div> <div> <p class=3D"MsoNormal">Let me remind you that the mobility-aware transport = draft is now in WGLC. It will end on Oct. 30, so please review=C2=A0the dra= ft.<u></u><u></u></p> </div> <div> <p class=3D"MsoNormal">You can use this thread to=C2=A0send your feedback.= =C2=A0<u></u><u></u></p> </div> <div> <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p> </div> <div> <p class=3D"MsoNormal">Cheers,<u></u><u></u></p> </div> <div> <p class=3D"MsoNormal">--satoru<u></u><u></u></p> </div> </div> <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p> <div> <div> <p class=3D"MsoNormal">On Thu, Oct 16, 2025 at 9:09<span style=3D"font-fami= ly:"Arial",sans-serif">=E2=80=AF</span>PM Satoru Matsushima via D= atatracker <<a href=3D"mailto:[email protected]" target=3D"_blank">norepl= [email protected]</a>> wrote:<u></u><u></u></p> </div> <blockquote style=3D"border-width:medium medium medium 1pt;border-style:non= e none none solid;border-color:currentcolor currentcolor currentcolor rgb(2= 04,204,204);padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in"> <p class=3D"MsoNormal" style=3D"margin-bottom:12pt"><br> Subject: WG Last Call: draft-ietf-dmm-tn-aware-mobility-22 (Ends 2025-10-30= )<br> <br> This message starts a 2-week WG Last Call for this document.<br> <br> Abstract:<br> =C2=A0 =C2=A0Network slicing in 5G enables logical networks for communicati= on<br> =C2=A0 =C2=A0services of multiple 5G customers to be multiplexed over the s= ame<br> =C2=A0 =C2=A0infrastructure.=C2=A0 While 5G slicing covers logical separati= on of<br> =C2=A0 =C2=A0various aspects of 5G infrastructure and services, user's = data plane<br> =C2=A0 =C2=A0packets over the Radio Access Network (RAN) and Core Network (= 5GC)<br> =C2=A0 =C2=A0use IP in many segments of an end-to-end 5G slice.=C2=A0 When = end-to-end<br> =C2=A0 =C2=A0slices in a 5G System use network resources, they are mapped t= o<br> =C2=A0 =C2=A0corresponding IP transport network slice(s) which in turn prov= ide the<br> =C2=A0 =C2=A0bandwidth, latency, isolation, and other criteria required for= the<br> =C2=A0 =C2=A0realization of a 5G slice.<br> <br> =C2=A0 =C2=A0This document describes mapping of 5G slices to transport netw= ork<br> =C2=A0 =C2=A0slices using UDP source port number of the GTP-U bearer when t= he IP<br> =C2=A0 =C2=A0transport network (slice provider) is separated by an "at= tachment<br> =C2=A0 =C2=A0circuit" from the networks in which the 5G network functi= ons are<br> =C2=A0 =C2=A0deployed, for example, 5G functions that are distributed acros= s data<br> =C2=A0 =C2=A0centers.=C2=A0 The slice mapping defined here is supported tra= nsparently<br> =C2=A0 =C2=A0when a 5G user device moves across 5G attachment points and se= ssion<br> =C2=A0 =C2=A0anchors.<br> <br> File can be retrieved from:<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> Please review and indicate your support or objection to proceed with the<br= > publication of this document by replying to this email keeping <a href=3D"m= ailto:[email protected]" target=3D"_blank"> [email protected]</a><br> in copy. Objections should be motivated and suggestions to resolve them are= <br> highly appreciated.<br> <br> Authors, and WG participants in general, are reminded again of the<br> Intellectual Property Rights (IPR) disclosure obligations described in BCP = 79<br> [1]. Appropriate IPR disclosures required for full conformance with the<br> provisions of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of<= br> any. Sanctions available for application to violators of IETF IPR Policy ca= n<br> be found at [3].<br> <br> Thank you.<br> <br> [1] <a href=3D"https://datatracker.ietf.org/doc/bcp78/" target=3D"_blank">h= ttps://datatracker.ietf.org/doc/bcp78/</a><br> [2] <a href=3D"https://datatracker.ietf.org/doc/bcp79/" target=3D"_blank">h= ttps://datatracker.ietf.org/doc/bcp79/</a><br> [3] <a href=3D"https://datatracker.ietf.org/doc/rfc6701/" target=3D"_blank"= >https://datatracker.ietf.org/doc/rfc6701/</a><br> <br> <br> <u></u><u></u></p> </blockquote> </div> </div> </div> </div> _______________________________________________<br> dmm mailing list -- <a href=3D"mailto:[email protected]" target=3D"_blank">dmm@i= etf.org</a><br> To unsubscribe send an email to <a href=3D"mailto:[email protected]" targe= t=3D"_blank">[email protected]</a><br> </div></blockquote></div> --00000000000021140906424eb605-- --===============2525437495146885289== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZG1tIG1haWxp bmcgbGlzdCAtLSBkbW1AaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFpbCB0byBk bW0tbGVhdmVAaWV0Zi5vcmcK --===============2525437495146885289==--