<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@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:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
pre
{mso-style-priority:99;
mso-style-link:"Préformaté HTML Car";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.PrformatHTMLCar
{mso-style-name:"Préformaté HTML Car";
mso-style-priority:99;
mso-style-link:"Préformaté HTML";
font-family:Consolas;
mso-fareast-language:FR;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:896937647;
mso-list-type:hybrid;
mso-list-template-ids:2015496918 -1538092828 67895299 67895301 67895297 67895299 67895301 67895297 67895299 67895301;}
@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:-18.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-font-family:Calibri;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
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:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
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:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="FR" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Dear Greg,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Regarding PID1 :<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><![if !supportLists]><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">The incompatibility of VCF and MCF services with Insert service is specified in 2.2.4 and in the new requirement
3.2.6. Justification for this restriction is rather straightforward since MCF and VCF services users provide complete Transfer Frames preventing periodic transmission of insert SDUs at frame rate. Note 2 of 3.2.6 already points to that justification.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Regarding PID 2 :<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><![if !supportLists]><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">CNES does not use the term “port” in TC.. Removing this undefined term in the recommendation is desirable.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Gilles<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D">Gilles MOURY</span><span lang="EN-US" style="color:#1F497D">
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D">CNES Toulouse</span><span lang="EN-US" style="color:#1F497D">
</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">De :</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> SLS-SLP <sls-slp-bounces@mailman.ccsds.org>
<b>De la part de</b> Marco.Rovatti@esa.int<br>
<b>Envoyé :</b> me</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">rcredi 10 février 2021 12:30<br>
<b>À :</b> Kazz, Greg J(US 312B) <greg.j.kazz@jpl.nasa.gov><br>
<b>Cc :</b> Kazz, Greg J (US 312B) via SLS-SLP <sls-slp@mailman.ccsds.org><br>
<b>Objet :</b> Re: [Sls-slp] PIDs concerning AOS & TC SDLP Pink Sheets<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Dear Greg,
</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Regarding <b><u>Proposed PID 1:</u></b></span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The restriction is also stated in para 2.2.4
</span><br>
<br>
<img width="787" height="355" style="width:8.2013in;height:3.7013in" id="_x0000_i1025" src="cid:image001.gif@01D6FFC3.8FA3CA70"><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I think your explanation is correct. The Insert Zone Service was thought to carry small chunks of fixed length user data in each Transfer Frame transmitted on the Physical Channel in order to provide
a low latency, "high priority", synchronous service. </span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">In the presence of Master Channel Service or Virtual Channel Service, this goal cannot be achieved because the sequence of Insert Zone SDUs would eventually present gaps which are incompatible with
the intended purpose of the service. </span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">However the above is true if we assume that the users of MCF or VCF Services do not include a blank place holder in their TFs to accommodate an Insert Zone SDU.
</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">In principle the above restriction might be removed if the user of MCF or VCF Servicea are constrained to provide a Transfer Frame format compliant with the presence of the insert zone.
</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Open for discussion.
</span><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Regarding <b><u>Proposed PID 2</u></b></span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I concur with the explanation you provided. Port is used as a synonym of SAP. No ESA on-board implementation is broken by the removal of the term from the standard. I expect that also Ground implementation
are not affected but maybe Gippo knows better. </span><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Best regards</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Marco</span> <br>
<br>
<br>
<br>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">From: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Kazz, Greg J\(US 312B\) via SLS-SLP" <<a href="mailto:sls-slp@mailman.ccsds.org">sls-slp@mailman.ccsds.org</a>></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">To: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Kazz, Greg J (US 312B) via SLS-SLP" <<a href="mailto:sls-slp@mailman.ccsds.org">sls-slp@mailman.ccsds.org</a>></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">10/02/2021 00:29</span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Subject: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">[Sls-slp] PIDs concerning AOS & TC SDLP Pink Sheets</span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Sent by: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"SLS-SLP" <<a href="mailto:sls-slp-bounces@mailman.ccsds.org">sls-slp-bounces@mailman.ccsds.org</a>></span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="3" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">Dear SLP WG,</span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">I was informed by Peter Shames, SEA Area Director, that he is considering generating two PIDs (Area Director Level) one for the attached AOS (732.0) and one for the TC
(232.0) SDLP pink sheets.</span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">My purpose of this email is to see if we (SLP WG) can come up with adequate changes to the text in question or provide adequate rationale for these specific pink sheet
changes for example in the NOTE section of the documents.</span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><u><span style="font-family:"Calibri",sans-serif">Proposed PID 1: AOS Section 3.2.6 AOS Transfer Frame – why exclude the Insert Zone under the condition ?</span></u><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">FROM: 3.2.6<i>.</i> “ The following restriction apply to AOS Transfer Frames: if at least a Virtual Channel Frame or a Master Channel Frame service exists, all AOS Transfer
Frames on the Physical Channel shall not include the Transfer Frame Insert Zone.”</span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">TO: ?</span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">The issue the PID brings up, is “what is the rationale for this restriction ?” Why can’t the physical channel contain an Insert Zone under this condition ? Provide the
rationale in the document, in order to avoid confusing the user.</span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">I believe the rationale has to do with the fact, that if a service user subscribes to either the VCF or the MCF service, then that user provides either complete Master
Channel Frames or complete Virtual Channel Frames to the service provider. However, in those cases, there is an ambiguity concerning the use of the Insert Zone service by that user. The protocol only allows for one use of the Insert Zone service on the Physical
Channel. Therefore to avoid any ambiguity, under this condition, there cannot be an Insert Zone.</span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">If I am incorrect, please let me know.</span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">So in order to address the PID, we could either modify 3.2.6 or provide clarification in the NOTE below it.
</span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">Your suggestions are welcome.</span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><u><span style="font-family:"Calibri",sans-serif">Proposed PID 2: TC SDLP Section 2.2.1 (and reoccurring) – removal of the term, “ports”</span></u><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">Issue: Why was the term, “ports” removed throughout the document ? By removing it from the document, does it break any implementations?</span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">I noticed that the term “port” is not defined in both the 2003 as well as the current version of 232.0. I believe the SLP WG removed the term, “port(s)” because it was
undefined and was not connected to the TC SDLP. In other words, “port(s)” was just a notional term, but never part of the actual TC SDLP. The only question remaining in the PID is “does it break any existing agency implementation, if that term is removed from
the protocol” ? </span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">I would like the SLP WG to weigh in on that question. I am not aware of any implementation issues from the NASA side.</span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">Please try and respond back to me by the end of this week i.e., no later than Feb. 12.</span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">Best regards,</span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Greg Kazz</span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Principal Engineer</span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Technical Group Supervisor,</span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">PSSE/EEISE/PPSE (312B)</span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Jet Propulsion Laboratory</span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">4800 Oak Grove Dr., M/S 301-490</span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Pasadena, CA 91109</span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">1+(818)393 6529(voice)</span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">1+(818)393 6871(fax)</span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">email:
<a href="mailto:greg.j.kazz@jpl.nasa.gov">greg.j.kazz@jpl.nasa.gov</a> </span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> [attachment "732x0p30_CESG_Approval.pdf" deleted by Marco Rovatti/estec/ESA] [attachment "232x0b3_CESG_Approval.pdf" deleted by Marco Rovatti/estec/ESA]
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<tt><span style="font-size:10.0pt">_______________________________________________</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<tt>SLS-SLP mailing list</tt><br>
<tt><a href="mailto:SLS-SLP@mailman.ccsds.org">SLS-SLP@mailman.ccsds.org</a></tt><br>
</span><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-slp"><tt><span style="font-size:10.0pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-slp</span></tt></a><span style="font-size:10.0pt;font-family:"Courier New""><br>
<br>
</span><o:p></o:p></p>
<pre>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre>
<pre>protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre>
<pre>this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre>
<pre>personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (<a href="mailto:dpo@esa.int">dpo@esa.int</a>).<o:p></o:p></pre>
</div>
</body>
</html>