<div dir='auto'>Let's start with a short survey to all GAC participants during ICANN65, to test their level of involvement with their local legislation relating to the DNS. We may get some leads.....<br><br><div data-smartmail="gmail_signature">Thanks! Carlos Raúl Gutiérrez</div></div><div class="gmail_extra"><br><div class="gmail_quote">El 10 abr. 2019 7:27, Erika Mann <erika@erikamann.com> escribió:<br type="attribution" /><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Carlos - we can add the GAC to the list as an important partner but I doubt many will be able in alerting ICANN about potentially problematic legislations they're or their parliaments are drafting. In many cases they will not even know. For example, I'm doubtful that the European Parliament, the European Commission or European Member States are aware about potentially - for the domain sector - problematic aspects of the copyright law they recently all supported. <div>Erika</div></div><br /><div class="elided-text"><div dir="ltr">On Wed, Apr 10, 2019 at 2:26 PM Carlos Raul Gutierrez <<a href="mailto:carlosraul@gutierrez.se">carlosraul@gutierrez.se</a>> wrote:<br /></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb( 204 , 204 , 204 );padding-left:1ex"><div dir="auto">A lot of good ideas but I don't see the GAC in any of those. The most probable source or shapping force of any initiative that may be closely related and affect the DNS is sitting in the next room at every meeting. What about asking them?<br /><br /><div>Thanks! Carlos Raúl Gutiérrez</div></div><div><br /><div class="elided-text">El 10 abr. 2019 4:01, Erika Mann <<a href="mailto:erika@erikamann.com">erika@erikamann.com</a>> escribió:<br type="attribution" /><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb( 204 , 204 , 204 );padding-left:1ex"><div dir="ltr">Keith, All - <div><br /></div><div>I believe the current format and information gathering practice (<a href="https://www.icann.org/en/system/files/files/legislative-regulatory-30jan19-en.pdf">https://www.icann.org/en/system/files/files/legislative-regulatory-30jan19-en.pdf</a>) is not sufficient and would therefore recommend few things:</div><div><ul><li>ICANN ORG should work with a professional firm in receiving regular updates (monitoring report) about regulatory issues that cause concern </li><li><ul><li>To make such a Monitoring Report (MR) not too expensive </li><li><ul><li>ICANN should focus on few regions, regions that cause the majority of concerns</li><li>Monitoring reports should be received 4 times/year </li><li>Early warning notes should be received as quickly as possible</li></ul></li></ul></li><li>The current Crowed Sourced Tracking Report should remain as an additional information source <a href="https://www.icann.org/en/system/files/files/legislative-regulatory-30jan19-en.pdf">https://www.icann.org/en/system/files/files/legislative-regulatory-30jan19-en.pdf</a></li><li>I agree with Paul that it is key "CANN’s government relations folks to visit us at Council and highlight the main issues it sees heading our way"</li><li>I agree with Flip, the list of topics that should be monitored need to be broadened</li><li>I agree with Ayden to some degree but recommend to focus on few aspect "ICANN should monitor 1) the impact the law/regulation/directive has had as it relates to ICANN's remit" and, once a legislation is introduced, ICANN must do a compliance assessment. I don't believe that lobbying strategies should be broadly discussed in the community. </li><li>I agree with Martin, the Crowed Sourced Tracking Report should cooperate with existing Regional Intelligence Tracking Reports. </li></ul><div>Kind regards, </div></div><div>Erika</div><div><br /></div></div><br /><div><div dir="ltr">On Thu, Apr 4, 2019 at 8:35 PM Drazek, Keith via council <<a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>> wrote:<br /></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb( 204 , 204 , 204 );padding-left:1ex">
<div>
<div>
<p>Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana:<u></u><u></u></p>
<p><u></u> <u></u></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.
<u></u><u></u></p>
<p><u></u> <u></u></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.<u></u><u></u></p>
<p><u></u> <u></u></p>
<p>Please work together and with Staff to help kick off this important and timely work.<u></u><u></u></p>
<p><u></u> <u></u></p>
<p>Thanks,<u></u><u></u></p>
<p>Keith<u></u><u></u></p>
<p><u></u> <u></u></p>
<p><u></u> <u></u></p>
<p><u></u> <u></u></p>
<p><u></u> <u></u></p>
</div>
</div>
_______________________________________________<br />
council mailing list<br />
<a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a><br />
<a href="https://mm.icann.org/mailman/listinfo/council">https://mm.icann.org/mailman/listinfo/council</a><br />
</blockquote></div>
</blockquote></div><br /></div></blockquote></div>
</blockquote></div><br></div>