<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<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:"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:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
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;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma",sans-serif;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
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:Consolas;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Segoe UI",sans-serif;}
p.msochpdefault, li.msochpdefault, div.msochpdefault
{mso-style-name:msochpdefault;
mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
p.PrformatHTML, li.PrformatHTML, div.PrformatHTML
{mso-style-name:"Préformaté HTML";
mso-style-link:"Préformaté HTML Car";
margin:0in;
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.prformathtmlcar0
{mso-style-name:prformathtmlcar;
font-family:Consolas;}
span.emailstyle19
{mso-style-name:emailstyle19;
font-family:"Calibri",sans-serif;
color:#1F497D;}
p.Textedebulles, li.Textedebulles, div.Textedebulles
{mso-style-name:"Texte de bulles";
mso-style-link:"Texte de bulles Car";
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.TextedebullesCar
{mso-style-name:"Texte de bulles Car";
mso-style-priority:99;
mso-style-link:"Texte de bulles";
font-family:"Tahoma",sans-serif;}
span.EmailStyle30
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
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:8.5in 11.0in;
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 lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Bruno’s proposal is a good technical solution by itself, but I have concerns about introducing additional requirements into ground crypto systems for generation
and storage of meta-keys.<o:p></o:p></span></p>
<p class="MsoNormal"><span 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:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The CRC may not itself be a critical security parameter in the FIPS 140 sense (I think it is not, but I defer to others’ judgment in this), but generation of
the CRC requires access to critical security parameters, both the Key ID and the actual key itself. So CRC generation would have to be performed within a validated crypto system, even if it were permissible to transmit and store the CRC outside the crypto
system.<o:p></o:p></span></p>
<p class="MsoNormal"><span 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:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">If Bruno’s proposal were adopted as-is, it appears unlikely to me that any generic, commercially-available crypto systems could satisfy the requirement. For
flight systems, this may not be an issue since flight implementations tend to be custom by their very nature. On the other hand, ground systems that otherwise might be able to integrate commercially-available crypto systems would be forced into procuring
custom implementations requiring e.g. FIPS 140 validation along with its additional time and expense.<o:p></o:p></span></p>
<p class="MsoNormal"><span 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:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span 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:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Craig<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> sls-sea-dls-bounces@mailman.ccsds.org [mailto:sls-sea-dls-bounces@mailman.ccsds.org]
<b>On Behalf Of </b>Moury Gilles<br>
<b>Sent:</b> Tuesday, April 19, 2016 3:46 AM<br>
<b>To:</b> Weiss, Howard <Howard.Weiss@parsons.com>; Saba Bruno <Bruno.Saba@cnes.fr>; Daniel.Fischer@esa.int; sls-sea-dls@mailman.ccsds.org<br>
<b>Subject:</b> RE: [Sls-sea-dls] Key Verification using CRC<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Shall we adopt Bruno’s proposal ? In that case, we probably do not need the challenge-response transaction.<o:p></o:p></span></p>
<p class="MsoNormal"><span 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:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Gilles<o:p></o:p></span></p>
<p class="MsoNormal"><span 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 0in 0in 0in">
<p class="MsoNormal"><b><span lang="FR" style="font-size:10.0pt;font-family:"Tahoma",sans-serif">De :</span></b><span lang="FR" style="font-size:10.0pt;font-family:"Tahoma",sans-serif">
<a href="mailto:sls-sea-dls-bounces@mailman.ccsds.org">sls-sea-dls-bounces@mailman.ccsds.org</a> [<a href="mailto:sls-sea-dls-bounces@mailman.ccsds.org">mailto:sls-sea-dls-bounces@mailman.ccsds.org</a>]
<b>De la part de</b> Weiss, Howard<br>
<b>Envoyé :</b> lundi 18 avril 2016 19:27<br>
<b>À :</b> Saba Bruno; <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><br>
<b>Objet :</b> RE: [Sls-sea-dls] Key Verification using CRC<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="FR"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span lang="FR" style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black">I agree with Bruno.<br>
<br>
Howie<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="FR" style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black"><o:p> </o:p></span></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span lang="FR" style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black"><o:p> </o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span lang="FR" style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black">
<hr size="2" width="100%" align="center">
</span></div>
<p class="MsoNormal"><b><span lang="FR" style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black">Howard Weiss</span></b><span lang="FR" style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black"><br>
</span><span lang="FR" style="font-size:7.5pt;font-family:"Tahoma",sans-serif;color:black">Technical Director</span><span lang="FR" style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black"><br>
<br>
<b>PARSONS</b></span><span lang="FR" style="font-size:7.5pt;font-family:"Tahoma",sans-serif;color:black"><br>
7110 Samuel Morse Drive<br>
Columbia, MD 21046<br>
443-430-8089 (office)<br>
410-262-1479 (cell)<br>
443-430-8238 (fax)<br>
<a href="mailto:howard.weiss@parsons.com">howard.weiss@parsons.com</a><br>
<a href="http://www.parsons.com">www.parsons.com</a><br>
<br>
</span><span lang="FR" style="font-size:7.5pt;font-family:"Tahoma",sans-serif;color:#339966">Please consider the environment before printing this message</span><span lang="FR" style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<div>
<div class="MsoNormal" align="center" style="text-align:center"><span lang="FR" style="color:black">
<hr size="2" width="100%" align="center">
</span></div>
<div id="divRpF272126">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span lang="FR" style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black">From:</span></b><span lang="FR" style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black">
<a href="mailto:sls-sea-dls-bounces@mailman.ccsds.org">sls-sea-dls-bounces@mailman.ccsds.org</a> [sls-sea-dls-bounces@mailman.ccsds.org] on behalf of Saba Bruno [Bruno.Saba@cnes.fr]<br>
<b>Sent:</b> Monday, April 18, 2016 9:48 AM<br>
<b>To:</b> <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><br>
<b>Subject:</b> RE: [Sls-sea-dls] Key Verification using CRC</span><span lang="FR" style="color:black"><o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="FR" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Dear all,</span><span lang="FR" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span lang="FR" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">One solution to avoid the use of a challenge-response system and stay with the simple CRC for on-board key checking is to compute the CRC on BOTH the Key-ID and
the key itself.</span><span lang="FR" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span lang="FR" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Ideally, what we know as a “key” would be a “Meta-Key”, comprising :</span><span lang="FR" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span lang="FR" style="color:black"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">-</span><span style="font-size:7.0pt;color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The Key ID, unique identifier of the key for the whole mission duration,</span><span lang="FR" style="color:black"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">-</span><span style="font-size:7.0pt;color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The Key itself (secret random data)</span><span lang="FR" style="color:black"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">-</span><span style="font-size:7.0pt;color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The CRC, computed on the Key ID and the key itself.</span><span lang="FR" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span lang="FR" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">This “Meta-Key” should be considered as an single entity, not splittable, being stored, transferred and distributed as is (on-board AND at ground level, from
generation to destruction).</span><span lang="FR" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span lang="FR" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Cheers,</span><span lang="FR" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span lang="FR" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span lang="FR" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D">Bruno Saba</span><span style="color:#1F497D">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D">CNES</span><span style="color:#1F497D">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D">DCT/TV/IN</span><span style="color:#1F497D">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D">18 Avenue Edouard Belin</span><span style="color:#1F497D">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D">31401 TOULOUSE Cedex 9</span><span style="color:#1F497D">
</span><span lang="FR" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR" style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D">Tel : + 33 (0) 5 61 28 28 76</span><span lang="FR" style="color:#1F497D">
<br>
</span><span lang="FR" style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D">Fax : + 33 (0) 5 61 28 19 96</span><span lang="FR" style="color:#1F497D">
</span><span lang="FR" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span lang="FR" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span lang="FR" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span lang="FR" style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black">De :</span></b><span lang="FR" style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black">
<a href="mailto:sls-sea-dls-bounces@mailman.ccsds.org">sls-sea-dls-bounces@mailman.ccsds.org</a> [<a href="mailto:sls-sea-dls-bounces@mailman.ccsds.org">mailto:sls-sea-dls-bounces@mailman.ccsds.org</a>]
<b>De la part de</b> <a href="mailto:Daniel.Fischer@esa.int">Daniel.Fischer@esa.int</a><br>
<b>Envoyé :</b> dimanche 17 avril 2016 13:13<br>
<b>À :</b> <a href="mailto:sls-sea-dls@mailman.ccsds.org">sls-sea-dls@mailman.ccsds.org</a><br>
<b>Objet :</b> [Sls-sea-dls] Key Verification using CRC</span><span lang="FR" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR" style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR" style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Dear all,</span><span lang="FR" style="color:black">
<br>
<br>
</span><span lang="FR" style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">I was discussing our new approach to key verification using the onboard-stored CRCs with David,</span><span lang="FR" style="color:black">
<br>
<br>
</span><span lang="FR" style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">He came up with a keen observation. </span><span lang="FR" style="color:black">
<br>
<br>
</span><span lang="FR" style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">The CRC-based key verification is somewhat weaker than one based on a challenge-response. The reason is that the CRC ensues you that the key at a certain slot is still
OK in terms of integrity. In contrast to the challenge-response approach it DOES NOT tell you that the key is the same as the key with same key ID on ground.</span><span lang="FR" style="color:black">
<br>
<br>
</span><span lang="FR" style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Is this an issue for us? What do you think? The only way we have to check key synchronisation is to use a key for actual traffic protection and see if it works.</span><span lang="FR" style="color:black">
<br>
<br>
</span><span lang="FR" style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">What do you think?</span><span lang="FR" style="color:black">
<br>
<br>
</span><span lang="FR" style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Cheers</span><span lang="FR" style="color:black">
<br>
</span><span lang="FR" style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Daniel</span><span lang="FR" style="color:black">
<br>
</span><span lang="FR" style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><br>
<br>
<br>
<br>
Dr. Daniel Fischer<br>
----------------------------<br>
Data Systems Manager<br>
Ground Segment Engineering Support Office (OPS-GE)<br>
Ground Systems Engineering Department<br>
Directorate of Operations<br>
<br>
European Space Agency - ESOC<br>
Robert-Bosch-Str. 5<br>
D-64293 Darmstadt - Germany<br>
Tel: +49 (0) 6151 90 2718 - Fax: +49 (0) 6151 90 2718<br>
Web: </span><span lang="FR" style="color:black"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.esa.int_&d=BQMFAw&c=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10&r=dT3K0y3n0RD9-56k-UVMPMP98PIQRd2Kzfa-AwqQOww&m=KmN17nxUMzCwV8w34kOrcf_v-AiSW05d3ZrGT3WEwEk&s=mA6vGF_WMAaO1e4I2x3Pnor6OGmfWEXhPWqN5MXu0eE&e=" target="_blank"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">http://www.esa.int</span>[esa.int]</a><o:p></o:p></span></p>
<pre><span lang="FR" style="color:black">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="FR" style="color:black">The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<o:p></o:p></span></pre>
<pre><span lang="FR" style="color:black">content is not permitted.<o:p></o:p></span></pre>
<pre><span lang="FR" style="color:black">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="FR" style="color:black">Emails can be altered and their integrity cannot be guaranteed by the sender.<o:p></o:p></span></pre>
<pre><span lang="FR" style="color:black"> <o:p></o:p></span></pre>
<pre><span lang="FR" style="color:black">Please consider the environment before printing this email.<o:p></o:p></span></pre>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>