[DMM] Re: WG Last Call: draft-ietf-dmm-tn-aware-mobility-2 2 (Ends 2025-10-30)

Jeff Tantsura <[email protected]> Sat, 1 Nov 2025 00:39:19 +0200
Newsgroups gmane.ietf.nemo
Message-ID <247BBF23-02D3-4C0C-A8DB-AF94FE6946CA__22812.3781083681$1761950401$gmane$org@gmail.com>
--===============7285091683563203666==
Content-Type: multipart/alternative;
 boundary=Apple-Mail-0ED31714-03D3-4E35-9584-F3D55F009008
Content-Transfer-Encoding: 7bit


--Apple-Mail-0ED31714-03D3-4E35-9584-F3D55F009008
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html class=3D"apple-mail-supports-explicit-dark-mode"><head><meta http-equi=
v=3D"content-type" content=3D"text/html; charset=3Dutf-8"></head><body dir=3D=
"auto">Support as co-author.<div><br><div>Not aware of any IPR that has not b=
een previously disclosed.</div><div><br id=3D"lineBreakAtBeginningOfSignatur=
e"><div dir=3D"ltr">Cheers,<br><div>Jeff</div></div><div dir=3D"ltr"><br><bl=
ockquote type=3D"cite">On Oct 29, 2025, at 19:22, Uma Chunduri &lt;umac.ietf=
@gmail.com&gt; wrote:<br><br></blockquote></div><blockquote type=3D"cite"><d=
iv dir=3D"ltr">=EF=BB=BF<div dir=3D"ltr">Support as co-author.<div><br></div=
><div>I don't have knowledge of any other IPRs related to this work other th=
an what's been disclosed already.<br><div><br></div><div>--</div><div>Uma C.=
</div></div></div><br><div class=3D"gmail_quote gmail_quote_container"><div d=
ir=3D"ltr" class=3D"gmail_attr">On Thu, Oct 16, 2025 at 5:09=E2=80=AFAM Sato=
ru Matsushima via Datatracker &lt;<a href=3D"mailto:[email protected]">norepl=
[email protected]</a>&gt; 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-lef=
t:1ex"><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>
&nbsp; &nbsp;Network slicing in 5G enables logical networks for communicatio=
n<br>
&nbsp; &nbsp;services of multiple 5G customers to be multiplexed over the sa=
me<br>
&nbsp; &nbsp;infrastructure.&nbsp; While 5G slicing covers logical separatio=
n of<br>
&nbsp; &nbsp;various aspects of 5G infrastructure and services, user's data p=
lane<br>
&nbsp; &nbsp;packets over the Radio Access Network (RAN) and Core Network (5=
GC)<br>
&nbsp; &nbsp;use IP in many segments of an end-to-end 5G slice.&nbsp; When e=
nd-to-end<br>
&nbsp; &nbsp;slices in a 5G System use network resources, they are mapped to=
<br>
&nbsp; &nbsp;corresponding IP transport network slice(s) which in turn provi=
de the<br>
&nbsp; &nbsp;bandwidth, latency, isolation, and other criteria required for t=
he<br>
&nbsp; &nbsp;realization of a 5G slice.<br>
<br>
&nbsp; &nbsp;This document describes mapping of 5G slices to transport netwo=
rk<br>
&nbsp; &nbsp;slices using UDP source port number of the GTP-U bearer when th=
e IP<br>
&nbsp; &nbsp;transport network (slice provider) is separated by an "attachme=
nt<br>
&nbsp; &nbsp;circuit" from the networks in which the 5G network functions ar=
e<br>
&nbsp; &nbsp;deployed, for example, 5G functions that are distributed across=
 data<br>
&nbsp; &nbsp;centers.&nbsp; The slice mapping defined here is supported tran=
sparently<br>
&nbsp; &nbsp;when a 5G user device moves across 5G attachment points and ses=
sion<br>
&nbsp; &nbsp;anchors.<br>
<br>
File can be retrieved from:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-dmm-tn-aware-mobility=
/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/dra=
ft-ietf-dmm-tn-aware-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"ma=
ilto:[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 7=
9<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<b=
r>
any. Sanctions available for application to violators of IETF IPR Policy can=
<br>
be found at [3].<br>
<br>
Thank you.<br>
<br>
[1] <a href=3D"https://datatracker.ietf.org/doc/bcp78/" rel=3D"noreferrer" t=
arget=3D"_blank">https://datatracker.ietf.org/doc/bcp78/</a><br>
[2] <a href=3D"https://datatracker.ietf.org/doc/bcp79/" rel=3D"noreferrer" t=
arget=3D"_blank">https://datatracker.ietf.org/doc/bcp79/</a><br>
[3] <a href=3D"https://datatracker.ietf.org/doc/rfc6701/" rel=3D"noreferrer"=
 target=3D"_blank">https://datatracker.ietf.org/doc/rfc6701/</a><br>
<br>
<br>
<br>
</blockquote></div>
</div></blockquote></div></div></body></html>=

--Apple-Mail-0ED31714-03D3-4E35-9584-F3D55F009008--


--===============7285091683563203666==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZG1tIG1haWxp
bmcgbGlzdCAtLSBkbW1AaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFpbCB0byBk
bW0tbGVhdmVAaWV0Zi5vcmcK

--===============7285091683563203666==--