April 2019 - council - lists.icann.org

Fwd: Re: Correspondence on Enforcement of ICANN's Expected Standards of Behavior
by Drazek, Keith 06 Apr '19

06 Apr '19

Hello all, Greg Shatan has submitted his response (attached) to the GNSO Council Leadership Team letter of 29 March 2019. Having satisfactorily done so, he will remain a member in good standing of the RPM PDP WG and other GNSO-related groups and lists. Regards, Keith Begin forwarded message: From: Greg Shatan <gregshatanipc(a)gmail.com<mailto:gregshatanipc@gmail.com>> Date: April 5, 2019 at 9:10:04 PM EDT To: "Drazek, Keith" <kdrazek(a)verisign.com<mailto:kdrazek@verisign.com>> Cc: "Corwin, Philip" <pcorwin(a)verisign.com<mailto:pcorwin@verisign.com>>, "Kathy Kleiman (kathy(a)kathykleiman.com<mailto:kathy@kathykleiman.com>)" <kathy(a)kathykleiman.com<mailto:kathy@kathykleiman.com>>, "brian.beckham(a)wipo.int<mailto:brian.beckham@wipo.int>" <brian.beckham(a)wipo.int<mailto:brian.beckham@wipo.int>>, "David Olive (david.olive(a)icann.org<mailto:david.olive@icann.org>)" <david.olive(a)icann.org<mailto:david.olive@icann.org>>, "Samantha.Eisner(a)icann.org<mailto:Samantha.Eisner@icann.org>" <Samantha.Eisner(a)icann.org<mailto:Samantha.Eisner@icann.org>>, "John Jeffrey (john.jeffrey(a)icann.org<mailto:john.jeffrey@icann.org>)" <john.jeffrey(a)icann.org<mailto:john.jeffrey@icann.org>>, "pmcgrady(a)winston.com<mailto:pmcgrady@winston.com>" <pmcgrady(a)winston.com<mailto:pmcgrady@winston.com>>, "rafik.dammak(a)gmail.com<mailto:rafik.dammak@gmail.com>" <rafik.dammak(a)gmail.com<mailto:rafik.dammak@gmail.com>>, "pam.little(a)alibaba-inc.com<mailto:pam.little@alibaba-inc.com>" <pam.little(a)alibaba-inc.com<mailto:pam.little@alibaba-inc.com>> Subject: [EXTERNAL] Re: Correspondence on Enforcement of ICANN's Expected Standards of Behavior Dear Keith, Rafik and Pam, Please find attached my response to your letter of March 29. Thank you for all your work on this matter. Best regards, Greg On Fri, Mar 29, 2019 at 2:08 PM Drazek, Keith <kdrazek(a)verisign.com<mailto:kdrazek@verisign.com>> wrote: Dear Greg, 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)

1 0

NEW LINK--Update Observers--Call for Volunteers: Registration Data Policy Implementation - pre-IRT
by Andrea Glandon 05 Apr '19

05 Apr '19

My apologies, Please use this link for observers to join: https://docs.google.com/forms/d/e/1FAIpQLSdqyFFrSFXIpwwpUoYCTqfnekQf9-m9pAB… Thank you! Kind Regards, Andrea Glandon From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of Andrea Glandon <andrea.glandon(a)icann.org> Date: Friday, April 5, 2019 at 14:55 To: "gnso-epdp-team(a)icann.org" <gnso-epdp-team(a)icann.org>, "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [gnso-secs] Update Observers--Call for Volunteers: Registration Data Policy Implementation - pre-IRT Dear all, Observers will now be able to sign up in a read only status to the pre-IRT email list. Any community members who would like to join the email list as an observer, should complete this form: https://drive.google.com/open?id=1VBLejg2GvisYuqWjsa34_84nBYaenZMWG2TITxaxa… [drive.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__drive.google.com_open-…> Please let me know if you have any questions. Thank you. Kind Regards, Andrea Glandon From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of Andrea Glandon <andrea.glandon(a)icann.org> Date: Friday, March 29, 2019 at 13:27 To: "gnso-epdp-team(a)icann.org" <gnso-epdp-team(a)icann.org>, "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [gnso-secs] Call for Volunteers: Registration Data Policy Implementation - pre-IRT 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.

1 0

Update Observers--Call for Volunteers: Registration Data Policy Implementation - pre-IRT
by Andrea Glandon 05 Apr '19

05 Apr '19

Dear all, Observers will now be able to sign up in a read only status to the pre-IRT email list. Any community members who would like to join the email list as an observer, should complete this form: https://drive.google.com/open?id=1VBLejg2GvisYuqWjsa34_84nBYaenZMWG2TITxaxa… Please let me know if you have any questions. Thank you. Kind Regards, Andrea Glandon From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of Andrea Glandon <andrea.glandon(a)icann.org> Date: Friday, March 29, 2019 at 13:27 To: "gnso-epdp-team(a)icann.org" <gnso-epdp-team(a)icann.org>, "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [gnso-secs] Call for Volunteers: Registration Data Policy Implementation - pre-IRT 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.

1 0

EPDP list of Observers is incomplete
by Ayden Férdeline 05 Apr '19

05 Apr '19

Dear all, At the moment, the list of Observers for the EPDP's mailing list is incomplete. When I have sent messages to the EPDP list, I have received replies from some individuals, seeking to influence me, whose names are not listed on the Observer page as Observers. It is possible that we do not even need to record the names of Observers. Certainly in the case of the pre-IRT, I have suggested that listing their names might be unnecessary - I'm not sure what it really adds. However this is another discussion altogether. If our existing practice in GNSO-chartered working groups is to record the names of Observers, and I believe it is, then I believe this list should be kept complete and up to date. I have asked that the EPDP Observer list be updated and ICANN staff have declined to update the list. The missing names are of ICANN staff members who work in GSE. It apparently would require the support of the GNSO Council to add their names to the page. As these staff are not supporting the EPDP, or at least are not supporting it to my knowledge, but have been reading the emails and seeking to influence EPDP members, then I believe their names should be made public along with the rest of the EPDP Observers, official staff support, members, and alternates. I do not understand why their names would not be published and I think it is inconsistent with the principles of accountability and transparency that ICANN claims to value. When I have pushed back and asked why these names cannot be added, I was told that it is to keep the wiki page short. However it already has over 200 names so it isn't short at the moment. I prefer to prioritise having a complete list, rather than a concise one, as in the case of the wiki, there are really no technical restrictions to adding the missing names to the page. We trust, or at least I trust, that when I visit something on the ICANN website, that it will be complete and accurate. If it isn't, I expect there to be a disclaimer or note explaining what it included, so I can make that decision myself as to its accuracy. The EPDP list of Observers does not state that some people observing the list will not have their names included. If that is the case, there should be a defined policy around who is/is not named, but I see no reason not to include the names of ICANN staff who are observing the mailing list and seeking to influence discussions behind the scenes. I am sending this message to the Council list because I have been advised by ICANN staff that the Observer list will only be updated if it is the expressed wish of either the GNSO Council or of the EPDP chair. I would like to ask the Council to support this request please. Thank you. Ayden Férdeline

8 10

Planning for ICANN 65 -- Policy Forum
by Drazek, Keith 05 Apr '19

05 Apr '19

Hi GNSO Stakeholder Group and Constituency Chairs: Just a brief note to address meeting planning for ICANN 65 in Marrakech. The GNSO Council leadership team and ICANN Policy staff are now working to provide detail to the draft schedule and to prioritize resource allocation. As each of you know, the annual June meeting is the Policy Forum, which is now typically held in a smaller venue and for only four days instead of six, so we have unique constraints on room availability. To be explicit, the GNSO is normally allocated TWO rooms with which to conduct all our business over four days (additional rooms may be available, but this is usually dependent on other SO/ACs not using their rooms and as such cannot be counted on). That means the PDP WG meetings, IRT meetings, GNSO Council meetings, and any SG/C meetings, need to fit within those constraints. According to its name, the Policy Form is meant to focus on advancing policy work, and we have several PDPs, and IRT, and a CCWG that are approaching important stages of their work, and where face-to-face engagement is most valuable. As a GNSO community, we need to ensure we give these groups the time they need to move things forward this year. Further, as you have seen via other email, we are currently working with other SO/AC Chairs to try to identify early any need for High-Interest Topic and Cross-Community sessions, so that some of the seven 90-minute slots currently allocated to HIT/CC might be reallocated to support our policy work. All that said, I would like to ask each of you to carefully prioritize your own SG/C requirements and preferences for meeting space and time. If we are able to reduce the number of HIT/CC sessions, we will have greater flexibility, but otherwise, we simply won't be able to accommodate all the sessions normally expected at the other two ICANN meetings. Thanks in advance for your cooperation and understanding! Best, Keith

2 2

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

05 Apr '19

Hi all, Mr. Kirikos has responded with the attached letter indicating he will not accept and abide by ICANN’s Expected Standards of Behavior (ESOB). As such, per the notice provided in the Council Leadership Team’s letter of 29 March, he will be placed on observer status in the RPM PDP WG and any other GNSO-related forum until such time we receive the necessary communication confirming acceptance of the ESOB, or such time the ICANN Ombuds finds he can return following any appeal. Thanks, Keith Begin forwarded message: From: George Kirikos <george(a)loffs.com<mailto:george@loffs.com>> Date: April 5, 2019 at 1:33:47 AM EDT To: "Drazek, Keith" <kdrazek(a)verisign.com<mailto:kdrazek@verisign.com>> Cc: "robin(a)imaginelaw.com<mailto:robin@imaginelaw.com>" <robin(a)imaginelaw.com<mailto:robin@imaginelaw.com>>, "abernstein(a)torys.com<mailto:abernstein@torys.com>" <abernstein(a)torys.com<mailto:abernstein@torys.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>> Subject: [EXTERNAL] Re: Re: Correspondence from GNSO Council Leadership Team to Mr. George Kirikos and Counsel Dear Mr. Drazek, Mr. Dammak, and Ms. Little, My response to your March 29, 2019 letter is attached. Sincerely, George ----------------------------------------------- George Kirikos CEO Leap of Faith Financial Services Inc. 34 Burnfield Avenue, Toronto, Ontario M6G 1Y5 Canada Tel: +1 (416) 588-0269 Fax: +1 (416) 588-5641 E-mail: George(a)LOFFS.com<mailto:George@LOFFS.com> Website: http://www.LOFFS.com This email and any attachments are for the sole use of the intended recipients and may be privileged or confidential. Any distribution, printing or other use by anyone else is prohibited. If you are not an intended recipient, please contact the sender immediately, and permanently delete this email and attachments. To stop receiving commercial electronic messages, visit http://optout.loffs.com/ On Mon, Apr 1, 2019 at 11:51 AM Drazek, Keith <kdrazek(a)verisign.com<mailto:kdrazek@verisign.com>> wrote: 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>

2 1

**REMINDER: EOI DEADLINE 8 APRIL 2019** Updated/Extended EPDP Chair EOI
by Julie Bisland 05 Apr '19

05 Apr '19

Hi all, The deadline for the EOI response has passed and there was only one respondent. In light of the EPDP and GNSO Council discussions in Kobe, I think it's appropriate to extend the deadline for two weeks to Monday, 8 April while providing some additional details about the anticipated work load and pace/intensity of Phase 2. I hope this will inform potential Chair candidates and encourage a more robust response. We have updated the attached EOI document accordingly, which will be posted later today. Please let me know if you have any questions. Regards, Keith From: Marika Konings <marika.konings(a)icann.org<mailto:marika.konings@icann.org>> Sent: Thursday, March 21, 2019 7:54 PM To: Drazek, Keith <kdrazek(a)verisign.com<mailto:kdrazek@verisign.com>> Subject: [EXTERNAL] Updated EPDP Team EOI How does the attached look? Note that I'll be traveling part of the day tomorrow so I may be less responsive. Please make sure to copy in Nathalie on the final version so she can co-ordinate the distribution. Thanks, Marika Marika Konings Vice President, Policy Development Support - GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>.

1 0

**REMINDER: EOI DEADLINE 8 APRIL 2019** Expressions of Interest Sought for Chair of GNSO EPDP on the Temporary Specification for gTLD Registration Data – Phase 2
by Julie Bisland 05 Apr '19

05 Apr '19

https://www.icann.org/news/announcement-2019-03-01-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> LOS ANGELES –1 March 2019 – The Generic Names Supporting Organization (GNSO) is looking for expressions of interest to chair Phase 2 of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data. The EPDP Team recently completed its Phase 1 work and is expected to commence planning for Phase 2 at ICANN64 meeting in Kobe, Japan. During Phase 2, the EPDP Team will work on a system for standardized access to non-public registration data, topics identified in the annex to the Temporary Specification, as well as a number of carry over items from Phase 1. The GNSO Council is looking to appoint a neutral Chair to the EPDP Team. With such an important issue under consideration, significant responsibility comes with the role to ensure the success of deliberations. The EPDP Team is expected to have regular calls, although it may be necessary to hold calls more frequently if need arises. Additionally, the EPDP Team may have face-to-face meetings in order to meet the required milestones of the EPDP. The EPDP Team is expected to start developing the work plan for Phase 2 at ICANN64 in Kobe for which the GNSO Council may provide further guidance. There will be no compensation associated with the role of the EPDP Team Chair; however, travel associated with any face-to-face meetings may be supported by ICANN org. To express interest in this role, please submit an Expression of Interest to EOI-EPDPTeam-Chair(a)icann.org<mailto:EOI-EPDPTeam-Chair@icann.org> by 22 March 2019 at 14:00 UTC. Please answer the following questions: · What is your interest in this position? · What particular skills and attributes do you have that will assist you in chairing the EPDP? · What is your knowledge of the Temporary Specification for gTLD Registration Data, EPDP Team's Phase 1 work and associated challenges and requirements particularly as it relates to the EPDP? · What is your experience in and knowledge of the GNSO Policy Development Process, ICANN's consensus policies, ICANN's registry agreements and the Registrar Accreditation Agreement related to gTLD registration data? · Are you able to commit the time required and necessary work needed to chair the EPDP, noting that this to a certain extend will be dependent on the EPDP Team's work plan for phase 2 which is under development? · Conflict of Interest Statement – do you have any affiliation with or involvement in any organization or entity with any financial or non-financial interest in the subject matter of this EPDP? · Please also include: · A link to an up-to-date Statement of Interest (SOI) - https://community.icann.org/display/gnsosoi/New+SOIs · A statement confirming your commitment and ability to act neutrally. Application materials will be reviewed by the Council leadership and will not be shared publicly. Names of applicants, including the recommended candidate, will be shared with the GNSO Council for its consideration. The Council leadership is expected to provide its recommendation to the GNSO Council in time for the GNSO Council meeting on 18 April 2019. Additional questions and inquiries can be sent to EOI-EPDPTeam-Chair(a)icann.org<mailto:EOI-EPDPTeam-Chair@icann.org>. More Information · Temporary Specification for gTLD Registration Data [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> · Additional information about the EPDP is located in Annex-A1 [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> of the ICANN Bylaws and the EPDP Manual [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> [PDF, 345 KB]. · EPDP Charter<https://community.icann.org/x/0opHBQ> · EPDP wiki<https://community.icann.org/x/IYEpBQ> · EPDP Phase 1 Final Report [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_draf…> [PDF, 2.7 MB] About EPDP On 17 May 2018, the ICANN Board approved the Temporary Specification for gTLD Registration Data. The Board took this action to establish temporary requirements for how ICANN and its contracted parties would continue to comply with existing ICANN contractual requirements and community-developed policies related to WHOIS, while also complying with the European Union's General Data Protection Regulation (GDPR). The Temporary Specification has been adopted under the procedure for Temporary Policies outlined in the Registry Agreement (RA) and Registrar Accreditation Agreement (RAA). Following adoption of the Temporary Specification, the Board "shall immediately implement the Consensus Policy development process set forth in ICANN's Bylaws." This Consensus Policy development process on the Temporary Specification would need to be carried out within a one-year period. Additionally, the scope includes discussion of a System for Standardized Access to Non-Public Registration Data. However, the discussion of a Standardized Access System will occur only after the EPDP Team has comprehensively answered a series of "gating questions" and non-objection by the GNSO Council. About ICANN ICANN's mission is to help ensure a stable, secure, and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world. ANNEX A – CHAIR RESPONSIBILITIES AND EXPECTATIONS As outlined in the GNSO Working Group Guidelines, the purpose of a Chair is to call meetings, preside over working group (WG) deliberations, manage the process so that all participants have the opportunity to contribute, and report the results of the WG to the Chartering Organization. These tasks require a dedicated time commitment as each call has to be prepared, the agenda concretized, and relevant material has to be reviewed. The Chair shall be neutral. While the Chair may be a member of any group which also has representation on the EPDP Team, the Chair shall not act in a manner which favors such group. The Chair shall not be a member of the PDP Team for purposes of consensus calls. In addition, it is required – that interested candidates have considerable experience in Chairing working groups, and direct experience with at least one GNSO Policy Development Process throughout its lifecycle would be an advantage. Familiarity with the functioning of a Working Group is important to understand the various leadership skills that are necessary to employ during a WG's lifecycle. For example, a chair has to ensure that debates are conducted in an open and transparent matter and that all interests are equally represented within the WG's discussions. During the later stages of a WG when recommendations are drafted, a Chair will benefit from understanding the viewpoints of various members to ensure that an acceptable and effective outcome – ideally in form of consensus – can be achieved. In short, the EPDP Team Chair is expected to: 1. Attend all EPDP Team meetings to ensure continuity and familiarity with the subject matter and the on-going discussions; 2. Prepare meetings by reading all circulated materials; 3. Be familiar with the subject matter, including but not limited to GDPR and data protection laws, and actively encourage participation during the calls 4. Be active on the EPDP Team mailing list and invite EPDP Team participants to share their viewpoints; 5. Drive forward the EPDP Team and assure that discussions remain on point; 6. Work actively towards achieving policy recommendations that ideally receive full consensus; 7. Ensure that particular outreach efforts are made when community reviews are done of the EPDP Team's output; 8. Underscore the importance of achieving overall representational balance on any sub-teams that are formed; 9. Encourage and, where necessary, enforce the ICANN Standards of Behavior and resolve any conflicts in a timely manner. 10. Co-ordinate with ICANN staff and ensure that the EPDP Team is supported as effectively as possible 11. Conduct consistent timely reporting to the GNSO Council on the progress of the EPDP. Finally, as also pointed out the in GNSO Working Group Guidelines, 'appointing a co-chair(s) or vice-chair(s) may facilitate the work of the Chair by ensuring continuity in case of absence, sharing of workload, and allowing the Chair to become engaged in a particular debate.' As a result, similar tasks and skills are expected from vice chairs, although the overall workload may be reduced as a result of being able to share this with the Chair. Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

ICANN65 GNSO Informal Council dinner
by Nathalie Peregrine 05 Apr '19

05 Apr '19

Dear councilors, ICANN65 is fast approaching, and with that, as per tradition, the GNSO Informal Council dinner will need a councilor to sponsor the event. The dinner is scheduled to take place on Monday 24 June from 19:00 local time onwards. Staff is on hand of course to assist the councilor-sponsor with venue research, RSVP gathering and liaising with the selected venue once it is confirmed. Please let me know if you would like to take part in organizing this event, or if from your past experience in Marrakesh, you may have any venues to suggest. Thank you! Kind regards, Nathalie Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

Fwd: [Gnso-epdp-team] NTIA Letter re: EPDP Phase 2
by Rafik Dammak 04 Apr '19

04 Apr '19

Hi all, Attached a letter from NTIA sent to ICANN board and was shared in EPDP list. Best, Rafik ---------- Forwarded message --------- From: Chris Disspain <chris(a)disspain.uk> Date: Fri, Apr 5, 2019, 06:12 Subject: [Gnso-epdp-team] NTIA Letter re: EPDP Phase 2 To: <gnso-epdp-team(a)icann.org> FYI Cheers, CD Begin forwarded message: > > > _______________________________________________ > icann-board mailing list > icann-board(a)icann.org > https://mm.icann.org/mailman/listinfo/icann-board _______________________________________________ Gnso-epdp-team mailing list Gnso-epdp-team(a)icann.org https://mm.icann.org/mailman/listinfo/gnso-epdp-team

1 0