April 2019 - council - lists.icann.org

Confirmation of GNSO Representative on the Empowered Community Administration
by Nathalie Peregrine 20 Oct '22

20 Oct '22

Dear John, Please find the attached a letter with the motion passed at the GNSO Council meeting on 29 November 2018. The Council confirmed the appointment of the GNSO Chair, currently Keith Drazek, representing the GNSO as the Decisional Participant on the Empowered Community Administration until the end of his term at ICANN66. The letter will be published on page: https://gnso.icann.org/en/council/correspondence<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> Thank you. Respectfully submitted. 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 4

ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
by Drazek, Keith 18 Jul '19

18 Jul '19

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

14 35

Loss of Adobe Connect
by Ayden Férdeline 10 Jul '19

10 Jul '19

Dear all, [ICANN has announced](https://www.icann.org/news/blog/transitioning-icann-s-remote-par… that it will be rapidly transitioning away from the Adobe Connect platform to Zoom. I am not sure if there was consultation with other parts of the community, or if there is support for this decision, but I was hoping to hear from other Councillors as to whether or not they thought this decision would have implications on our work. I have used Zoom before and found the platform's interface to not be particularly intuitive, so I am worried. Perhaps someone could put me at ease that this will not be a consequential change. Thanks. Best wishes, Ayden

5 9

Re: [council] The Information Transparency Initiative (ITI) Feedback Site is Now Live - ICANN - Blog by David Conrad
by Mary Wong 03 Jul '19

03 Jul '19

Dear Ayden and all, We apologize if there were difficulties with accessing the feedback tool – there ought not to be any, so please do try it again if you wish to provide feedback. Please be assured that ICANN organization is committed to and interested in gathering the community’s feedback on each of the features that we will be rolling out with the objective of improving the findability, transparency, and accessibility of ICANN public content. The deadlines are, unfortunately, what they are in order to ensure that we are able to deliver on this major project on budget and on time. There will certainly be multiple and additional opportunities and forums for continuing community feedback, as noted in David’s blog that is referenced in the announcement below. Thank you. Best regards, Mary From: council <council-bounces(a)gnso.icann.org> on behalf of Ayden Férdeline <icann(a)ferdeline.com> Reply-To: Ayden Férdeline <icann(a)ferdeline.com> Date: Wednesday, April 25, 2018 at 09:17 To: Heather Forrest <haforrestesq(a)gmail.com> Cc: GNSO Council List <council(a)gnso.icann.org> Subject: Re: [council] Fwd: [So-ac-sg-cleaders] The Information Transparency Initiative (ITI) Feedback Site is Now Live - ICANN - Blog by David Conrad Given comments are being sought for less than a week, this does not strike me as a genuine consultative activity but appears to be a token form of participation intended to manipulate public opinion. This new website implies a shift towards greater consultation and community participation in ICANN's content strategy, but we cannot actually wield any influence by commenting here. (And not just because if you press the 'provide feedback' button, you see "The feedback survey is temporarily unavailable.") From what I understand we are not even being asked to comment on anything important. The list of 250 definitions, which I would like to review for neutrality and accuracy, are not online and it sounds like they have already been approved internally and are not open to community review. Are we really being asked to comment on just the glossary tool itself, and did ICANN really produce a video mockup and slide deck of something so incredibly mundane when it is up for public comment for just a week? Please forgive the negative sentiment to my message here, but it really seems a poor allocation of resources to me. Ayden Férdeline ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On 25 April 2018 3:03 PM, Heather Forrest <haforrestesq(a)gmail.com> wrote: Dear Council colleagues, I am pleased to pass on David Olive's update, below, on the Information Transparency Initiative. Best wishes, Heather ---------- Forwarded message ---------- From: "David Olive" <david.olive(a)icann.org<mailto:david.olive@icann.org>> Date: 24/04/2018 10:37 AM Subject: [So-ac-sg-cleaders] The Information Transparency Initiative (ITI) Feedback Site is Now Live - ICANN - Blog by David Conrad To: "so-ac-sg-cleaders(a)icann.org<mailto:so-ac-sg-cleaders@icann.org>" <so-ac-sg-cleaders(a)icann.org<mailto:so-ac-sg-cleaders@icann.org>> Cc: "David Conrad" <david.conrad(a)icann.org<mailto:david.conrad@icann.org>>, "Jana Juginovic" <jana.juginovic(a)icann.org<mailto:jana.juginovic@icann.org>> https://www.icann.org/news/blog/the-information-transparency-initiative-iti…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…> The Information Transparency Initiative (ITI) Feedback Site is Now Live I'm pleased to announce that today, we launched the ITI feedback site[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…> (feedback.icann.org[feedback.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__feedback.icann.org&d=Dw…>). As I have written about in previous blogs and discussed at ICANN60 and ICANN61 sessions, this site[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…> is intended to provide you, the ICANN community, with the ability to share your input on the content and features the ITI team is working on to improve the findability, transparency, and accessibility of ICANN public content. The first item we are looking for your comments on is an updated Acronyms and Terms feature[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…> to replace the existing feature[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. Our update doubles the number of terms available, provides up-to-date definitions for the terms, and improves search. Unlike most of the ITI project, we will launch this updated feature on the current https://icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_&d=DwMGa…> before 31 May 2018. The deadline to provide your input on the proposed updates to Acronyms and Terms is 30 April 2018, 23:59 UTC. Please visit feedback.icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…> to experience the proposed changes and complete a short survey. How the ITI Feedback Site Works The ITI Team will regularly post documents, mockups, or video walkthroughs of new content and features. The proposed content or feature items are listed on the homepage under the heading "Feedback Needed." Each item lists a deadline by which you need to provide input. Simply click on the item you're interested in. This will take you to another page, which provides you with the option to either download a mockup or watch a video walkthrough. Once you have completed that task, click on the "Feedback" button to complete a short survey or email your feedback to informationtransparency(a)icann.org<mailto:informationtransparency@icann.org>. Once the deadline has passed, the ITI Team will collect and publish all comments to feedback.icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…>. All published results of the survey will be anonymous, unless otherwise requested by the submitter. We will review all submissions and make our best efforts to implement the feedback, prioritizing input that serves the goals of improving search and accessibility, and increasing the transparency of our content. Feedback Deadlines We do have a tight deadline for community comments – one week for each new item. The reason for this timeline is we need to maintain a rigorous development schedule to ensure we are delivering the project on time and within budget. However, feedback.icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…> is not your only avenue to share input. ITI has many other opportunities to learn about ITI and provide comments including: * Regular sessions at ICANN Public Meetings. * Special sessions or webinars for Supporting Organizations and Advisory Committees (SO/ACs) on request or for special features and content like Public Comment. * Monthly blogs and newsletters. * Via email at informationtransparency(a)icann.org<mailto:informationtransparency@icann.org> Feedback Translations As I outlined above, we are working at a brisk development pace. This does limit our ability to fully translate feedback.icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…> and its survey. But, if you want to share feedback in another language, email us at informationtransparency(a)icann.org<mailto:informationtransparency@icann.org>. It is important to emphasize that one of the primary goals of ITI is a multilingual https://icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_&d=DwMGa…>, and the sooner we complete this project, the sooner we can deliver on that goal. ITI Goals ITI's goal is not a revamp of https://icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_&d=DwMGa…>. While the ITI team is working on making improvements to your User Experience (UX) on https://icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_&d=DwMGa…>, the vast majority of our efforts are focused on: * Creating content governance through new, enforced workflows and the creation of a consistent, multilingual taxonomy. * Building new technical infrastructures including a first-ever for ICANN document management system (DMS) and a new content management system (CMS). This new infrastructure will enforce this governance and enable improved content findability. Much of this foundational work won't be available on the feedback site for your input, but we will show the intended benefits of this work through the content and features we will share. ITI Update The ITI team has been hard at work completing that foundational work I mentioned above. We have completed the following tasks since the January 2018 launch of ITI: * The foundational build of the DMS and CMS, and the integration between the two platforms. * Sixty percent of the content audit and the taxonomy creation. * Interviews with SO/AC leaders, registrants, registrars, Fellows, and other ICANN stakeholders. We have also begun work on the following items: * Content modelling, workflow creation, and content governance enforcement in the DMS. * Accessibility guidelines and multilingual site implementation planning. ITI will launch in December 2019. ITI Backgrounders For those of you unfamiliar with ITI, you can read about what it is and how it will benefit the ICANN community in my kickoff blog[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…>. You can learn more about how the content audit and taxonomy will help your search experience in my January blog[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…>. We also outlined the differences between ITI and the Open Data Initiative (ODI) in our pre-ICANN61 blog[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…>. We Need Your Feedback Remember, we need your input to help us make the specific improvements to search, transparency, and accessibility that you need and want. Please visit the ITI feedback site[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…> and email us anytime at informationtransparency(a)icann.org<mailto:informationtransparency@icann.org>. Comments Log in to Comment[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_users_si…> or Sign Up[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_users_si…> Details * ICANN Blog * Author: David Conrad, Chief Technology Officer (CTO) and Senior Vice-President * 23 Apr 2018 David A. Olive Senior Vice President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) _______________________________________________ So-ac-sg-cleaders mailing list So-ac-sg-cleaders(a)icann.org<mailto:So-ac-sg-cleaders@icann.org> https://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders

4 7

GNSO Council Response to ICANN on PPSAI
by Drazek, Keith 30 Apr '19

30 Apr '19

Hi Cyrus, Please find attached the GNSO Council's response to your letter of 4 March 2019. Regards, Keith Drazek GNSO Chair

1 0

GNSO Council Communication on CCEG-IG
by Drazek, Keith 30 Apr '19

30 Apr '19

Hi Katrina, Maureen and Olivier, Please find attached the GNSO Council view on the status of the Cross-Community Engagement Group on Internet Governance (CCEG-IG). Thank you for your patience as the GNSO Council conducted our assessment. Best regards, Keith Drazek GNSO Chair

1 0

TIME SENSITIVE: ICANN Board Meeting Agenda -- IDN Variant Guidelines 4.0
by Drazek, Keith 30 Apr '19

30 Apr '19

Hi all, According to the ICANN Board meeting agenda<https://www.icann.org/resources/board-material/agenda-2019-05-03-en> for 3 May 2019, the issue of “Approval of Guidelines for the Implementation of Internationalized Domain Names Version 4.0” is currently on the consent agenda. We have just received the communication below/attached from the Registries Stakeholder Group highlighting concerns, both procedural and substantive, around Board approval of the guidelines at this time. Please take a few minutes to review. As we, the GNSO Council, have just begun our review and consideration of the IDN Variant topic, both at the TLD and second-level, and any associated policy implications, I plan to request a deferral of the Board’s approval of this motion. Concurrently, we need to respond to the related 8 April 2019 letter<https://www.icann.org/en/system/files/correspondence/namazi-to-sataki-draze…> from Cyrus. I will work on a draft for Council review. Please let me know if you have any questions or concerns. Best, Keith From: Austin, Donna <Donna.Austin(a)team.neustar> Sent: Monday, April 29, 2019 8:42 PM To: Rubens Kuhl <rubensk(a)nic.br>; Maxim Alzoba <m.alzoba(a)gmail.com>; Drazek, Keith <kdrazek(a)verisign.com> Subject: [EXTERNAL] IDN Email for Councilors Dear Keith, Rubens and Maxim, On behalf of the RySG, I am sending along a document outlining our concerns around IDN variant TLDs, the IDN Guidelines 4.0 and the implementation of IDN tables. As stated in the attached, the RySG is requesting that the GNSO Council take a number of actions to address these concerns, including, most urgently, requesting that the ICANN Board defer its scheduled vote on the IDN Guidelines 4.0 until the impacts of the implementation of those guidelines is better understood. We request that you bring these concerns to the attention of the GNSO Council and we appreciate the Council’s consideration of these important matters. Thank you, Donna Donna Austin Chair, RySG

8 8

Community Digest: 29 April Update
by Nathalie Peregrine 30 Apr '19

30 Apr '19

[http://r20.rs6.net/on.jsp?ca=a16a33f6-c025-4995-9a26-59c1331a7d9a&a=1122025…] Monday, 29 April 2019 ICANN Community Leadership Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] This twice-weekly digest helps ICANN community leaders track requests and provides updates from ICANN org. Due to a scheduling error, the 25 April 2019 issue was not distributed. Apologies. TABLE OF CONTENTS Requests · REMINDER: Input to Establish IRP Standing Panel Information Sharing · NEW: Evolving ICANN's Multistakeholder Model · NEW: CSC Findings on PTI Performance (March 2019) · LOOKING AHEAD: ICANN66 Travel Support Timeline ICANN65 Planning · COMING UP: CROP Deadline for ICANN65 · REMINDER: ICANN65 Travel Support Deadlines · THIS WEEK: Publication Support for ICANN65 · SAVE THE DATE: ICANN65 Community Leadership Reception · REMINDER: Meet with the ATRT3 Team at ICANN65 Public Comment · Proposal for Hebrew Script Root Zone Label Generation Rules · Proposed Renewal of .info Registry Agreement · Proposed Renewal of .org Registry Agreement · Proposed Renewal of .asia Registry Agreement · Proposed Renewal of .biz Registry Agreement · Evolving ICANN's Multistakeholder Model · Label Generation Rules for the Root Zone Version 3 (RZ-LGR-3) Requests REMINDER: Input to Establish IRP Standing Panel Executive: John Jeffrey, General Counsel and Secretary FOR: All SO/AC Chairs REQUEST ICANN organization needs input on the open questions [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> regarding how the Supporting Organizations (SOs) and Advisory Committees (ACs) will coordinate their participation in the process for the selection of a standing panel to preside over ICANN’s Independent Review Process (IRP) proceedings. The questions identified here [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> need to be resolved in order to move forward with the work on establishing a standing panel. ACTION Please send your input on the open questions [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> to the public email list: <i<mailto:irp-standing-panel@icann.org>rp-standing-panel(a)icann.org<mailto:irp-standing-panel@icann.org>>. For more information, please contact Liz Le at <elizabeth.le(a)icann.org<mailto:elizabeth.le@icann.org>>. BACKGROUND The IRP is an accountability mechanism provided by the ICANN Bylaws that allows for third-party review of actions (or inactions) by the ICANN Board or staff that are allegedly in violation of the Bylaws or Articles of Incorporation. The Bylaws provide that an omnibus standing panel shall be established from which panelists shall be selected to preside over specific IRP disputes. The ICANN Bylaws specify that ICANN shall, in consultation with the SOs and ACs, establish the standing panel. The Bylaws requires ICANN, in consultation with the SOs and ACs, to pursue a four-step process to establish the standing panel. As part of the process, the SOs and ACs must collectively agree on one slate of candidates for the standing panel to be submitted to the ICANN Board for approval. Information Sharing NEW: Evolving ICANN's Multistakeholder Model Executive: Theresa Swinehart, Senior Vice President, Multistakeholder Strategy and Strategic Initiatives FOR: All Community Leaders INFORMATION SHARING Following up on the 14 March 2019 session at ICANN64 on how ICANN can evolve its multistakeholder model, a public comment proceeding [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> on the topic opened on 25 April 2019 and will close 4 June 2019. A webinar will be held the week of 13 May 2019 to continue the conversation with the community and to encourage public comment. More details on the webinar will follow soon. Brian Cute will lead the conversation to develop and prioritize a list of issues that are hampering the multistakeholder model from being more effective and efficient. When the public comment proceeding closes, the Issues List will be updated based on comments received. A second webinar will be scheduled prior to ICANN65 in June 2019 to review the Issues List and discuss the work plan to be developed by the end of 2019. BACKGROUND This current Issues List combines community inputs from ICANN63 where the ICANN Board, Advisory Committees, and Supporting Organizations discussed Strategic Objective #2 as well as community inputs from a facilitated session at ICANN64. At ICANN64 the community was invited to add specificity to the issues identified at ICANN63, to offer new issues that are hampering the effectiveness of ICANN's multistakeholder model and to offer reasons why an issue should be removed from the Issues List. The Issues List, updated with community inputs from ICANN64, is the focus of this public comment proceeding. NEW: CSC Findings on PTI Performance (March 2019) From: Byron Holland, Customer Standing Committee (CSC) Chair FOR: All Community Leaders INFORMATION SHARING I am pleased to inform you the CSC has concluded that Public Technical Identifier overall performance over March 2019 was “Satisfactory." PTI met the service level agreement at 98.4% for the month of March 2019. The single missed service level is subject to a CSC recommendation to be adjusted. The adjustment would recategorize this month's performance for this metric as 'met'. The related PTI report to the CSC, listing the individual service level metrics along with their actual and historical performance, can be found at: https://www.iana.org/performance/ [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>csc [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>-reports [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. I am also very pleased to inform you that the CSC and PTI made considerable progress in changing the Service Level Agreements identified in our Findings report. We will keep you informed. BACKGROUND Generally, the CSC regular meeting is scheduled at or around the 15th every month, and the CSCFindings report on the PTI performance is sent out shortly after that meeting. If you would like to be informed of upcoming meetings or receive CSC reports directly, you may want to subscribe to our announce list at h [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>ttps://mm.icann.org/mailman/listinfo/ [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>csc [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>-announce [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. Any comments on our reporting to you is welcome. The CSC became effective October 1, 2016. Background information on the committee along with transcripts of our meetings and other useful information can be found at https://www.icann.org/ [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>csc [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. LOOKING AHEAD: ICANN66 Travel Support Timeline Executive: Sally Costerton, Senior Advisor to the President and CEO; Senior Vice President, Global Stakeholder Engagement FOR: All Community Leaders INFORMATION SHARING All travel support requests are now due 120 days prior to the next ICANN Public Meeting. This was previously a 90-day deadline. Therefore, the deadline for ICANN66 travel support is Friday, 5 July 2019. If applicable, community groups will need to adjust their election timelines accordingly to ensure new leaders are eligible in time for the ICAN66 travel support deadline. ICANN65 Planning COMING UP: CROP Deadline for ICANN65 Executive: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING The Community Regional Outreach Program (CROP) for FY19 will end on 30 June 2019. For groups planning to use CROP funds to conduct outreach during ICANN65, requests must be submitted no later than Monday, 6 May 2019. No exceptions will be made. When submitting a CROP travel request, please keep in mind the following: · Trip requests must be approved by your respective community leadership team. · For FY19, the trip request must be filled in by the CROP participant (you) via the CROP Wiki space. · In order to access the Wiki space, you must first have an account; please let your CROP Coordinator know if you need an account. · All individuals requesting CROP funding must also review the CROP Guidelines prior to submitting a request: https://community.icann.org/x/yicFBQ [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. Please contact <crop-staff(a)icann.org<mailto:crop-staff@icann.org>> with any questions. REMINDER: ICANN65 Travel Support Deadlines Executive: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING Friday, 10 May 2018 is the cut-off date to replace supported travelers. THIS WEEK: Publication Support for ICANN65 Executive: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING Translation Deadline If your ICANN65 publication requires translation, please provide the final material(s) by Friday, 3 May. This ensures that there is enough time to translate the publication by the print deadline. Print-Only Deadline If you only need your ICANN65 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, 17 May. Please work directly with your support staff to submit these requests. SAVE THE DATE: ICANN65 Community Leadership Reception Executive: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING Save the date for the ICANN65 Community Leadership Reception with members of the ICANN Board and Executive Team on Sunday, 23 June 2019, 18:00-20:00 CET in Marrakech, Morocco. Details will be confirmed as the date approaches. REMINDER: Meet with the ATRT3 Team Executive: Theresa Swinehart, Senior Vice President, Multistakeholder Strategy and Strategic Initiatives FOR: All SO/AC Chairs INFORMATION SHARING The third Accountability and Transparency Review Team (ATRT3) will meet in Marrakech to advance its work. As some of the team will be in Marrakech we would like to ask for a 30 to 40-minute slot on your community group's agenda, if possible. Community input is key to the success of this process. If you are able to accommodate us on your agenda, please send us an email to <atrt3-coordination(a)icann.org> to let us know a day and time that would suit. We will send you a preliminary set of questions ahead of the meeting to aid the discussion. We also welcome any questions you wish to raise in advance. Our goal for Marrakech is to: - Socialize our terms of reference and scope; - Conduct investigation of identified objectives - Seek input from the community to help us shape our findings and draft recommendations. BACKGROUND The ATRT review is mandated by ICANN Bylaws Section 4.6 (b) to examine ICANN’s execution of its commitment to maintain and improve robust mechanisms for public input, accountability, and transparency so as to ensure that the outcomes of its decision-making reflect the public interest and are accountable to the Internet community. Prior to meeting in Marrakech, the review team met on 3-5 April in Los Angeles for its first substantive meeting to develop our terms of reference and workplan, in response to the Board Resolution (2018.10.25.15) requesting that “ATRT3 adopt its Terms of Reference and Work Plan within 60 days of convening its first meeting, and submit these documents to the Board and to the leadership of the Supporting Organizations and the Advisory Committees, to confirm that the team's scope and timeline are consistent with the requirements of the ICANN Bylaws and ICANN community expectations.” We look forward to hearing from you. Many thanks and best regards, Cheryl Langdon-Orr and Pat Kane, ATRT3 Co-Chairs Public Comment Proposed Renewal of .info Registry Agreement [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Monday, 29 April 2019 Proposed Renewal of .org Registry Agreement [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Monday, 29 April 2019 Proposed Renewal of .asia Registry Agreement [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Tuesday, 7 May 2019 Proposed Renewal of .biz Registry Agreement [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Tuesday, 14 May 2019 Evolving ICANN's Multistakeholder Model [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Tuesday, 4 June 2019 Label Generation Rules for the Root Zone Version 3 (RZ-LGR-3) [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Tuesday, 4 June 2019 Volume 1, Issue 14 | Archive [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> | Next Issue: Thursday, 2 May 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 our service provider [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 [Trusted Email from Constant Contact - Try it FREE today.][constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…> Try it free today [constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…>

1 0

PDP 3.0 call
by Arsène Tungali 29 Apr '19

29 Apr '19

Hi there, Can I be dialed out at +243993810967 Thanks, Arsene ------------------------ **Arsène Tungali* <http://about.me/ArseneTungali>* Co-Founder & Executive Director, *Rudi international <http://www.rudiinternational.org>*, CEO,* Smart Services Sarl <https://www.smart-kitoko.com/>*, Tel: +243 993810967 (DRC) GPG: 523644A0 2015 Mandela Washington Fellow < http://tungali.blogspot.com/2015/06/selected-for-2015-mandela-washington.ht…> (YALI) - ICANN GNSO Council Member <https://gnso.icann.org/en/about/gnso-council.htm> Member. UN IGF MAG <https://www.un.org/press/en/2018/pi2247.doc.htm> Member

1 0

FOR REVIEW: Draft GNSO Council Communication on CCEG-IG
by Drazek, Keith 28 Apr '19

28 Apr '19

Hi all, Believe it or not, I finally focused on drafting the GNSO Council letter to the CCEG-IG, ccNSO and ALAC on our position related to the CCEG-IG. Please review the attached and let me know if you have any comments/concerns. I'll plan on sending on Tuesday at 2300 UTC if I don't receive any feedback. Thanks for your extreme patience on this one. Best, Keith

2 1