<div class="__aliyun_email_body_block"><div style="clear:both;">Thank you very much to those who contributed to the draft.</div><div style="clear:both;"><br ></div><div style="clear:both;">I have made a few more suggested edits, including the following for clarity and to avoid repetition:</div><ul style="list-style-type:disc;"><li ><div style="clear:both;"><span style="caret-color:#000000;color:#000000;font-style:normal;font-variant-caps:normal;font-weight:normal;text-align:start;text-indent:.0px;text-transform:none;text-decoration:none;font-size:14.0px;font-family:tahoma;">add a definition: </span><em ><span style="caret-color:#000000;color:#000000;font-variant-caps:normal;font-weight:normal;text-align:start;text-indent:.0px;text-transform:none;text-decoration:none;font-size:14.0px;font-family:tahoma;">ICANN’s contracts with registries and registrars, consensus policies, and policies in effect or in development (“ICANN’s Contracts and Policies”)</span></em></div></li><li ><div style="clear:both;">merge the second and fifth points to read:</div></li></ul><div style="clear:both;"><p class="MsoListParagraph" style="margin:.0px .0px .0px 48.0px;text-indent:-24.0px;"><span style="font-size:16.0px;font-family:Symbol;">·<span style="font-variant-caps:normal;font-weight:normal;font-stretch:normal;font-size:9.0px;line-height:normal;font-family:Times New Roman;"> <em > </em></span></span><em ><span style="font-size:16.0px;font-family:Calibri;">Second, we encourage ICANN <span class="spellcheck_typo">org</span> to conduct standard regulatory impact assessments so that the community can understand the intended rationale for a law/regulation/directive, specific extracts of the proposed text that could have implications on ICANN’s Contracts and Policies, and outline concretely what implications are anticipated. A timeline should be included so the community can understand how imminent the law/regulation/directive is and when it needs to take action. Once such law or regulation has been adopted, ICANN <span class="spellcheck_typo">org</span> should undertake a compliance assessment as soon as possible to ensure sufficient time to address any deficiencies or issues.</span></em></p></div><div style="clear:both;"><br ></div><div style="clear:both;">I suggest we aim to send the finalized version by COB this Friday 19th July. So if you have further edits or any concerns or objections, please post to the Council mailing list. </div><div style="clear:both;"><br ></div><div style="clear:both;">Kind regards,</div><div style="clear:both;"><br ></div><div style="clear:both;">Pam</div><div style="clear:both;"><br ></div><div style="clear:both;"><br ></div><div style="clear:both;"><br ></div><div style="clear:both;"><span style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;color:#000000;"><br ></span></div><div style="clear:both;"> <br ></div><div style="clear:both;"><span style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;color:#000000;"><br ></span></div><blockquote style="margin-right:0;margin-top:0;margin-bottom:0;"><div style="clear:both;"><span style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;color:#000000;">------------------------------------------------------------------</span></div><div style="clear:both;"><span style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;color:#000000;">Sender:Flip Petillion <fpetillion@petillion.law></span></div><div style="clear:both;"><span style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;color:#000000;">Sent At:2019 Jul. 16 (Tue.) 00:39</span></div><div style="clear:both;"><span style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;color:#000000;">Recipient:Darcy Southwell <darcy.southwell@endurance.com>; philippe.fouquart@orange.com <philippe.fouquart@orange.com></span></div><div style="clear:both;"><span style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;color:#000000;">Cc:gnso-secs@icann.org <gnso-secs@icann.org>; council@gnso.icann.org <council@gnso.icann.org></span></div><div style="clear:both;"><span style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;color:#000000;">Subject:Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements</span></div><div style="clear:both;"><span style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;color:#000000;"><br ></span></div><style >!-- @font-face{font-family:Cambria Math;panose-1:2 4 5 3 5 4 6 3 2 4;}{font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}{font-family:Gill Sans MT Pro Light;panose-1:2 11 3 2 2 1 4 2 2 3;}{font-family:Candara;panose-1:2 14 5 2 3 3 3 2 2 4;}{font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;}{font-family:Consolas;panose-1:2 11 6 9 2 2 4 3 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal{margin:.0cm;margin-bottom:.0pt;font-size:11.0pt;font-family:Calibri,sans-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;}pre{mso-style-priority:99;mso-style-link:HTML Preformatted Char;margin:.0cm;margin-bottom:.0pt;font-size:10.0pt;font-family:Courier New;}p.msonormal0, li.msonormal0, div.msonormal0{mso-style-name:msonormal;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;}{mso-list-id:1443063336;mso-list-template-ids:-1498874098;}{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;}{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;}{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;}{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;}{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;}{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;}{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;}{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;}{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;}ol{margin-bottom:.0cm;}ul{margin-bottom:.0cm;}--></style><div class="WordSection1"><p class="MsoNormal">All:</p><p class="MsoNormal"> </p><p class="MsoNormal">I made a change in the third issue.<br ><br >
Best</p><p class="MsoNormal"> </p><p class="MsoNormal">Flip</p><p class="MsoNormal"> </p><div ><p class="MsoNormal">Flip Petillion </p><p class="MsoNormal">fpetillion@petillion.law</p><p class="MsoNormal">+32484652653</p><p class="MsoNormal">www.petillion.law</p><p class="MsoNormal"> </p><p class="MsoNormal"><a href="http://www.petillion.law/" target="_blank"><span style="color:#0563c1;text-decoration:none;"><img alt="signature_2145422569" border="0" height="43" src="cid:__aliyun156323169870742781" width="191" style="width:2.0in;height:.4in;"></span></a></p><p class="MsoNormal"><span style="font-family:Gill Sans MT Pro Light,sans-serif;color:black;"> </span></p><p class="MsoNormal"><span style="font-family:Gill Sans MT Pro Light,sans-serif;color:black;"> </span><span style="font-size:13.0px;font-family:Gill Sans MT Pro Light,sans-serif;color:black;">Attorneys – Advocaten - Avocats</span></p><p class="MsoNormal"> </p><p class="MsoNormal"> </p></div><p class="MsoNormal"> </p><p class="MsoNormal"> </p><div style="border-style:solid none none;border-top-width:1.0px;border-top-color:#b5c4df;padding:4.0px .0cm .0cm;"><p class="MsoNormal"><b ><span style="font-size:16.0px;color:black;">From: </span></b><span style="font-size:16.0px;color:black;">council <council-bounces@gnso.icann.org> on behalf of Darcy Southwell <darcy.southwell@endurance.com><br ><b >Date: </b>Friday, 12 July 2019 at 17:07<br ><b >To: </b>"philippe.fouquart@orange.com" <philippe.fouquart@orange.com><br ><b >Cc: </b>"gnso-secs@icann.org" <gnso-secs@icann.org>, "council@gnso.icann.org" <council@gnso.icann.org><br ><b >Subject: </b>Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements</span></p></div><div ><p class="MsoNormal"> </p></div><div ><div ><p class="MsoNormal"><span style="font-size:16.0px;font-family:Arial,sans-serif;">All, I made a minor clarification in the fifth issue.</span></p></div><div ><p class="MsoNormal"><span style="font-size:16.0px;font-family:Arial,sans-serif;"> </span></p></div><div ><p class="MsoNormal"><span style="font-size:16.0px;font-family:Arial,sans-serif;">Thanks,</span></p></div><div ><p class="MsoNormal"><span style="font-size:16.0px;font-family:Arial,sans-serif;">Darcy</span></p></div></div><p class="MsoNormal"> </p><div ><div ><p class="MsoNormal">On Tue, Jul 9, 2019 at 8:26 AM <<a href="mailto:philippe.fouquart@orange.com" target="_blank">philippe.fouquart@orange.com</a>> wrote:</p></div><div ><div ><p class="MsoNormal"><span style="font-size:13.0px;font-family:Arial,sans-serif;color:black;">Thanks (and I don’t even have the holidays to blame :s ). Both Ayden’s points, and the rephrasing suggested
by Darcy are excellent. </span></p><p class="MsoNormal"><span style="font-size:13.0px;font-family:Arial,sans-serif;color:black;"> </span></p><p class="MsoNormal"><span style="font-size:13.0px;font-family:Arial,sans-serif;color:black;">The first item relative to community’s input has been raised a number of times; I remember asking a question
during a CSG meeting with the Board in Kobe. Not that the answer was unsatisfactory but it was hardly practical.
</span></p><p class="MsoNormal"><span style="font-size:13.0px;font-family:Arial,sans-serif;color:black;"> </span></p><p class="MsoNormal"><span style="font-size:13.0px;font-family:Arial,sans-serif;color:black;">Ultimately, I think we need to keep in mind the primary goal of all this, ie (I think) should there be
a “new GDPR in the making” (in terms of having an impact on policies), the community should be able to detect it with this tool. I’m not sure it would in its current state, so the points are well made.
</span></p><p class="MsoNormal"><span style="font-size:13.0px;font-family:Arial,sans-serif;color:black;"> </span></p><p class="MsoNormal"><span style="font-size:13.0px;font-family:Arial,sans-serif;color:black;">Regards,</span></p><p class="MsoNormal"><span style="font-size:13.0px;font-family:Arial,sans-serif;color:black;">Philippe</span></p><p class="MsoNormal"><span style="font-size:13.0px;font-family:Arial,sans-serif;color:black;"> </span></p><div ><div style="border-style:solid none none;border-top-width:1.0px;border-top-color:#b5c4df;padding:4.0px .0cm .0cm;"><p class="MsoNormal"><b ><span style="font-size:13.0px;font-family:Tahoma,sans-serif;">From:</span></b><span style="font-size:13.0px;font-family:Tahoma,sans-serif;"> council [mailto:<a href="mailto:council-bounces@gnso.icann.org" target="_blank">council-bounces@gnso.icann.org</a>]
<b >On Behalf Of </b>McGrady, Paul D.<br ><b >Sent:</b> Monday, July 08, 2019 1:30 PM<br ><b >To:</b> Darcy Southwell; Ayden Férdeline; Steve Chan<br ><b >Cc:</b> <a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a>;
<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a><br ><b >Subject:</b> Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements</span></p></div></div><p class="MsoNormal"> </p><p class="MsoNormal"><span style="color:#1f497d;">Thanks Darcy. These edits look great. Sorry so slow in responding. I was overtaken by the holiday!</span></p><p class="MsoNormal"><span style="color:#1f497d;"> </span></p><p class="MsoNormal"><span style="color:#1f497d;">Best,</span></p><p class="MsoNormal"><span style="color:#1f497d;">Paul</span></p><p class="MsoNormal"><span style="color:#1f497d;"> </span></p><p class="MsoNormal"><span style="color:#1f497d;"> </span></p><div ><div style="border-style:solid none none;border-top-width:1.0px;border-top-color:#e1e1e1;padding:4.0px .0cm .0cm;"><p class="MsoNormal"><b >From:</b> Darcy Southwell <<a href="mailto:darcy.southwell@endurance.com" target="_blank">darcy.southwell@endurance.com</a>>
<br ><b >Sent:</b> Monday, July 1, 2019 6:58 PM<br ><b >To:</b> McGrady, Paul D. <<a href="mailto:PMcGrady@taftlaw.com" target="_blank">PMcGrady@taftlaw.com</a>>; Ayden Férdeline <<a href="mailto:icann@ferdeline.com" target="_blank">icann@ferdeline.com</a>>; Steve Chan <<a href="mailto:steve.chan@icann.org" target="_blank">steve.chan@icann.org</a>><br ><b >Cc:</b> <a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a>;
<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a><br ><b >Subject:</b> Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements</p></div></div><p class="MsoNormal"> </p><p class="MsoNormal"><span style="font-family:Candara,sans-serif;">Thanks for taking the lead, Ayden, and for your edits, Paul. I support Paul’s edits. I have proposed some additional edits in addition
to Paul’s in the attached.</span></p><p class="MsoNormal"><span style="font-family:Candara,sans-serif;"> </span></p><p class="MsoNormal"><span style="font-family:Candara,sans-serif;">I think it may be better received if we qualify what we’re seeking from ICANN Org, rather than referencing ICANN activities, which
could be perceived as so sweepingly broad that it’s not doable.</span></p><p class="MsoNormal"><span style="font-family:Candara,sans-serif;"> </span></p><p class="MsoNormal"><span style="font-family:Candara,sans-serif;">Thanks,</span></p><p class="MsoNormal"><span style="font-family:Candara,sans-serif;">Darcy</span></p><p class="MsoNormal"><span style="font-family:Candara,sans-serif;"> </span></p><div style="border-style:solid none none;border-top-width:1.0px;border-top-color:#b5c4df;padding:4.0px .0cm .0cm;"><p class="MsoNormal"><b ><span style="color:black;">From:
</span></b><span style="color:black;">council <<a href="mailto:council-bounces@gnso.icann.org" target="_blank">council-bounces@gnso.icann.org</a>> on behalf of "McGrady, Paul D." <<a href="mailto:PMcGrady@taftlaw.com" target="_blank">PMcGrady@taftlaw.com</a>><br ><b >Date: </b>Sunday, June 30, 2019 at 8:28 AM<br ><b >To: </b>Ayden Férdeline <<a href="mailto:icann@ferdeline.com" target="_blank">icann@ferdeline.com</a>>, Steve Chan <<a href="mailto:steve.chan@icann.org" target="_blank">steve.chan@icann.org</a>><br ><b >Cc: </b>"<a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a>" <<a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a>>, "<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 >Subject: </b>Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements</span></p></div><div ><p class="MsoNormal"> </p></div><p class="MsoNormal"><span style="color:#1f497d;">Thanks Ayden.</span></p><p class="MsoNormal"><span style="color:#1f497d;"> </span></p><p class="MsoNormal"><span style="color:#1f497d;">All, attached is a revision version with a few edits, mostly around tone.
</span></p><p class="MsoNormal"><span style="color:#1f497d;"> </span></p><p class="MsoNormal"><span style="color:#1f497d;">Best,</span></p><p class="MsoNormal"><span style="color:#1f497d;">Paul</span></p><p class="MsoNormal"><span style="color:#1f497d;"> </span></p><p class="MsoNormal"><span style="color:#1f497d;"> </span></p><p class="MsoNormal"><span style="color:#1f497d;"> </span></p><p class="MsoNormal"> </p><p ><span style="font-size:13.0px;font-family:Arial,sans-serif;color:#816d5c;">This message may contain information that is attorney-client privileged, attorney work product or otherwise confidential. If you are not an intended recipient, use and disclosure
of this message are prohibited. If you received this transmission in error, please notify the sender by reply e-mail and delete the message and any attachments.</span></p><p class="MsoNormal"><b >From:</b> council <<a href="mailto:council-bounces@gnso.icann.org" target="_blank">council-bounces@gnso.icann.org</a>>
<b >On Behalf Of </b>Ayden Férdeline<br ><b >Sent:</b> Sunday, June 30, 2019 6:25 AM<br ><b >To:</b> Steve Chan <<a href="mailto:steve.chan@icann.org" target="_blank">steve.chan@icann.org</a>><br ><b >Cc:</b> <a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a>;
<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a><br ><b >Subject:</b> Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements</p><p class="MsoNormal"> </p><div ><p class="MsoNormal">I have drafted a message on behalf of the Council for Council's consideration on this topic. This is based upon our previous conversations. Please find attached and pasted below
my signature. Thanks.</p></div><div ><p class="MsoNormal"> </p></div><div ><p class="MsoNormal">Ayden Férdeline
</p></div><div ><p class="MsoNormal">--</p></div><div ><p class="MsoNormal"> </p></div><div ><p class="MsoNormal"><b >Recommended Improvements from the GNSO Council on ICANN Org Legislative Statement</b></p></div><div ><p class="MsoNormal"> </p></div><div ><p class="MsoNormal">The GNSO Council supports ICANN org in its initiative to identify legislative and regulatory efforts across the globe that may have impacts on ICANN activities. However, we have
some recommended improvements to the approach that ICANN org takes.</p></div><ul ><li class="MsoNormal">
First, the GNSO Council believes that the current, crowdsourced approach where the community is expected to identify errors and omissions in the Global Legislative and Regulatory Developments Report is inappropriate. If ICANN is a professional organization
then its professional staff should be comprehensively monitoring the regulatory landscape within which we operate.</li><li class="MsoNormal">
Second, we encourage ICANN org to conduct proper regulatory impact assessments so that the community can understand the intended rationale for a law/regulation/directive, specific extracts of the proposed text that could have implications on activities within
ICANN’s remit, and outline concretely what implications are anticipated for ICANN. A timeline should be included so we understand how imminent the law/regulation/directive is and when we need to take action.
</li><li class="MsoNormal">
Third, we encourage ICANN org to partner with a professional firm to receive regular updates (at least every three months) focused on those key regions which cause the majority of concerns. These reports must be made available to ICANN community members in
a timely manner.</li><li class="MsoNormal">
Fourth, while the GNSO Council would be pleased to accept ongoing monitoring reports, we would also welcome the opportunity to be briefed at our face-to-face meetings by ICANN’s government relations team and to enter into a dialogue about issues that have the
potential to cause us concern. </li><li class="MsoNormal">
Fifth, once a law or regulation has been adopted, ICANN org must undertake a compliance assessment in order to fully understand what implications there may or may not be on ICANN activities.</li><li class="MsoNormal">
Sixth, the GNSO Council considers the GAC to be an important partner in these discussions and we would be delighted if they are able to alert us to potentially problematic legislation. However, we understand that often the GAC is not in a position to be able
to do so, so we believe the onus must ultimately fall on ICANN org to structure the dialogue and to monitor regulatory and legislative developments.</li></ul><div ><p class="MsoNormal"> Thank you for welcoming our input.</p></div><div ><p class="MsoNormal"> </p></div><div ><p class="MsoNormal"><span style="font-family:Cambria Math,serif;">‐‐‐‐‐‐‐</span> Original Message
<span style="font-family:Cambria Math,serif;">‐‐‐‐‐‐‐</span></p></div><div ><p class="MsoNormal">On Sunday, 23 June 2019 18:01, Steve Chan <<a href="mailto:steve.chan@icann.org" target="_blank">steve.chan@icann.org</a>> wrote:</p></div><div ><p class="MsoNormal"> </p></div><div ><p >Dear Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana,</p><p > </p><p >In reviewing the Council’s action items, we recognized that the item below is still outstanding:</p><p > </p><p style="margin-left:48.0px;"><i >Small group of Councilors</i> to develop draft message to ICANN Org to provide input on legislative tracker. Based on feedback, Council leadership to consider scheduling follow up discussion at ICANN65. </p><p > </p><p >We wanted to bring this to your attention, as you all volunteered to work on this item. While the latter part of the action item (e.g., engaging at ICANN65) is likely impractical at this point, you may still want to draft a message to send to ICANN org.
As Keith noted, please work together and let staff know if you need any assistance.</p><p > </p><p >Best,</p><p >Steve</p><p > </p><div style="border-style:solid none none;border-top-width:1.0px;border-top-color:#b5c4df;padding:4.0px .0cm .0cm;"><p ><b ><span style="color:black;">From: </span></b><span style="color:black;">council <<a href="mailto:council-bounces@gnso.icann.org" target="_blank">council-bounces@gnso.icann.org</a>> on behalf of "Drazek, Keith via council" <<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a>><br ><b >Reply-To: </b>"Drazek, Keith" <<a href="mailto:kdrazek@verisign.com" target="_blank">kdrazek@verisign.com</a>><br ><b >Date: </b>Thursday, April 4, 2019 at 7:35 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>" <<a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a>><br ><b >Subject: </b>[council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements</span></p></div><div ><p > </p></div><p >Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana:</p><p > </p><p >During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort.</p><p > </p><p >As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities.
While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development.</p><p > </p><p >Please work together and with Staff to help kick off this important and timely work.</p><p > </p><p >Thanks,</p><p >Keith</p><p > </p><p > </p><p > </p><p > </p></div><div ><p class="MsoNormal"> </p></div><p class="MsoNormal"><br ><span style="font-size:10.0px;font-family:Arial,sans-serif;color:gray;"><br ></span>_______________________________________________ council mailing list <a href="mailto:council@gnso.icann.org" target="_blank">
council@gnso.icann.org</a> <a href="https://mm.icann.org/mailman/listinfo/council" target="_blank">
https://mm.icann.org/mailman/listinfo/council</a> _______________________________________________ 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 (<a href="https://www.icann.org/privacy/policy" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" target="_blank">https://www.icann.org/privacy/tos</a>). 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.</p><p class="MsoNormal" style="margin-bottom:16.0px;"> </p></div><pre >_________________________________________________________________________________________________________________________</pre><pre > </pre><pre >Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc</pre><pre >pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler</pre><pre >a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,</pre><pre >Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.</pre><pre > </pre><pre >This message and its attachments may contain confidential or privileged information that may be protected by law;</pre><pre >they should not be distributed, used or copied without authorisation.</pre><pre >If you have received this email in error, please notify the sender and delete this message and its attachments.</pre><pre >As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.</pre><pre >Thank you.</pre></div></div></div></blockquote></div>