<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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;}
@font-face
{font-family:"Helvetica 75 Bold";
panose-1:2 11 8 4 2 2 2 2 2 4;}
@font-face
{font-family:"Segoe UI Emoji";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* 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:"Préformaté HTML Car";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.PrformatHTMLCar
{mso-style-name:"Préformaté HTML Car";
mso-style-priority:99;
mso-style-link:"Préformaté HTML";
font-family:Consolas;}
p.msipfootered91ed98, li.msipfootered91ed98, div.msipfootered91ed98
{mso-style-name:msipfootered91ed98;
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.xapple-converted-space
{mso-style-name:x_apple-converted-space;}
span.EmailStyle22
{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:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:287394753;
mso-list-template-ids:17757222;}
@list l0:level1
{mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level2
{mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level4
{mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level7
{mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1
{mso-list-id:1825126129;
mso-list-template-ids:98231140;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="FR" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Dear Councilors,<o:p></o:p></span></p>
<p class="MsoNormal"><span 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">Staff has started preparing a final revision of the letter with the comments received so far. Thanks Kurt, Greg, Manju.
<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">In the meantime, please see Jeff’s suggestion below, shared with his permission, to add “preestablished” before “</span><span lang="EN-AU">published milestones” as well as the sentence</span><span lang="EN-AU" style="mso-fareast-language:EN-US">
</span><span lang="EN-US" style="mso-fareast-language:EN-US">“</span><span lang="EN-US">This letter should not be interpreted as the Council accepting any delays in either of these projects.”
<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">We discussed this within leadership and don’t think this is inconsistent with the exchange we have had so far (including Greg’s edits), and useful given the latest exchanges with the ODP team. As a rule, however, we don’t
want to add text that has not been circulated. If you think otherwise, please say so by Friday 1700UTC. <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="mso-fareast-language:EN-US">Thank you.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Philippe<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"><o:p> </o:p></p>
<p class="msipfootered91ed98" align="center" style="margin:0cm;text-align:center">
<span style="font-size:8.0pt;font-family:"Helvetica 75 Bold",sans-serif;color:#ED7D31">Orange Restricted</span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b>From:</b> Jeff Neuman <jeff@jjnsolutions.com> <br>
<b>Sent:</b> Wednesday, June 29, 2022 11:20 PM<br>
<b>To:</b> FOUQUART Philippe INNOV/NET <philippe.fouquart@orange.com>; Tomslin Samme-Nlar (mesumbeslin@gmail.com) <mesumbeslin@gmail.com>; Sebastien@registry.godaddy<br>
<b>Cc:</b> kurt@kjpritz.com<br>
<b>Subject:</b> FW: [council] SSAD Light Impact Council - draft response<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US">Dear council leadership,<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">I understand there is a desire to send this letter tonight or tomorrow. I just wanted to give you an update on the call I had with the SubPro ODP ICANN team. I am in the process of drafting up my other notes to send
a full note to the Council (which I should send around tomorrow or Friday).<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 the SubPro ODP, there have been no instructions yet to the ODP Team that the SSAD Light work has been approved for them to start working on. Therefore, the ODP Team is still working on their current deadlines.<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">However, if and when there are instructions to proceed with the SSAD ODP Light design, they reminded me that it will be
<u>at least</u> a 6 week delay. Although the ODP Team has not yet figured out what delays would actually be caused by the SSAD Light project, they committed to me that they would immediately develop a new timeline for the SubPro ODP letting us know the specific
intended delays. The confirmed that if it were just 6 weeks that would be pushing against the December holiday time when ICANN closes down and this may cause the ODA to not be released until Mid-January which would of course result in a 10-week delay. It
is also unknown how that would impact their other milestones. For example, I believe there is no ICANN Board Meeting in December so the earliest the ODP Team could brief the Board on the ODA would be January. But they are unsure when the Board Workshop will
be (which is the natural place where they intended to update the Board).<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">This could mean that the Board could not be updated until February unless the ICANN Board moved their intended workshop or figured out another time to discuss these. In any case, it puts a vote by the ICANN Board on
the GNSO SubPro Policies in March at risk.<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">And of course this will ultimately lead to a decision in September when the SSAD Light proposal is presented on whether to move ahead with the implementation of that and whether the implementation of that will also delay
implementation of SubPro.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">The ICANN ODP team that is not also on the SSAD Light project will continue to work on the SubPro ODP during any delay. I have asked them to present creative ideas on how we can mitigate the impact of any of these delays
on future activities. This includes releasing parts of the ODA earlier than others (if that is even possible) or any other ideas to mitigate the delays.<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">I am not a councilor, but as an impacted GNSO member, I believe a sentence must be added to the letter that states :”This letter should not be interpreted as the Council accepting any delays in either of these projects.”
I have therefore cc’d Kurt. If you want to send it to the Council, feel free. But when I read the letter in my opinion it very lightly says that they should try to meet published milestones, but we don’t have the expertise to say anything else.<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">I disagree with that…but even if we accept that notion, this letter as drafted basically gives ICANN carte blanche to do whatever they want. Therefore, the added setence states what I believe we expect.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><br>
Finally, I added the word “Pre-established” before the words published milestones. ICANN can always meet published milestones If they keep publishing new timelines
</span><span lang="EN-US" style="font-family:"Segoe UI Emoji",sans-serif">😉</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">Its your call on what you want to do, but I think the letter should be stronger on what we expect. Its not our job to organize their resources, yes. But, it is their job to perform.<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>
<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 width="177" height="81" style="width:1.8472in;height:.8402in" id="Picture_x0020_2" src="cid:image001.png@01D88BDB.1CDC7BE0"></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 style="font-family:"Arial",sans-serif;color:#06175F">Jeffrey J. Neuman</span><o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black">Founder & CEO</span><o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:#06175F">JJN Solutions, LLC</span><o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black">p: +1.202.549.5079</span><o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black">E:
</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><a href="mailto:jeff@jjnsolutions.com"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#1155CC">jeff@jjnsolutions.com</span></a></span><o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black"><a href="http://jjnsolutions.com">http://jjnsolutions.com</a></span><o:p></o:p></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 <<a href="mailto:council-bounces@gnso.icann.org">council-bounces@gnso.icann.org</a>>
<b>On Behalf Of </b>philippe.fouquart--- via council<br>
<b>Sent:</b> Tuesday, June 28, 2022 8:28 AM<br>
<b>To:</b> kurt kjpritz.com <<a href="mailto:kurt@kjpritz.com">kurt@kjpritz.com</a>><br>
<b>Cc:</b> <a href="mailto:gnso-secs@icann.org">gnso-secs@icann.org</a>; <a href="mailto:council@gnso.icann.org">
council@gnso.icann.org</a><br>
<b>Subject:</b> Re: [council] SSAD Light Impact Council - draft response<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-US">Hi Kurt. <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">Thanks for sorting out the order of priorities in the letter, this is helpful. Some of the elements of the first iteration being more records of the discussion, we will see whether there’s benefit in bringing some of
them back without losing in conciseness or being repetitive.<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">Everyone, <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">please share any other comment you may have by the end of the day, for us to send this later this week.<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">Thanks.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Philippe<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>
<p class="msipfootered91ed98" align="center" style="margin:0cm;text-align:center">
<span style="font-size:8.0pt;font-family:"Helvetica 75 Bold",sans-serif;color:#ED7D31">Orange Restricted</span><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"> kurt kjpritz.com <<a href="mailto:kurt@kjpritz.com">kurt@kjpritz.com</a>>
<br>
<b>Sent:</b> Monday, June 27, 2022 10:52 PM<br>
<b>To:</b> FOUQUART Philippe INNOV/NET <<a href="mailto:philippe.fouquart@orange.com">philippe.fouquart@orange.com</a>><br>
<b>Cc:</b> <a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>; <a href="mailto:gnso-secs@icann.org">
gnso-secs@icann.org</a><br>
<b>Subject:</b> Re: [council] SSAD Light Impact Council - draft response<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">Hi Philippe: <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Thanks for the opportunity to comment on this draft. Please consider the attached and feel free to use some, all or none of it. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">I have added a brief bit of context at the start as this issue did not arise from the Board-Council interaction but rather came in separately from the staff.
</span>I maintained the two main messages:<span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3">
<span lang="EN-US">to emphasize the importance of both (SSAD and SubPro) initiatives, and <o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3">
<span lang="EN-US">that the Council does not view itself in a position, nor does it consider it the role of the Council, to dictate the allocation of ICANN org resources now that these policy recommendations are with the ICANN Board.<o:p></o:p></span></li></ol>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">There was some re-arranging / re-wording that would render a redline somewhat ineffective but I can produce one. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">I hope you find this constructive and helpful. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Best regards,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Kurt<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US"> <o:p></o:p></span></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span lang="EN-US">On Jun 22, 2022, at 3:22 AM, philippe.fouquart--- via council <</span><a href="mailto:council@gnso.icann.org"><span lang="EN-US">council@gnso.icann.org</span></a><span lang="EN-US">> wrote:<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">Dear Councilors,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">For you review, please find attached a draft letter to the Board regarding the impact of the development of an SSAD Light Design Paper on other ongoing work, including the SubPro ODP. This is intended to capture the conclusions
of last week’s discussion item.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Please provide your comments within a week, by Wednesday 29<sup>th</sup><span class="xapple-converted-space"> </span>COB UTC.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Hope all those who could attend the The Hague meeting travelled safe and well back home.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal">Regards,<span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal">Philippe<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>
</div>
<pre style="font-variant-caps:normal;text-align:start;word-spacing:0px"><span style="font-size:9.0pt">_________________________________________________________________________________________________________________________</span><span lang="EN-US"><o:p></o:p></span></pre>
<pre><span style="font-size:9.0pt"> </span><span lang="EN-US"><o:p></o:p></span></pre>
<pre><span style="font-size:9.0pt">Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc</span><span lang="EN-US"><o:p></o:p></span></pre>
<pre><span style="font-size:9.0pt">pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler</span><span lang="EN-US"><o:p></o:p></span></pre>
<pre><span style="font-size:9.0pt">a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,</span><span lang="EN-US"><o:p></o:p></span></pre>
<pre><span style="font-size:9.0pt">Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. </span><span lang="EN-US" style="font-size:9.0pt">Merci.</span><span lang="EN-US"><o:p></o:p></span></pre>
<pre><span lang="EN-US" style="font-size:9.0pt"> </span><span lang="EN-US"><o:p></o:p></span></pre>
<pre><span lang="EN-US" style="font-size:9.0pt">This message and its attachments may contain confidential or privileged information that may be protected by law;</span><span lang="EN-US"><o:p></o:p></span></pre>
<pre><span lang="EN-US" style="font-size:9.0pt">they should not be distributed, used or copied without authorisation.</span><span lang="EN-US"><o:p></o:p></span></pre>
<pre><span lang="EN-US" style="font-size:9.0pt">If you have received this email in error, please notify the sender and delete this message and its attachments.</span><span lang="EN-US"><o:p></o:p></span></pre>
<pre><span lang="EN-US" style="font-size:9.0pt">As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.</span><span lang="EN-US"><o:p></o:p></span></pre>
<pre><span lang="EN-US" style="font-size:9.0pt">Thank you.</span><span lang="EN-US"><o:p></o:p></span></pre>
<p class="MsoNormal"><span lang="EN-US"><SSAD Light Impact Council Response - upd 16 June 2022.docx></span><span lang="EN-US" style="font-size:9.0pt;font-family:"Helvetica",sans-serif">_______________________________________________<br>
council mailing list<br>
</span><a href="mailto:council@gnso.icann.org"><span lang="EN-US" style="font-size:9.0pt;font-family:"Helvetica",sans-serif">council@gnso.icann.org</span></a><span lang="EN-US" style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><br>
</span><a href="https://mm.icann.org/mailman/listinfo/council"><span lang="EN-US" style="font-size:9.0pt;font-family:"Helvetica",sans-serif">https://mm.icann.org/mailman/listinfo/council</span></a><span lang="EN-US" style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><br>
<br>
_______________________________________________<br>
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (</span><a href="https://www.icann.org/privacy/policy"><span lang="EN-US" style="font-size:9.0pt;font-family:"Helvetica",sans-serif">https://www.icann.org/privacy/policy</span></a><span lang="EN-US" style="font-size:9.0pt;font-family:"Helvetica",sans-serif">)
and the website Terms of Service (</span><a href="https://www.icann.org/privacy/tos"><span lang="EN-US" style="font-size:9.0pt;font-family:"Helvetica",sans-serif">https://www.icann.org/privacy/tos</span></a><span lang="EN-US" style="font-size:9.0pt;font-family:"Helvetica",sans-serif">).
You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
</div>
<pre>_________________________________________________________________________________________________________________________<span lang="EN-US"><o:p></o:p></span></pre>
<pre> <span lang="EN-US"><o:p></o:p></span></pre>
<pre>Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc<span lang="EN-US"><o:p></o:p></span></pre>
<pre>pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler<span lang="EN-US"><o:p></o:p></span></pre>
<pre>a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,<span lang="EN-US"><o:p></o:p></span></pre>
<pre>Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.<span lang="EN-US"><o:p></o:p></span></pre>
<pre> <span lang="EN-US"><o:p></o:p></span></pre>
<pre>This message and its attachments may contain confidential or privileged information that may be protected by law;<span lang="EN-US"><o:p></o:p></span></pre>
<pre>they should not be distributed, used or copied without authorisation.<span lang="EN-US"><o:p></o:p></span></pre>
<pre>If you have received this email in error, please notify the sender and delete this message and its attachments.<span lang="EN-US"><o:p></o:p></span></pre>
<pre>As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.<span lang="EN-US"><o:p></o:p></span></pre>
<pre>Thank you.<span lang="EN-US"><o:p></o:p></span></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>