April 2019 - council - lists.icann.org

Important Update to ICANN's Travel Support with Potential Impact on SG/C Leaders and Elections
by Drazek, Keith 04 Apr '19

04 Apr '19

Dear GNSO Stakeholder Group and Constituency Chairs: This is an important update related to ICANN's travel support program. This may have an impact on GNSO Stakeholder Group and Constituency elections and leaders, particularly newly appointed leaders. * All travel support requests are now due 120 days prior to the next ICANN Public Meeting. This was previously a 90-day deadline. Therefore, the deadline for ICANN66 travel support is Friday, 5 July 2019. * If applicable, community groups will need to adjust their election timelines accordingly to ensure new leaders are eligible in time for the ICAN66 travel support deadline. Please note that extensions will not be granted for election timeline purposes as has previously been the case. * Stakeholder Group and Constituency officer names (members of leadership teams and councilors) will therefore all need to be submitted for funded traveler support prior to the deadline of the 5th July 2019. Please review your respective election procedures and timelines so ICANN travel support funding can be allocated appropriately and accordingly. Alternatively, newly appointed leaders and councilors may not be eligible for travel support at the first meeting following their election. Please confirm receipt and let me know if you have any questions. Thanks and regards, Keith

1 1

REMINDER: Call for GNSO Council Liaison to the EPDP Phase 1 Implementation Review Team (IRT) and Pre-IRT
by Drazek, Keith 04 Apr '19

04 Apr '19

Hi all, In our 4 March 2019 motion to approve the EPDP Phase 1 Final Report, we also voted to approve the initiation of Phase 2 AND to begin preparing for implementation work on the Phase 1 recommendations. As discussed during our wrap-up session in Kobe, with the initiation of an informal “Pre-IRT” group, recognizing that the formal IRT will be formed after Board approval, the Council needs to appoint a Liaison. For further background on the Phase 1 implementation work, the relevant resolved clause language from the 4 March motion is as follows: “Noting the unique circumstances and external deadlines associated with the Temporary Specification and the work of this EPDP, the GNSO Council supports the EPDP Team's recommendation to informally convene the Implementation Review Team now to allow additional time for the necessary planning to take place before ICANN Board consideration of this Final Report. The IRT would be formally convened upon Board approval. As such, the GNSO Council directs ICANN Org to informally convene the Implementation Review team as soon as possible. The Implementation Review Team will be tasked with assisting ICANN org in developing the implementation details for the EPDP recommendations, evaluating the proposed implementation of the recommendations as approved by the Board, and working with ICANN staff to ensure that the resultant implementation conforms to the intent of the approved recommendations. The Implementation Review Team shall operate in accordance with the Implementation Review Team Principles and Guidance approved by the GNSO Council in June 2015.” Attached are the two documents relevant to the GNSO Council liaison to an IRT. The first one provides a detailed description of the expectations in relation to the IRT liaison role, while the second one is intended as a liaison briefing / handover following appointment (although it may also be helpful for those interested in the role to see what is expected from the liaison at the outset). Please advise if you are interested and available to act as Council Liaison to the EPDP Phase 1 Pre-IRT, and eventual IRT. Thanks in advance! Keith

1 0

REMINDER-Call for Volunteers: Registration Data Policy Implementation - pre-IRT
by Andrea Glandon 04 Apr '19

04 Apr '19

Call for Volunteers: Registration Data Policy Implementation - Informal pre-IRT ICANN org is currently seeking volunteers to participate in an informal Pre-Implementation Review Team, or “pre-IRT.” The pre-IRT will assist the ICANN implementation project team in planning implementation work for the EPDP Team’s policy recommendations. As background, the GNSO Council approved and EPDP Team recommended that the GNSO Council and ICANN Org should informally convene the Implementation Review Team to allow for the necessary planning to take place before ICANN Board consideration of its Final Report, following which the IRT would be formally convened (See EPDP Team Recommendation 28). This pre-IRT will act as a temporary implementation review team, which will assist with the gTLD registration data policy implementation planning until the formal Implementation Review Team is officially convened. All members of the pre-IRT are expected to transition to the IRT. The work of the pre-IRT will consist of the following: * Review the proposed implementation plan as drafted by ICANN org * Assist where questions or clarifications from ICANN org arise * Advise on technical and operational details related to the implementation of EPDP recommendations For this pre-IRT, ICANN org is seeking volunteers who are current or former EPDP Team members and assisted in the Team’s Phase 1 work, and accordingly, possess a deep understanding of the EPDP Team’s policy recommendations and accompanying rationale. All volunteers responding to this call are expected to understand the role and remit of the IRT for the implementation project. The work of the pre-IRT is estimated to last until May 2019 when the IRT is expected to convene to take over the work. The pre-IRT is anticipated to have weekly teleconferences starting in early April 2019 for one hour each. Between the meetings, the pre-IRT will be working using collaborative tools. The expected time commitment for supporting the implementation is about three hours per week. How to apply To participate, please send an email to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>. If you wish to join the IRT and not the Pre-IRT, please wait to respond to the Call for IRT, which will come later. Background On 17 May 2018, the ICANN Board of Directors (ICANN Board) adopted the Temporary Specification for generic top-level domain (gTLD) Registration Data [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> ("Temporary Specification") pursuant to the procedures for the establishment of temporary policies in ICANN's agreements with Registry Operators and Registrars ("Contracts"). The Temporary Specification provides modifications to existing requirements in the Registrar Accreditation and Registry Agreements in order to comply with the European Union's General Data Protection Regulation ("GDPR"). Following adoption of a temporary specification, the procedure for Temporary Policies as outlined in the Registrar Accreditation and Registry Agreements provides the Board "shall immediately implement the Consensus Policy development process set forth in ICANN's Bylaws." Additionally, the procedure provides this Consensus Policy development process on the Temporary Specification must be carried out within a one-year period as the Temporary Specification can only remain in force for up to one year; from the effective date of 25 May 2018, i.e., the Temporary Specification will expire on 25 May 2019. On 19 July 2018, the GNSO Council initiated<https://community.icann.org/display/gnsocouncilmeetings/Motions+19+July+2018> an Expedited Policy Development Process (EPDP) and chartered [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> the EPDP on the Temporary Specification for gTLD Registration Data team. Unlike other GNSO PDP efforts, which are open for anyone to join, the GNSO Council chose to limit the membership composition of this EPDP, primarily in recognition of the need to complete the work in a relatively short timeframe and to resource the effort responsibly. GNSO Stakeholder Groups, the Governmental Advisory Committee (GAC), the Country Code Names Supporting Organization (ccNSO), the At-Large Advisory Committee (ALAC), the Root Server System Advisory Committee (RSSAC), and the Security and Stability Advisory Committee (SSAC) were each invited to appoint up to a set number of members and alternates, as outlined in the charter<https://community.icann.org/display/EOTSFGRD/EPDP+Team+Charter?preview=/885…>. In addition, the ICANN Board and ICANN Org were invited to assign a limited number of liaisons to this effort. A call for volunteers to the aforementioned groups was issued in July and the EPDP Team held its first meeting on 1 August 2018<https://community.icann.org/display/EOTSFGRD/2018-08-01+EPDP+Team+call+%231>. On 4 March 2019, the GNSO Council adopted the EPDP Team’s Final Report and submitted it to the Board for their consideration. The Board is currently conducting a public comment that is scheduled to close on 17 April 2019.

3 3

Fwd: Circle ID piece on PDP 3.0
by Rafik Dammak 03 Apr '19

03 Apr '19

Hi all, Jeff kindly shared his blog post about PDP 3.0. Food for thought. Best, Rafik ---------- Forwarded message --------- De : Jeff Neuman Date: mar. 2 avr. 2019 à 22:47 Subject: Circle ID piece on PDP 3.0 To: Keith, Rafik and Pam, I just wanted to draft your attention to a piece I did for Circle ID on PDP 3.0. Please feel free to post this to the Council and let me know if there is anything I can do to help with the efforts. http://www.circleid.com/posts/20190401_dwill_pdp_3_save_the_multi_stakehold… I have enclosed a PDF copy as well. Best regards, *Jeff Neuman* Senior Vice President *Com Laude | Valideus *1751 Pinnacle Drive Suite 600, McLean VA 22102, USA M: +1.202.549.5079 D: +1.703.635.7514 E: *jeff.neuman(a)comlaude.com <jeff.neuman(a)comlaude.com>* www.comlaude.com [image: cid:image001.jpg@01D451AA.189512A0] Liability cannot be accepted for statements made which are clearly the sender’s own and not made on behalf of Com Laude USA or Valideus USA. This message is intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to us, and immediately and permanently delete it. Do not use, copy or disclose the information contained in this message or in any attachment.Com Laude USA and Valideus are trading names of Consonum, Inc.

2 1

Reminder: Document and Motion deadline Monday 8 April 2019 at 23:59 UTC for GNSO Council Meeting 18 April 2019 at 21:00 UTC
by Nathalie Peregrine 03 Apr '19

03 Apr '19

Dear all, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday 8 April 2019 at 23:59 UTC) of the GNSO Council Meeting on Thursday 18 April 2019 at 21:00 UTC. Motions should be sent to the Council mailing list by a councilor and will then be posted on the Wiki at: https://community.icann.org/x/uBBIBg Thank you very much. With kind regards, Nathalie

1 2

Updated Action Items: GNSO Council meeting ICANN64 Kobe
by Nathalie Peregrine 01 Apr '19

01 Apr '19

Dear all, Please find the list of Action Items below updated with those from the GNSO Wrap Up session in Kobe, ICANN64. The Action item wiki page<https://community.icann.org/display/gnsocouncilmeetings/Action+Items> has been adjusted accordingly. Thank you, Nathalie From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Wednesday, March 27, 2019 at 3:39 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [gnso-secs] Action Items: GNSO Council meeting ICANN64 Kobe Dear Councilors, With sincere apologies for the delay, please find the action items below, as stated during the meeting, arising from the GNSO Council sessions held during ICANN64 in Kobe. Please take note of the proposed timing for delivering on these actions. Please ensure your wiki logins are up to date as all action items have been assigned to councilors and/or staff and posted on the Action Item wiki page here<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…>. Please refer to this page for the recent status updates on the Action items. **Note the action items highlighted for all councilors** ACTION ITEMS FROM THE GNSO COUNCIL MEETING ICANN 64 Kobe GNSO Working Session CCWG Auction Proceeds update: Action item: * Council to consider the question of whether the provision of legal services be construed as the provision of benefits (during the wrap-up session). * Erika Mann/Marika Konings to forward slides and relevant legal analysis provided by Legal/Board to the CCWG on Auction Proceeds. * Councilors and their respective GNSO Stakeholder groups to encourage their appointed members to dutifully participate and provide regular updates on the status of work. To review GNSO appointed members, see https://community.icann.org/x/FpjDAw. Prep for meetings with Board, ccNSO, GAC Action item: * Erika Mann to send information about new European copyright law * [See also wrap-up session - Erika, Tatiana, Ayden, Michele, Philippe, Darcy, and Flip volunteered] Small group of Councilors to develop draft message to ICANN Org to provide input on legislative tracker (e.g., identify gaps, improvements, more tailored to ICANN environment). Based on feedback, Council leadership to consider scheduling follow up discussion at ICANN65, possibly with ICANN Org participation. PDP update: discussion of SubPro progress Action items: * Council leadership to propose path forward to obtain clarification / provide view concerning intersection between the Name Collisions Analysis Project and SubPro PDP * PDP 3.0 small team to engage with PDP Chairs to obtain input on different improvements related to PDP WGs and leadership Joint ccNSO GNSO - 11 March 2019 Action items: * Harmonizing Confusing Similarity review: Council leadership to liaise with SubPro leadership to determine how best to coordinate with ccNSO and then propose approach to the Council. * Comments ICANN’s 2021-2025 Strat Plan, FY20 Operating Plan and Budget: common concerns: SCBO to do analysis between ccNSO/GNSO comments, identify elements for common cause. Look at how the reserve fund replenishment can be sustained. GNSO Council Meeting - 13 March 2019 Item 2: Opening Remarks / Review of Projects & Action List Action Item(s): * Council leadership to look into status of existing action item related to preparation of the 3.7 appeal after action report from the IGO-INGO Access to Curative Rights Protection Mechanisms. * Council Chair to follow up on the existing action item regarding the drafting of a response to CCWG/EG on Internet Governance. * ICANN Staff to mark EPDP/TSG action item as complete * Council leadership to confirm expectations of TSG are well understood, next steps. Reach out to find out next steps of TSG Item 3: Consent Agenda Action Item(s): * In accordance with terms of the CSC Effectiveness Review Template, the Chair of GNSO Council and the Chair of ccNSO Council are requested to recommend report to IANA Naming Function Review Team (IFRT) as soon as that is established. * The GNSO Council instructs the GNSO Secretariat to share the results of this motion with the CSC. [COMPLETED] * Keith Drazek, serving as the EC Admin, to inform the EC Secretary of the confirmation of Becky Burr to serve in seat 13 on the ICANN Board of Directors. Item 4: COUNCIL DISCUSSION – Privacy/Proxy Services Accreditation Issues Implementation Review Team Action Item(s): * Council to prepare response to letter from Cyrus, considering whether the PPSAI IRT should continue to be on hold and/or whether the transfer policy referral should be worked on now, noting that public comment on the new P/P policy (which was the original trigger) may not take place for a while. In relation to unpausing of the PPSAI IRT, Council to consider whether it would be possible to parse out EPDP-dependent versus non-EPDP dependent items. Item 5: COUNCIL UPDATE – GNSO Policy Development Process 3.0 Implementation Action Item(s): * Small group of Councilors to ensure that recurring updates are provided to the Council (e.g., on no less than a quarterly basis) Item 6: COUNCIL DISCUSSION – Discussion of the Inter-Registrar Transfer Policy (IRTP) Policy Status Report Action Item(s): * Council to further consider next steps in relation to the review of the Transfer Policy which would result in providing GDD information/response on expected next steps and/or seek additional information as the Council considers how to approach the Transfer Policy review, for example, holistically instead of piecemeal. 9.1 - New GNSO Chair election timeline with travel guidelines (120 days for funded traveler submissions) Action Item(s): * Councilors to continue discussion with their respective groups to help understand the impact of the changes to the timeline for submitting travelers in relation to elections and react accordingly. GNSO Wrap Up session Approach and volunteers for GNSO Council review of GAC Communique * Staff to put the GAC Communique into the Council review template * Julf Helsingius, as Council liaison to the GAC, and Michele, Paul, Philippe, Tatiana to coordinate and prepare the Council response to the GAC Communique Letters from ICANN’s General Counsel (enforceability of ICANN’s Expected Standards of Behavior and the disciplinary situation in the RPM PDP WG) * Council leadership to draft response to ICANN General Counsel for Council review and subsequent transmission by ICANN Staff. Curative Rights Final Report – next steps * Council leadership to follow up on existing action item to prepare draft motion language for the various options proposed and available to the Council. Volunteers to draft Council letter re. improvements to the legislation tracker * None - volunteers captured in Action Item from wrap-up session Planning for ICANN65 - any input that Council leadership should consider as it prepares the agenda? * Council leadership to ensure SO/AC leaders are aware of the priorities of Councilors (e.g., emphasis on policy work, allocating time for policy work for the CCWG on Auction Proceeds, EPDP Phase 2, SubPro, RPMs, avoiding duplicative sessions) and take into account in preparing the draft GNSO schedule. Council liaison to EPDP IRT Council to seek volunteer on email list to serve as Council liaison to the informal IRT for EPDP phase 1

1 0

Fwd: Correspondence from GNSO Council Leadership Team to Mr. George Kirikos and Counsel
by Drazek, Keith 01 Apr '19

01 Apr '19

Hi all, FYI, a further exchange on this topic. Best, Keith Begin forwarded message: From: "Drazek, Keith" <kdrazek(a)verisign.com<mailto:kdrazek@verisign.com>> Date: April 1, 2019 at 11:51:39 AM EDT To: "robin(a)imaginelaw.com<mailto:robin@imaginelaw.com>" <robin(a)imaginelaw.com<mailto:robin@imaginelaw.com>> Cc: "abernstein(a)torys.com<mailto:abernstein@torys.com>" <abernstein(a)torys.com<mailto:abernstein@torys.com>>, "george(a)loffs.com<mailto:george@loffs.com>" <george(a)loffs.com<mailto:george@loffs.com>>, "brian.beckham(a)wipo.int<mailto:brian.beckham@wipo.int>" <brian.beckham(a)wipo.int<mailto:brian.beckham@wipo.int>>, "Corwin, Philip" <pcorwin(a)verisign.com<mailto:pcorwin@verisign.com>>, "kathy(a)kathykleiman.com<mailto:kathy@kathykleiman.com>" <kathy(a)kathykleiman.com<mailto:kathy@kathykleiman.com>>, "pmcgrady(a)winston.com<mailto:pmcgrady@winston.com>" <pmcgrady(a)winston.com<mailto:pmcgrady@winston.com>>, "Samantha.Eisner(a)icann.org<mailto:Samantha.Eisner@icann.org>" <Samantha.Eisner(a)icann.org<mailto:Samantha.Eisner@icann.org>>, "david.olive(a)icann.org<mailto:david.olive@icann.org>" <david.olive(a)icann.org<mailto:david.olive@icann.org>>, "john.jeffrey(a)icann.org<mailto:john.jeffrey@icann.org>" <john.jeffrey(a)icann.org<mailto:john.jeffrey@icann.org>>, "pam.little(a)alibaba-inc.com<mailto:pam.little@alibaba-inc.com>" <pam.little(a)alibaba-inc.com<mailto:pam.little@alibaba-inc.com>>, "rafik.dammak(a)gmail.com<mailto:rafik.dammak@gmail.com>" <rafik.dammak(a)gmail.com<mailto:rafik.dammak@gmail.com>>, "gregshatanipc(a)gmail.com<mailto:gregshatanipc@gmail.com>" <gregshatanipc(a)gmail.com<mailto:gregshatanipc@gmail.com>> Subject: RE: [EXTERNAL] Re: Correspondence from GNSO Council Leadership Team to Mr. George Kirikos and Counsel Dear Robin, Thank you for your email acknowledging receipt of the GNSO Council Leadership Team’s 29 March 2019 letter. Our request for acceptance and acknowledgement of enforceability of ICANN’s Expected Standards of Behavior is forward-looking and does not preclude your further engagement with ICANN’s General Counsel on the issues raised in your letter of 10 March 2019. The GNSO Council Leadership Team acknowledged that opportunity for further communication and elected to take no additional action at this time concerning the ongoing disciplinary issues involving Mr. Kirikos and Mr. Shatan. In fact, we did not require even the minimum threshold of an apology as outlined in ICANN’s escalation framework. Rather, we hope and expect this to be a fresh start for all parties and the RPM PDP WG based on respect for ICANN’s Expected Standards of Behavior. As such, we believe it is perfectly reasonable that Mr. Kirikos and Mr. Shatan respond to our letter by Friday, 5 April acknowledging and accepting the Expected Standards of Behavior, with a commitment to abide by them moving forward, subject to enforcement by the Co-Chairs and/or GNSO Council Leadership Team (as appropriate). As covered in our letter, the GNSO Council has a clear responsibility to ensure PDP Working Groups can conduct their work in a manner that is professional, efficient, timely, and consistent with ICANN’s Expected Standards of Behavior, and we take that obligation seriously. If we do not receive confirmation of this by 5 April, we will move Mr. Kirikos (and/or Mr. Shatan) to observer status within the RPM PDP WG, with an opportunity to be re-activated as a full member if and when we receive the necessary response. Thank you for your understanding. Sincerely, Keith Drazek GNSO Chair (on behalf of the GNSO Council Leadership Team) From: Robin Gross <robin(a)imaginelaw.com<mailto:robin@imaginelaw.com>> Sent: Friday, March 29, 2019 7:15 PM To: Drazek, Keith <kdrazek(a)verisign.com<mailto:kdrazek@verisign.com>> Cc: abernstein(a)torys.com<mailto:abernstein@torys.com>; george(a)loffs.com<mailto:george@loffs.com>; brian.beckham(a)wipo.int<mailto:brian.beckham@wipo.int>; Corwin, Philip <pcorwin(a)verisign.com<mailto:pcorwin@verisign.com>>; Kathy Kleiman <kathy(a)kathykleiman.com<mailto:kathy@kathykleiman.com>>; pmcgrady(a)winston.com<mailto:pmcgrady@winston.com>; Samantha Eisner <Samantha.Eisner(a)icann.org<mailto:Samantha.Eisner@icann.org>>; David Olive <david.olive(a)icann.org<mailto:david.olive@icann.org>>; John Jeffrey <john.jeffrey(a)icann.org<mailto:john.jeffrey@icann.org>>; pam.little(a)alibaba-inc.com<mailto:pam.little@alibaba-inc.com>; rafik.dammak(a)gmail.com<mailto:rafik.dammak@gmail.com>; Greg Shatan <gregshatanipc(a)gmail.com<mailto:gregshatanipc@gmail.com>> Subject: [EXTERNAL] Re: Correspondence from GNSO Council Leadership Team to Mr. George Kirikos and Counsel Dear Keith, Seven days is insufficient time to consider and respond to your letter. We request 14 days to respond, given your letter comes 19 days since our March 10, 2019 letter. Please let us know by 2 pm Eastern time on Monday April 1, 2019 whether this is acceptable. We are cc'ing Mr. Shatan, so that he be given equal time to consider his own response. We note for the record that we offered in good faith, in our March 10, 2019 letter, to have a telephone call in order to narrow the issues in dispute, but no response to that offer has ever been received. Thank you, Robin Gross Attorney for George Kirikos On Mar 29, 2019, at 11:02 AM, Drazek, Keith <kdrazek(a)verisign.com<mailto:kdrazek@verisign.com>> wrote: Dear Mr. Bernstein, Ms. Gross and Mr. Kirikos, Please find attached a letter from the GNSO Council Leadership Team concerning enforcement of ICANN’s Expected Standards of Behavior. We look forward to your reply. Sincerely, Keith Drazek GNSO Chair (on behalf of the GNSO Council Leadership Team) <GNSO Council Leadership Team Letter to Bernstein-Gross-Kirikos -- 29 March 2019.pdf>

1 0