<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=us-ascii">
<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: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:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"Pr\00E9format\00E9 HTML Car";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
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:11.0pt;
font-family:"Calibri",sans-serif;}
span.PrformatHTMLCar
{mso-style-name:"Pr\00E9format\00E9 HTML Car";
mso-style-priority:99;
mso-style-link:"Pr\00E9format\00E9 HTML";
font-family:Consolas;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
p.HTMLPreformatted, li.HTMLPreformatted, div.HTMLPreformatted
{mso-style-name:"HTML Preformatted";
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Arial",sans-serif;
color:windowtext;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:370226656;
mso-list-type:hybrid;
mso-list-template-ids:1007577188 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1
{mso-list-id:871068554;
mso-list-template-ids:-1882933632;}
@list l2
{mso-list-id:1238899051;
mso-list-template-ids:-871051688;}
@list l2:level1
{mso-level-start-at:2;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l3
{mso-list-id:1424454287;
mso-list-template-ids:1489915438;}
@list l3:level1
{mso-level-start-at:3;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US">Dear Councilors,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US">With Council’s endorsement, we would like to conclude our review, and stabilise the description that we will be using. For this leadership
suggests to put this on our Consent agenda for the next Council call. If you consider this requires time for (further) discussion, feel free to take it out of the consent agenda.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US">I would also like to acknowledge the comments made by Jeff, which is why I’m responding to Jeff’s email, noting that we would like to
take them for discussion outside this description and notably the first item we will take this as a question to the SG/Cs and in our preparation for our bilaterals with GAC. <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US">Thanks.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US">Philippe<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"><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"><b><span lang="EN-GB">From:</span></b><span lang="EN-GB"> Jeff Neuman [mailto:jeff@jjnsolutions.com]
<br>
<b>Sent:</b> Wednesday, August 25, 2021 5:14 PM<br>
<b>To:</b> FOUQUART Philippe INNOV/NET <philippe.fouquart@orange.com><br>
<b>Cc:</b> council@gnso.icann.org<br>
<b>Subject:</b> RE: [council] GNSO liaison to the GAC - Proposed updates<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Thanks Philippe for sending this around.<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">Dear Councilors,<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">Just to provide some more information, I wanted to provide some additional context and a couple of changes I would like to see discussed. I was provided this document on Monday and did get the chance to provide some
feedback, some of which resulted in changes. In addition, it is my understanding that Philippe met with GAC Leadership to discuss their view of the role and the performance of the current Liaison and my understanding is that the GAC was happy with the role
(and my performance) and that they did not have changes to recommend at this time in terms of how the Liaison interacts with the GAC. The GAC point of contact, however, relayed to me that it was their intention to start inviting the Liaison to intersessional
meetings that involved GNSO issues (which is provided for in the description, but is not something they have historically done).<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">With respect to this document:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<ol style="margin-top:0cm" start="1" type="1">
<li class="MsoNormal" style="mso-list:l0 level1 lfo3"><span lang="EN-US">One of the changes I recommended, which was not put into the draft, because it would require discussion with not only the Council, but also the SG/C Leaders, is the way that the Liaison
is appointed. This is the only position evaluated by the SSC (I believe) where a nomination must come from an SG/C Leader, but also requires that the person nominated then fill out a long expression of interest statement. When I applied last year, everyone
was confused. I submitted the information required, but it was rejected because the form (which only I could fill out) was submitted by me instead of an SG/C chair. So I had to fill out the form again, print it out, scan it via e-mail to SG/C leaders and
ask that one of them actually submit the application to the GNSO Secretariat. This required the leader to essentially take the document I did and send it to the Secretariat. It was inefficient, time consuming, and frankly may have scared anyone else away
from applying (as I was the only applicant). Here is what I would propose take its place:<o:p></o:p></span></li></ol>
<p class="MsoListParagraph"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoListParagraph"><i><span lang="EN-US">Any person can submit an application, which should include at a minimum…..[the stuff currently in #1]. These applications should be made available to all Stakeholder Group/Constituencies, etc. so that the
SGs/Cs can choose to provide comments on a candidate and/or endorse a candidate. SG/Cs are not required to provide comments and/or an endorsement, but any comments and/or endorsement that are submitted must be taken into consideration by the SSC.</span></i><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoListParagraph"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoListParagraph"><span lang="EN-US">This would allow for SG/C input, take away all the current inefficiencies, and would be a LOT less confusing.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<ol style="margin-top:0cm" start="2" type="1">
<li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo3;text-autospace:none">
<span lang="EN-US" style="color:windowtext">There is still confusion over the sentence “</span><span lang="EN-US">Liaise with
</span><span lang="EN-US" style="color:#A5262C">GNSO </span><span lang="EN-US">policy staff who may assist, as needed, in the preparation of briefing materials and/or responses to questions.” ICANN Staff has one interpretation which as we discussed several
meetings ago, is at odds with the way others interpret it. Therefore, I would like to see this resolved. The GAC has made it clear (appropriately) that the Liaison should not see any items of strategy in the briefing notes or things that are sensitive to
GAC discussions. That said, in my conversations with the GAC Point of Contact, if we wanted to insert the “GNSO View” on certain issues, that this should not be an issue. This is because the briefing by ICANN staff are purely factual and do not contain any
“GNSO spin”, context or in some cases, the rationale. ICANN staff rightfully does not believe that they can draft that kind of thing as the Secretariat because they need to be neutral. But the GNSO Council and/or the Liaison can.<o:p></o:p></span></li></ol>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt;text-autospace:none"><b><span lang="EN-US" style="color:black">I strongly encourage you to read the briefing notes from the last meeting (</span></b><a href="https://gac.icann.org/briefing-materials/icann71-gac-briefings-v1.pdf"><b><span lang="EN-US">https://gac.icann.org/briefing-materials/icann71-gac-briefings-v1.pdf</span></b></a><b><span lang="EN-US">).
Take a look at page 17 of 23 (in the PDF it is page 23] to see the short discussion on GNSO activity on DNS Abuse. When I read it, it left me with the impression that the GNSO Council ignored the GAC’s proposals submitted in 2019 (which I didn’t even know
about since they were proposals submitted to the previous Council) and that we essentially had not intended to follow up on any of the issues.<o:p></o:p></span></b></p>
<p class="MsoNormal" style="margin-left:36.0pt;text-autospace:none"><b><span lang="EN-US" style="color:black"><o:p> </o:p></span></b></p>
<p class="MsoNormal" style="margin-left:36.0pt;text-autospace:none"><b><span lang="EN-US" style="color:black">ICANN Org also added a new section in the briefing documents asking “Questions for GAC Representative Consideration.” I am not saying that there is
anything wrong with ICANN Org doing this, but unless you read the documents after the fact, you would never know these questions were asked. If you look at page 33 of the PDF, you will see examples of questions ICANN Org asked when discussing SubPro….it related
solely to IDNs. <u>Again, this may produce interesting information and I think it would be helpful for the GNSO to get some of this information.<o:p></o:p></u></span></b></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"><o:p> </o:p></span></p>
<ol style="margin-top:0cm" start="3" type="1">
<li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo3"><span lang="EN-US">Minor last point – We should be clear that the Annual Report of the Liaison should be timed to be the document deadline for the Annual Meeting as the current provision does
not say when the annual report should be delivered.<o:p></o:p></span></li></ol>
<p class="MsoListParagraph"><span lang="EN-US" style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Depending on how these discussions go, I am still evaluating whether or not to seek another term as the Liaison. As I expressed to Council Leadership, when I decide to take a role, I only do so because I believe I can
make a difference. I believe I have made a difference especially in how we communicate with the GAC. I have enjoyed unprecedented access to GAC meetings not only to observe, but to participate. I have tried to educate GAC members not only on GNSO positions,
but also the important “why” these are the positions. Although I have found that many GAC members are well informed about actual outputs from the GNSO, the rationale for these outputs is not always known or understood. I have tried to offer opportunities
for GNSO Working Group leaders to present to the GAC, and I have had great exchanges with the GAC Point of Contact and in planning for ICANN meetings. More on that as we get closer to ICANN 72.
<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">Thank you for reading and considering these comments.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US">Sincerely,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Jeff<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"><o:p> </o:p></span></p>
<div>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse">
<tbody>
<tr>
<td width="192" valign="bottom" style="width:144.3pt;border:none;border-top:solid #06175F 3.0pt;padding:0cm 5.4pt 0cm 5.4pt">
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black;border:none windowtext 1.0pt;padding:0cm"><img border="0" width="178" height="81" id="Picture_x0020_1" src="cid:image003.png@01D7A8D4.EF2A2A10" alt="cid:image001.png@01D79992.FBED8040"></span><o:p></o:p></p>
</td>
<td width="173" valign="bottom" style="width:129.95pt;border:none;border-top:solid #06175F 3.0pt;padding:0cm 5.4pt 0cm 5.4pt">
<p class="MsoNormal" style="text-align:justify"><span lang="EN-GB" style="font-family:"Arial",sans-serif;color:#06175F">Jeffrey J. Neuman</span><span lang="EN-GB" style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span lang="EN-GB" style="font-family:"Arial",sans-serif;color:black">Founder & CEO</span><span lang="EN-GB" style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span lang="EN-GB" style="font-family:"Arial",sans-serif;color:#06175F">JJN Solutions, LLC</span><span lang="EN-GB" style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span lang="EN-GB" style="font-family:"Arial",sans-serif;color:black">p: +1.202.549.5079</span><span lang="EN-GB" style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span lang="EN-GB" style="font-family:"Arial",sans-serif;color:black">E:
</span><a href="mailto:jeff@jjnsolutions.com"><span lang="EN-GB" style="font-family:"Arial",sans-serif;color:#1155CC">jeff@jjnsolutions.com</span></a><span lang="EN-GB" style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><a href="http://jjnsolutions.com"><span lang="EN-GB" style="font-family:"Arial",sans-serif">http://jjnsolutions.com</span></a><span lang="EN-GB" style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US"><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"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> council <</span><a href="mailto:council-bounces@gnso.icann.org"><span lang="EN-US">council-bounces@gnso.icann.org</span></a><span lang="EN-US">>
<b>On Behalf Of </b>philippe.fouquart--- via council<br>
<b>Sent:</b> Wednesday, August 25, 2021 6:27 AM<br>
<b>To:</b> </span><a href="mailto:council@gnso.icann.org"><span lang="EN-US">council@gnso.icann.org</span></a><span lang="EN-US"><br>
<b>Subject:</b> [council] GNSO liaison to the GAC - Proposed updates<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">Dear Councilors,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">As you may recall, Council leadership took as an action item to develop proposed language to further clarify the role and expectations in relation to the GNSO Council Liaison to the GAC from the perspective of the Council.
Based on the input received during the different discussions, you will find attached our proposed updates.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">As a reminder, the original document describing the role and responsibilities of the GNSO Liaison to the GAC was developed by the GAC-GNSO Consultation Group many years ago (2014) and used to launch the first call for
applications to fill the role of GNSO Liaison to the GAC. Throughout the years, several updates were made, for example, to reflect that the SSC has been assigned the responsibility to review the applications, the change from F2F to virtual meetings and the
requirement to provide an annual report to the Council. These updates and some further proposed updates have also been reflected in the form of redline changes in the attached. However, we would like to request you to focus your attention on the changes highlighted
in yellow, which, per the Council’s discussion, aim to further clarify the Council’s expectations with regard to the Liaison’s responsibility and interaction with the Council. Leadership has also suggested some updates to the renewal section to bring it more
in line with other appointments. <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">As this does not affect the Liaison’s responsibilities towards the GAC, we don’t anticipate a formal consultation with the GAC is necessary about these changes, but as part of ongoing conversations with the GAC leadership,
we will update our GAC counterpart accordingly. <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">Please share any feedback or suggestions you may have via the mailing list by 5 September 2021. Hopefully we can resolve and address any comments or suggestions you may have online so that we can formally accept this
updated version at one of our September Council meeting. <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Philippe<o:p></o:p></p>
<pre>_________________________________________________________________________________________________________________________<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc<o:p></o:p></pre>
<pre>pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler<o:p></o:p></pre>
<pre>a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,<o:p></o:p></pre>
<pre>Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. <span lang="EN-GB">Merci.<o:p></o:p></span></pre>
<pre><span lang="EN-GB"><o:p> </o:p></span></pre>
<pre><span lang="EN-GB">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="EN-GB">they should not be distributed, used or copied without authorisation.<o:p></o:p></span></pre>
<pre><span lang="EN-GB">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="EN-GB">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>Thank you.<o:p></o:p></pre>
</div>
<PRE>_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
</PRE></body>
</html>