[DMM] Re: WG Last Call: draft-ietf-dmm-tn-aware-mobility-2 2 (Ends 2025-10-30)
Satoru Matsushima <[email protected]> Thu, 27 Nov 2025 21:39:10 +0900
| Newsgroups | gmane.ietf.nemo |
|---|---|
| Message-ID | <CAFwJXX53b1+k+dM43g47SEpUaDhf79QZSeZ_pYztwT_nZXibkQ@mail.gmail.com> |
--===============5588476380613622056== Content-Type: multipart/alternative; boundary="000000000000690a43064492cde5" --000000000000690a43064492cde5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks John, > It would be good to revise to realistic services SST =3D 1 (eMMB), SST = =3D 2 (URLLC) and SST =3D 3 (MioT). That sounds good. So the example values denoted as 200A/1000/300C follow SST(8)+SD(24) format of (S-)NSSAI. Is that correct? For me those values look 2 bytes in hex. Where are the remaining 2 bytes? Please correct me if I'm wrong. --satoru On Wed, Nov 26, 2025 at 3:09=E2=80=AFAM Kaippallimalil John < [email protected]> wrote: > Hi Satoru, All, > > > > Thanks for the review and pointers. > > > > - Section 3.1: Change /end-user (UE) sessions/PDU sessions/ and consider > describing the meaning of "PDU session" at its first occurrence. > > In section 1, PDU session has already been defined =E2=80=9CA PDU session= in 5G is > a logical connection that provides a path between a User Equipment (UE) a= nd > a data network such as the internet=E2=80=9D] > > Will revise end-user (UE) session to PDU session in 3.1. > > > > - Change /to that signaled for the PDU session/to the S-NSSAI signaled fo= r > the PDU session/ > > Will revise. > > > > There is one other change that would help (this is sort of triggered from > an LS exchange on slices in this November 3GPP meeting): > > In 3.2 and 3.3, the example NSSAIs that consist of SST (Service Slice > Type) and SD (Slice Differentiator) is not accurate. It shows 3 different > services A, B, C with the same SST (=E2=80=9C0=E2=80=9D ). > > It would be good to revise to realistic services SST =3D 1 (eMMB), SST = =3D 2 > (URLLC) and SST =3D 3 (MioT). > > That would change the (S-)NSSAI values in Figures 2 and 3 as follows > (NSSAI consists of SST=3D 8 bit field, followed by SD =3D24 bit field) > > NSSAI =3D 000A =C3=A0 200A (URLLC service, customer A), > > NSSAI =3D 000B =C3=A0 1000 (eMBB service, all customers/locations) > > NSSAI =3D 000C =C3=A0 300C (MioT service, customer C) > > This would require some revision in the of 3.2 to align with the above > change. > > No change in 3.3 other than revising 000B =C3=A0 1000. > > Note that this is only change of an example in 3.2 and does not in any wa= y > affect the logic of mapping proposed in the draft (i.e., NSSAI to UDP por= t > (range) is a direct map). > > > > If the group agrees, I would like to make this additional change. > > > > Best Regards, > > John > > > > > > *From:* Satoru Matsushima <[email protected]> > *Sent:* Tuesday, November 25, 2025 8:05 AM > *To:* Kaippallimalil John <[email protected]> > *Cc:* Xavier de Foy <[email protected]>; [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 John, > > > > Could you please confirm if you plan to address the following specific > comments from Xavier de Foy? > > > > - Section 3.1: Change /end-user (UE) sessions/PDU sessions/ and consider > describing the meaning of "PDU session" at its first occurrence. > > - Change /to that signaled for the PDU session/to the S-NSSAI signaled fo= r > the PDU session/ > > > > I was unable to find the resolutions for these particular points in the > latest diff and your slides in the last DMM meeting. > > > > Thanks, > > --satoru > > > > On Tue, Nov 4, 2025 at 11:22=E2=80=AFPM Kaippallimalil John < > [email protected]> wrote: > > Hi Xavier, > > > Thank you for the comments and support. > > > > Please see the new revision that implements the suggested changes below. > > Link to diff: > > > https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fautho= r-tools.ietf.org%2Fiddiff%3Furl2%3Ddraft-ietf-dmm-tn-aware-mobility-23&data= =3D05%7C02%7Cjohn.kaippallimalil%40futurewei.com%7Ca53923a3718f4b44e9b608de= 1bad41bc%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C638978628121984873%7C= Unknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXa= W4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=3DrRuK6uT3gVgtpA= K0YvjXQ5IuG%2FC8YnGdGIZI1BQfvXg%3D&reserved=3D0 > <https://author-tools.ietf.org/iddiff?url2=3Ddraft-ietf-dmm-tn-aware-mobi= lity-23> > > > > Best Regards, > > John > > > > > > *From:* Xavier de Foy <[email protected]> > *Sent:* Wednesday, October 29, 2025 11:35 AM > *To:* Satoru Matsushima <[email protected]>; [email protected]= g; > [email protected]; [email protected] > *Subject:* Re: [DMM] Re: WG Last Call: > draft-ietf-dmm-tn-aware-mobility-22 (Ends 2025-10-30) > > > > 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/ma= p > a 3GPP slice to a slice in an IP transport network/ -OR- /map a 3GPP slic= e > 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) interfac= e > 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 b= y > the 3GPP user plane node." Maybe: "Each EP_Transport is configured with a= n > 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 o= ut > 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] > > --000000000000690a43064492cde5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Thanks John,<div><br></div><div>> It would be good to r= evise to realistic services SST =3D 1 (eMMB), SST =3D 2 (URLLC) and SST =3D= 3 (MioT).</div><br class=3D"gmail-Apple-interchange-newline"><div>That sou= nds=C2=A0good. So the example values denoted as 200A/1000/300C follow SST(8= )+SD(24) format of (S-)NSSAI. Is that correct?</div><div>For me those value= s=C2=A0look=C2=A02 bytes in hex. Where=C2=A0are the remaining 2 bytes? Plea= se correct me if I'm wrong.=C2=A0</div><div>--satoru</div></div><br><di= v class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gma= il_attr">On Wed, Nov 26, 2025 at 3:09=E2=80=AFAM Kaippallimalil John <<a= href=3D"mailto:[email protected]">john.kaippallimalil@futu= rewei.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= -left:1ex"><div class=3D"msg-2663389585622715882"> <div lang=3D"EN-US" style=3D"overflow-wrap: break-word;"> <div class=3D"m_-2663389585622715882WordSection1"> <p class=3D"MsoNormal">Hi Satoru, All,<u></u><u></u></p> <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p> <p class=3D"MsoNormal">Thanks for the review and pointers.<u></u><u></u></p= > <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p> <p class=3D"MsoNormal">- Section 3.1: Change /end-user (UE) sessions/PDU se= ssions/ and consider describing the meaning of "PDU session" at i= ts first occurrence.<u></u><u></u></p> <p class=3D"MsoNormal">In section 1, PDU session has already been defined = =E2=80=9CA PDU session in 5G is a logical connection that provides a path b= etween a User Equipment (UE) and a data network such as the internet=E2=80= =9D]<u></u><u></u></p> <p class=3D"MsoNormal">Will revise end-user (UE) session to PDU session in = 3.1.<u></u><u></u></p> <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p> <p class=3D"MsoNormal">- Change /to that signaled for the PDU session/to th= e S-NSSAI signaled for the PDU session/<u></u><u></u></p> <p class=3D"MsoNormal">Will revise.<u></u><u></u></p> <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p> <p class=3D"MsoNormal">There is one other change that would help (this is s= ort of triggered from an LS exchange on slices in this November 3GPP meetin= g):<u></u><u></u></p> <p class=3D"MsoNormal">In 3.2 and 3.3, the example NSSAIs that consist of S= ST (Service Slice Type) and SD (Slice Differentiator) is not accurate. It s= hows 3 different services A, B, C with the same SST (=E2=80=9C0=E2=80=9D ).= <u></u><u></u></p> <p class=3D"MsoNormal">It would be good to revise to realistic services SST= =3D 1 (eMMB), SST =3D 2 (URLLC) and SST =3D 3 (MioT).<u></u><u></u></p> <p class=3D"MsoNormal">That would change the (S-)NSSAI values in Figures 2 = and 3 as follows (NSSAI consists of SST=3D 8 bit field, followed by SD =3D2= 4 bit field)<u></u><u></u></p> <p class=3D"MsoNormal">NSSAI =3D 000A =C2=A0<span style=3D"font-family:Wing= dings">=C3=A0</span> 200A (URLLC service, customer A),<u></u><u></u></p> <p class=3D"MsoNormal">NSSAI =3D 000B <span style=3D"font-family:Wingdings"= >=C3=A0</span> 1000 (eMBB service, all customers/locations)<u></u><u></u></= p> <p class=3D"MsoNormal">NSSAI =3D 000C <span style=3D"font-family:Wingdings"= >=C3=A0</span> 300C (MioT service, customer C)<u></u><u></u></p> <p class=3D"MsoNormal">This would require some revision in the of 3.2 to al= ign with the above change. <u></u><u></u></p> <p class=3D"MsoNormal">No change in 3.3 other than revising 000B <span styl= e=3D"font-family:Wingdings"> =C3=A0</span> 1000.<u></u><u></u></p> <p class=3D"MsoNormal">Note that this is only change of an example in 3.2 a= nd does not in any way affect the logic of mapping proposed in the draft (i= .e., NSSAI to UDP port (range) is a direct map).<u></u><u></u></p> <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p> <p class=3D"MsoNormal">If the group agrees, I would like to make this addit= ional change.<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> <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p> <div style=3D"border-top:none;border-right:none;border-bottom:none;border-l= eft:1.5pt solid blue;padding:0in 0in 0in 4pt"> <div> <div style=3D"border-right:none;border-bottom:none;border-left:none;border-= top:1pt solid rgb(225,225,225);padding:3pt 0in 0in"> <p class=3D"MsoNormal"><b><span style=3D"font-size:11pt;font-family:Calibri= ,sans-serif">From:</span></b><span style=3D"font-size:11pt;font-family:Cali= bri,sans-serif"> Satoru Matsushima <<a href=3D"mailto:satoru.matsushima@= gmail.com" target=3D"_blank">[email protected]</a>> <br> <b>Sent:</b> Tuesday, November 25, 2025 8:05 AM<br> <b>To:</b> Kaippallimalil John <<a href=3D"mailto:john.kaippallimalil@fu= turewei.com" target=3D"_blank">[email protected]</a>><br= > <b>Cc:</b> Xavier de Foy <<a href=3D"mailto:[email protected]" targ= et=3D"_blank">[email protected]</a>>; <a href=3D"mailto:dmm-chairs@= ietf.org" target=3D"_blank">[email protected]</a>; <a href=3D"mailto:dmm@= ietf.org" target=3D"_blank">[email protected]</a>; <a href=3D"mailto:draft-ietf-= [email protected]" target=3D"_blank">draft-ietf-dmm-tn-aware-m= [email protected]</a><br> <b>Subject:</b> Re: [DMM] Re: WG Last Call: draft-ietf-dmm-tn-aware-mobilit= y-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> <div> <p class=3D"MsoNormal">Hi John,<u></u><u></u></p> </div> <div> <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p> </div> <div> <p class=3D"MsoNormal">Could you please confirm if you plan to address the = following specific comments from Xavier de Foy?<u></u><u></u></p> </div> <div> <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p> </div> <div> <p class=3D"MsoNormal">- Section 3.1: Change /end-user (UE) sessions/PDU se= ssions/ and consider describing the meaning of "PDU session" at i= ts first occurrence.<u></u><u></u></p> </div> <div> <p class=3D"MsoNormal">- Change /to that signaled for the PDU session/to th= e S-NSSAI signaled for the PDU session/<u></u><u></u></p> </div> <div> <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p> </div> <div> <p class=3D"MsoNormal">I was unable to find the resolutions for these parti= cular points in the latest diff and your slides in the last DMM meeting.<u>= </u><u></u></p> </div> <div> <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p> </div> <div> <p class=3D"MsoNormal">Thanks,<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 Tue, Nov 4, 2025 at 11:22<span style=3D"font-fami= ly:Arial,sans-serif">=E2=80=AF</span>PM Kaippallimalil John <<a href=3D"= mailto:[email protected]" target=3D"_blank">john.kaippallim= [email protected]</a>> wrote:<u></u><u></u></p> </div> <blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b= order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4= .8pt;margin-right:0in"> <div> <div> <div> <p class=3D"MsoNormal">Hi Xavier,<u></u><u></u></p> <p class=3D"MsoNormal"><br> Thank you for the comments and support.<u></u><u></u></p> <p class=3D"MsoNormal">=C2=A0<u></u><u></u></p> <p class=3D"MsoNormal">Please see the new revision that implements the sugg= ested changes below.<u></u><u></u></p> <p class=3D"MsoNormal">Link to diff:<u></u><u></u></p> <p class=3D"m_-2663389585622715882m-8372609505521162702msoplaintext"><a hre= f=3D"https://author-tools.ietf.org/iddiff?url2=3Ddraft-ietf-dmm-tn-aware-mo= bility-23" target=3D"_blank">https://nam11.safelinks.protection.outlook.com= /?url=3Dhttps%3A%2F%2Fauthor-tools.ietf.org%2Fiddiff%3Furl2%3Ddraft-ietf-dm= m-tn-aware-mobility-23&data=3D05%7C02%7Cjohn.kaippallimalil%40futurewei= .com%7Ca53923a3718f4b44e9b608de1bad41bc%7C0fee8ff2a3b240189c753a1d5591fedc%= 7C1%7C0%7C638978628121984873%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydW= UsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%= 7C%7C%7C&sdata=3DrRuK6uT3gVgtpAK0YvjXQ5IuG%2FC8YnGdGIZI1BQfvXg%3D&r= eserved=3D0</a><u></u><u></u></p> <p class=3D"MsoNormal">=C2=A0<u></u><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">=C2=A0<u></u><u></u></p> <p class=3D"MsoNormal">=C2=A0<u></u><u></u></p> <div style=3D"border-top:none;border-right:none;border-bottom:none;border-l= eft:1.5pt solid blue;padding:0in 0in 0in 4pt"> <div> <div style=3D"border-right:none;border-bottom:none;border-left:none;border-= top:1pt solid rgb(225,225,225);padding:3pt 0in 0in"> <p class=3D"MsoNormal"><b><span style=3D"font-size:11pt;font-family:Calibri= ,sans-serif">From:</span></b><span style=3D"font-size:11pt;font-family:Cali= bri,sans-serif"> Xavier de Foy <<a href=3D"mailto:[email protected]= " target=3D"_blank">[email protected]</a>> <br> <b>Sent:</b> Wednesday, October 29, 2025 11:35 AM<br> <b>To:</b> Satoru Matsushima <<a href=3D"mailto:satoru.matsushima@gmail.= com" target=3D"_blank">[email protected]</a>>; <a href=3D"mailto:[email protected]" target=3D"_blank">[email protected]= g</a>; <a href=3D"mailto:[email protected]" target=3D"_blank"> [email protected]</a>; <a href=3D"mailto:[email protected]= rg" target=3D"_blank"> [email protected]</a><br> <b>Subject:</b> Re: [DMM] Re: WG Last Call: draft-ietf-dmm-tn-aware-mobilit= y-22 (Ends 2025-10-30)</span><u></u><u></u></p> </div> </div> <p class=3D"MsoNormal">=C2=A0<u></u><u></u></p> <div> <p class=3D"MsoNormal">I support the publication of draft-ietf-dmm-tn-aware= -mobility and provide a few minor comments below, for the authors' cons= ideration. =C2=A0<u></u><u></u></p> <div> <p class=3D"MsoNormal">=C2=A0<u></u><u></u></p> </div> <div> <p class=3D"MsoNormal">=C2=A0<u></u><u></u></p> </div> <p class=3D"MsoNormal" style=3D"margin-bottom:12pt">- #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=C2=A0 IP transpor= t network slice at a provider edge/<br> <br> - #3.1: /end-user (UE) sessions/PDU sessions/, because the term PDU session= is used multiple times in the document already.<br> =C2=A0 - Note: consider expanding the term UE as User Equipment in the firs= t occurence of the term in the draft.<br> =C2=A0 - Note: consider 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 us= er plane nodes (gNB, UPF) are provisioned with GTP transport interface info= rmation parameters in [TS.28.541-3GPP]./3GPP user plane nodes (gNB, UPF) ar= e provisioned with GTP end point transport (EP_transport) interface information parameters in [TS.28.541-3G= PP]./<br> - #3.3: a few sentences 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."<br> =C2=A0 - "This S-NSSAI in the user plane setup can be used to associat= e 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."<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 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 th= e paragraph may be adapted correspondingly, if you agree with this comment.= One example of non-security characteristic that comes to mind is regulator= y/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).<u></u><u></u></p> <div> <p class=3D"MsoNormal">- #6: /authenticaiton/authentication/<u></u><u></u><= /p> </div> <div> <p class=3D"MsoNormal">=C2=A0<u></u><u></u></p> </div> <div> <p class=3D"MsoNormal">Best Regards,<u></u><u></u></p> </div> <div> <p class=3D"MsoNormal">Xavier<u></u><u></u></p> </div> </div> <p class=3D"MsoNormal">=C2=A0<u></u><u></u></p> <div> <div> <p class=3D"MsoNormal">On Wed, Oct 29, 2025 at 7:23<span style=3D"font-fami= ly:Arial,sans-serif">=E2=80=AF</span>AM Kaippallimalil John <<a href=3D"= mailto:[email protected]" target=3D"_blank">john.kaippallim= [email protected]</a>> wrote:<u></u><u></u></p> </div> <blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b= order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin:5pt 0i= n 5pt 4.8pt"> <div> <div> <div> <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">=C2=A0<u></u><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">=C2=A0<u></u><u></u></p> <div style=3D"border-left:1.5pt solid blue;padding:0in 0in 0in 4pt;border-t= op:currentcolor;border-right:currentcolor;border-bottom:currentcolor"> <div> <div> <p class=3D"MsoNormal"><b><span style=3D"font-size:11pt;font-family:Calibri= ,sans-serif">From:</span></b><span style=3D"font-size:11pt;font-family:Cali= bri,sans-serif"> Satoru Matsushima <<a href=3D"mailto:satoru.matsushima@= gmail.com" target=3D"_blank">[email protected]</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">[email protected]</a>; <a href= =3D"mailto:[email protected]" target=3D"_blank"> [email protected]</a><br> <b>Subject:</b> Re: WG Last Call: draft-ietf-dmm-tn-aware-mobility-22 (Ends= 2025-10-30)</span><u></u><u></u></p> </div> </div> <p class=3D"MsoNormal">=C2=A0<u></u><u></u></p> <div> <p class=3D"MsoNormal">DMMer,<u></u><u></u></p> <div> <p class=3D"MsoNormal">=C2=A0<u></u><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">=C2=A0<u></u><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">=C2=A0<u></u><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 Datatracker &= lt;<a href=3D"mailto:[email protected]" target=3D"_blank">[email protected]</= a>> wrote:<u></u><u></u></p> </div> <blockquote style=3D"border-left:1pt solid rgb(204,204,204);padding:0in 0in= 0in 6pt;margin:5pt 0in 5pt 4.8pt;border-top:currentcolor;border-right:curr= entcolor;border-bottom:currentcolor"> <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><u></u><u></u></p> </blockquote> </div> </div> </div> </div> <p class=3D"MsoNormal">_______________________________________________<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><u></u><u></u></p> </div> </blockquote> </div> </div> </div> </div> </div> </blockquote> </div> </div> </div> </div> </div></blockquote></div> --000000000000690a43064492cde5-- --===============5588476380613622056== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZG1tIG1haWxp bmcgbGlzdCAtLSBkbW1AaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFpbCB0byBk bW0tbGVhdmVAaWV0Zi5vcmcK --===============5588476380613622056==--