<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 14 (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:Courier;
panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
{font-family:Courier;
panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 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:12.0pt;
font-family:"Times New Roman","serif";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Texte de bulles Car";
margin:0cm;
margin-bottom:.0001pt;
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;}
span.TextedebullesCar
{mso-style-name:"Texte de bulles Car";
mso-style-priority:99;
mso-style-link:"Texte de bulles";
font-family:"Tahoma","sans-serif";}
p.HTMLPreformatted, li.HTMLPreformatted, div.HTMLPreformatted
{mso-style-name:"HTML Preformatted";
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Courier;}
p.BalloonText, li.BalloonText, div.BalloonText
{mso-style-name:"Balloon Text";
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Calibri","sans-serif";}
span.EmailStyle27
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle28
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle29
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle30
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle31
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></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 bgcolor="white" lang="FR" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Greg,<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"><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">OK, I will insert this point in SDLS WG agenda.<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"><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">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">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"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D">Gilles MOURY</span><span style="color:#1F497D">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D">CNES Toulouse</span><span style="color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">De :</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Kazz, Greg J (312B) [mailto:greg.j.kazz@jpl.nasa.gov]
<br>
<b>Envoyé :</b> mercredi 12 avril 2017 17:30<br>
<b>À :</b> Moury Gilles; Gian.Paolo.Calzolari@esa.int<br>
<b>Cc :</b> Daniel.Fischer@esa.int; Greenberg, Edward (312B); sls-sea-dls@mailman.ccsds.org<br>
<b>Objet :</b> Re: [Sls-sea-dls] Fw: Question regarding the SDLS EP Standard<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Gilles,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Thursday at 13:30 (after the lunch) is good.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">SLP WG is meeting in a room next to the Cafeteria (Cafeteria 3 i.e., C-3) so I recommend the two groups meet there.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">I will add it to the SLP WG agenda.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Greg<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-family:"Calibri","sans-serif";color:black">From:
</span></b><span lang="EN-US" style="font-family:"Calibri","sans-serif";color:black">Moury Gilles <<a href="mailto:Gilles.Moury@cnes.fr">Gilles.Moury@cnes.fr</a>><br>
<b>Date: </b>Wednesday, April 12, 2017 at 6:09 AM<br>
<b>To: </b>"<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>" <<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>>, Greg Kazz <<a href="mailto:greg.j.kazz@jpl.nasa.gov">greg.j.kazz@jpl.nasa.gov</a>><br>
<b>Cc: </b>"<a href="mailto:Daniel.Fischer@esa.int">Daniel.Fischer@esa.int</a>" <<a href="mailto:Daniel.Fischer@esa.int">Daniel.Fischer@esa.int</a>>, "Greenberg, Edward (312B)" <<a href="mailto:edward.greenberg@jpl.nasa.gov">edward.greenberg@jpl.nasa.gov</a>>,
"<a href="mailto:sls-sea-dls@mailman.ccsds.org">sls-sea-dls@mailman.ccsds.org</a>" <<a href="mailto:sls-sea-dls@mailman.ccsds.org">sls-sea-dls@mailman.ccsds.org</a>><br>
<b>Subject: </b>RE: [Sls-sea-dls] Fw: Question regarding the SDLS EP Standard<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">We could also schedule a 1H30 session on Thursday morning or afternoon when both SLP and SDLS WG meet.</span><span lang="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"> </span><span lang="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"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">De :</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a> [<a href="mailto:Gian.Paolo.Calzolari@esa.int">mailto:Gian.Paolo.Calzolari@esa.int</a>]
<br>
<b>Envoyé :</b> mardi 11 avril 2017 19:33<br>
<b>À :</b> Kazz, Greg J (312B)<br>
<b>Cc :</b> Moury Gilles; <a href="mailto:Daniel.Fischer@esa.int">Daniel.Fischer@esa.int</a>; Greenberg, Edward (312B);
<a href="mailto:sls-sea-dls@mailman.ccsds.org">sls-sea-dls@mailman.ccsds.org</a><br>
<b>Objet :</b> Re: [Sls-sea-dls] Fw: Question regarding the SDLS EP Standard</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">If you do that first thing on friday am somebody from sdls may be able to attend too. <br>
<br>
Sent from my iPhone<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US"><br>
On 11 Apr 2017, at 18:37, Kazz, Greg J (312B) <<a href="mailto:greg.j.kazz@jpl.nasa.gov">greg.j.kazz@jpl.nasa.gov</a>> wrote:<o:p></o:p></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">I think it is a good proposal and it is a topic we will address during the SLP WG meeting on Friday AM and perhaps also it could be discussed during the SDLS
meeting on Wed.</span><span lang="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"">However, we don’t have a SLS area joint meeting scheduled in San Antonio.
</span><span lang="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"">Perhaps we could take some time on Friday afternoon in the SLS plenary to come up with a joint way forward based upon the discussions in those other two forums.</span><span lang="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""> </span><span lang="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"">G.P. – what do you think?</span><span lang="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""> </span><span lang="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"">Thanks!</span><span lang="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"">Greg</span><span lang="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""> </span><span lang="EN-US"><o:p></o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-family:"Calibri","sans-serif";color:black">From:
</span></b><span lang="EN-US" style="font-family:"Calibri","sans-serif";color:black">Moury Gilles <<a href="mailto:Gilles.Moury@cnes.fr">Gilles.Moury@cnes.fr</a>><br>
<b>Date: </b>Tuesday, April 11, 2017 at 4:08 AM<br>
<b>To: </b>"<a href="mailto:Daniel.Fischer@esa.int">Daniel.Fischer@esa.int</a>" <<a href="mailto:Daniel.Fischer@esa.int">Daniel.Fischer@esa.int</a>>, "Greenberg, Edward (312B)" <<a href="mailto:edward.greenberg@jpl.nasa.gov">edward.greenberg@jpl.nasa.gov</a>><br>
<b>Cc: </b>Greg Kazz <<a href="mailto:greg.j.kazz@jpl.nasa.gov">greg.j.kazz@jpl.nasa.gov</a>>, "<a href="mailto:sls-sea-dls@mailman.ccsds.org">sls-sea-dls@mailman.ccsds.org</a>" <<a href="mailto:sls-sea-dls@mailman.ccsds.org">sls-sea-dls@mailman.ccsds.org</a>>,
Calzolari Gian-Paolo <<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>><br>
<b>Subject: </b>RE: [Sls-sea-dls] Fw: Question regarding the SDLS EP Standard</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Dear Ed,</span><span lang="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"> </span><span lang="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">I tend to agree with Daniel : this problem of GVCID ambiguity for bidirectional spacelinks is a general problem that will be encountered not only
by SDLS EP (for SA management procedures) but also for all bidirectional protocols like AOS, USLP for which GVCID does not carry the direction (forward or return) of the VC we are dealing with. The solution you propose to introduce 2 new IDs (GVCIDS, GVCIDR)
would solve the ambiguity but needs to be agreed SLS-wide. Greg and Gian-Paolo: what is your opinion ?</span><span lang="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"> </span><span lang="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">Best regards,</span><span lang="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"> </span><span lang="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">Gilles</span><span lang="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"> </span><span lang="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"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">De :</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<a href="mailto:Daniel.Fischer@esa.int">Daniel.Fischer@esa.int</a> [<a href="mailto:Daniel.Fischer@esa.int">mailto:Daniel.Fischer@esa.int</a>]
<br>
<b>Envoyé :</b> mardi 11 avril 2017 12:32<br>
<b>À :</b> Greenberg, Edward (312B)<br>
<b>Cc :</b> Moury Gilles; Kazz, Greg J (312B); <a href="mailto:sls-sea-dls@mailman.ccsds.org">
sls-sea-dls@mailman.ccsds.org</a><br>
<b>Objet :</b> RE: [Sls-sea-dls] Fw: Question regarding the SDLS EP Standard</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="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"">Dear Ed,</span><span lang="EN-US">
<br>
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif"">Sorry for not coming back to you earlier. I think we will discuss your recommendation in the upcoming meetings.</span><span lang="EN-US">
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif"">In my opinion the scope of the impact of the new definitions of the GVCIDR/S is not limited to SDLS or SDLS Extended Procedures and needs to be discussed in a wider frame.</span><span lang="EN-US">
<br>
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif"">Cheers,</span><span lang="EN-US">
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif"">Daniel</span><span lang="EN-US">
<br>
<br>
</span><b><span lang="EN-US" style="font-size:7.5pt;font-family:"Verdana","sans-serif";color:#00A1E0">Dr. Daniel Fischer</span></b><span lang="EN-US" style="font-size:7.5pt;font-family:"Verdana","sans-serif";color:gray"><br>
Head of the Engineering Support Section, OPS-GES<br>
Ground Systems Engineering Department</span><span lang="EN-US"> <br>
</span><span lang="EN-US" style="font-size:7.5pt;font-family:"Verdana","sans-serif";color:gray">Directorate of Operations</span><span lang="EN-US">
<o:p></o:p></span></p>
<p><b><span lang="EN-US" style="font-size:7.5pt;font-family:"Verdana","sans-serif";color:gray">ESA - ESOC</span></b><span lang="EN-US" style="font-size:7.5pt;font-family:"Verdana","sans-serif";color:gray"><br>
Robert-Bosch-Str. 5, D-64392 Darmstadt, Germany</span><span lang="EN-US"> <o:p></o:p></span></p>
<p><span lang="EN-US" style="font-size:7.5pt;font-family:"Verdana","sans-serif";color:gray">Tel. +49 6151 90 2718 | E-mail:
<a href="mailto:Daniel.Fischer@esa.int">Daniel.Fischer@esa.int</a></span><span lang="EN-US">
<br>
<br>
<br>
<br>
</span><span lang="EN-US" style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">From: </span><span lang="EN-US" style="font-size:7.5pt;font-family:"Arial","sans-serif"">"Greenberg, Edward (312B)" <<a href="mailto:edward.greenberg@jpl.nasa.gov">edward.greenberg@jpl.nasa.gov</a>></span><span lang="EN-US">
<br>
</span><span lang="EN-US" style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">To: </span><span lang="EN-US" style="font-size:7.5pt;font-family:"Arial","sans-serif"">Moury Gilles <<a href="mailto:Gilles.Moury@cnes.fr">Gilles.Moury@cnes.fr</a>>,
"<a href="mailto:Daniel.Fischer@esa.int">Daniel.Fischer@esa.int</a>" <<a href="mailto:Daniel.Fischer@esa.int">Daniel.Fischer@esa.int</a>>, "<a href="mailto:sls-sea-dls@mailman.ccsds.org">sls-sea-dls@mailman.ccsds.org</a>" <<a href="mailto:sls-sea-dls@mailman.ccsds.org">sls-sea-dls@mailman.ccsds.org</a>></span><span lang="EN-US">
<br>
</span><span lang="EN-US" style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">Cc: </span><span lang="EN-US" style="font-size:7.5pt;font-family:"Arial","sans-serif"">"Kazz, Greg J (312B)" <<a href="mailto:greg.j.kazz@jpl.nasa.gov">greg.j.kazz@jpl.nasa.gov</a>></span><span lang="EN-US">
<br>
</span><span lang="EN-US" style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">Date: </span><span lang="EN-US" style="font-size:7.5pt;font-family:"Arial","sans-serif"">11/04/2017 01:36</span><span lang="EN-US">
<br>
</span><span lang="EN-US" style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">Subject: </span><span lang="EN-US" style="font-size:7.5pt;font-family:"Arial","sans-serif"">RE: [Sls-sea-dls] Fw: Question regarding the SDLS EP Standard</span><span lang="EN-US">
<o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span lang="EN-US">
<hr size="2" width="100%" noshade="" style="color:#A0A0A0" align="center">
</span></div>
<p class="MsoNormal"><span lang="EN-US"><br>
<br>
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080">I never had a response to my recommendation. I made this recommendation for compatibility with AOS, proximity 1 and USLP since these protocols can be used in
both directions thus the PVN is not a discriminator. TM and TC have a 2 bit PVN and they are both ‘00’.
</span><span lang="EN-US"><br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080"> </span><span lang="EN-US">
<br>
</span><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Greenberg, Edward (312B)
<b><br>
Sent:</b> Friday, March 31, 2017 2:24 PM<b><br>
To:</b> 'Moury Gilles'; <a href="mailto:Daniel.Fischer@esa.int">Daniel.Fischer@esa.int</a>;
<a href="mailto:sls-sea-dls@mailman.ccsds.org">sls-sea-dls@mailman.ccsds.org</a><b><br>
Subject:</b> RE: [Sls-sea-dls] Fw: Question regarding the SDLS EP Standard</span><span lang="EN-US">
<br>
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080">The SCID identifies the Spacecraft. The SOURCE/DESTINATION FLAG identifies the sending side or the receiving side. Thus by including the SOURCE/DESTINATION
FLAG into the GVCID/GMAPID you determine the sending side GVCID verses the receiving side GVCID. By simply modifying the term GVCID to GVCIDS for the sending side and GVCIDR for the receiving side you separate the VCs by directionality which is exactly what
you want. </span><span lang="EN-US"> <br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080"> </span><span lang="EN-US">
<br>
</span><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> SLS-SEA-DLS [</span><span lang="EN-US"><a href="mailto:sls-sea-dls-bounces@mailman.ccsds.org"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">mailto:sls-sea-dls-bounces@mailman.ccsds.org</span></a></span><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">]
<b>On Behalf Of </b>Moury Gilles<b><br>
Sent:</b> Friday, March 31, 2017 2:00 AM<b><br>
To:</b> </span><span lang="EN-US"><a href="mailto:Daniel.Fischer@esa.int"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Daniel.Fischer@esa.int</span></a></span><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">;
</span><span lang="EN-US"><a href="mailto:sls-sea-dls@mailman.ccsds.org"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">sls-sea-dls@mailman.ccsds.org</span></a></span><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><br>
Subject:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Re: [Sls-sea-dls] Fw: Question regarding the SDLS EP Standard</span><span lang="EN-US">
<br>
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080">Dear all,</span><span lang="EN-US">
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080"> </span><span lang="EN-US">
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080">My response to David’s questions would be :</span><span lang="EN-US">
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080"> </span><span lang="EN-US">
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080">Q1 : values 0 and 65535 are reserved (for master keys I understand). Text should be modified.</span><span lang="EN-US">
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080"> </span><span lang="EN-US">
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080">Q2 : EP baseline mode relies on SDLS baseline mode. SDLS baseline mode uses AES-GCM. In that case, the SN is replaced by the IV which is 96 bits. Therefore,
the Set ARC procedure of the EP baseline mode is actually setting the IV. I would recommend adding this clarification in the EP baseline mode specification and changing the length of the “New anti-replay counter value” field from 64 to 96 bits for consistency
with SDLS baseline mode.</span><span lang="EN-US"> <br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080"> </span><span lang="EN-US">
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080">Q3 : My proposal would be the following:</span><span lang="EN-US">
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:Symbol;color:#004080">·
</span><span lang="EN-US" style="font-size:10.0pt;color:#004080"> </span><span lang="EN-US" style="font-size:10.0pt;font-family:Symbol;color:#004080">
</span><span lang="EN-US" style="font-size:10.0pt;color:#004080"> </span><span lang="EN-US" style="font-size:10.0pt;font-family:Symbol;color:#004080">
</span><span lang="EN-US" style="font-size:10.0pt;color:#004080"> </span><span lang="EN-US" style="font-size:10.0pt;font-family:Symbol;color:#004080">
</span><span lang="EN-US" style="font-size:10.0pt;color:#004080"> </span><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080">For the EP baseline mode, a format is specified for the GVCID/GMAPID field of the Start SA
PDU with the following sub-fields:</span><span lang="EN-US"> <br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Courier New";color:#004080">o
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080">TFVN (4 bits)</span><span lang="EN-US">
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Courier New";color:#004080">o
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080">SCID (16 bits)</span><span lang="EN-US">
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Courier New";color:#004080">o
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080">VCID (6 bits)</span><span lang="EN-US">
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Courier New";color:#004080">o
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080">MAPID (6bits)</span><span lang="EN-US">
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:Symbol;color:#004080">·
</span><span lang="EN-US" style="font-size:10.0pt;color:#004080"> </span><span lang="EN-US" style="font-size:10.0pt;font-family:Symbol;color:#004080">
</span><span lang="EN-US" style="font-size:10.0pt;color:#004080"> </span><span lang="EN-US" style="font-size:10.0pt;font-family:Symbol;color:#004080">
</span><span lang="EN-US" style="font-size:10.0pt;color:#004080"> </span><span lang="EN-US" style="font-size:10.0pt;font-family:Symbol;color:#004080">
</span><span lang="EN-US" style="font-size:10.0pt;color:#004080"> </span><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080">Since we have specified TFVN sub-field length as 4 bits, we have 2 spare bits there. We could
use one of them to distinguish TC from TM : ‘000’ would code for TC TFVN and ‘100’ would code for TM TFVN, while ‘001’ would code for AOS and ‘010’ for Prox-1 (which is not covered by SDLS by the way).</span><span lang="EN-US">
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080"> </span><span lang="EN-US">
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080">Best regards,</span><span lang="EN-US">
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080">Gilles</span><span lang="EN-US">
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080"> </span><span lang="EN-US">
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080"> </span><span lang="EN-US">
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080"> </span><span lang="EN-US">
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#004080">Gilles MOURY</span><span lang="EN-US" style="color:#004080">
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#004080"><br>
CNES Toulouse</span><span lang="EN-US" style="color:#004080"> </span><span lang="EN-US"><br>
</span><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">De :</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> SLS-SEA-DLS [</span><span lang="EN-US"><a href="mailto:sls-sea-dls-bounces@mailman.ccsds.org"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">mailto:sls-sea-dls-bounces@mailman.ccsds.org</span></a></span><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">]
<b>De la part de</b> </span><span lang="EN-US"><a href="mailto:Daniel.Fischer@esa.int"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Daniel.Fischer@esa.int</span></a></span><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><br>
Envoyé :</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> vendredi 31 mars 2017 08:57<b><br>
À :</b> </span><span lang="EN-US"><a href="mailto:sls-sea-dls@mailman.ccsds.org"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">sls-sea-dls@mailman.ccsds.org</span></a></span><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><br>
Objet :</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> [Sls-sea-dls] Fw: Question regarding the SDLS EP Standard</span><span lang="EN-US">
<br>
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif"">Dear all,</span><span lang="EN-US">
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
Could ask you to take a look at the questions that David sent a while go...some of them need answers before a red book can be produced.</span><span lang="EN-US">
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
My take:</span><span lang="EN-US"> </span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
Q1 is a typo and will be corrected. --> No further discussion needed</span><span lang="EN-US">
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
Q2: This should be the case. What do the others think? Do we need to be explicit there?</span><span lang="EN-US">
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
Q3: This is a critical one and we don't have an answer at the moment. I remember we discussed this in the WG already but I am not sure we came to a conclusion. This needs to be clarified in the standard. Any opinions?</span><span lang="EN-US">
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
Cheers,<br>
Daniel.</span><span lang="EN-US"> <br>
</span><b><span lang="EN-US" style="font-size:7.5pt;font-family:"Verdana","sans-serif";color:#00A1E0"><br>
Dr. Daniel Fischer</span></b><span lang="EN-US" style="font-size:7.5pt;font-family:"Verdana","sans-serif";color:gray"><br>
Head of the Engineering Support Section, OPS-GES<br>
Ground Systems Engineering Department</span><span lang="EN-US"> </span><span lang="EN-US" style="font-size:7.5pt;font-family:"Verdana","sans-serif";color:gray"><br>
Directorate of Operations</span><span lang="EN-US"> <o:p></o:p></span></p>
<p><b><span lang="EN-US" style="font-size:7.5pt;font-family:"Verdana","sans-serif";color:gray">ESA - ESOC</span></b><span lang="EN-US" style="font-size:7.5pt;font-family:"Verdana","sans-serif";color:gray"><br>
Robert-Bosch-Str. 5, D-64392 Darmstadt, Germany</span><span lang="EN-US"> <o:p></o:p></span></p>
<p><span lang="EN-US" style="font-size:7.5pt;font-family:"Verdana","sans-serif";color:gray">Tel. +49 6151 90 2718 | E-mail:
</span><span lang="EN-US"><a href="mailto:Daniel.Fischer@esa.int"><span style="font-size:7.5pt;font-family:"Verdana","sans-serif"">Daniel.Fischer@esa.int</span></a>
</span><span lang="EN-US" style="font-size:7.5pt;font-family:"Arial","sans-serif";color:purple"><br>
----- Forwarded by Daniel Fischer/esoc/ESA on 31/03/2017 08:51 -----</span><span lang="EN-US">
<br>
</span><span lang="EN-US" style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F"><br>
From: </span><span lang="EN-US"><a href="mailto:David.Koisser@esa.int"><span style="font-size:7.5pt;font-family:"Arial","sans-serif"">David.Koisser@esa.int</span></a>
</span><span lang="EN-US" style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F"><br>
To: </span><span lang="EN-US"><a href="mailto:sls-sea-dls@mailman.ccsds.org"><span style="font-size:7.5pt;font-family:"Arial","sans-serif"">sls-sea-dls@mailman.ccsds.org</span></a>
</span><span lang="EN-US" style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F"><br>
Cc: </span><span lang="EN-US" style="font-size:7.5pt;font-family:"Arial","sans-serif"">"John P. Lucas" <</span><span lang="EN-US"><a href="mailto:John.P.Lucas@ivv.nasa.gov"><span style="font-size:7.5pt;font-family:"Arial","sans-serif"">John.P.Lucas@ivv.nasa.gov</span></a></span><span lang="EN-US" style="font-size:7.5pt;font-family:"Arial","sans-serif"">></span><span lang="EN-US">
</span><span lang="EN-US" style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F"><br>
Date: </span><span lang="EN-US" style="font-size:7.5pt;font-family:"Arial","sans-serif"">01/03/2017 11:04</span><span lang="EN-US">
</span><span lang="EN-US" style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F"><br>
Subject: </span><span lang="EN-US" style="font-size:7.5pt;font-family:"Arial","sans-serif"">[Sls-sea-dls] Question regarding the SDLS EP Standard</span><span lang="EN-US">
</span><span lang="EN-US" style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F"><br>
Sent by: </span><span lang="EN-US" style="font-size:7.5pt;font-family:"Arial","sans-serif"">"SLS-SEA-DLS" <</span><span lang="EN-US"><a href="mailto:sls-sea-dls-bounces@mailman.ccsds.org"><span style="font-size:7.5pt;font-family:"Arial","sans-serif"">sls-sea-dls-bounces@mailman.ccsds.org</span></a></span><span lang="EN-US" style="font-size:7.5pt;font-family:"Arial","sans-serif"">></span><span lang="EN-US">
<o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span lang="EN-US">
<hr size="2" width="100%" noshade="" style="color:#A0A0A0" align="center">
</span></div>
<p class="MsoNormal"><span lang="EN-US"><br>
<br>
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif""><br>
Dear SDLS WG members,</span><span lang="EN-US"> </span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
<br>
John and I have completed setting up the interoperability testing environment and now we are doing a few finishing touches. Whilst doing this a few questions arose regarding the SDLS EP standard:</span><span lang="EN-US">
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
<br>
1. In Section E4.2.2 (in the baseline mode description of Key Activation) and the following key procedures, it defines the Key ID fields to have a length of 16 bits. And then states:</span><span lang="EN-US">
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
"Values 0-65535 shall not be used to reference session keys."</span><span lang="EN-US">
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
Which would be all possible Key IDs and leave none for any session keys. Can you clarify?</span><span lang="EN-US">
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
<br>
2. While we are fairly sure it is implied: Does the M&C procedure Set ARC set the IV instead of the SN parameter in the regarding cases (e.g. AES-GCM)?</span><span lang="EN-US">
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
<br>
3. The standard is not addressing how to distinguish if a GVCID is regarding the TM or TC channels for the Start SA procedure. An example to clarify:
<br>
<br>
A mission wants a different SA assigned on VC 0 for the uplink (e.g. authentication only) than the VC 0 for the downlink (e.g. authenticated encryption). To be able to set this with the Start SA procedure, it needs a way to distinguish between the TC and TM
channel mapping to SPIs. As the GVCID is defined as:</span><span lang="EN-US"> </span>
<span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
GVCID = TFVN + SCID + VCID</span><span lang="EN-US"> </span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
And the 2 bits long TFVN may have the following values: 01 -> AOS; 10 -> Proximity-1; 00 -> TM- *or* TC-SDLP</span><span lang="EN-US">
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
The GVCID alone is not enough to distinguish between TC and TM and we are currently using a custom data structure for unambiguously identifying the channels in the Start SA procedure.</span><span lang="EN-US">
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
<br>
Best Regards,</span><span lang="EN-US"> </span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
David Koisser</span><span lang="EN-US"> </span><span lang="EN-US" style="font-size:10.0pt;font-family:"Courier New""><br>
This message and any attachments are intended for the use of the addressee or addressees only.<br>
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<br>
content is not permitted.<br>
If you received this message in error, please notify the sender and delete it from your system.<br>
Emails can be altered and their integrity cannot be guaranteed by the sender.</span><span lang="EN-US" style="font-family:"Courier New""><br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Courier New""><br>
Please consider the environment before printing this email.</span><span lang="EN-US" style="font-family:"Courier New""><br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Courier New""><br>
_______________________________________________<br>
SLS-SEA-DLS mailing list<u><span style="color:blue"><br>
</span></u></span><span lang="EN-US"><a href="mailto:SLS-SEA-DLS@mailman.ccsds.org"><span style="font-size:10.0pt;font-family:"Courier New"">SLS-SEA-DLS@mailman.ccsds.org</span></a><u><span style="color:blue"><br>
</span></u><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-sea-dls"><span style="font-size:10.0pt;font-family:"Courier New"">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-sea-dls</span></a><br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
</span><span lang="EN-US"><br>
<br>
</span><b><i><span lang="EN-US" style="font-size:7.5pt;font-family:"Arial","sans-serif";color:gray"><br>
Disclaimer</span></i></b><span lang="EN-US"> </span><i><span lang="EN-US" style="font-size:7.5pt;font-family:"Arial","sans-serif";color:gray"><br>
This message and any attachments are intended for the use of the addressee or addressees only. The unauthorized disclosure, use, dissemination or copying (either in whole or in part) of its content is not permitted. If you received this message in error, please
notify the sender and delete it from your system. Emails can be altered and their integrity cannot be guaranteed by the sender. Please consider the environment before printing this email.</span></i><span lang="EN-US">
<o:p></o:p></span></p>
<p style="margin-bottom:12.0pt"><tt><span lang="EN-US" style="font-size:10.0pt">This message and any attachments are intended for the use of the addressee or addressees only.</span></tt><span lang="EN-US" style="font-family:"Courier New""><br>
</span><tt><span lang="EN-US" style="font-size:10.0pt">The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its</span></tt><span lang="EN-US" style="font-family:"Courier New""><br>
</span><tt><span lang="EN-US" style="font-size:10.0pt">content is not permitted.</span></tt><span lang="EN-US" style="font-family:"Courier New""><br>
</span><tt><span lang="EN-US" style="font-size:10.0pt">If you received this message in error, please notify the sender and delete it from your system.</span></tt><span lang="EN-US" style="font-family:"Courier New""><br>
</span><tt><span lang="EN-US" style="font-size:10.0pt">Emails can be altered and their integrity cannot be guaranteed by the sender.</span></tt><span lang="EN-US" style="font-family:"Courier New""><br>
<br>
</span><tt><span lang="EN-US" style="font-size:10.0pt">Please consider the environment before printing this email.</span></tt><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
</span><span lang="EN-US"><br>
<br>
</span><b><i><span lang="EN-US" style="font-size:7.5pt;font-family:"Arial","sans-serif";color:gray">Disclaimer</span></i></b><span lang="EN-US">
<br>
</span><i><span lang="EN-US" style="font-size:7.5pt;font-family:"Arial","sans-serif";color:gray">This message and any attachments are intended for the use of the addressee or addressees only. The unauthorized disclosure, use, dissemination or copying (either
in whole or in part) of its content is not permitted. If you received this message in error, please notify the sender and delete it from your system. Emails can be altered and their integrity cannot be guaranteed by the sender. Please consider the environment
before printing this email.</span></i><span lang="EN-US"><o:p></o:p></span></p>
</div>
</blockquote>
<pre><span lang="EN-US" style="font-size:10.0pt;font-family:"Courier New"">This message and any attachments are intended for the use of the addressee or addressees only.<o:p></o:p></span></pre>
<pre><span lang="EN-US" style="font-size:10.0pt;font-family:"Courier New"">The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<o:p></o:p></span></pre>
<pre><span lang="EN-US" style="font-size:10.0pt;font-family:"Courier New"">content is not permitted.<o:p></o:p></span></pre>
<pre><span lang="EN-US" style="font-size:10.0pt;font-family:"Courier New"">If you received this message in error, please notify the sender and delete it from your system.<o:p></o:p></span></pre>
<pre><span lang="EN-US" style="font-size:10.0pt;font-family:"Courier New"">Emails can be altered and their integrity cannot be guaranteed by the sender.<o:p></o:p></span></pre>
<pre><span lang="EN-US" style="font-size:10.0pt;font-family:"Courier New""> <o:p></o:p></span></pre>
<pre><span lang="EN-US" style="font-size:10.0pt;font-family:"Courier New"">Please consider the environment before printing this email.<o:p></o:p></span></pre>
<pre><span lang="EN-US" style="font-size:10.0pt;font-family:"Courier New""> <o:p></o:p></span></pre>
</div>
</body>
</html>