[DMM] draft-liebsch-dmm-mts-03 review
Kaippallimalil John <[email protected]> Mon, 22 Sep 2025 13:10:49 +0000
| Newsgroups | gmane.ietf.nemo |
|---|---|
| Message-ID | <SN4PR13MB53117D58262D3BC6F7CB0EC1E812A__42953.9525228151$1758546674$gmane$org@SN4PR13MB5311.namprd13.prod.outlook.com> |
--===============0533823547919493819==
Content-Language: en-US
Content-Type: multipart/alternative;
boundary="_000_SN4PR13MB53117D58262D3BC6F7CB0EC1E812ASN4PR13MB5311namp_"
--_000_SN4PR13MB53117D58262D3BC6F7CB0EC1E812ASN4PR13MB5311namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hi Marco, All,
The draft identifies a gap/problem in 5G systems and the need to (re)select=
and steer flows.
This draft can provide value and insight into a complex area. There are gap=
s currently as 5G/3GPP does not fully cover the N6/IP segments of the E2E p=
ath.
However, the draft describes too much of existing/standards (using differen=
t names and terms), and it is not easy for a reader to distinguish the gaps=
from already specified standards.
A couple of suggestions:
1. Since the architecture in section 4 is 5G, why not use the same termi=
nology/refer to TS 23.501. And add concepts that are new.
This will make the text shorter and allow readers to see clearly what the g=
aps are. For example, what part of the architecture in Figure 4 is covered =
in 23.501, and what isn't (same for many others).
2. Regarding the gaps, there are architectural principles and options in=
section 5 + but the draft does not outline the tradeoffs or say when one o=
ption is preferrable over the other.
For example: if services/network require to only maximize bandwidth utiliza=
tion vs. guarantees on latency/bandwidth. And, resilience, complexity (e.g=
., O(n^2) vs O (n), scalability, etc.
Another aspect is the relation between this draft and CATS. Where are they =
complementary, or an alternative and the rationale for choosing among these=
methods of steering.
Some detailed comments:
1. Abstract & section 4.1 refer to "two architectural principles" but is=
not clarified what it is until much later.
The reader must read until section 5 to understand what it is about steerin=
g. It should be stated much earlier and described later for easier reading.
2. Section 2 / Introduction: discusses " how existing or new IETF techno=
logy can serve as enabler to accomplish service continuity for a mobile use=
r in such agile and dynamic system by means of controlled treatment of a mo=
bile user's end-to-end traffic for steering, with an option to extend for a=
dvanced treatment policies, such as traffic engineering."
Many concepts, and options make it hard to follow:
(1) the scope has steering and "advanced treatment policies", and steering =
policies. What exactly are the differences?
(2) does advanced treatment policies refer to QoS aspects?
(3) steering and service continuity: does user mobility trigger steering, o=
r does measurement on path trigger steering, or both?
(4) The draft has many terms like "flexible deployment", dynamic re-configu=
rability, complexity which can be understood in different ways.
3. Section 4.2. MCS Proactive UPA relocation : "proactive" is a bit conf=
using and depends on perspective.
(1) "Due to mobility, the MCS may relocate the mobile user's UPA from UPA1 =
to UPA2": that would seem more reactive?
(2) "In case the user's IP address needs to continue only as long as the da=
ta session with ASF1 takes .." How does UPA know how long the session lasts=
?
4. Section 4.2 "In order to keep routing paths short and latency low, th=
e ASF may be relocated from ASF1 to ASF2". How does ASF /data network know =
how to do this?
Does MCS proactively relocate the UPA (UPA1 -> UPA2) based on some measurem=
ents of the path UPA1 - ASF1 and expect to have better performance after th=
e move UPA2 -> ASF1?
1. Section 4.4: "A MCS provide may deploy distributed UPAs in order to s=
horten the route and resulting latency for the communication between two mo=
bile users"
Why is there a need to move UPA for shorter paths? Isn't it possible to hav=
e a routed network (with DPNs) that select the shortest/lower latency path =
etc.
The problem seems to be that the UPA is not distributed enough (that one ha=
s to move from UPA1 -> UPA2 to get a shorter path to UPA3)
2. Section 5:/ deployment options. Between the different options what is=
the trade-off in terms of scale and complexity (of provisioning/maintainin=
g the paths)
See overall comments also.
Best Regards,
John
--_000_SN4PR13MB53117D58262D3BC6F7CB0EC1E812ASN4PR13MB5311namp_
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:Aptos;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Aptos",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.EmailStyle21
{mso-style-type:personal-compose;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@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:99640765;
mso-list-type:hybrid;
mso-list-template-ids:-971591752 1631364954 67698691 67698693 67698689 676=
98691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:0;
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;}
@list l1
{mso-list-id:122388277;
mso-list-type:hybrid;
mso-list-template-ids:2102457978 -2138150170 67698691 67698693 67698689 67=
698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-start-at:4;
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 l1: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 l1: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 l1: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 l1: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 l1: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 l1: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 l1: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 l1: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;}
@list l2
{mso-list-id:251864717;
mso-list-template-ids:-1304905460;}
@list l2:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level2
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level3
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level5
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level6
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level8
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level9
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3
{mso-list-id:437142097;
mso-list-template-ids:-925482796;}
@list l4
{mso-list-id:509108239;
mso-list-type:hybrid;
mso-list-template-ids:-474594134 67698703 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l4:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l4:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l4:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l5
{mso-list-id:1792429955;
mso-list-type:hybrid;
mso-list-template-ids:2000321596 67698703 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l5:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l5:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l5:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l6
{mso-list-id:1883058533;
mso-list-type:hybrid;
mso-list-template-ids:-1095222864 67698711 -1 -1 -1 -1 -1 -1 -1 -1;}
@list l6:level1
{mso-level-number-format:alpha-lower;
mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6: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 l6: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 l6: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 l6: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 l6: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 l6: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 l6: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 l6: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 Marco, All,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">The draft identifies a gap/problem in 5G systems and=
the need to (re)select and steer flows.<o:p></o:p></p>
<p class=3D"MsoNormal">This draft can provide value and insight into a comp=
lex area. There are gaps currently as 5G/3GPP does not fully cover the N6/I=
P segments of the E2E path.<br>
<br>
<o:p></o:p></p>
<p class=3D"MsoNormal">However, the draft describes too much of existing/st=
andards (using different names and terms), and it is not easy for a reader =
to distinguish the gaps from already specified standards.<o:p></o:p></p>
<p class=3D"MsoNormal">A couple of suggestions:<o:p></o:p></p>
<ol style=3D"margin-top:0in" start=3D"1" type=3D"1">
<li class=3D"MsoListParagraph" style=3D"margin-left:0in;mso-list:l4 level1 =
lfo8">Since the architecture in section 4 is 5G, why not use the same termi=
nology/refer to TS 23.501. And add concepts that are new.<br>
This will make the text shorter and allow readers to see clearly what the g=
aps are. For example, what part of the architecture in Figure 4 is covered =
in 23.501, and what isn’t (same for many others).<br>
<br>
<o:p></o:p></li><li class=3D"MsoListParagraph" style=3D"margin-left:0in;mso=
-list:l4 level1 lfo8">Regarding the gaps, there are architectural principle=
s and options in section 5 + but the draft does not outline the tradeoffs o=
r say when one option is preferrable over the other.
<br>
For example: if services/network require to only maximize bandwidth utiliza=
tion vs. guarantees on latency/bandwidth. And, resilience, complexity  =
;(e.g., O(n^2) vs O (n), scalability, etc.<br>
Another aspect is the relation between this draft and CATS. Where are they =
complementary, or an alternative and the rationale for choosing among these=
methods of steering.<o:p></o:p></li></ol>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">Some detailed comments:<o:p></o:p></p>
<ol style=3D"margin-top:0in" start=3D"1" type=3D"a">
<li class=3D"MsoListParagraph" style=3D"margin-left:0in;mso-list:l6 level1 =
lfo9">Abstract & section 4.1 refer to “<span style=3D"font-family=
:"Courier New"">two architectural principles</span>” but is=
not clarified what it is until much later.
<br>
The reader must read until section 5 to understand what it is about steerin=
g. It should be stated much earlier and described later for easier reading.=
<br>
<br>
<o:p></o:p></li><li class=3D"MsoListParagraph" style=3D"margin-left:0in;mso=
-list:l6 level1 lfo9">Section 2 / Introduction: discusses “ how exist=
ing or new IETF technology can serve as enabler to accomplish service conti=
nuity for a mobile user in such agile and dynamic system by
means of controlled treatment of a mobile user's end-to-end traffic for st=
eering, with an option to extend for advanced treatment policies, such as t=
raffic engineering.”<br>
Many concepts, and options make it hard to follow:<br>
(1) the scope has steering and “advanced treatment policies”, a=
nd steering policies. What exactly are the differences?
<br>
(2) does advanced treatment policies refer to QoS aspects?<br>
(3) steering and service continuity: does user mobility trigger steering, o=
r does measurement on path trigger steering, or both?<br>
(4) The draft has many terms like “flexible deployment”, dynami=
c re-configurability, complexity which can be understood in different ways.=
<br>
<br>
<o:p></o:p></li><li class=3D"MsoListParagraph" style=3D"margin-left:0in;mso=
-list:l6 level1 lfo9">Section 4.2. MCS Proactive UPA relocation : “pr=
oactive” is a bit confusing and depends on perspective.
<br>
(1) “Due to mobility, the MCS may relocate the mobile user's UPA from=
UPA1 to UPA2”: that would seem more reactive?
<br>
(2) “In case the user's IP address needs to continue only as long as =
the data session with ASF1 takes ..” How does UPA know how long the s=
ession lasts?
<br>
<br>
<o:p></o:p></li><li class=3D"MsoListParagraph" style=3D"margin-left:0in;mso=
-list:l6 level1 lfo9">Section 4.2 “In order to keep routing paths sho=
rt and latency low, the ASF may be relocated from ASF1 to ASF2”. How =
does ASF /data network know how to do this?<br>
Does MCS proactively relocate the UPA (UPA1 -> UPA2) based on some measu=
rements of the path UPA1 – ASF1 and expect to have better performance=
after the move UPA2 -> ASF1?<o:p></o:p></li></ol>
<p class=3D"MsoListParagraph"><o:p> </o:p></p>
<ol style=3D"margin-top:0in" start=3D"5" type=3D"a">
<li class=3D"MsoListParagraph" style=3D"margin-left:0in;mso-list:l6 level1 =
lfo9">Section 4.4: “A MCS provide may deploy distributed UPAs in orde=
r to shorten the route and resulting latency for the communication between =
two mobile users”<br>
Why is there a need to move UPA for shorter paths? Isn’t it possible =
to have a routed network (with DPNs) that select the shortest/lower latency=
path etc.<br>
The problem seems to be that the UPA is not distributed enough (that one ha=
s to move from UPA1 -> UPA2 to get a shorter path to UPA3)<br>
<br>
<o:p></o:p></li><li class=3D"MsoListParagraph" style=3D"margin-left:0in;mso=
-list:l6 level1 lfo9">Section 5:/ deployment options. Between the different=
options what is the trade-off in terms of scale and complexity (of provisi=
oning/maintaining the paths)<br>
See overall comments also.<br>
<br>
<o:p></o:p></li></ol>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">John<o:p></o:p></p>
</div>
</body>
</html>
--_000_SN4PR13MB53117D58262D3BC6F7CB0EC1E812ASN4PR13MB5311namp_--
--===============0533823547919493819==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZG1tIG1haWxp
bmcgbGlzdCAtLSBkbW1AaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFpbCB0byBk
bW0tbGVhdmVAaWV0Zi5vcmcK
--===============0533823547919493819==--