September 2018 - council - lists.icann.org

Re: [council] The Information Transparency Initiative (ITI) Feedback Site is Now Live - ICANN - Blog by David Conrad
by Mary Wong July 3, 2019

July 3, 2019

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 motions 27 September 2018
by Nathalie Peregrine Sept. 28, 2018

Sept. 28, 2018

Dear all, Please find below the resolutions from the GNSO Council at its meeting on Thursday, 27 September 2018. These have also been published<https://gnso.icann.org/en/council/resolutions#201809> on the GNSO website. Consent Agenda: Approval of the process for the Customer Standing Committee (CSC) Effectiveness Review and appointment of GNSO representatives Whereas, 1. The Customer Standing Committee (CSC) was established as one of the post IANA Transition entities and conducted its first meeting on 6 October 2016. 2. The ICANN Bylaws, Section 17.3 (b) states, “The effectiveness of the CSC shall be reviewed two years after the first meeting of the CSC; and then every three years thereafter. The method of review will be determined by the ccNSO and GNSO and the findings of the review will be published on the Website.” 3. On 27 June 2018, in the process of adopting the amended CSC Charter as required by the ICANN Bylaws, Section 17.3 (c), the Council resolved [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> that it, “… notes the recommendation in the Final Report that the ccNSO and GNSO Councils conduct an analysis of the requirements of the IANA Naming Function Review and the CSC Effectiveness Review with a view to creating synergies and avoiding overlap, and has appointed two Councilors to conduct the recommended analysis in cooperation with two representatives from the ccNSO.” 4. Donna Austin and Philippe Fouquart, as the two appointed GNSO Councilors, and Debbie Monahan and Martin Boyle from the ccNSO, have met and discussed the requirements of the IANA Naming Function Review and the CSC Effectiveness Review and explored a number of options for addressing any potential or perceived overlap. 5. These discussions have concluded that the most practical and efficient path forward is for the ccNSO and GNSO to each appoint two members to conduct the CSC Effectiveness Review that will consider the effectiveness of the CSC in performing its responsibilities as outlined in the CSC Charter and that the findings of the Review, as adopted by both the GNSO and ccNSO Councils, will become an input to the IANA Naming Function Review. 6. This is on the basis that the recently concluded CSC Charter Review established that the CSC is working well and is non-controversial; the Final Report of the CSC Charter Review provides a good platform from which to conduct an effectiveness Review; and that the primary purpose of the IANA Naming Function Review is to review the performance of PTI in performing the IANA Function and therefore is not likely to spend too much time reviewing the effectiveness of the CSC. Resolved, 1. The GNSO Council approves the method of review as suggested; 2. The GNSO Council appoints Donna Austin and Philippe Fouquart as the GNSO Council representatives of the CSC Effectiveness Review; and 3. The GNSO Council requests that the GNSO Secretariat notify ICANN Org no later than 30 September that the GNSO has approved of the method of review and GNSO representatives for CSC Effectiveness Review. Approval of the Members and Liaisons of the Customer Standing Committee (CSC) Whereas, 1. The inaugural slate of the CSC was confirmed by the GNSO Council on 9 August 2016; 2. The initial term of some of the inaugural CSC members and liaisons is due to expire on 6 October 2018; 3. The GNSO Council was notified [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> on 7 September 2018 by ICANN Org that the ccNSO and RySG have appointed Brett Carr and Gaurav Vedi respectively to serve as members of the CSC for the period 1 October 2018 to 30 September 2020; the RSSAC has re-appointed Lars-Johan Liman to continue service as a liaison to the CSC through 30 September 2020; and the GAC has appointed Nigel Cassimire to serve as a liaisons to the CSC for the period 1 October 2018 to 30 September 2020; 4. In accordance with Section 17.2.d of the ICANN Bylaws, “... the ccNSO and GNSO shall approve each annual slate of members and liaisons being recommended for a new term”; 5. The CSC Charter provides that “… while it will not be the role of the ccNSO and GNSO to question the validity of any recommended appointments to the CSC they will take into account the overall composition of the proposed CSC in terms of geographic diversity and skill sets”; and 6. The GNSO Council has reviewed the list of CSC members and liaisons. Resolved, 1. The GNSO Council approves the full slate of members and liaisons: Members: Byron Holland (Chair). Appointing Organization: ccNSO. Term: 2016 – 2019 Brett Carr. New appointment Appointing Organization: ccNSO. Expected Term: 01 October 2018 to 30 September 2020 Elaine Pruis. Appointing Organization: RySG. Term: 2016 – 2019 Gaurav Vedi, new appointment. Appointing Organization: RySG. Expected Term: 01 October 2018 to 30 September 2020 Liaisons: Lars-Johan Liman, re-appointment. Appointing Organization: RSSAC. Expected Term: 01 October 2018 to 30 September 2020 Nigel Cassimire, new appointment. Appointing Organization: GAC. Expected Term: 01 October 2018 to 30 September 2020 Jeff Bedser. Appointing Organization: SSAC. Term: 2016 -2019 Mohamed El Bashir. Appointing Organization: ALAC. Term: 2016 - 2019 James Gannon. Appointing Organization: GNSO (Non-Registry). Term: 2016 -2019 Naela Sarras. Appointing Organization: PTI. Term: no term limit (see also: https://www.icann.org/en/system/files/correspondence/nguyen-to-forest-satak… [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…>.) 1. The GNSO Council requests that the GNSO Secretariat notify ICANN Org no later than 30 September that the GNSO has approved the full list of CSC liaisons and members. Vote results [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> GNSO Council consideration of CCWG-Accountability WS2 Final Report and Recommendations Submitted by Heather Forrest Seconded by Darcy Southwell Whereas, 1. The GNSO Council, together with other ICANN Supporting Organizations and Advisory Committees, chartered the Cross-Community Working Group on Enhancing ICANN Accountability (CCWG-Accountability) on 13 November 2014 'to deliver proposals that would enhance ICANN's accountability towards all stakeholders’. 2. The GNSO Council approved the CCWG-Accountability Supplemental Final Proposal on Work Stream 1 Recommendations on 9 March 2016, which included recommendation #12: Committing to Further Accountability Work in Work Stream 2 (WS2). 3. The GNSO Council approved on 18 May 2017 the extension of WS2 for one year to the end of June 2018. 4. The CCWG-Accountability published its WS2 Final Report for public comment on 30 March 2018 (see https://www.icann.org/public-comments/ccwg-acct-ws2-final-2018-03-30-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> ). 5. Several GNSO Stakeholder Groups (SGs) and/or Constituencies (Cs) submitted their input on WS2 Final Report (see https://mm.icann.org/pipermail/comments-ccwg-acct-ws2-final-30mar18/2018q2/…) 6. The CCWG-Accountability reviewed all the input received and submitted its WS2 Final Report Recommendations to the Chartering Organizations on 9 July 2018 (see https://mm.icann.org/pipermail/accountability-cross-community/2018-July/014…) for their consideration. 7. The GNSO Council has reviewed and discussed the CCWG-Accountability WS2 Final Report and Recommendations. Resolved, 1. The GNSO Council adopts the CCWG-Accountability WS2 Final Report and Recommendations (see https://community.icann.org/display/WEIA?preview=/59640761/88575033/FULL%20… w<https://community.icann.org/display/WEIA?preview=/59640761/88575033/FULL%20…>) 2. The GNSO Council instructs the GNSO Secretariat to share the results of this motion with the Chairs of the CCWG-Accountability as soon as possible. 3. The GNSO Council expresses its sincere appreciation to the CCWG-Accountability, the GNSO members and participants in that effort, and especially the GNSO-appointed Chair, Thomas Rickert, for all their hard work in achieving the delivery of the WS2 Final Report and Recommendations. Vote results [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> Approval of the Final Recommendations from the Reconvened Working Group on Red Cross Names - deferred to September Council meeting from Council meeting held on August 2018 Submitted by Heather Forrest Seconded by Donna Austin Whereas: 1. In November 2013, the Working Group for the Protection of International Governmental Organizations (IGO) and International Non-Governmental Organizations (INGO) in All gTLDs completed a Policy Development Process (PDP) and submitted its Final Report to the GNSO Council (https://gnso.icann.org/en/issues/igo-ingo-final-10nov13-en.pdf [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_issu…>, including Minority Statements: https://gnso.icann.org/en/issues/igo-ingo-final-minority-positions-10nov13- en.pdf [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_issu…>); 2. On 20 November 2013, the GNSO Council approved all the consensus recommendations in the PDP Final Report (http://gnso.icann.org/en/council/resolutions#20131120-2 [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_counc…>); 3. On 30 April 2014, the ICANN Board approved those of the GNSO’s consensus recommendations that were consistent with advice received from the Governmental Advisory Committee (GAC) on the topic of IGO and INGO protections (which approval, in relation to the Red Cross, was limited to withholding from registration at both the top and second levels the specific terms designated as so-called “Scope 1” identifiers by the PDP Working Group (i.e., “Red Cross”, “Red Crescent”, “Red Crystal” and “Red Lion & Sun” in all six official languages of the United Nations)) and requested additional time to consider those remaining consensus PDP recommendations that were not consistent with GAC advice (http://www.icann.org/en/groups/board/documents/resolutions-30apr14-en.htm#2… [icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_en_groups…>); 4. In March 2017, representatives of the GAC and GNSO held a discussion at the ICANN58 Public Meeting in Copenhagen, facilitated by former ICANN Board member Dr. Bruce Tonkin, to discuss a possible path forward for reconciling GAC advice and GNSO policy on the topic of protection at the second level of the domain name system for IGO acronyms and the remaining names and acronyms associated with the Red Cross (being those designated by the IGO-INGO PDP Working Group as “Scope 2” identifiers); 5. Following the March 2017 facilitated discussion, the ICANN Board passed a resolution requesting that the GNSO Council consider initiating the Policy Amendment Process documented in the GNSO PDP Manual in respect of certain of the so-called “Scope 2” identifiers for the Red Cross, i.e., the full names of the National Societies recognized within the International Red Cross and Red Crescent movement, and the full names of the International Red Cross and Red Crescent Movement, the International Committee of the Red Cross, and the International Federation of Red Cross and Red Crescent Societies (in the six official languages of the United Nations) (https://www.icann.org/resources/board-material/resolutions-2017-03-16- en#2.e.i<file:///C:/Users/Berry/AppData/Local/Microsoft/Windows/INetCache/Content.Outlook/707X05B7/65236743>); 6. In May 2017, the GNSO Council passed a resolution noting that the March 2017 facilitated discussions had highlighted a set of exceptional circumstances (in the availability of a finite list of names and documented evidence of the legal basis for their protection) constituting a justifiable basis for the Council’s taking the extraordinary step of reconvening the original IGO-INGO PDP Working Group pursuant to Section 16 of the GNSO PDP Manual for the specific purpose of considering possible modifications to its previous consensus policy recommendations concerning and limited to the so-called “Scope 2” Red Cross full names noted by the Board, and including a defined, finite list of variants of those names, and with acronyms and any other names not falling within the scope of this reconvened effort (https://gnso.icann.org/en/council/resolutions#20170503-071 [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…>); 7. The Reconvened PDP Working Group held its first meeting on 14 June 2017, and has since worked diligently to develop a set of recommendations that were published for public comment on 21 June 2018 (https://www.icann.org/public-comments/red-cross-protection-initial-2018-06-… [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…>); and 8. Following the close of the public comment period on 31 July 2018, the Reconvened PDP Working Group reviewed the comments that were received and completed its Final Report and finite List of names, which it submitted to the GNSO Council for its consideration on 6 August 2018 (https://gnso.icann.org/en/issues/igo-ingo/red-cross-protection-policy-amend… [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_issu…>)( https://gnso.icann.org/en/issues/igo-ingo/red-cross-identifiers-proposed-re… [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_issu…>). Resolved: 1. The GNSO Council has reviewed the Final Report and approves all of the consensus recommendations made by the Reconvened PDP Working Group; 2. The GNSO Council thanks the Reconvened PDP Working Group for its diligence and its successful work in attaining consensus on all recommendations; 3. The GNSO Council thanks the International Red Cross and Red Crescent Movement for its efforts in providing the documentation and information needed to justify and underpin the consensus recommendations; and 4. The GNSO Council directs ICANN staff to prepare a Recommendations Report for delivery to the ICANN Board in accordance with the process outlined in the ICANN Bylaws. Vote results [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…>

1 0

FW: [Communication] Contracted Parties Briefing ICANN63
by Marika Konings Sept. 27, 2018

Sept. 27, 2018

For your information. From: ICANN Global Support <noreply-globalsupport(a)icann.org> Date: Thursday, September 27, 2018 at 11:50 AM To: Janella Conroy <janella.conroy(a)icann.org> Subject: Contracted Parties Briefing ICANN63 [cid:image001.jpg@01D45653.A326CB90] 27 September 2018 Greetings, As ICANN’s Global Domains Division (GDD) prepares for the ICANN63<https://meetings.icann.org/en/barcelona63> meeting in Barcelona, Spain, we would like to highlight some recent, more notable, community-impacting activities and projects below. We look forward to your feedback and continued participation. New & Noteworthy Meet with us at ICANN63 Barcelona If you plan to attend ICANN63 and want to schedule an in-person meeting with your GDD engagement manager or other members of the ICANN organization, please submit your request to globalsupport(a)icann.org<mailto:globalsupport@icann.org> no later than Friday, 12 October 2018 with the following information: • Your name and title* • Company affiliation(s)* • Names, email addresses and phone numbers of other attendees* • A brief description of the topic(s) you wish to address • Requested ICANN org attendees (if applicable) • Your date and time preference(s) (20–25 October between 9:00–17:30 local time) We will do our best to accommodate requests and ensure that relevant ICANN org staff join the meeting. The full meeting schedule<https://63.schedule.icann.org/> will be available 1 October 2018. * Note: By submitting your personal data, you agree that your personal data will be processed in accordance with the ICANN Privacy Policy<https://www.icann.org/privacy/policy>, and agree to abide by the Terms of Service<https://www.icann.org/privacy/tos>. Temporary Specification for gTLD Registration Data On 21 August 2018, the Board reaffirmed the Temporary Specification<https://www.icann.org/resources/pages/gtld-registration-data-specs-en> for gTLD Registration Data for an additional ninety (90) days. This Temporary Specification was initially adopted by Board Resolution<https://www.icann.org/resources/board-material/resolutions-2018-05-17-en> on 17 May 2018, pursuant to procedures outlined for establishing temporary policies in ICANN's agreements with registry operators and registrars. This Temporary Specification became effective on 25 May 2018 and may be reaffirmed for successive 90-day periods by the ICANN Board for a total period not to exceed one year from the effective date. Update on the Registration Data Access Protocol (RDAP) The RDAP pilot discussion group and the ICANN organization posted a proposed generic top-level domain (gTLD) RDAP profile for Public Comment<https://www.icann.org/public-comments/proposed-rdap-profile-2018-08-31-en>, which follows the Board-approved requirements of the Temporary Specification for gTLD Registration Data. ICANN org continues to work with the contracted parties to reach agreement on proposals for gTLD RDAP service level agreement (SLA) and registry reporting requirements. The proposals will be posted for public comment once an agreement is reached. While RDAP delivers registration data similar to WHOIS, its implementation is expected to help standardize registration data access and query response formats. Learn more about this process, the plans surrounding the review, the proposed gTLD RDAP profile, SLA and reporting requirements here<https://www.icann.org/news/blog/moving-forward-with-rdap>. As a reminder, the Temporary Specification for gTLD Registration Data<https://www.icann.org/resources/pages/gtld-registration-data-specs-en> requires gTLD registry operators and registrars to implement an RDAP service within a 135-day period after notification from ICANN. All registry operators and registrars should begin preparing now. ICANN Publishes Key Signing Key (KSK) Rollover Guide As the ICANN organization prepares to change the cryptographic keys that help protect the Internet's Domain Name System (DNS), the organization has published a guide to let people know what to expect. The changing of the keys, known as the "Root Key Signing Key (KSK) Rollover," is currently scheduled for 11 October 2018. Registrars and registry operators must ensure their DNS resolvers are properly configured with the new key. The new ICANN guide provides information for audiences with varying levels of technical expertise, to help prepare for the rollover. The guide can be accessed here<https://www.icann.org/en/system/files/files/ksk-rollover-expect-17sep18-en.…>. 2019 GDD Industry Summit, Registration Operations Workshop, DNS Symposium, and DNS Operations, Analysis and Research Center (DNS-OARC) The 2019 Global Domains Division Industry Summit<https://www.icann.org/gddsummit> will be held in Bangkok, Thailand at the Shangri-La<http://www.shangri-la.com/bangkok/shangrila/> hotel from 6–9 May. This event will be followed by Registration Operations Workshop<http://regiops.net/> (9 May), DNS Symposium<https://www.icann.org/ids> (10–11 May), and DNS OARC<https://indico.dns-oarc.net/event/29/> (12–13 May) meetings. Enhancements to TMDB Security Settings Coming Soon A reminder for all contracted parties, the security configuration for the Trademark Database (TMDB) interfaces will be updated on 10 December 2018. Beginning 10 October 2018, the TMDB Operational Testing & Evaluation (OT&E) systems will be available for validation and testing. All contracted parties who utilize the TMDB systems are encouraged to use this testing period to ensure a seamless transition to the new security settings. More information is available here<https://www.icann.org/en/system/files/files/tmdb-maintenance-notice-19sep18…>. Keep Contacts Current in ICANN Systems A reminder for all contracted parties: To avoid missing an important communication, please take a moment now to confirm your contacts are up to date in ICANN’s systems. Please review the details and instructions for registrars here<https://www.icann.org/resources/pages/registrar-contact-updates-2015-09-22-…>. Registry operators should log into the Naming Services portal<https://icann-nsp.okta.com/login/login.htm?fromURI=%2Fapp%2Fsalesforce%2Fex…> to request an update to contacts. Reminder to Participate in the Sunrise and Trademark Claims Survey The Sunrise and Trademark Claims Survey is available for individuals interested in sharing their feedback about Rights Protection Mechanisms (RPMs). The Sunrise and Trademark Claims RPMs were adopted as part of the New Generic Top-Level Domain (gTLD) Program. The survey period was extended and will run until Friday, 5 October 2018. If you started but did not complete the survey, please click the survey link below and resume the survey beginning with your last question. We appreciate your feedback. It is essential for evaluating RPMs and ICANN’s data collection efforts related to them. Registry Operator Survey<http://icannregistryoperators.cloudssi.com/cgi-bin/ciwweb.pl?hid_studyname=…>: If your company operates non-brand new gTLDs. Registrar Survey<http://icannregistrar.cloudssi.com/cgi-bin/ciwweb.pl?hid_studyname=Registra…>: If respondents started the survey but have not yet finished. Policy Implementation Updates Privacy and Proxy Service Provider Implementation Review Team The Implementation Review Team (IRT) is reviewing the proposed accreditation program requirements before proceeding to Public Comment. The IRT will have a working meeting at ICANN63. More information about the IRT’s work is available on the IRT wiki page<https://community.icann.org/display/IRT>. Registrars New Registrar Resources The Registrar Services team recently published several new resources. These include the GDD General Operations Handbook<https://www.icann.org/en/system/files/files/registrar-handbook-21aug18-en.p…>, Registrar Communications page<https://www.icann.org/resources/pages/registrar-communications-2018-05-24-en>, the Registrar Library<https://www.icann.org/registrar-library>, New Registrar Accreditation Application questions<https://www.icann.org/resources/pages/raa-application-2018-09-19-en> and Registrar Billing Frequently Asked Questions<https://www.icann.org/en/system/files/files/registrar-billing-faq-21aug18-e…>. Many of these materials have been translated and are available on the Registrar Resources<https://www.icann.org/resources/pages/registrar-additional-resources-2018-0…> page. Registrar Billing Changes ICANN org will invoice the registrars’ accreditation fees annually unless registrars request quarterly invoicing. This is detailed in the 2013 Registrar Accreditation Application<https://www.icann.org/en/system/files/files/approved-with-specs-27jun13-en.…> and will reduce the transfer fees for registrars. If you prefer to be billed quarterly for these fees, please contact globalsupport(a)icann.org<mailto:globalsupport@icann.org>. See Billing FAQs<https://www.icann.org/en/system/files/files/registrar-billing-faq-21aug18-e…> or Registrar Fees<https://www.icann.org/resources/pages/registrar-fees-2018-08-10-en> for more information. Registrar Fee Vote Every year, ICANN requests registrar approval for the registrars’ fee schedule. The proposed Fiscal Year 2019 Registrar Fee Schedule retains all elements of the schedule approved for the previous six (6) years. See the FY19 budget<https://www.icann.org/en/system/files/files/adopted-total-budget-fy19-30may…> for further details. On 5 September, registrars received an invitation to vote. We encourage your participation by Friday, 5 October 2018. Registries Registry-Registrar Agreement Amendments to comply with the Temporary Specification - Translated versions now available All Registry Operators need to ensure their Registry-Registrar Agreement (RRA) complies with Section 6.3 of the Temporary Specification for gTLD Registration Data<https://www.icann.org/resources/pages/gtld-registration-data-specs-en/#6>. ICANN, in conjunction with the gTLD Registries and Registrars Stakeholder Groups, has developed an amendment terms template to facilitate RRA updates to comply with the Temporary Specification. Instructions to make these changes are available here<https://www.icann.org/resources/pages/rra-amendment-procedure-gtld-registra…>. Please note you’ll need to provide the cover note<https://www.icann.org/en/system/files/files/rra-amendment-cover-note-gtld-r…>, a clean and redline version of the amended RRA and a list of the impacted TLDs in your submission to ICANN org. The template<https://www.icann.org/en/system/files/files/gtld-registration-data-temp-spe…> is now available in Arabic<https://www.icann.org/ar/system/files/files/rra-amendment-terms-temp-spec-0…>, Chinese<https://www.icann.org/zh/system/files/files/rra-amendment-terms-temp-spec-0…>, French<https://www.icann.org/fr/system/files/files/rra-amendment-terms-temp-spec-0…>, Russian<https://www.icann.org/ru/system/files/files/rra-amendment-terms-temp-spec-0…>, and Spanish<https://www.icann.org/es/system/files/files/rra-amendment-terms-temp-spec-0…>. For other RRA Amendments unrelated to the Temporary Specification, please refer to the Registry-Registrar Agreement Amendment procedure<https://www.icann.org/resources/pages/rra-amendment-procedure-2015-04-06-en> and the new How to Guide<https://www.icann.org/en/system/files/files/rra-amendment-guide-13jun18-en.…>. We hope this information provides you with additional insight and transparency into our ongoing activities and look forward to your feedback. Best regards, Cyrus Namazi Vice President, Domain Name Services and Industry Engagement ICANN Global Domains Division ________________________________ To reference past registry operator communications please click here<https://www.icann.org/resources/pages/registry-communications-2017-10-04-en>. To reference past registrar communications please click here<https://www.icann.org/resources/pages/registrar-communications-2018-05-24-en>.

1 0

Reminder: Action required to continue receiving the New gTLD Subsequent Procedures PDP WG monthly newsletter
by Emily Barabas Sept. 27, 2018

Sept. 27, 2018

Dear all, As a reminder, if you would like to continue to receive the New gTLD Subsequent Procedures PDP WG monthly newsletter in the future, you will need to click on the following link and sign up: https://docs.google.com/forms/d/e/1FAIpQLSfp9C6imlr3cvCyuKg86ZQPfBGt_ze1LIr…. Please sign up before 1 October to ensure that you receive the October edition. Anyone can subscribe! Please share this information with your communities or individuals who may be interested in signing up to receive the newsletter. If you do not want to receive the newsletter in the future, no action is required. If you decide to sign up later, a link to the sign-up sheet is also available on the Working Group wiki: https://community.icann.org/x/RgV1Aw. Kind regards, Emily From: Gnso-newgtld-wg <gnso-newgtld-wg-bounces(a)icann.org> on behalf of Emily Barabas <emily.barabas(a)icann.org> Reply-To: Emily Barabas <emily.barabas(a)icann.org> Date: Wednesday, 12 September 2018 at 01:05 To: "gnso-newgtld-wg(a)icann.org" <gnso-newgtld-wg(a)icann.org> Subject: [Gnso-newgtld-wg] Subscribe to GNSO New gTLD Subsequent Procedures PDP Working Group Monthly Newsletter Don't miss the monthly newsletter in a new format [http://r20.rs6.net/on.jsp?ca=887f3867-9d43-459d-85ec-fb5fadec1112&a=1122025…] [http://files.constantcontact.com/304b3fd3501/68834adc-df18-4fd7-aa31-484e82…] [https://files.constantcontact.com/304b3fd3501/fec1c4f8-7720-4274-be5b-701de…] Subscribe to SubPro Monthly Newsletter [http://files.constantcontact.com/304b3fd3501/84f8a7d6-8904-4f0f-bc15-014e6e…] Dear newsletter recipient: We are updating the New gTLD Subsequent Procedures Policy Development Process Working Group monthly newsletter to a new email newsletter format. We want to ensure you are not receiving unwanted emails. If you would like to continue receiving this newsletter in the future, please click the link below to access the subscription form. If you previously received newsletters in your inbox, you will still need to complete the subscription form to continue receiving newsletters in the future. If you choose to subscribe, this will give ICANN org permission to send the monthly newsletter to your email address. It also provides ICANN org with an accurate list of subscribers. If you choose to subscribe, you agree to the following statement: "By submitting my personal data, I agree that my personal data will be processed in accordance with the ICANN Privacy Policy [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>, and agree to abide by the website Terms of Service [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>." We please ask that you subscribe by 01 October 2018. If you do not wish to receive future monthly newsletters about this working group, no action from you is needed. Future newsletters will be archived here [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. Click Here to Subscribe to SubPro Monthly Newsletter [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> If you cannot access the subscription form, contact emily.barabas(a)icann.org<mailto:emily.barabas@icann.org> to request assistance. We are always exploring ways to improve and make it easier for our community to remain informed. Best Regards, ICANN Policy Staff Follow the GNSO on Twitter [Twitter]‌ [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe gnso-newgtld-wg(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 emily.barabas(a)icann.org<mailto:emily.barabas@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

MP3, Adobe Connect recording and chat transcript/ GNSO Council meeting on Thursday, 27 September 2018 at 04:00 UTC.
by Nathalie Peregrine Sept. 27, 2018

Sept. 27, 2018

Dear GNSO Council, Please find below the MP3, Adobe Connect recording and chat of the GNSO Council meeting held on Thursday, 27 September 2018 at 04:00 UTC. MP3: https://audio.icann.org/gnso/gnso-council-27sep18-en.mp3 Adobe Connect Recording URL: https://participate.icann.org/p725mdkjv10/ Adobe Connect chat at: https://gnso.icann.org/sites/default/files/file/field-file-attach/transcrip… All on page: https://gnso.icann.org/en/group-activities/calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…> Thank you. Happy listening and reading! With kind regards, Nathalie --- Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

EPDP & Accreditation/Access Model
by Darcy Southwell Sept. 26, 2018

Sept. 26, 2018

The BC/IPC recently sent a letter to ICANN org (https://www.icann.org/en/system/files/correspondence/bc-ipc-to-marby-07sep1 8-en.pdf) about the accreditation and access model. This letter seems problematic at this stage of the game. We discussed this issue ad nauseam during the EPDP Charter development and the Council has tasked the EPDP with addressing the Annex. To ask ICANN org to circumvent the EPDP undermines the policy development process and seems disingenuous to the Council's approval of the Charter. In addition, the EDPB's July 5 letter states responsibility for designing an access model lies with ICANN and the registries/registrars, not just ICANN as indicated in the BC/IPC letter. Will our BC and/or IPC councilors please shed some light on this? Thanks, Darcy

7 8

CSC Related motions for the 27 September 2018 Council Meeting
by Austin, Donna Sept. 25, 2018

Sept. 25, 2018

All Just some additional information on the CSC Effectiveness Review Process. Attached is a draft Template for the CSC Effectiveness Review that explains the intent of the review and elements of the CSC Charter that the Review Team will use as the basis for measuring effectiveness. Apologies for not providing this earlier. I can also report that the ccNSO Council adopted the draft Template during a recent Council meeting and appointed Debbie Monahan and Martin Boyle to represent the ccNSO. Donna From: council [mailto:council-bounces@gnso.icann.org] On Behalf Of Austin, Donna via council Sent: Monday, September 17, 2018 3:42 PM To: council(a)gnso.icann.org Subject: [council] CSC Related motions for the 27 September 2018 Council Meeting All Two motions related to the Customer Standing Committee that are currently on the Consent Agenda for the Council Meeting on 27 September 2018: * Approval of the CSC Effectiveness Review process and GNSO representatives * Approval of Members and Liaisons for the CSC Donna Donna Austin Neustar, Inc. / Senior Policy Manager, Registry Solutions Mobile: +1 310 890 9655 donna.austin(a)team.neustar<mailto:donna.austin@team.neustar> / Website: home.neustar<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.home.neustar_&d=DwM…> Follow Neustar: LinkedIn<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_compan…> / Twitter<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.twitter.com_neustar…> Reduce your environmental footprint. Print only if necessary. ________________________________ The information contained in this email message is intended only for the use of the recipient(s) named above and may contain confidential and/or privileged information. If you are not the intended recipient you have received this email message in error and any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately and delete the original message.

1 0

EPDP Weekly Update - Email Newsletter Subscription
by Ariel Liang Sept. 24, 2018

Sept. 24, 2018

Dear All, On behalf of the leadership team of the EPDP on Temporary Specification for gTLD Registration Data, I am writing to share that beginning next week, the EPDP weekly update will be made available in a new email newsletter format instead of a PDF attachment. The new email newsletter format has the following advantages: * Presents information in a simple and adaptable template; * Enhances accessibility to information due to its mobile-friendly platform; * Can be distributed widely online; * Provides information as to how readers interact with the content; * Ensures a consistent approach for providing GNSO policy updates (e.g., the monthly newsletter of the New gTLD Subsequent Procedures (SubPro) PDP Working Group has also been moved to this new platform). Given the Council’s role as the policy manager of GNSO PDPs and the rapid progression of the EPDP Team’s work, staff proposes to subscribe all Council members so that you will automatically receive the weekly update in a timely manner. This will only involve the email address you use to receive messages from the Council list and you will not receive any information other than the weekly update as your email address will only be subscribed for that specific purpose. Staff will also unsubscribe Council members when their terms on the Council come to an end. We will also be inviting members of the EPDP Team and interested SO/AC Leaders to subscribe to the EPDP weekly update. All editions of the EPDP weekly update will continue being archived on the wiki<https://community.icann.org/x/mRxpBQ> and website<https://gnso.icann.org/en/group-activities/active/gtld-registration-data-ep…>. Please note that this message applies only to the EPDP weekly update. As a reminder, you will need to subscribe yourself if you wish to receive the SubPro PDP Monthly Newsletter – you may do so here<https://goo.gl/forms/y32WZXOCPugoSd6G3> by Monday, 1 October. We are always exploring ways to improve and make it easier for our community to remain informed. We welcome your input/feedback so we can improve PDP and other policy updates in the future. Best Regards, Ariel Liang Ariel Xinyue Liang GNSO Policy Support Specialist Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +1 310 804 2761 Skype: ariel.liang.icann www.icann.org

1 0

EPDP weekly update
by Rafik Dammak Sept. 24, 2018

Sept. 24, 2018

Hi all, please find attached the EPDP weekly update. I will also give an update as scheduled during in the GNSO council call this week. Best Regards, Rafik

1 0

FW: [gnso-secs] NCPH nominee for GNSO council chair election
by Nathalie Peregrine Sept. 24, 2018

Sept. 24, 2018

Dear all, The Non-Contracted Party House has nominated Rafik Dammak as its candidate for the GNSO Chair 2018 election. Kind regards, Nathalie Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…> From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of farzaneh badii <farzaneh.badii(a)gmail.com> Date: Monday, September 24, 2018 at 8:30 PM To: Barbara Wanner <bwanner(a)uscib.org>, "csg-excomm(a)ICANN.org" <csg-excomm(a)icann.org>, "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [gnso-secs] NCPH nominee for GNSO council chair election Dear GNSO Secretariat, NCPH nominates Rafik Dammak to run for the GNSO council chair 2018 election. Best regards, Farzaneh -- Farzaneh

1 0