July 2019 - council - lists.icann.org

Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
by Marie Pattullo 29 Jul '19

29 Jul '19

Hi all, Sorry if I missed it, but where are we on this, please? Also repeating my question from last week, “do we know how this will be used, as in: when they get community feedback, what will they actually do with it? Just add it to a list? Or is there a process envisaged to (e.g.) forward relevant updates to SOs/SGs/Cs or even external consultants/experts etc.? Should we ask them for clarity on that?” Elsa, to your point below, as we suggested in the redraft, I think the highlighted bit may answer your question? 5. The GNSO Council considers the GAC to be an important partner in these discussions and we would be delighted if GAC members could alert us to draft legislation which might have an impact on ICANN’s contracts and policies. However, we understand that often the GAC is not in a position to be able to do so, so we believe the onus must ultimately fall on ICANN org to structure the dialogue and to monitor regulatory and legislative developments. They/their colleagues will be the one doing such drafting so they should be a good resource, I think. Kind regards. Marie From: council <council-bounces(a)gnso.icann.org> On Behalf Of Elsa S Sent: Wednesday, July 17, 2019 4:37 PM To: Drazek, Keith <kdrazek(a)verisign.com> Cc: council(a)gnso.icann.org; gnso-secs(a)icann.org; council-bounces(a)gnso.icann.org Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thanks to all who worked on this draft. I have a question about the fifth line: i don’t see the point of singling out the GAC given that we have already mentioned the importance of community input and the need for ICANN to take the lead on structuring dialogue and monitoring in the other points. For reference: Fifth, the GNSO Council considers the GAC to be an important partner in these discussions and we would be delighted if they are able to alert us to potentially problematic legislation. However, we understand that often the GAC is not in a position to be able to do so, so we believe the onus must ultimately fall on ICANN org to structure the dialogue and to monitor regulatory and legislative developments. Best, Elsa — On Tue, Jul 16, 2019 at 5:59 AM Drazek, Keith via council <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> wrote: Hi all, Thanks for all the good work on this response. I have added one more bullet to the letter, which acknowledges and supports further consideration of the potential for the CCEG-IG to serve a formal or informal collaborating function between ICANN Board, ICANN Org, and the community (including GAC) on this important work. Best, Keith From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of Pam Little Sent: Tuesday, July 16, 2019 10:08 AM To: Darcy Southwell <darcy.southwell(a)endurance.com<mailto:darcy.southwell@endurance.com>>; philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com>; council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> Cc: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>; council(a)gnso.icann.org<mailto:council@gnso.icann.org> Subject: [EXTERNAL] Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Hi all, Apologies - I inadvertently omitted the version that Flip posted earlier, which contained further changes to the third issue. Please use the attached version instead. Kind regards, Pam ------------------------------------------------------------------ Sender:PAMELALITTLE <pam.little(a)alibaba-inc.com<mailto:pam.little@alibaba-inc.com>> Sent At:2019 Jul. 16 (Tue.) 09:01 Recipient:Darcy Southwell <darcy.southwell(a)endurance.com<mailto:darcy.southwell@endurance.com>>; philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com> <philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com>>; council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> Cc:gnso-secs@icann.org<mailto:Cc%3Agnso-secs@icann.org> <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>>; council(a)gnso.icann.org<mailto:council@gnso.icann.org> <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject:Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thank you very much to those who contributed to the draft. I have made a few more suggested edits, including the following for clarity and to avoid repetition: * add a definition: ICANN’s contracts with registries and registrars, consensus policies, and policies in effect or in development (“ICANN’s Contracts and Policies”) * merge the second and fifth points to read: • Second, we encourage ICANN org to conduct standard regulatory impact assessments so that the community can understand the intended rationale for a law/regulation/directive, specific extracts of the proposed text that could have implications on ICANN’s Contracts and Policies, and outline concretely what implications are anticipated. A timeline should be included so the community can understand how imminent the law/regulation/directive is and when it needs to take action. Once such law or regulation has been adopted, ICANN org should undertake a compliance assessment as soon as possible to ensure sufficient time to address any deficiencies or issues. I suggest we aim to send the finalized version by COB this Friday 19th July. So if you have further edits or any concerns or objections, please post to the Council mailing list. Kind regards, Pam ------------------------------------------------------------------ Sender:Flip Petillion <fpetillion(a)petillion.law<mailto:fpetillion@petillion.law>> Sent At:2019 Jul. 16 (Tue.) 00:39 Recipient:Darcy Southwell <darcy.southwell(a)endurance.com<mailto:darcy.southwell@endurance.com>>; philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com> <philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com>> Cc:gnso-secs@icann.org<mailto:Cc%3Agnso-secs@icann.org> <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>>; council(a)gnso.icann.org<mailto:council@gnso.icann.org> <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject:Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements All: I made a change in the third issue. Best Flip Flip Petillion fpetillion(a)petillion.law<mailto:fpetillion@petillion.law> +32484652653 www.petillion.law<http://www.petillion.law> [signature_2145422569]<http://www.petillion.law/> Attorneys – Advocaten - Avocats From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of Darcy Southwell <darcy.southwell(a)endurance.com<mailto:darcy.southwell@endurance.com>> Date: Friday, 12 July 2019 at 17:07 To: "philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com>" <philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com>> Cc: "gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>" <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>>, "council(a)gnso.icann.org<mailto:council@gnso.icann.org>" <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements All, I made a minor clarification in the fifth issue. Thanks, Darcy On Tue, Jul 9, 2019 at 8:26 AM <philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com>> wrote: Thanks (and I don’t even have the holidays to blame :s ). Both Ayden’s points, and the rephrasing suggested by Darcy are excellent. The first item relative to community’s input has been raised a number of times; I remember asking a question during a CSG meeting with the Board in Kobe. Not that the answer was unsatisfactory but it was hardly practical. Ultimately, I think we need to keep in mind the primary goal of all this, ie (I think) should there be a “new GDPR in the making” (in terms of having an impact on policies), the community should be able to detect it with this tool. I’m not sure it would in its current state, so the points are well made. Regards, Philippe From: council [mailto:council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>] On Behalf Of McGrady, Paul D. Sent: Monday, July 08, 2019 1:30 PM To: Darcy Southwell; Ayden Férdeline; Steve Chan Cc: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>; council(a)gnso.icann.org<mailto:council@gnso.icann.org> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thanks Darcy. These edits look great. Sorry so slow in responding. I was overtaken by the holiday! Best, Paul From: Darcy Southwell <darcy.southwell(a)endurance.com<mailto:darcy.southwell@endurance.com>> Sent: Monday, July 1, 2019 6:58 PM To: McGrady, Paul D. <PMcGrady(a)taftlaw.com<mailto:PMcGrady@taftlaw.com>>; Ayden Férdeline <icann(a)ferdeline.com<mailto:icann@ferdeline.com>>; Steve Chan <steve.chan(a)icann.org<mailto:steve.chan@icann.org>> Cc: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>; council(a)gnso.icann.org<mailto:council@gnso.icann.org> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thanks for taking the lead, Ayden, and for your edits, Paul. I support Paul’s edits. I have proposed some additional edits in addition to Paul’s in the attached. I think it may be better received if we qualify what we’re seeking from ICANN Org, rather than referencing ICANN activities, which could be perceived as so sweepingly broad that it’s not doable. Thanks, Darcy From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of "McGrady, Paul D." <PMcGrady(a)taftlaw.com<mailto:PMcGrady@taftlaw.com>> Date: Sunday, June 30, 2019 at 8:28 AM To: Ayden Férdeline <icann(a)ferdeline.com<mailto:icann@ferdeline.com>>, Steve Chan <steve.chan(a)icann.org<mailto:steve.chan@icann.org>> Cc: "gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>" <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>>, "council(a)gnso.icann.org<mailto:council@gnso.icann.org>" <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thanks Ayden. All, attached is a revision version with a few edits, mostly around tone. Best, Paul This message may contain information that is attorney-client privileged, attorney work product or otherwise confidential. If you are not an intended recipient, use and disclosure of this message are prohibited. If you received this transmission in error, please notify the sender by reply e-mail and delete the message and any attachments. From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of Ayden Férdeline Sent: Sunday, June 30, 2019 6:25 AM To: Steve Chan <steve.chan(a)icann.org<mailto:steve.chan@icann.org>> Cc: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>; council(a)gnso.icann.org<mailto:council@gnso.icann.org> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements I have drafted a message on behalf of the Council for Council's consideration on this topic. This is based upon our previous conversations. Please find attached and pasted below my signature. Thanks. Ayden Férdeline -- Recommended Improvements from the GNSO Council on ICANN Org Legislative Statement The GNSO Council supports ICANN org in its initiative to identify legislative and regulatory efforts across the globe that may have impacts on ICANN activities. However, we have some recommended improvements to the approach that ICANN org takes. * First, the GNSO Council believes that the current, crowdsourced approach where the community is expected to identify errors and omissions in the Global Legislative and Regulatory Developments Report is inappropriate. If ICANN is a professional organization then its professional staff should be comprehensively monitoring the regulatory landscape within which we operate. * Second, we encourage ICANN org to conduct proper regulatory impact assessments so that the community can understand the intended rationale for a law/regulation/directive, specific extracts of the proposed text that could have implications on activities within ICANN’s remit, and outline concretely what implications are anticipated for ICANN. A timeline should be included so we understand how imminent the law/regulation/directive is and when we need to take action. * Third, we encourage ICANN org to partner with a professional firm to receive regular updates (at least every three months) focused on those key regions which cause the majority of concerns. These reports must be made available to ICANN community members in a timely manner. * Fourth, while the GNSO Council would be pleased to accept ongoing monitoring reports, we would also welcome the opportunity to be briefed at our face-to-face meetings by ICANN’s government relations team and to enter into a dialogue about issues that have the potential to cause us concern. * Fifth, once a law or regulation has been adopted, ICANN org must undertake a compliance assessment in order to fully understand what implications there may or may not be on ICANN activities. * Sixth, the GNSO Council considers the GAC to be an important partner in these discussions and we would be delighted if they are able to alert us to potentially problematic legislation. However, we understand that often the GAC is not in a position to be able to do so, so we believe the onus must ultimately fall on ICANN org to structure the dialogue and to monitor regulatory and legislative developments. Thank you for welcoming our input. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, 23 June 2019 18:01, Steve Chan <steve.chan(a)icann.org<mailto:steve.chan@icann.org>> wrote: Dear Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana, In reviewing the Council’s action items, we recognized that the item below is still outstanding: Small group of Councilors to develop draft message to ICANN Org to provide input on legislative tracker. Based on feedback, Council leadership to consider scheduling follow up discussion at ICANN65. We wanted to bring this to your attention, as you all volunteered to work on this item. While the latter part of the action item (e.g., engaging at ICANN65) is likely impractical at this point, you may still want to draft a message to send to ICANN org. As Keith noted, please work together and let staff know if you need any assistance. Best, Steve From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of "Drazek, Keith via council" <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Reply-To: "Drazek, Keith" <kdrazek(a)verisign.com<mailto:kdrazek@verisign.com>> Date: Thursday, April 4, 2019 at 7:35 PM To: "council(a)gnso.icann.org<mailto:council@gnso.icann.org>" <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Cc: "gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>" <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>> Subject: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana: During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort. As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development. Please work together and with Staff to help kick off this important and timely work. Thanks, Keith _______________________________________________ council mailing list council(a)gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ council mailing list council(a)gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

3 3

Re: [council] [Ext] RE: Call for volunteers IRP-IOT and proposed Council endorsement process
by Emily Barabas 26 Jul '19

26 Jul '19

Sent on behalf of Keith Drazek: Dear all, Noting that the message below may not have made it to the Council mailing list, please respond no later than Monday, 29 July if you have concerns or disagree with the Council leadership’s recommendation that Council endorse all seven of the IRP-IOT candidates listed below. The deadline for submission to the ICANN Board is 31 July. Thanks, Keith From: "Drazek, Keith" <kdrazek(a)verisign.com> Date: Friday, 19 July 2019 at 12:14 To: "Drazek, Keith" <kdrazek(a)verisign.com>, Emily Barabas <emily.barabas(a)icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [Ext] RE: [council] Call for volunteers IRP-IOT and proposed Council endorsement process Hi all, Following up our discussion on this topic, please advise no later than Friday, 26 July if you have concerns or disagree with the Council leadership’s recommendation that we endorse all seven of the IRP-IOT candidates listed below. The deadline for submission to the ICANN Board is 31 July. Thanks, Keith From: council <council-bounces(a)gnso.icann.org> On Behalf Of Drazek, Keith via council Sent: Thursday, July 18, 2019 7:13 PM To: emily.barabas(a)icann.org; council(a)gnso.icann.org Cc: gnso-secs(a)icann.org Subject: [EXTERNAL] Re: [council] Call for volunteers IRP-IOT and proposed Council endorsement process Thanks Emily. We will add the IRP-IOT topic to AOB on our agenda today. Keith From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of Emily Barabas Sent: Thursday, July 18, 2019 10:37 AM To: council(a)gnso.icann.org<mailto:council@gnso.icann.org> Subject: [EXTERNAL] Re: [council] Call for volunteers IRP-IOT and proposed Council endorsement process Dear all, With apologies for the delay, you can find the Expressions of Interest from the candidates here: * Kristina Rosette EOI: https://docs.google.com/document/d/13QfP6UX4Mi7RjpTqkGVl0Oj-E-D5MOAMqaGB8mu… [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> * Jay Sudowski EOI: https://docs.google.com/document/d/18wOG0x1U8rakh8kvRDq3EmVgK3fjiclST1ID-TD… [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> * Susan Payne EOI: https://docs.google.com/document/d/1cfqs2GWYNmjOJgWU-yUhmr9ACJZF1xfd7jCFk6u… [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> * Raphael Beauregard-Lacroix EOI: https://docs.google.com/document/d/18tbTVC-g_DNQb3eP--WhSkZKeMWSFua6XvTfYqZ… [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> * Helen Lee EOI: https://docs.google.com/document/d/1RY32yE2vsx3N_nP0Qx2vYBonYPeM7ghLJWoDvqf… [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> * Paul Rosenzweig EOI: https://docs.google.com/document/d/1W363-XHioqxfywhxb4zCB14ugJm6GnLY6H1EvYm… [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> * Flip Petillion EOI: https://docs.google.com/document/d/1fqZx5HkmqsjXJhSoxW5yHAJ0kyobsJT6e5K0TPQ… [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> Kind regards, Emily From: Emily Barabas <emily.barabas(a)icann.org<mailto:emily.barabas@icann.org>> Date: Wednesday, 17 July 2019 at 09:54 To: "council(a)gnso.icann.org<mailto:council@gnso.icann.org>" <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: Re: [council] Call for volunteers IRP-IOT and proposed Council endorsement process Dear Councilors, As a follow up to the message below, seven IRP-IOT candidates expressed interest in receiving endorsement from the GNSO: * Flip Petillion * Paul Rosenzweig * Helen Lee * Raphael Beauregard-Lacroix * Susan Payne * Jay Sudowski * Kristina Rosette Council leadership considered the Expressions of Interest from these candidates and recommends providing endorsement for all seven candidates. There will be an opportunity for Councilors to discuss this recommendation further during the upcoming Council call. Kind regards, Emily From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org<mailto:nathalie.peregrine@icann.org>> Date: Wednesday, 3 July 2019 at 12:18 To: "council(a)gnso.icann.org<mailto:council@gnso.icann.org>" <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Cc: "gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>" <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>> Subject: [council] Call for volunteers IRP-IOT and proposed Council endorsement process Dear Council Members, SG/C Chairs, As you may be aware, the ICANN Board Accountability Mechanisms Committee (BAMC) recently launched a call for volunteers to recompose the Independent Review Process (IRP) Implementation Oversight Team (IOT) (see https://www.icann.org/en/system/files/correspondence/sanchez-to-siddiqui-et… [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…>). The letter also notes that ‘if any SO/AC wishes to vet candidates through its own candidate selection process, the BAMC welcomes that work, diligence, and indication of support when passing the candidate further into the process’. As during recent discussions, Council members as well as GNSO community members have highlighted the importance of this process and the need for the GNSO to contribute candidates with expertise to this process, Council leadership would like to propose the following steps: 1. Any candidates interested in GNSO Council endorsement should send their Expressions of Interest describing how his or her experience aligns with the skills identified, as well as a commitment to the estimated time demands to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> by Friday 12 July 2019. 2. Council leadership will evaluate the applications against the skills and experience outlined in the call for volunteers (see also below). 3. Council leadership will share with the Council the proposed candidates for GNSO Council endorsement by 17 July 2019 at the latest. 4. Council to consider proposed candidates for endorsement during 18 July 2019 GNSO Council meeting. 5. GNSO Secretariat to submit EOIs of endorsed candidates by 31 July 2019 at the latest. 6. All the EOIs of the candidates that meet the qualifications will be provided to the BAMC for evaluation and identification of new members. If you have any questions or concerns about this proposed process, please let us know as soon as possible. We appreciate that the timeline is short, but we hope this will not prevent you from encouraging members who have the required skills and experience from applying. To be clear, nothing prevents those not seeking GNSO Council endorsement from submitting their applications directly to the BAMC. With best regards, Pam Little and Rafik Dammak, Vice Chairs, GNSO Council On behalf of GNSO Council Leadership From https://www.icann.org/en/system/files/correspondence/sanchez-to-siddiqui-et… [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> Skills and Experience Required The IOT has very important work remaining, including the finalization of a set of Updated Supplementary Procedures that will define the conduct of IRPs and assure that the purposes of the IRP are upheld. These Procedures must also align with principles of international arbitration. As a result, those members of our community that you identify and encourage to join the IOT, should have the necessary legal or judicial skills and experience in disputes such as IRPs, arbitrations, or other alternate dispute resolution processes. Specific familiarity with ICANN’s accountability mechanisms is another important skill that we hope to see amongst new members. No single candidate must bring all of this experience, but as we look at the IOT as a whole, we are striving for a variety of experiences that, taken together, make the IOT well-suited to finalize a set of procedures to conduct IRP proceedings. IOT members must also have the time and availability to attend at least a one hour call each week to participate on IOT telephonic meetings, as well as sufficient availability to contribute to the work online. 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

FW: [gnso-secs] [ECAdmin] Notice of Expiration of a Rejection Action Petition Period
by Terri Agnew 26 Jul '19

26 Jul '19

FYI, please see below. Thank you, Terri From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of "Stephen Deerhake @ ASNIC" <sdeerhake(a)nic.as> Date: Thursday, July 25, 2019 at 6:56 AM To: John Jeffrey <john.jeffrey(a)icann.org>, Goran Marby <goran.marby(a)icann.org>, Cherine Chalaby <cherine.chalaby(a)board.icann.org>, "ecadmin(a)icann.org" <ecadmin(a)icann.org> Subject: [gnso-secs] [ECAdmin] Notice of Expiration of a Rejection Action Petition Period Greetings, Please see the attached document, submitted on behalf of the Empowered Community Administration, regarding the expiration of a recent Rejection Action Petition Period. Best Regards, Stephen Deerhake ccNSO Representative to the Empowered Community Administration

1 0

[ICANN Community Leaders] FYI: 25 July Update
by Michelle DeSmyter 25 Jul '19

25 Jul '19

FYI: [Image removed by sender.] Thursday, 25 July 2019 ICANN Community Leadership Digest [Image removed by sender.] This twice-weekly digest helps ICANN community leaders track requests and provides updates from ICANN org. TABLE OF CONTENTS Information Sharing · REMINDER: Post-ICANN65 Policy Report Now Available · REMINDER: NextGen@ICANN Survey · REMINDER: Update and Information on IRP IOT Re-Composition · REMINDER: Planning Assumptions for Subsequent Procedures for New gTLDs ICANN66 Planning · NEXT WEEK: Plenary Session Topics: Proposals Due Friday, 2 August · LOOKING AHEAD: Publication Support Deadlines Public Comment · CLOSING TOMORROW: Fundamental Bylaws Amendment Proposal -- IANA Naming Function Review · CLOSING TOMORROW: Revisions to the ICANN Bylaws re SSAC and RSSAC Leadership · CLOSING TOMORROW: Proposed IANA SLAs for Publishing LGRs/IDN Tables · Draft Final Report of the Second Country Code Names Supporting Organization Review · Draft Financial Assumptions & Projections and Operating Initiatives for the Development of the Fiscal Years 2021-2025 Operating & Financial Plan · Evolving the Governance of the Root Server System · Proposed Definition of Name Collisions and Scope of Inquiry for the Name Collisions Analysis Project · GNSO Policy Development Process on IGO-INGO Access to Curative Rights Protection Mechanisms Policy Recommendations for ICANN Board Consideration Information Sharing REMINDER: Post-ICANN65 Policy Report Now Available Executive: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING The Post-ICANN65 Policy Report [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> written by the ICANN Policy Development Support team captures decisions and outcomes from the Supporting Organizations and Advisory Committees. While the report provides an overview of activities held during the Policy Forum, it also looks ahead at the work to come in the upcoming months. Included in the report are various resources to support the ongoing, sustained engagement of the community on several important issues. REMINDER: NextGen@ICANN Survey Executive: Sally Costerton, Senior Adviser to President and Senior Vice President, Global Stakeholder Engagement FOR: All Community Leaders INFORMATION SHARING The ICANN organization is initiating a community consultation [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> to identify improvement opportunities for the NextGen@ICANN Program [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. The review will start with gathering community input via a survey about several aspects of the NextGen@ICANN Program, including its purpose, goals, processes, and synergies with the ICANN academic community. The survey [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> (PDF with background at the beginning and questionnaire questions at the end) is intended for all ICANN community groups; individuals are encouraged to work with their relevant Supporting Organizations, Advisory Committees, stakeholder groups, and constituencies. Responses are due Monday, 9 September. Based on the input received from the survey, ICANN org will draft a proposal for program improvements that will be published for Public Comment. Once all feedback is received, ICANN org will prepare the final proposal for program improvements. Sally Costerton's blog about the NextGen@ICANN Community Consultation [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> REMINDER: Update and Information on IRP IOT Re-Composition Executive: John Jeffrey, General Counsel FOR: All SO/AC Chairs INFORMATION SHARING As the ICANN Board committee with oversight responsibility of ICANN's accountability mechanisms, the Board Accountability Mechanisms Committee (BAMC) considers the work of the [Independent Review Process (IRP)] Implementation Oversight Team (IOT) to be paramount to ICANN's accountability...we seek your help in finding additional volunteers within the community that meet the qualifications identified in the attached letter, outlining skills and experience requirements, to join the IOT and help to conclude its work in a timely fashion. Read more [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. REMINDER: Planning Assumptions for Subsequent Procedures for New gTLDs Executive: Cyrus Namazi, Senior Vice President, Global Domains Division FOR: All Community Leaders INFORMATION SHARING 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 expects to publish its final report with its recommendations by December 2019. These recommendations may lead to procedural changes for subsequent rounds of gTLD applications, which ICANN org must implement and manage. In the course of our 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 assumptions have been shared with the ICANN Board, and now ICANN org would like to share them with relevant parts of the community. ICANN66 Planning NEXT WEEK: Plenary Session Topics: Proposals Due Friday, 2 August Executive: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING The official submission period to propose plenary session topics for ICANN66 is from Monday, 22 July to Friday, 2 August. The proposal form [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> is now open. An online report of proposals will be shared with the ICANN Public Meeting Community Planning Group as soon as it becomes available. LOOKING AHEAD: Publication Support Deadlines Executive: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING Design Deadline If you require design assistance for an ICANN66 publication, all text, images, layout, and publication type/size requirements (i.e. newsletter, 1-pager, tri-fold, etc.) are due Friday, 23 August. Due to budget constraints, please keep in mind that all materials, new or updated, need to be evergreen. Translation Deadline If your ICANN66 publication requires translation, please provide the final material(s) by Friday, 6 September. This ensures that there is enough time to translate the publication by the print deadline. If your materials require design assistance (outlined above), please note that the final materials will have to be complete, including the edit/approval process, by this deadline in order to be translated. Print-Only Deadline If you only need your ICANN66 publication printed (meaning your publication is ready to send directly to the printer and needs no translation or design/layout modifications), please provide the file along with the quantity you want printed and dimensions of the publication by Friday, 20 September. Please work directly with your Policy support staff to submit these requests to chantelle.doerksen(a)icann.org and liana.teo(a)icann.org. Public Comment Fundamental Bylaws Amendment Proposal -- IANA Naming Function Review [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> CLOSING TOMORROW: Friday, 26 July 2019 Revisions to the ICANN Bylaws re SSAC and RSSAC Leadership [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> CLOSING TOMORROW: Friday, 26 July 2019 Proposed IANA SLAs for Publishing LGRs/IDN Tables [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> CLOSING TOMORROW: Friday, 26 July 2019 Draft Final Report of the Second Country Code Names Supporting Organization Review [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Sunday, 4 August 2019 Draft Financial Assumptions & Projections and Operating Initiatives for the Development of the Fiscal Years 2021-2025 Operating & Financial Plan [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Monday, 5 August 2019 Evolving the Governance of the Root Server System [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 9 August 2019 Proposed Definition of Name Collisions and Scope of Inquiry for the Name Collisions Analysis Project [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Monday, 12 August 2019 GNSO Policy Development Process on IGO-INGO Access to Curative Rights Protection Mechanisms Policy Recommendations for ICANN Board Consideration [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Tuesday, 20 August 2019 Volume 1, Issue 35 | Archive [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> | Next Issue: Monday, 29 July 2019 ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe so-ac-sg-cleaders(a)icann.org [visitor.constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__visitor.constantcontac…> Update Profile [visitor.constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__visitor.constantcontac…> | About Constant Contact [constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…> Sent by david.olive(a)icann.org<mailto:david.olive@icann.org> in collaboration with [Image removed by sender. Trusted Email from Constant Contact - Try it FREE today.][constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…> Try email marketing for free today! [constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…>

1 0

FW: [gnso-secs] [ECAdmin] Notice of Expiration of Rejection Action Petition Period for the Five-Year Strategic Plan for FY21-25
by Terri Agnew 24 Jul '19

24 Jul '19

FYI – please see email below on behalf of the staff supporting Empowered Community Administration. From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of Ozan Sahin <ozan.sahin(a)icann.org> Date: Wednesday, July 24, 2019 at 7:15 AM To: "ecadmin(a)icann.org" <ecadmin(a)icann.org> Subject: [gnso-secs] [ECAdmin] Notice of Expiration of Rejection Action Petition Period for the Five-Year Strategic Plan for FY21-25 Dear Empowered Community Administration representatives, In accordance with the timelines and procedures set out in Annex D of the ICANN Bylaws, staff notes that the 21-day Rejection Action Petition Period pertaining to the Five-Year Strategic Plan for FY21-25 that was approved by the Board has expired. No Rejection Action Petition Notices (as defined in Annex D, Section 2.2(c)(i)) were received by the Empowered Community Administration within the prescribed timeframe. As such, under Annex D, Section 2.2(c)(ii), the Rejection Process for the Five-Year Strategic Plan for FY21-25 is thus automatically terminated. The next step is for the Empowered Community Administration to, within twenty-four (24) hours of the expiration of the Rejection Action Petition Period, deliver to the ICANN Secretary a notice certifying that the Rejection Process has been terminated with respect to this particular Rejection Action. ICANN will then be obliged to promptly post the Rejection Process Termination Notice on the ICANN website. Please let staff know if the Empowered Community Administration wishes for staff to draft the requisite Rejection Process Termination Notices for your sign-off, and if you require any other assistance. Best regards, Ozan Sahin (on behalf of the staff supporting Empowered Community Administration) From: ECAdmin <ecadmin-bounces(a)icann.org> on behalf of Ozan Sahin <ozan.sahin(a)icann.org> Date: Wednesday, July 3, 2019 at 12:24 AM To: "ecadmin(a)icann.org" <ecadmin(a)icann.org> Subject: Re: [ECAdmin] Secretary's Notice to Empowered Community of Board Approval of Five-Year Strategic Plan for FY21-25 Dear Empowered Community Administration representatives, Under the ICANN Bylaws, delivery of the Secretary’s Notice on 2 July: (1) requires Decisional Participants to “promptly inform their constituents” of the delivery of such notice; and (2) triggers the 21-day Rejection Action Petition Period, during which an individual may submit a petition to any Decisional Participant, seeking to reject the Board action. This 21-day period commenced on 2 July 2019 and will end at 23:59 PDT on 23 July 2019, or 06.59 UTC on 24 July 2019. Please refer to Article 2, Annex D of the ICANN Bylaws for additional details on the Rejection Process, including all pertinent deadlines and requirements for Rejection Action Petitions: https://www.icann.org/resources/pages/governance/bylaws-en/#annexD [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> Please do not hesitate to contact staff if you have any questions, or if we may be of further assistance. Best regards, Ozan Sahin (on behalf of staff supporting the Empowered Community Administration) From: ECAdmin <ecadmin-bounces(a)icann.org> on behalf of Peg Rettino <peg.rettino(a)icann.org> Date: Tuesday, July 2, 2019 at 11:28 PM To: "ecadmin(a)icann.org" <ecadmin(a)icann.org>, "chair(a)nro.net" <chair(a)nro.net>, Maureen Hilyard <maureen.hilyard(a)gmail.com>, "katrina(a)nic.lv" <katrina(a)nic.lv>, "Drazek, Keith" <kdrazek(a)verisign.com>, Manal Ismail <manal(a)tra.gov.eg> Cc: Goran Marby <goran.marby(a)icann.org>, Cherine Chalaby <cherine.chalaby(a)board.icann.org> Subject: [ECAdmin] Secretary's Notice to Empowered Community of Board Approval of Five-Year Strategic Plan for FY21-25 Greetings, Attached please find the Secretary’s Notice to Empowered Community of Board Approval of Five-Year Strategic Plan for FY21-25 sent on behalf of John Jeffrey. Best, Peg -- Peg Rettino Project Specialist & Executive Assistant to John Jeffrey General Counsel and Secretary ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 peg.rettino(a)icann.org<mailto:peg.rettino@icann.org> Skype: peg.rettino Direct: 310-301-3868

1 0

**with updated action item for agenda item 4 / Draft minutes of the GNSO Council meeting 18 July 2019
by Terri Agnew 23 Jul '19

23 Jul '19

**with updated action item for agenda item 4 Dear Councilors, Attached, please find the draft minutes of the GNSO Council meeting Thursday, 18 July 2019 for your review. If there are no comments, these minutes will be published on the website as approved, according to the GNSO Rules of Procedure <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> section 3.5 "If no objections are received within 10 days, the minutes will be deemed to have been approved for posting" on 2nd August 2019. Thank you very much. With kind regards, Terri --- Terri Agnew Operations Support - GNSO Lead Administrator Internet Corporation for Assigned Names and Numbers (ICANN) Email: terri.agnew(a)icann.org<mailto:terri.agnew@icann.org> Skype ID: terri.agnew.icann Find out more about the GNSO by visiting: https://learn.icann.org/ <https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…> See All SO and AC events on the ICANN Global calendar [features.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__features.icann.org_cal…>

1 0

Draft minutes of the GNSO Council meeting 18 July 2019
by Terri Agnew 23 Jul '19

23 Jul '19

Dear Councilors, Attached, please find the draft minutes of the GNSO Council meeting Thursday, 18 July 2019 for your review. If there are no comments, these minutes will be published on the website as approved, according to the GNSO Rules of Procedure <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> section 3.5 "If no objections are received within 10 days, the minutes will be deemed to have been approved for posting" on 2nd August 2019. Thank you very much. With kind regards, Terri --- Terri Agnew Operations Support - GNSO Lead Administrator Internet Corporation for Assigned Names and Numbers (ICANN) Email: terri.agnew(a)icann.org<mailto:terri.agnew@icann.org> Skype ID: terri.agnew.icann Find out more about the GNSO by visiting: https://learn.icann.org/ <https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…> See All SO and AC events on the ICANN Global calendar<https://features.icann.org/calendar>

1 0

FYI: 22 July Update
by Michelle DeSmyter 22 Jul '19

22 Jul '19

FYI: [Image removed by sender.] Monday, 22 July 2019 ICANN Community Leadership Digest [Image removed by sender.] This twice-weekly digest helps ICANN community leaders track requests and provides updates from ICANN org. TABLE OF CONTENTS Information Sharing · REMINDER: Post-ICANN65 Policy Report Now Available · REMINDER: NextGen@ICANN Survey · REMINDER: Update and Information on IRP IOT Re-Composition · REMINDER: Planning Assumptions for Subsequent Procedures for New gTLDs ICANN66 Planning · NEXT WEEK: Plenary Session Topics: Proposals Due Friday, 2 August · LOOKING AHEAD: Publication Support Deadlines Public Comment · CLOSING THIS WEEK: Fundamental Bylaws Amendment Proposal -- IANA Naming Function Review · CLOSING THIS WEEK: Revisions to the ICANN Bylaws re SSAC and RSSAC Leadership · CLOSING THIS WEEK: Proposed IANA SLAs for Publishing LGRs/IDN Tables · Draft Final Report of the Second Country Code Names Supporting Organization Review · Draft Financial Assumptions & Projections and Operating Initiatives for the Development of the Fiscal Years 2021-2025 Operating & Financial Plan · Evolving the Governance of the Root Server System · Proposed Definition of Name Collisions and Scope of Inquiry for the Name Collisions Analysis Project Information Sharing REMINDER: Post-ICANN65 Policy Report Now Available Executive: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING The Post-ICANN65 Policy Repor [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>t [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> written by the ICANN Policy Development Support team captures decisions and outcomes from the Supporting Organizations and Advisory Committees. While the report provides an overview of activities held during the Policy Forum, it also looks ahead at the work to come in the upcoming months. Included in the report are various resources to support the ongoing, sustained engagement of the community on several important issues. REMINDER: NextGen@ICANN Survey Executive: Sally Costerton, Senior Adviser to President and Senior Vice President, Global Stakeholder Engagement FOR: All Community Leaders INFORMATION SHARING The ICANN organization is initiating a community consultation [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> to identify improvement opportunities for the NextGen@ICANN Program [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. The review will start with gathering community input via a survey about several aspects of the NextGen@ICANN Program, including its purpose, goals, processes, and synergies with the ICANN academic community. The survey [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> (PDF with background at the beginning and questionnaire questions at the end) is intended for all ICANN community groups; individuals are encouraged to work with their relevant Supporting Organizations, Advisory Committees, stakeholder groups, and constituencies. Responses are due Monday, 9 September. Based on the input received from the survey, ICANN org will draft a proposal for program improvements that will be published for Public Comment. Once all feedback is received, ICANN org will prepare the final proposal for program improvements. Sally Costerton's blog about the NextGen@ICANN Community Consultation [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> REMINDER: Update and Information on IRP IOT Re-Composition Executive: John Jeffrey, General Counsel FOR: All SO/AC Chairs INFORMATION SHARING As the ICANN Board committee with oversight responsibility of ICANN's accountability mechanisms, the Board Accountability Mechanisms Committee (BAMC) considers the work of the [Independent Review Process (IRP)] Implementation Oversight Team (IOT) to be paramount to ICANN's accountability...we seek your help in finding additional volunteers within the community that meet the qualifications identified in the attached letter, outlining skills and experience requirements, to join the IOT and help to conclude its work in a timely fashion. Read more [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. REMINDER: Planning Assumptions for Subsequent Procedures for New gTLDs Executive: Cyrus Namazi, Senior Vice President, Global Domains Division FOR: All Community Leaders INFORMATION SHARING 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 expects to publish its final report with its recommendations by December 2019. These recommendations may lead to procedural changes for subsequent rounds of gTLD applications, which ICANN org must implement and manage. In the course of our 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 assumptions have been shared with the ICANN Board, and now ICANN org would like to share them with relevant parts of the community. ICANN66 Planning NEXT WEEK: Plenary Session Topics: Proposals Due Friday, 2 August Executive: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING The official submission period to propose plenary session topics for ICANN66 is from Monday, 22 July to Friday, 2 August. The proposal form [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> is now open. An online report of proposals will be shared with the ICANN Public Meeting Community Planning Group as soon as it becomes available. LOOKING AHEAD: Publication Support Deadlines Executive: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING Design Deadline If you require design assistance for an ICANN66 publication, all text, images, layout, and publication type/size requirements (i.e. newsletter, 1-pager, tri-fold, etc.) are due Friday, 23 August. Due to budget constraints, please keep in mind that all materials, new or updated, need to be evergreen. Translation Deadline If your ICANN66 publication requires translation, please provide the final material(s) by Friday, 6 September. This ensures that there is enough time to translate the publication by the print deadline. If your materials require design assistance (outlined above), please note that the final materials will have to be complete, including the edit/approval process, by this deadline in order to be translated. Print-Only Deadline If you only need your ICANN66 publication printed (meaning your publication is ready to send directly to the printer and needs no translation or design/layout modifications), please provide the file along with the quantity you want printed and dimensions of the publication by Friday, 20 September. Please work directly with your Policy support staff to submit these requests. Public Comment Fundamental Bylaws Amendment Proposal -- IANA Naming Function Review [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> CLOSING THIS WEEK: Friday, 26 July 2019 Revisions to the ICANN Bylaws re SSAC and RSSAC Leadership [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> CLOSING THIS WEEK: Friday, 26 July 2019 Proposed IANA SLAs for Publishing LGRs/IDN Tables [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> CLOSING THIS WEEK: Friday, 26 July 2019 Draft Final Report of the Second Country Code Names Supporting Organization Review [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Sunday, 4 August 2019 Draft Financial Assumptions & Projections and Operating Initiatives for the Development of the Fiscal Years 2021-2025 Operating & Financial Plan [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Monday, 5 August 2019 Evolving the Governance of the Root Server System [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 9 August 2019 Proposed Definition of Name Collisions and Scope of Inquiry for the Name Collisions Analysis Project [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Monday, 12 August 2019 Volume 1, Issue 34 | Archive [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> | Next Issue: Thursday, 25 July 2019 ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe so-ac-sg-cleaders(a)icann.org [visitor.constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__visitor.constantcontac…> Update Profile [visitor.constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__visitor.constantcontac…> | About Constant Contact [constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…> Sent by david.olive(a)icann.org<mailto:david.olive@icann.org> in collaboration with [Image removed by sender. Trusted Email from Constant Contact - Try it FREE today.][constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…> Try email marketing for free today! [constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…>

1 0

Seeking volunteers - GNSO Council liaisons
by Emily Barabas 22 Jul '19

22 Jul '19

Dear current and incoming GNSO Councilors, Looking ahead to the Annual General Meeting, our outgoing Councilors will leave several Council liaison positions vacant. This year, we are seeking volunteers early to fill these positions, so that the outgoing and incoming Liaisons have an opportunity to overlap. The goal is to have a smooth transition with sufficient time for knowledge transfer. For the incoming Councilors, you can read more about the role and responsibilities of Council liaisons here: https://gnso.icann.org/sites/default/files/file/field-file-attach/gnso-liai…. Note that if you are interested in volunteering, the current liaison, WG leadership, and staff will support your onboarding. We are seeking volunteers for the following: * Council Liaison to the Review of All Rights Protection Mechanisms (RPM) in All gTLDs PDP Working Group (to replace Paul McGrady) * Council Liaison to the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data Phase 1 Implementation Review Team (IRT) (to replace Rubens Kuhl) * Council Liaison to the Translation/Transliteration of Internationalized Registration Data PDP Recommendations Implementation Review Team (IRT) (to replace Rubens Kuhl) Additional information about these projects can be found here: https://gnso.icann.org/en/council/project Incoming Councilors are welcome to reach out to staff support with any questions and are, of course, encouraged to volunteer! Kind regards, Emily Emily Barabas | Policy Manager ICANN | Internet Corporation for Assigned Names and Numbers Email: emily.barabas(a)icann.org | Phone: +31 (0)6 84507976

3 5

FW: Secretary's Notice to Empowered Community of Board Approval of Five-Year Strategic Plan for FY21-25
by Drazek, Keith 19 Jul '19

19 Jul '19

Hi all, The attached notice, dated 2 July 2019, concerns the GNSO’s obligations as a decisional participant in the Empowered Community vis-à-vis approval of the FY21-25 Strategic Plan. This notice triggered the bylaw-mandated 21-day period for decisional participants to consider initiating a Rejection Action Process (RAP). Here’s the relevant language from the letter: “This Board Notice triggers the Empowered Community Rejection Action Process as set out at Annex D, Section 2 of the ICANN Bylaws. The timeline for the Empowered Community’s exercise of this Rejection Action Process will be tracked, including the associated deadlines, at https://www.icann.org/ec. The first deadline is a 21-day period for Decisional Participants to each consider if it will raise a petition.” As such, we have until 24 July 2019 to take action if needed. (NOTE: This original email was sent by ICANN the day I went on vacation and I only got to it upon my return. Procedurally, we are working to address this situation to avoid single-threaded communications on such important matters, and/or to ensure Staff have a standing action to forward such communications to the full Council list. I apologize for the delay in forwarding this.) We can discuss further on the Council call this week. Best, Keith From: Drazek, Keith Sent: Tuesday, July 16, 2019 11:27 AM To: gnso-chairs(a)icann.org; gnso-secs(a)icann.org Subject: FW: Secretary's Notice to Empowered Community of Board Approval of Five-Year Strategic Plan for FY21-25 Just catching up on email. This may have already been forwarded, but this is formal notice concerning the GNSO’s obligations w/r/t the RAP and a deadline of 23 July. Keith From: Peg Rettino <peg.rettino(a)icann.org<mailto:peg.rettino@icann.org>> Sent: Tuesday, July 02, 2019 10:27 PM To: ecadmin(a)icann.org<mailto:ecadmin@icann.org>; chair(a)nro.net<mailto:chair@nro.net>; Maureen Hilyard <maureen.hilyard(a)gmail.com<mailto:maureen.hilyard@gmail.com>>; katrina(a)nic.lv<mailto:katrina@nic.lv>; Drazek, Keith <kdrazek(a)verisign.com<mailto:kdrazek@verisign.com>>; Manal Ismail <manal(a)tra.gov.eg<mailto:manal@tra.gov.eg>> Cc: Goran Marby <goran.marby(a)icann.org<mailto:goran.marby@icann.org>>; Cherine Chalaby <cherine.chalaby(a)board.icann.org<mailto:cherine.chalaby@board.icann.org>> Subject: [EXTERNAL] Secretary's Notice to Empowered Community of Board Approval of Five-Year Strategic Plan for FY21-25 Greetings, Attached please find the Secretary’s Notice to Empowered Community of Board Approval of Five-Year Strategic Plan for FY21-25 sent on behalf of John Jeffrey. Best, Peg -- Peg Rettino Project Specialist & Executive Assistant to John Jeffrey General Counsel and Secretary ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 peg.rettino(a)icann.org<mailto:peg.rettino@icann.org> Skype: peg.rettino Direct: 310-301-3868

2 2