<html 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)">
<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:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.gmail-m-3847161661948672374msolistparagraph, li.gmail-m-3847161661948672374msolistparagraph, div.gmail-m-3847161661948672374msolistparagraph
{mso-style-name:gmail-m_-3847161661948672374msolistparagraph;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:980773852;
mso-list-template-ids:1639318960;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1
{mso-list-id:1151099303;
mso-list-template-ids:507427642;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style>
</head>
<body lang="en-BE" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Dear councilors,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Forwarding Janis’ email to the Council mailing list (although the email address was correctly cc-ed), as it doesn’t appear yet on the mailing list archives.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Kind regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Nathalie<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language: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 style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Gnso-secs <gnso-secs-bounces@icann.org> on behalf of "gnso-secs@icann.org" <gnso-secs@icann.org><br>
<b>Reply to: </b>Janis Karklins <karklinsj@gmail.com><br>
<b>Date: </b>Wednesday, 5 January 2022 at 11:15<br>
<b>To: </b>"philippe.fouquart@orange.com" <philippe.fouquart@orange.com><br>
<b>Cc: </b>Steve Chan <steve.chan@icann.org>, "julf@julf.com" <julf@julf.com>, "council@gnso.icann.org" <council@gnso.icann.org>, "gnso-secs@icann.org" <gnso-secs@icann.org>, "secretariat@icannregistrars.org" <secretariat@icannregistrars.org>, "milton@gatech.edu"
<milton@gatech.edu>, Andrea Glandon <andrea.glandon@icann.org>, "brian.king@markmonitor.com" <Brian.King@markmonitor.com>, Berry Cobb <Berry.Cobb@icann.org>, "mmcross@amazon.com" <mmcross@amazon.com>, "matt@brandsight.com" <matt@brandsight.com>, "fasonga@gmail.com"
<fasonga@gmail.com>, "benakin@gmail.com" <benakin@gmail.com>, "thomas@rickert.law" <thomas@rickert.law>, "alan@donuts.email" <alan@donuts.email>, Ashley Heineman <aheineman@godaddy.com>, "secretariat@rysg.info" <secretariat@rysg.info>, "lschulman@inta.org"
<lschulman@inta.org>, James Bladel <jbladel@godaddy.com>, Emily Barabas <emily.barabas@icann.org>, Steve DelBianco <sdelbianco@netchoice.org>, Brenda Brewer <brenda.brewer@icann.org>, "volker.greimann@centralnic.com" <volker.greimann@centralnic.com>, "aelsadr@tucows.com"
<aelsadr@tucows.com>, Marc Anderson <mcanderson@verisign.com>, Ariel Liang <ariel.liang@icann.org>, "plommer@gmail.com" <plommer@gmail.com>, "mason.cole@appdetex.com" <mason.cole@appdetex.com>, "marksv@microsoft.com" <marksv@microsoft.com>, "Caitlin.rubergen@icann.org"
<Caitlin.rubergen@icann.org>, Mary Wong <mary.wong@icann.org>, "franck_journoud@motionpictures.org" <Franck_Journoud@motionpictures.org>, "stefan.filipovic01@gmail.com" <stefan.filipovic01@gmail.com>, "bruna.mrtns@gmail.com" <bruna.mrtns@gmail.com>, Marika
Konings <marika.konings@icann.org>, Stephanie Perrin <stephanie.perrin@mail.utoronto.ca>, Julie Hedlund <julie.hedlund@icann.org>, "chair@rysg.info" <chair@rysg.info>, "margiemilam@fb.com" <margiemilam@fb.com>, Wolf-Ulrich Knoben <Wolf-Ulrich.Knoben@t-online.de><br>
<b>Subject: </b>Re: [gnso-secs] EPDP Ph2 SSAD ODP and next steps<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Good morning, Philippe, and all on the list. <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Let me start by wishing very happy, successful and productive 2022. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">My initial reaction to your and Council leadership reflection is two fold - one always can hope for a better result, but also process can't be eternal. It already has been sufficiently long.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Cost is an issue and we should look into ways to reduce it. Automation of processes may be a solution. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">We will not be able to change GDPR. Hence, manual review of requests will remain with us until the GDPR will be modified or Central Gateway recommendations systematically will be identical to the results of the manual review and CPs will
accept to follow the CG recommendations. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">But all re rest in SSAD needs to be automated. That includes accreditation. Scrapping accreditation will not resolve the issue, but rather increase work (and the cost) for CPs who will need to do manual verification of identity of each
requestor.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Automation of accreditation seems feasible. I recall my application for the Canadian visa (to attend ICANN meeting). I filed an online application and 15 min and 7$ later my request was approved. I doubt that a human was involved in that
decision. Something similar can be done within SSAD following existing policy recommendations on accreditation.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Hope that might help. Or at least fuel conversation of the group.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">With greetings from Strasbourg<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">JK <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Tue, Jan 4, 2022 at 8:13 PM <<a href="mailto:philippe.fouquart@orange.com">philippe.fouquart@orange.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">Dear Councilors,
</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">Dear EPDP Phase 2 members,
</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">Dear SG/C Chairs,</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">I trust this finds you all well.
</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">Following the informal SSAD ODP update on 20 December, in which representatives from the ICANN Board GDPR Caucus, ICANN org, the GNSO Council and GNSO appointed
members of the EPDP Phase 2 team participated, Council leadership has worked with the staff support team on the attached paper which aims to provide a high level outline of the different ideas and suggestions that were made during that meeting. This is intended
to serve as a basis for further discussions within the GNSO community for how to prepare for next steps in the consultation with the ICANN Board, which is in the process of being scheduled.</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">To continue our conversation, obtain further input on possible next steps and assess whether there is possible convergence concerning next steps, we would like
to schedule another call for the Council and GNSO appointed members of the EPDP Phase 2 on
<u>Wednesday 12 January at 6.00 UTC</u> (a calendar invite will follow shortly). Of course, if there are any ideas or suggestions that have not been captured in the paper, or any new ones that have come to mind since our last meeting, please feel free to share
these by replying all to this email. </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">And Best Wishes for the New Year.</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">Regards,</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">Philippe</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif"> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif"> </span><span lang="FR"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> FOUQUART Philippe INNOV/NET
<br>
<b>Sent:</b> Friday, December 3, 2021 4:15 PM<br>
<b>To:</b> '<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a>' <<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a>><br>
<b>Cc:</b> <a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a><br>
<b>Subject:</b> EPDP Ph2 SSAD ODP and next steps</span><span lang="FR"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">Dear Councilors,</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">For those that have attended the recent SSAD ODP Webinars, you may be aware that the SSAD ODP Team is in the process of finalizing its analysis, including its
work on the SSAD Cost Model. As a result, the Council requested consultation with the ICANN Board is expected to be scheduled in January 2022. To prepare accordingly for this consultation and possible next steps, Council leadership has worked with the staff
support team to put forward the following proposed schedule:</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> </span><span lang="FR"><o:p></o:p></span></p>
<ul type="disc">
<li class="gmail-m-3847161661948672374msolistparagraph" style="mso-list:l0 level1 lfo1">
<span lang="EN-US">16 December 2021 at 14.00 UTC – GNSO Council meeting to discuss the approach outlined in this email</span><span lang="FR"><o:p></o:p></span></li><li class="gmail-m-3847161661948672374msolistparagraph" style="mso-list:l0 level1 lfo1">
<span lang="EN-US">20 December 2021 at 21.00 UTC – Update session on SSAD ODP, including SSAD Cost Model information for Council and GNSO appointed EPDP Team members (closed session)</span><span lang="FR"><o:p></o:p></span></li><li class="gmail-m-3847161661948672374msolistparagraph" style="mso-list:l0 level1 lfo1">
<span lang="EN-US">Between 21 December and January 2022, GNSO Council with input from SG/Cs to prepare for GNSO Council – ICANN Board consultation (e.g. informal conversations, formal meetings, mailing list discussion, small team – to be discussed)</span><span lang="FR"><o:p></o:p></span></li><li class="gmail-m-3847161661948672374msolistparagraph" style="mso-list:l0 level1 lfo1">
<span lang="EN-US">January 2022 (date TBC) – GNSO Council & ICANN Board consultation</span><span lang="FR"><o:p></o:p></span></li></ul>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">Although at this stage we do not have any further insight into what the SSAD Cost Model will tell us or how it may, or may not, change the positions on the SSAD
recommendations, there are roughly three scenarios that can be anticipated:</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> </span><span lang="FR"><o:p></o:p></span></p>
<ol start="1" type="1">
<li class="gmail-m-3847161661948672374msolistparagraph" style="mso-list:l1 level1 lfo2">
<span lang="EN-US">ICANN Board determines that the adoption of the recommendations is in the best interest of the ICANN community and ICANN and adopts the SSAD recommendations – no further action expected from the GNSO Council at this stage;</span><span lang="FR"><o:p></o:p></span></li><li class="gmail-m-3847161661948672374msolistparagraph" style="mso-list:l1 level1 lfo2">
<span lang="EN-US">ICANN Board determines that the adoption of the recommendation is not in the best interest of the ICANN community or ICANN and does not adopt all or part of the recommendations – the GNSO Council will be requested to affirm or modify its
recommendations in the form of a “Supplemental Recommendation”. </span><span lang="FR"><o:p></o:p></span></li><li class="gmail-m-3847161661948672374msolistparagraph" style="mso-list:l1 level1 lfo2">
<span lang="EN-US">The GNSO Council decides to avail itself of section 16 (“Amendments or Modifications of Approved Policies”) and agrees to modify or amend the recommendations before the ICANN Board considers the recommendations for approval.
</span><span lang="FR"><o:p></o:p></span></li></ol>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">To be clear, Council Leadership does not want to get ahead of the discussion and as such, we are not making any kind of prediction about which scenario is most
likely, but we would like the Council and SG/Cs to start thinking about these scenarios and consider what is needed to be prepared for the next steps.
</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">Our main objective here is to make sure that conversations within the GNSO as well as with the ICANN Board are constructive and effective – it is on all of us
to work towards an approach and outcome that we are all willing and able to defend and live with.
</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">Please come prepared to share your feedback during the Council meeting on 16 December. Of course, you are encouraged to already start the conversation on the
mailing list. </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">Best regards,</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">Philippe</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif"> </span><span lang="FR"><o:p></o:p></span></p>
</div>
<pre><span lang="FR">_________________________________________________________________________________________________________________________<o:p></o:p></span></pre>
<pre><span lang="FR"><o:p> </o:p></span></pre>
<pre><span lang="FR">Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc<o:p></o:p></span></pre>
<pre><span lang="FR">pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler<o:p></o:p></span></pre>
<pre><span lang="FR">a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,<o:p></o:p></span></pre>
<pre><span lang="FR">Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.<o:p></o:p></span></pre>
<pre><span lang="FR"><o:p> </o:p></span></pre>
<pre><span lang="FR">This message and its attachments may contain confidential or privileged information that may be protected by law;<o:p></o:p></span></pre>
<pre><span lang="FR">they should not be distributed, used or copied without authorisation.<o:p></o:p></span></pre>
<pre><span lang="FR">If you have received this email in error, please notify the sender and delete this message and its attachments.<o:p></o:p></span></pre>
<pre><span lang="FR">As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.<o:p></o:p></span></pre>
<pre><span lang="FR">Thank you.<o:p></o:p></span></pre>
</div>
</blockquote>
</div>
</div>
</body>
</html>