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

--===============3901380342253384356==
Content-Type: multipart/alternative; boundary="000000000000b612ae06424f5fbc"

--000000000000b612ae06424f5fbc
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Support as co-author.

I don't have knowledge of any other IPRs related to this work other than
what's been disclosed already.

--
Uma C.

On Thu, Oct 16, 2025 at 5:09=E2=80=AFAM 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/
>
>
>
>

--000000000000b612ae06424f5fbc
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Support as co-author.<div><br></div><div>I don&#39;t have =
knowledge of any other IPRs related to this work other than what&#39;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 dir=3D"ltr" =
class=3D"gmail_attr">On Thu, Oct 16, 2025 at 5:09=E2=80=AFAM Satoru Matsush=
ima via Datatracker &lt;<a href=3D"mailto:[email protected]">[email protected]=
g</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-left: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>
=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&#39;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 &quot;at=
tachment<br>
=C2=A0 =C2=A0circuit&quot; 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/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/d=
raft-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"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/" rel=3D"noreferrer" =
target=3D"_blank">https://datatracker.ietf.org/doc/bcp78/</a><br>
[2] <a href=3D"https://datatracker.ietf.org/doc/bcp79/" rel=3D"noreferrer" =
target=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>

--000000000000b612ae06424f5fbc--


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

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZG1tIG1haWxp
bmcgbGlzdCAtLSBkbW1AaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFpbCB0byBk
bW0tbGVhdmVAaWV0Zi5vcmcK

--===============3901380342253384356==--