<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">Returning to this thread to talk about accuracy. </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Keith sent the draft response of the council (attached) today. The letter acknowledged the receipt of the CEO letter about accuracy and suggested to the CEO that the council will discuss and provides guidance.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Interpreting from the CEO letter, I believe ICANN org has <a href="https://gnso.icann.org/sites/default/files/file/field-file-attach/marby-to-drazek-21jun19-en.pdf">stopped carrying out ARS </a> because ICANN is not certain whether it can access personal information in WHOIS directory to undertake the check. This might be because ICANN does not want to accept that it is a joint controller so asking whether EPDP has plans to facilitate such access for ICANN. </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Perhaps ICANN wants to have a data processing agreement with the CPs to be able to carry out the accuracy checks. I am not sure. What I know is that phase 2 of EPDP is about "the disclosure of the data to the third parties". But ICANN most certainly is not a third party in this situation. So I don't know how EPDP can help ICANN in this situation.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">I think ICANN org needs to clarify why it cannot carry out the service. They imply that because WHOIS is not public anymore they can't do it. But can they have access to data through a data processing agreement with CPs? I really don't know how and who should be discussing this. Especially because ARS was not a consensus policy! </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><font face="verdana, sans-serif">Farzaneh </font></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Aug 14, 2019 at 9:03 PM farzaneh badii <<a href="mailto:farzaneh.badii@gmail.com">farzaneh.badii@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">Thanks Rafik. </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">I don't think I can attend our policy meeting so discussing on the mailing list:</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">1. <b><a href="https://gnso.icann.org/sites/default/files/file/field-file-attach/chalaby-to-drazek-15may19-en.pdf" target="_blank">Board rejection of EPDP recommendation 12 </a>to delete data from the organization field</b>: The reason the board has rejected this recommendation is concerning. The Board justifies the rejection by arguing that: </div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">"The Board action is in the best interests of ICANN and the community and will serve<b> <font color="#ff0000">the global public interest </font></b>by allowing ICANN and gTLD registry operators..."</blockquote><div> </div><div><div class="gmail_default" style="font-family:verdana,sans-serif">I turned the global public interest red in the text. I don't think the Board has explained well enough why it is not in the "global public interest" to delete the organization field. While on the first page of the letter board says deletion of org field is not in the global public interest, in Annex A it says that: "The Board
requests that as part of Phase 2, the EPDP
consider the extent to which deletion (as
opposed to redaction) that results in loss of or
changes to the name of the registrant is in the
public interest and consistent with ICANN’s
mission." so what will happen if EPDP phase 2 says that there is no problem with deletion of org field and doesnt violate the global public interest? Does the board oblige? </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">To argue a bit substantively (I know the council doesn't do that):</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Note that the board does not oppose redaction of the field but it opposes the deletion of the field. In Annex A in the synopsis column, it says that "Once implemented the
Recommendation may result in loss of
identifying information about who the
registrant is." ICANN is not in the business of identifying the registrant and who the registrant is. The registration directory should ensure that the registrant is contactable. I also don't follow the argument that by deleting the org field, there will be loss of identifying information about who the registrant is! Loss of contactability should matter. As far as I know, the registrant has to provide the first name and last name and email address phone number etc (redacted) even if from an organization. </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">I have attached the Council draft response. <br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">It would be good to know what would happen if EPDP phase 2 still comes to the conclusion that it is in the interest of to delete this field. Did I miss something mentioned about it somewhere?</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">In general I think the Board needs to be much clearer in explaining its rationale when it rejects policy recommendations because of "global public interest". More than once the IRP has ruled that the Board has to state reasons as to why something is not in the public interest. I think that is a procedural issue which the council might want to add to its letter. </div><div class="gmail_default" style="font-family:verdana,sans-serif">One board member voted against the resolution (though against the non approval of recommendation 1 purpose 2). I think we need to carefully read these arguments. <a href="https://www.icann.org/en/system/files/files/director-voting-statement-resolution-gnso-epdp-recs-temp-spec-gtld-registration-data-15may19-en.pdf" style="font-family:Arial,Helvetica,sans-serif" target="_blank">https://www.icann.org/en/system/files/files/director-voting-statement-resolution-gnso-epdp-recs-temp-spec-gtld-registration-data-15may19-en.pdf</a></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">I will comment on Accuracy soon.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div><div dir="ltr" class="gmail-m_4011678932018038556m_2639835793245639237gmail_signature"><div dir="ltr"><div><font face="verdana, sans-serif">Farzaneh </font></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Aug 14, 2019 at 6:29 PM Rafik Dammak <<a href="mailto:rafik.dammak@gmail.com" target="_blank">rafik.dammak@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div>Hi all,</div><div dir="auto"><br></div><div dir="auto">You will find below the agenda for the next GNSO Council meeting. We will have as usual our NCSG Policy meeting next week prior to it and we will go through that agenda.</div><div dir="auto"><br></div><div dir="auto">Best Regards,</div><div dir="auto"><br></div><div dir="auto">Rafik </div><div dir="auto"><br></div><div dir="auto"><br><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">---------- Forwarded message ---------<br><br></div>
<div lang="EN-US">
<div class="gmail-m_4011678932018038556gmail-m_2639835793245639237gmail-m_16645776936372392m_-6892338079487375289WordSection1">
<p class="MsoNormal"><span style="font-size:11pt">Dear all,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt">Please below find the final proposed agenda for the GNSO Council Meeting on 22 August 2019 at 12:00 UTC</span><u></u><u></u></p>
<h1 style="margin-right:0in;margin-bottom:6pt;margin-left:0in">
<a name="m_4011678932018038556_m_2639835793245639237_m_16645776936372392_m_-6892338079487375289__cj23lp5puih8" rel="noreferrer"></a><span style="font-size:23pt;color:black">Final GNSO Council Agenda 22 August 2019 </span><span style="font-family:Calibri,sans-serif"><u></u><u></u></span></h1>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access:
</span><a href="https://community.icann.org/x/Ba_jBg" rel="noreferrer" target="_blank"><span style="color:rgb(17,85,204)">https://community.icann.org/x/Ba_jBg</span></a><span style="color:black"> </span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">This agenda was established according to the
</span><a href="https://gnso.icann.org/en/council/op-procedures-30jan18-en.pdf" rel="noreferrer" target="_blank"><span style="color:rgb(17,85,204)">GNSO Operating Procedures</span></a><span style="color:black"> v3.3, updated on 30 January 2018</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">For convenience:</span><u></u><u></u></p>
<ul style="margin-top:0in" type="disc">
<li style="color:black;margin-top:0in;margin-bottom:0.0001pt;vertical-align:baseline">
An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda.<u></u><u></u></li><li style="color:black;margin-top:0in;margin-bottom:0.0001pt;vertical-align:baseline">
An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda.<u></u><u></u></li></ul>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">GNSO Council meeting held at 12:00 UTC</span><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">Coordinated Universal Time: 12:00 UTC:
</span><a href="https://tinyurl.com/y2qdox2m" rel="noreferrer" target="_blank"><span style="color:rgb(17,85,204);background:white">https://tinyurl.com/y2qdox2m</span></a><span style="color:black;background:white"> </span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">05:00 Los Angeles; 08:00 Washington; 13:00 London; 17:00 Islamabad; 21:00 Tokyo; 22:00 Melbourne </span><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><b><span style="color:rgb(51,51,51)">GNSO Council Meeting Audio Cast</span></b><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:rgb(51,51,51)">Listen in browser:</span><span style="color:black">
</span><span style="color:rgb(51,51,51);background:rgb(252,252,252)"> </span><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000_stream02&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=k7uKdjSb7_ZjItyVqrCYHo_rKms9SFxlmbYEJqG-y9I&m=t8tA0swdFU4cXV859e2ze-mvsKMIL7r2xdUjAVSq8kY&s=iX9P_cnifF6wZ1CUhDXJ72aamEebgCvf5_hNTB9MCMQ&e=" rel="noreferrer" target="_blank"><span style="color:rgb(0,82,204);background:rgb(252,252,252)">http://stream.icann.org:8000/stream02 </span></a><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:rgb(51,51,51)">Listen in application such as iTunes:
</span><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000_stream02.m3u&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=k7uKdjSb7_ZjItyVqrCYHo_rKms9SFxlmbYEJqG-y9I&m=t8tA0swdFU4cXV859e2ze-mvsKMIL7r2xdUjAVSq8kY&s=UG8nMX2K5hLP9_ULPQa-Pf4eURwavq2yvx1a2lCZrGw&e=" rel="noreferrer" target="_blank"><span style="color:rgb(0,82,204);background:rgb(252,252,252)">http://stream.icann.org:8000/stream02.m3u </span></a><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black">Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call.</span><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">___________________________________</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><b><span style="color:black">Item 1: Administrative Matters (10 mins)</span></b><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">1.1 - Roll Call</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">1.2 - Updates to Statements of Interest</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">1.3 - Review / Amend Agenda</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: </span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><a href="https://gnso.icann.org/sites/default/files/policy/2019/minutes/Draft%20minutes%2026%20June%202019%20GNSO%20Council.pdf" rel="noreferrer" target="_blank"><span style="color:rgb(17,85,204);background:white">Minutes</span></a><span style="color:black;background:white">
of the GNSO Council meeting on the 26 June 2019 were posted on the 13 July 2019</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><a href="https://gnso.icann.org/sites/default/files/policy/2019/minutes/draft-minutes-18jul2019-gnso-council-en.pdf" rel="noreferrer" target="_blank"><span style="color:rgb(17,85,204);background:white">Minutes</span></a><span style="color:black;background:white">
of the GNSO Council meeting on the 18 July 2019 were posted on the 02 August 2019</span><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in 0in 0.0001pt"><b><span style="color:black">Item 2: Opening Remarks / Review of Projects & Action List (10 minutes)</span></b><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of
</span><a href="https://gnso.icann.org/en/council/project" rel="noreferrer" target="_blank"><span style="color:rgb(17,85,204)">Projects List
</span></a><span style="color:black">and </span><a href="https://community.icann.org/x/RgZlAg" rel="noreferrer" target="_blank"><span style="color:rgb(17,85,204)">Action Item List</span></a><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black"> </span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><b><span style="color:black">Item 3: Consent Agenda (0 minutes) </span></b><u></u><u></u></p>
<ul style="margin-top:0in" type="disc">
<li style="color:black;margin-top:0in;margin-bottom:0.0001pt;vertical-align:baseline">
None<u></u><u></u></li></ul>
<p style="margin:0in 0in 0.0001pt"><b><span style="color:black"> </span></b><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><b><span style="color:black">Item 4: COUNCIL DISCUSSION - GNSO Council Letter on Status of Consultation in Relation to Non-Adopted EPDP Phase 1 Parts of Recommendations (purpose 2 and recommendation #12) (15 minutes) </span></b><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">On 15 May, the ICANN Board</span><a href="https://gnso.icann.org/sites/default/files/file/field-file-attach/chalaby-to-drazek-15may19-en.pdf" rel="noreferrer" target="_blank"><span style="color:rgb(17,85,204)"> informed</span></a><span style="color:black">
the GNSO Council of the Board’s action in relation to the GNSO’s EPDP Phase 1policy recommendations. The Board did not adopt two of the recommendations in full, where the Board has identified that portions of those recommendations are not in the best interests
of the ICANN Community or ICANN and is initiating the consultation process between the Board and the GNSO Council. This concerns recommendation #1, purpose 2 and recommendation #12, deletion of data in the Organization field. As required under the ICANN Bylaws
at Annex A-1,Section 6.b, a Board Statement is attached as Annex A to the letter, articulating the reasons for the Board’s non-adoption of these two items. As per the Bylaw requirements (Annex A-1, Section 6.c), “the Council shall review the Board Statement
for discussion with the Board as soon as feasible after the Council's receipt of the Board Statement.” During the Council’s Extraordinary Meeting on 28 May 2019, it reviewed the Board Statement and conducted a lengthy discussion on the best path forward.</span><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">On 30 May 2019, Keith Drazek, the GNSO Chair provided an update
<span style="background:rgb(252,252,252)">to the EPDP Team on the expected next steps in relation to the ICANN Board’s action on Phase 1 recommendations
</span>and requested that the EPDP Team provide input to identify any questions, comments or concerns in relation to ICANN Board’s action on the EPDP Phase 1 Recommendations. Subsequently, on 9 June 2019,
<span style="background:white">Janis Karklins, </span>Chair of the EPDP, informed the GNSO Chair of the following preliminary input noting that
<span style="background:white">there was not sufficient time to formalize and agree on an EPDP Team response:</span></span><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black;background:white">“• In relation to purpose 2, there is a general understanding for why the Board decided to not adopt this purpose and the EPDP Team confirms that it considers it
firmly within its scope for phase 2 to further review this purpose in the context of the System for Standardized Access / Disclosure (SSAD);</span><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black;background:white">• For recommendation #12, some additional context has been provided that may help explain the thinking behind the EPDP Team’s original recommendation. However, there
is no agreement at this stage on whether or not the Board’s non-adoption should be supported.”</span><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">During the Council’s June 2019 meeting, it continued to consider the
</span><a href="https://mm.icann.org/pipermail/council/2019-May/022754.html" rel="noreferrer" target="_blank"><span style="color:rgb(17,85,204)">next steps</span></a><span style="color:black">, taking into account a discussion with the ICANN Board at ICANN65. The reasoning and intent of the deletion
part of recommendation #12 was explained to the Board, as well as the intent of purpose 2 and it was agreed that a letter should be drafted and sent to the ICANN Board as well as the EPDP Team to provide an update on the current thinking of the GNSO Council
and likely next steps. </span><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">During the Council’s July 2019 meeting, the Council reviewed the draft letter to be sent to the ICANN Board and the EPDP Team. Based on the input received during the call as well as subsequently
on the mailing list, Council leadership circulated a revised version for review on [date]. </span><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">Here, the Council will review the revised letter to be sent to the ICANN Board.</span><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">See also Annex A-1, Section 6. Board Approval Process below for further details.</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black"> </span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><i><span style="color:black">Section 6.<b> Board Approval Processes</b> </span></i><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in 0in 0.0001pt"><i><span style="color:black">The Board will meet to discuss the EPDP recommendation(s) as soon as feasible, but preferably not later than the second meeting after receipt of the Recommendations Report from the Staff
Manager. Board deliberation on the EPDP Recommendations contained within the Recommendations Report shall proceed as follows:</span></i><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in 0in 0.0001pt;text-indent:0in;vertical-align:baseline">
<u></u><i><span style="color:black"><span>a.<span style="font:7pt "Times New Roman"">
</span></span></span></i><u></u><span dir="LTR"></span><i><span style="color:black">Any EPDP Recommendations approved by a GNSO Supermajority Vote shall be adopted by the Board unless, by a vote of more than two-thirds (2/3) of the Board, the Board determines
that such policy is not in the best interests of the ICANN community or ICANN. If the GNSO Council recommendation was approved by less than a GNSO Supermajority Vote, a majority vote of the Board will be sufficient to determine that such policy is not in the
best interests of the ICANN community or ICANN.<u></u><u></u></span></i></p>
<p style="margin:0in 0in 0.0001pt;text-indent:0in;vertical-align:baseline">
<u></u><i><span style="color:black"><span>b.<span style="font:7pt "Times New Roman"">
</span></span></span></i><u></u><span dir="LTR"></span><i><span style="color:black"> In the event that the Board determines, in accordance with paragraph a above, that the proposed EPDP Recommendations are not in the best interests of the ICANN community
or ICANN (the Corporation), the Board shall (i) articulate the reasons for its determination in a report to the Council (the "Board Statement"); and (ii) submit the Board Statement to the Council.<u></u><u></u></span></i></p>
<p style="margin:0in 0in 0.0001pt;text-indent:0in;vertical-align:baseline">
<u></u><i><span style="color:black"><span>c.<span style="font:7pt "Times New Roman"">
</span></span></span></i><u></u><span dir="LTR"></span><i><span style="color:black">The Council shall review the Board Statement for discussion with the Board as soon as feasible after the Council's receipt of the Board Statement. The Board shall determine
the method (e.g., by teleconference, email, or otherwise) by which the Council and Board will discuss the Board Statement. <u></u><u></u></span></i></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in 0in 0.0001pt"><i><span style="color:black">At the conclusion of the Council and Board discussions, the Council shall meet to affirm or modify its recommendation, and communicate that conclusion (the "Supplemental Recommendation")
to the Board, including an explanation for the then-current recommendation. In the event that the Council is able to reach a GNSO Supermajority Vote on the Supplemental Recommendation, the Board shall adopt the recommendation unless more than two-thirds (2/3)
of the Board determines that such guidance is not in the interests of the ICANN community or ICANN. For any Supplemental Recommendation approved by less than a GNSO Supermajority Vote, a majority vote of the Board shall be sufficient to determine that the
guidance in the Supplemental Recommendation is not in the best interest of the ICANN community or ICANN.</span></i><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black">4.1 – Overview of updates made (Council leadership)</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black">4.2 – Council discussion</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black">4.3 – Next steps</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"> <u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><b><span style="color:black">Item 5: COUNCIL DISCUSSION – ICANN Org’s Request for Clarification on Data Accuracy and Phase-2 of the Expedited Policy Development Process (EPDP) on the Temporary Specification
for gTLD Registration Data (15 minutes)</span></b><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black">On 21 June 2019, the GNSO Council received a
</span><a href="https://gnso.icann.org/sites/default/files/file/field-file-attach/marby-to-drazek-21jun19-en.pdf" rel="noreferrer" target="_blank"><span style="color:rgb(17,85,204)">letter</span></a><span style="color:black"> from ICANN Org, which was seeking a better understanding of the Expedited
Policy Development Process (EPDP) Team’s plans “to consider the subject of "data accuracy" as it relates to gTLD registration data and related services, such as the
</span><a href="https://whois.icann.org/en/whoisars" rel="noreferrer" target="_blank"><span style="color:rgb(17,85,204)">WHOIS Accuracy Reporting System (ARS)</span></a><span style="color:black">.”</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black">Further, “ICANN org notes that footnote #6 on page 7 of the EPDP Phase 1 Final Report states: “The topic of accuracy as related to GDPR compliance is expected to be considered
further as well as the WHOIS Accuracy Reporting System.” However, it is not clear who would consider this topic and when. Therefore, ICANN org seeks the GNSO Council’s clarification on whether the Phase 2 EPDP Team will be considering the subject of data accuracy,
including projects that utilize gTLD registration data, such as WHOIS ARS.” </span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black">On 8 July 2019, GNSO Council Liaison to the EPDP Team, Rafik Dammak forwarded the letter to the EPDP Team seeking their input to better inform the Council in its preparation
for a response to ICANN org. </span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black">During its meeting on 18 July 2019, the Council had an initial exchange of views on this topic which continued on the mailing list. Here the Council will take into consideration
the input provided and decide how to substantively respond to the questions and concerns from ICANN Org. </span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black">5.1 – Introduction of topic (Council leadership)</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black">5.2 – Council discussion</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black">5.3 – Next steps</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"> <u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><b><span style="color:black">Item 6: COUNCIL DISCUSSION – ICANN Board referrals of CCT-RT recommendations to GNSO Council and GNSO PDP WGs</span></b><span style="color:black">
<b>(15 minutes)</b></span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black">On 10 June 2019, ICANN org communicated to the GNSO Council that the ICANN Board resolution passed on 1 March 2019 – see</span><a href="https://www.icann.org/resources/board-material/resolutions-2019-03-01-en%20%5bicann.org%5d" rel="noreferrer" target="_blank"><span style="color:black">
</span><span style="color:rgb(17,85,204)">https://www.icann.org/resources/board-material/resolutions-2019-03-01-en [icann.org]</span></a><span style="color:black"> - calls for a set of Competition, Consumer Trust, and Consumer Choice Review Team (CCT-RT) Final Recommendations
to be passed through to community groups. As articulated in the Board resolution, “recognizing that the Board has the obligation and responsibility to balance the work of ICANN in order to preserve the ability for ICANN org to serve its Mission and the public
interest, the Board decided on three categories of action”:</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"> <u></u><u></u></p>
<ul style="margin-top:0in" type="disc">
<li style="color:black;margin-top:0in;margin-bottom:0.0001pt;background:white;vertical-align:baseline">
Accepting recommendations, subject to costing and implementation considerations;<u></u><u></u></li><li style="color:black;margin-top:0in;margin-bottom:0.0001pt;background:white;vertical-align:baseline">
Placing recommendations (in whole or in part) in "Pending" status, directing ICANN org to perform specific actions to enable the Board to take further actions;<u></u><u></u></li><li style="color:black;margin-top:0in;margin-bottom:0.0001pt;background:white;vertical-align:baseline">
Passing recommendations (in whole or in part) to community groups the CCT-RT identified for their consideration. The Board noted fourteen such recommendations (9, 10, 12, 16, 19, 20, 25, 27, 28, 29, 32, 33, 34, 35).<u></u><u></u></li></ul>
<p style="margin-right:0in;margin-left:0in;margin-bottom:0.0001pt;background:white">
<span style="color:black">The Council was specifically invited to review to pages 1-4 of the scorecard</span><a href="https://www.icann.org/en/system/files/files/resolutions-final-cct-recs-scorecard-01mar19-en.pdf%5bicann.org%5d" rel="noreferrer" target="_blank"><span style="color:black">
</span><span style="color:rgb(17,85,204)">https://www.icann.org/en/system/files/files/resolutions-final-cct-recs-scorecard-01mar19-en.pdf[icann.org]</span></a><span style="color:black"> which compile pass-through recommendations, including the groups they are addressed
to. The recommendations the ICANN Board resolved to pass through to the GNSO Council, in whole or in part, for its consideration:</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"> <u></u><u></u></p>
<ul style="margin-top:0in" type="disc">
<li style="color:black;margin-top:0in;margin-bottom:0.0001pt;background:white;vertical-align:baseline">
<b>Recommendation 10</b>.<u></u><u></u></li><li style="color:black;margin-top:0in;margin-bottom:0.0001pt;background:white;vertical-align:baseline">
<b>Recommendation 16 (in part)</b> Note: this recommendation was also passed through to the New gTLD Subsequent Procedures PDP WG, Registries Stakeholder Group, Registrar Stakeholder Group, Generic Names Supporting Organization, Second Security, Stability &
Resiliency of DNS Review Team as suggested by the CCT-RT. In the scorecard, the Board noted that “it is not accepting the policy directives that may be inherent here but rather, passes on such elements of the recommendation to the relevant community groups
to consider”.<u></u><u></u></li><li style="color:black;margin-top:0in;margin-bottom:0.0001pt;background:white;vertical-align:baseline">
<b>Recommendation 27</b>.<u></u><u></u></li><li style="color:black;margin-top:0in;margin-bottom:0.0001pt;background:white;vertical-align:baseline">
<b>Recommendation 28</b>.<u></u><u></u></li><li style="color:black;margin-top:0in;margin-bottom:0.0001pt;background:white;vertical-align:baseline">
<b>Recommendation 29</b>. Note: this recommendation was also passed through to the New gTLD Subsequent Procedures PDP WG, as suggested by the CCT-RT. To inform work relating to recommendations 29 and 30, the ICANN Board suggested that the New gTLD Subsequent
Procedures PDP WG could take on, “should they choose to do so, defining the term ‘Global South’ or agreeing on another term to describe underserved or underrepresented regions or stakeholders in coordination with ICANN org”<i>.</i><u></u><u></u></li></ul>
<p style="margin-right:0in;margin-left:0in;margin-bottom:0.0001pt;background:white">
<span style="color:black">The Board noted in its resolution that: “in passing these recommendations through, the Board is neither accepting, nor rejecting the recommendations. […] Passing recommendations through to community groups is not a directive that the
groups identified should formally address any of the issues within those recommendations. It is within the purview of each group to identify whether work will be taken on and the topics that the group will address”</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black">A small group of Council volunteers reviewed the recommendations passed through to the GNSO Council as well as a number of Recommendations were passed through to gTLD Subsequent
Procedures PDP Working Group and/or Rights Protection Mechanisms (RPM) PDP Working Group. In order to have a better picture of where all the Recommendations passed to the GNSO and its PDPs stand, the GNSO Chair is planning to write to the leadership of the
Working Groups seeking their feedback.</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black">An initial draft with the small team's proposed GNSO Council response to those 5 Recommendations passed through directly to the GNSO were circulated to the GNSO Council on
23 July for review and consideration [</span><a href="https://gnso.icann.org/sites/default/files/file/field-file-attach/proposed-council-response-cct-review-team-recommendations-23jul19-en.pdf" rel="noreferrer" target="_blank"><span style="color:rgb(17,85,204)">https://gnso.icann.org/sites/default/files/file/field-file-attach/proposed-council-response-cct-review-team-recommendations-23jul19-en.pdf</span></a><span style="color:black">].</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black">Here the Council will consider the initial draft and receive an update on the feedback received from the PDP WGs to which recommendations were also passed through.</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black;background:white">6.1 – Introduction of topic (Pam Little)</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black;background:white">6.2 – Council discussion</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black">6.3 – Next steps </span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"> <u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><b><span style="color:black">Item 7: COUNCIL DISCUSSION - ICANN Org assumptions for new round of new gTLDs (15 minutes)</span></b><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black">In December 2015 the GNSO initiated a Policy Development Process (PDP) to determine if changes to existing policy recommendations are needed before the next round of gTLDs.
The PDP Working Group’s final report and recommendations may lead to procedural changes for subsequent rounds of gTLD applications, which ICANN org must implement and manage. </span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black">In the course of ICANN org’s preparatory work toward the planning and implementation of the new policy, ICANN org has compiled a number of fundamental operationally focused
assumptions to help with the preliminary planning and operational readiness of the organization. These were shared with the ICANN Board and on 17 June these were also shared with all ICANN constituencies, including the GNSO Council [<a href="https://gnso.icann.org/en/correspondence/pre-engagement-comms-assumptions-paper-17jun19-en.pdf" rel="noreferrer" target="_blank">https://gnso.icann.org/en/correspondence/pre-engagement-comms-assumptions-paper-17jun19-en.pdf</a>].
ICANN org noted that if the GNSO Council members are also interested in further engagement and providing feedback and perspective on these assumptions GDD would be happy to arrange a mutually convenient time for a discussion.</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black">This is an opportunity for the GNSO Council to ask possible clarifying questions, consider the assumptions and determine whether the GNSO Council would want to provide further
feedback.</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black;background:white">7.1 – Introduction of topic (GDD Cyrus Namazi & Trang Nguyen</span><span style="color:black">)</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black;background:white">7.2 – Council discussion</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black;background:white">7.3 – Next steps</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black"> </span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><b><span style="color:black;background:white">Item 8: COUNCIL DISCUSSION – Proposed Amendments to Consensus Policy Implementation Framework (CFIP) (15 minutes)</span></b><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black">The Consensus Policy Implementation Framework (CPIF) represents ICANN org’s Global Domains Division’s “roadmap” for implementing community-developed and approved consensus
policy recommendations. Point H of the Framework mandates that ICANN org “continually review the implementation framework and related materials to encapsulate additional best-practices or to adjust the steps as a result of lessons learned with previous consensus
policy projects.” In accordance with this mandate, please find attached an amended version of the CPIF for your consideration.</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black">On 12 July 2019, ICANN org shared a proposed set of amendments focusing on establishing standardized processes for post-implementation consensus policy reviews and for amending
the CPIF document on an ongoing basis with the GNSO Council [</span><a href="https://gnso.icann.org/sites/default/files/file/field-file-attach/gdd-consensus-policy-implementation-framework-12jul19-en.pdf" rel="noreferrer" target="_blank"><span style="color:rgb(17,85,204)">https://gnso.icann.org/sites/default/files/file/field-file-attach/gdd-consensus-policy-implementation-framework-12jul19-en.pdf</span></a><span style="color:black">].
In addition to a number of minor language updates, the following sections have been added to or created: </span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black"> </span><u></u><u></u></p>
<ol style="margin-top:0in" start="1" type="1">
<li style="color:black;margin-top:0in;margin-bottom:0.0001pt;background:white;vertical-align:baseline">
<u>Section V, “Support and Review”</u>: <span style="color:red">Section expanded </span>
to reference the proposed post-implementation consensus policy review process added in the
<span style="color:red">new </span>Section VI<u></u><u></u></li><li style="color:black;margin-top:0in;margin-bottom:0.0001pt;background:white;vertical-align:baseline">
<u>Section VI, “Post-Implementation Consensus Policy Review Process”</u>: <span style="color:red">
New section </span>added to detail proposed steps for carrying out reviews of implemented consensus policies <u></u><u></u></li><li style="color:black;margin-top:0in;margin-bottom:0.0001pt;background:white;vertical-align:baseline">
<u>Section VII, “Consensus Policy Implementation Framework Amendment Process”</u>:
<span style="color:red">New section </span>added to detail proposed steps for amending the CPIF<u></u><u></u></li></ol>
<p style="margin-right:0in;margin-left:0in;margin-bottom:0.0001pt;background:white">
<span style="color:black">Similar to ICANN org’s effort last year to update the framework and “test” the amendment process, minor updates have been left as redlines throughout the document; more substantive changes are shown as redlines and have “rationale”
comments associated with them. The amended version will ultimately be posted to <a href="http://icann.org" rel="noreferrer" target="_blank">icann.org</a>’s implementation page at
</span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_policy_implementation&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=LQL0N6AleunBLdGbhHpeiUul5Jjk7XRWhB1CggE8-c4&s=h0Rf1fJ-_IqQiU1Xx9O_gWorYlrdOIEcCtb58Ck3X70&e=" rel="noreferrer" target="_blank"><span style="color:rgb(149,79,114)">https://www.icann.org/policy/implementation
[icann.org]</span></a><span style="color:black">.</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black">Here the GNSO Council will have an opportunity to review the proposed amendments and provide feedback.</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black;background:white">8.1 – Introduction of topic (Brian Aitchison, GDD)</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black;background:white">8.2 – Council discussion</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black;background:white">8.3 – Next steps</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"> <u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><b><span style="color:black;background:white">Item 9 - PDP 3.0 Small Group Update/Discussion (15 minutes)</span></b><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;text-align:justify;background:white"><span style="color:black">The PDP 3.0 Small Team has completed five (5) out of fourteen (14) PDP 3.0 improvements so far. The rest of the nine (9) improvements are all in the pipeline
with various levels of progress. </span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;text-align:justify;background:white"><span style="color:black"> </span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;text-align:justify;background:white"><span style="color:black">In advance of the 22 August Council meeting, the PDP 3.0 Small Team sent the following documents for four (4) completed PDP 3.0 improvements as the first
deliverable to the GNSO Council for review. They are packaged together as they are concerned with the expectations, requirements, and/or participation methods for PDP working groups members and/or leaders. </span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;text-align:justify;background:white"><span style="color:black">Note that Improvement #14 (Criteria to Evaluate Request for Data Gathering) has also been completed, but it will be delivered in a separate package together
with other completed, related improvements prior to future GNSO Council meetings.</span><u></u><u></u></p>
<ul style="margin-top:0in" type="disc">
<li style="color:rgb(23,43,77);margin-top:8pt;margin-bottom:0.0001pt;text-align:justify;background:white;vertical-align:baseline">
<b><span style="color:black">Improvement #1</span></b><span style="color:black">:</span>
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1bs-5FbQwITOJvDIWgaj0FV2A-5FbbX02EptU_edit&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=zI4Vnyooq9a1W5ms98tIKFBVs650-Ow6eI8mZTR41nQ&s=NQWQW82eHvmwPVEqH6WEzN_zNsSDp-6ggfsdgoTfolQ&e=" rel="noreferrer" target="_blank">
<span style="color:rgb(17,85,204)">Terms of participation for working group members</span><span style="color:rgb(149,79,114)"> [docs.google.com]</span></a><u></u><u></u></li><li style="color:rgb(23,43,77);margin-top:0in;margin-bottom:0.0001pt;text-align:justify;background:white;vertical-align:baseline">
<b><span style="color:black">Improvement #2</span></b><span style="color:black">:
</span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1N-2DU9dvu-5FIBkW1FvpGY-5FaGr0uW6VZTW9Y_edit&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=zI4Vnyooq9a1W5ms98tIKFBVs650-Ow6eI8mZTR41nQ&s=CAr218H1XVZ1Mv2rZk09KXF3Yx1zg_OMQy4VHiuq5bE&e=" rel="noreferrer" target="_blank"><span style="color:rgb(17,85,204)">Consider
alternatives to open working group model</span><span style="color:rgb(149,79,114)"> [docs.google.com]</span></a><u></u><u></u></li><li style="color:black;margin-top:0in;margin-bottom:0.0001pt;text-align:justify;background:white;vertical-align:baseline">
<b>Improvement #3</b>: Criteria for joining of new members after a PDP working group is formed or re-chartered<u></u><u></u>
<ul style="margin-top:0in" type="circle">
<li style="color:rgb(23,43,77);margin-top:0in;margin-bottom:0.0001pt;text-align:justify;background:white;vertical-align:baseline">
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1qp7rv4wB8TNzkPdi5yuKlpfIjgt81ClOZsq4EcA5QEg_edit&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=zI4Vnyooq9a1W5ms98tIKFBVs650-Ow6eI8mZTR41nQ&s=PUPlLiZ6KY3QZKo8SfVL3gtvNXDykQxVo5rcVUMHZAk&e=" rel="noreferrer" target="_blank"><span lang="FR" style="color:rgb(17,85,204)">Main
document</span><span lang="FR" style="color:rgb(149,79,114)"> [docs.google.com]</span></a><span lang="FR"><u></u><u></u></span></li><li style="color:rgb(23,43,77);margin-top:0in;margin-bottom:0.0001pt;text-align:justify;background:white;vertical-align:baseline">
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_14uAsBg0-5FBnhJ6nqjitsHutm1AcFKhRsa4VAsR-2DWtMKI_edit&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=zI4Vnyooq9a1W5ms98tIKFBVs650-Ow6eI8mZTR41nQ&s=VYrjxU44hlJ47t7Dz4thWq95P6fjq7X0XnRnGb3CRZE&e=" rel="noreferrer" target="_blank"><span style="color:rgb(17,85,204)">Working
Group Member Skills Guide</span><span style="color:rgb(149,79,114)"> [docs.google.com]</span></a><u></u><u></u></li></ul>
</li><li style="color:rgb(23,43,77);margin-top:0in;margin-bottom:0.0001pt;text-align:justify;background:white;vertical-align:baseline">
<b><span style="color:black">Improvement #6</span></b><span style="color:black">:
</span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1DxRS7jYHh1i5USyrr0wP6dpJhQjRqrMnnT-5FxWuzhSqU_edit&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=zI4Vnyooq9a1W5ms98tIKFBVs650-Ow6eI8mZTR41nQ&s=Ez9yDWucFrjzlA_qCktmdcCZ_845o1YX3DwWgVwwWfU&e=" rel="noreferrer" target="_blank"><span style="color:rgb(17,85,204)">Document
expectations for working group leaders (Chairs/Co- Chairs/Leads) that outlines role & responsibilities as well as minimum skills / expertise required</span><span style="color:rgb(149,79,114)"> [docs.google.com]</span></a><u></u><u></u></li></ul>
<p style="margin-right:0in;margin-left:0in;margin-bottom:0.0001pt;background:white">
<span style="color:black">Here the GNSO Council will consider the documents for four (4) completed PDP 3.0 improvements.</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black">9.1 - Introduction of topic (Rafik Dammak)</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black">9.2 - Council discussion</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black">9.3 - Next steps </span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"> <u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><b><span style="color:black">Item 10: ANY OTHER BUSINESS (10 minutes)</span></b><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black">10.1 - ICANN66 Draft Schedule Review & travel booking reminder</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black">10.2 - GNSO Strategic Planning Session January 2020</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black">10.3 - Confirmation of volunteers for Council liaisons to PDP/IRTs beginning at the AGM</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"><span style="color:black">10.4 - EPDP Phase 2 Work plan package (see
</span><a href="https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-phase-2-project-management-work-plan-15aug19-en.pdf" rel="noreferrer" target="_blank"><span style="color:rgb(17,85,204)">https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-phase-2-project-management-work-plan-15aug19-en.pdf</span></a><span style="color:black">) </span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt;background:white"> <u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">_______________________________</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i))</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">See </span>
<a href="https://www.icann.org/resources/pages/governance/bylaws-en/#article11" rel="noreferrer" target="_blank"><span style="color:rgb(17,85,204)">https://www.icann.org/resources/pages/governance/bylaws-en/#article11</span></a><span style="color:black">.</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4)</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">See </span>
<a href="https://gnso.icann.org/sites/default/files/file/field-file-attach/op-procedures-30jan18-en.pdf" rel="noreferrer" target="_blank"><span style="color:rgb(17,85,204)">https://gnso.icann.org/sites/default/files/file/field-file-attach/op-procedures-30jan18-en.pdf</span></a><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">References for Coordinated Universal Time of 21:00 UTC </span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">Local time between March and October Summer in the NORTHERN hemisphere</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">----------------------------------------------------------------------------</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">California, USA (PDT) UTC-7 05:00</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">San José, Costa Rica (CST) UTC-6 06:00</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">New York/Washington DC, USA (EDT) UTC-4 08:00</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><span lang="PT-BR" style="color:black">Buenos Aires, Argentina (ART) UTC-3 09:00</span><span lang="PT-BR"><u></u><u></u></span></p>
<p style="margin:0in 0in 0.0001pt"><span lang="PT-BR" style="color:black">Rio de Janeiro, Brazil (BRT) UTC-3 09:00</span><span lang="PT-BR"><u></u><u></u></span></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">London, United Kingdom (GMT) UTC+1 13:00</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">Kinshasa, Democratic Republic of Congo (WAT) UTC+1 13:00</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><span lang="FR" style="color:black">Paris, France (CET) UTC+2 14:00</span><span lang="FR"><u></u><u></u></span></p>
<p style="margin:0in 0in 0.0001pt"><span lang="FR" style="color:black">Moscow, Russia (MSK) UTC +3 15:00</span><span lang="FR"><u></u><u></u></span></p>
<p style="margin:0in 0in 0.0001pt"><span lang="FR" style="color:black">Islamabad, Pakistan (PKT) UTC+5 17:00 </span><span lang="FR"><u></u><u></u></span></p>
<p style="margin:0in 0in 0.0001pt"><span lang="FR" style="color:black">Singapore (SGT) UTC+8 20:00 </span><span lang="FR"><u></u><u></u></span></p>
<p style="margin:0in 0in 0.0001pt"><span lang="FR" style="color:black">Tokyo, Japan (JST) UTC+9 21:00 </span><span lang="FR"><u></u><u></u></span></p>
<p style="margin:0in 0in 0.0001pt"><span lang="FR" style="color:black">Melbourne, Australia (AEDT) UTC+11 22:00 </span><span lang="FR"><u></u><u></u></span></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">----------------------------------------------------------------------------</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">DST starts/ends on Sunday 27 of October 2019, 2:00 or 3:00 local time (with exceptions) for EU countries and on Sunday 03 of November 2019 for the US.</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">----------------------------------------------------------------------</span><u></u><u></u></p>
<p style="margin:0in 0in 0.0001pt"><span style="color:black">For other places see
</span><a href="http://www.timeanddate.com/" rel="noreferrer" target="_blank"><span style="color:rgb(17,85,204)">http://www.timeanddate.com</span></a><span style="color:black"> and
</span><a href="https://tinyurl.com/y2qdox2m" rel="noreferrer" target="_blank"><span style="color:rgb(17,85,204);background:white">https://tinyurl.com/y2qdox2m</span></a><span style="color:black;background:white">
</span><span style="font-size:10pt;font-family:Arial,sans-serif;color:black;background:white"> </span><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal" align="center" style="text-align:center"><span style="font-size:11pt"> </span><u></u><u></u></p>
</div>
</div>.</div></div></div>
</blockquote></div>
</blockquote></div>