<div dir="ltr"><div class="gmail_default" style=""><div class="gmail_default" style="text-align:start;text-indent:0px;text-decoration-style:initial;text-decoration-color:initial;background-color:rgb(255,255,255)"><font face="verdana, sans-serif" style=""><font face="arial, sans-serif"><span style="font-size:12.8px">I allocated some of the Board questions to names. You will be in charge of reading them and the </span></font><span style="font-size:12.8px">questions</span><font face="arial, sans-serif"><span style="font-size:12.8px"> are in order of priority. We might not get to ask them all. </span></font></font></div><div class="gmail_default" style="font-family:arial,sans-serif;color:rgb(34,34,34);font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;background-color:rgb(255,255,255)"><font face="verdana, sans-serif"><br></font></div><div class="gmail_default" style="font-family:arial,sans-serif;color:rgb(34,34,34);font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;background-color:rgb(255,255,255)"><font face="verdana, sans-serif"><br></font></div><div class="gmail_default" style="font-family:arial,sans-serif;color:rgb(34,34,34);font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;background-color:rgb(255,255,255)"><font face="verdana, sans-serif">1. ICANN and GDPR compliance: there are still issues with compliance models offered by ICANN such as lack of data minimization, maintaining thick data and giving power to GAC to come up with the tiered access and certification. Does the<span> </span><span class="gmail-il">board</span><span> </span>see these aspects of the models as problematic? we would like to know the opinion of<span> </span><span class="gmail-il">Board</span><span> </span>on these issues. (Stephanie Perrin)</font></div><div class="gmail_default" style="font-family:arial,sans-serif;color:rgb(34,34,34);font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;background-color:rgb(255,255,255)"><font face="verdana, sans-serif"><br></font></div><div class="gmail_default" style="font-family:arial,sans-serif;color:rgb(34,34,34);font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;background-color:rgb(255,255,255)"><font face="verdana, sans-serif">2. Although we had talked to some<span> </span><span class="gmail-il">Board</span><span> </span>members about the<span> </span><span class="gmail-il">jurisdiction</span><span> </span>subgroup recommendations and their importance to facilitate global access to DNS,<span> </span><span class="gmail-il">Board</span><span> </span>Comments on<span> </span><span class="gmail-il">Jurisdiction</span><span> </span>Sub Group were far from positive.  For example, it was even suggested by the<span> </span><span class="gmail-il">board</span><span> </span>to consider opportunity costs in the study that needs to be done for seeking a general OFAC license. Global access to DNS is in ICANN mission if the<span> </span><span class="gmail-il">Board </span>believes that then asking to do opportunity costs for something that enables ICANN to do its mission might not be workable. There are other examples of not supportive comments to<span> </span><span class="gmail-il">jurisdiction</span><span> </span>recommendations which we will discuss during the meeting if needed. (Farzaneh Badiei)</font></div><div class="gmail_default" style="font-family:arial,sans-serif;color:rgb(34,34,34);font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;background-color:rgb(255,255,255)"><font face="verdana, sans-serif"><br></font></div><div class="gmail_default" style="font-family:arial,sans-serif;color:rgb(34,34,34);font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;background-color:rgb(255,255,255)"><font face="verdana, sans-serif">3. Some of the budget cuts at ICANN will directly or indirectly affect our policy work. ICANN has an increase in personnel budget while there are a lot of cuts in community budget, and GNSO policy team which supports the GNSO policy development has had serious cuts. Community Additional Budget Request has been reduced by half and CROP was removed from this year budget without any announcement. We want to know the opinion of<span> </span><span class="gmail-il">Board</span><span> </span>about these cuts. (Ayden)</font></div><div class="gmail_default" style="font-family:arial,sans-serif;color:rgb(34,34,34);font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;background-color:rgb(255,255,255)"><font face="verdana, sans-serif"><br></font></div><div class="gmail_default" style="font-family:arial,sans-serif;color:rgb(34,34,34);font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;background-color:rgb(255,255,255)"><br></div><div class="gmail_default" style="font-family:arial,sans-serif;color:rgb(34,34,34);font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;background-color:rgb(255,255,255)"><font face="verdana, sans-serif">4. CCT-Review- Implementation: We are concerned about CCT-Review recommendations. Some of their very controversial recommendations been supported by GAC.  The Review team has gone so far to recommend a contractual change (it recommends it to ICANN<span> </span><span class="gmail-il">Board</span>, GNSO, and a WG). The change (which we opposed in our public comment) says that:[ A. Consider directing ICANN org, in its discussions with registries, to negotiate amendments to existing Registry Agreements, or in negotiations of new Registry Agreements associated with subsequent rounds of new gTLDs to include provisions in the agreements providing incentives, including financial incentives for registries, especially open registries, to adopt proactive anti-abuse measures.] At the moment we don't see our comments on their recommendations being given due consideration. How does the<span> </span>board plan to implement these CCT-Review recommendations and what would be the implications if the final version of review does not include community comments? (Rafik Dammak)</font></div><div class="gmail_default" style="font-family:arial,sans-serif;color:rgb(34,34,34);font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;background-color:rgb(255,255,255)"><font face="verdana, sans-serif"><br></font></div><div class="gmail_default" style="font-family:arial,sans-serif;color:rgb(34,34,34);font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;background-color:rgb(255,255,255)"><font face="verdana, sans-serif"><br></font></div><div class="gmail_default" style="font-family:arial,sans-serif;color:rgb(34,34,34);font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;background-color:rgb(255,255,255)"><font face="verdana, sans-serif"><div class="gmail_default" style="color:rgb(34,34,34);font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)"><font face="verdana, sans-serif" style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-transform:none;white-space:normal;word-spacing:0px">4. On many levels, GAC advice has been given undue attention. Post IANA transition, we would like the<span> </span><span class="gmail-il">Board</span><span> </span>to honor ICANN bylaws and not look at GAC whenever it does not have a solution for a problem. This has been happening, for example in the GDPR models suggested by ICANN, (in the second model) GAC has the primary role of certification. What should we do so that the<span> </span><span class="gmail-il">Board</span><span> </span>does not look at GAC as a source of solutions in matters related to GNSO remit? [this also happened in the<span> </span><span class="gmail-gr_ gmail-gr_48 gmail-gr-alert gmail-gr_spell gmail-gr_inline_cards gmail-gr_run_anim gmail-ContextualSpelling gmail-ins-del gmail-multiReplace" id="gmail-48" style="display:inline;border-bottom:2px solid transparent;background-repeat:no-repeat;color:inherit;font-size:inherit">two letter</span><span> </span>second level domain names that correspond with country codes (ccTLD).<span> </span><span class="gmail-il">Board</span><span> </span>considered GAC advice which was not even based on consensus and implemented it without any consultation with GNSO although the two letters consisted of generic names. Please refer to<span> </span><span class="gmail-il">NCSG</span><span> </span>public comment on this issue for more information: </font><font face="verdana, sans-serif"><span style="font-size:12.8px"><a href="https://forum.icann.org/lists/comments-proposed-measures-two-char-08jul16/pdf7DRdQjpIWq.pdf" target="_blank" style="color:rgb(17,85,204)">https://forum.<wbr>icann.org/lists/comments-<wbr>proposed-measures-two-char-<wbr>08jul16/pdf7DRdQjpIWq.pdf</a></span></font><span style="color:rgb(34,34,34);font-family:verdana,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-transform:none;white-space:normal;word-spacing:0px">] (Tatiana Tropina)</span></div><br class="gmail-Apple-interchange-newline"><br></font></div><br clear="all"></div><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><font face="verdana, sans-serif">Farzaneh </font></div></div></div></div>
</div>