July 2019 - council - lists.icann.org

Final Proposed Agenda GNSO Council Meeting - 18 July 2019 at 21:00 UTC
by Nathalie Peregrine July 9, 2019

July 9, 2019

Dear all, Please below find the final proposed agenda for the GNSO Council Meeting on 18 July 2019 at 21:00 UTC Final GNSO Council Agenda 18 July 2019 Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://community.icann.org/x/haOjBg This agenda was established according to the GNSO Operating Procedures<https://gnso.icann.org/en/council/op-procedures-30jan18-en.pdf> v3.3, updated on 30 January 2018 For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. GNSO Council meeting held at 21:00 UTC Coordinated Universal Time: 21:00 UTC: https://tinyurl.com/y35nu9lu 14:00 Los Angeles; 17:00 Washington; 21:00 London; (+1 day) 02:00 Islamabad; 06:00 Tokyo; 07:00 Melbourne GNSO Council Meeting Audio Cast To join the event, click on the link: Listen in browser: http://stream.icann.org:8000/stream02 <https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Listen in application such as iTunes: http://stream.icann.org:8000/stream02.m3u <https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________ Item 1: Administrative Matters (10 mins) 1.1 - Roll Call 1.2 - Updates to Statements of Interest 1.3 - Review / Amend Agenda 1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes<https://gnso.icann.org/sites/default/files/policy/2019/minutes/draft-minute…> of the extraordinary GNSO Council meeting on the 28th May 2019 were posted on the 13th June 2019 Minutes [link to be added when available] of the GNSO Council meeting on the 26 June 2019 will be posted on the 13 July 2019 Item 2: Opening Remarks / Review of Projects & Action List (15 minutes) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List <https://gnso.icann.org/en/council/project> and Action Item List<https://community.icann.org/x/RgZlAg> Item 3: Consent Agenda (10 minutes) * Motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+18+July+2019> to adopt the GNSO Council response [Link to be added when available] to the GAC Marrakech Communique<https://gac.icann.org/contentMigrated/icann65-marrakech-communique> Item 4: COUNCIL DISCUSSION - GNSO Council Letter on Status of Consultation in Relation to Non-Adopted EPDP Phase 1 Parts of Recommendations (purpose 2 and recommendation #12) (15 minutes) On 15 May, the ICANN Board informed<https://gnso.icann.org/sites/default/files/file/field-file-attach/chalaby-t…> the GNSO Council of the Board’s action in relation to the GNSO’s EPDP Phase 1policy recommendations. The Board did not adopt two of the recommendations in full, where the Board has identified that portions of those recommendations are not in the best interests of the ICANN Community or ICANN and is initiating the consultation process between the Board and the GNSO Council. This concerns recommendation #1, purpose 2 and recommendation #12, deletion of data in the Organization field. As required under the ICANN Bylaws at Annex A-1,Section 6.b, a Board Statement is attached as Annex A to the letter, articulating the reasons for the Board’s non-adoption of these two items. As per the Bylaw requirements (Annex A-1, Section 6.c), “the Council shall review the Board Statement for discussion with the Board as soon as feasible after the Council's receipt of the Board Statement.” During the Council’s Extraordinary Meeting on 28 May 2019, it reviewed the Board Statement and conducted a lengthy discussion on the best path forward. On 30 May 2019, Keith Drazek, the GNSO Chair provided an update to the EPDP Team on the expected next steps in relation to the ICANN Board’s action on Phase 1 recommendations and requested that the EPDP Team provide input to identify any questions, comments or concerns in relation to ICANN Board’s action on the EPDP Phase 1 Recommendations. Subsequently, on 9 June 2019, Janis Karklins, Chair of the EPDP, informed the GNSO Chair of the following preliminary input noting that there was not sufficient time to formalize and agree on an EPDP Team response: “• In relation to purpose 2, there is a general understanding for why the Board decided to not adopt this purpose and the EPDP Team confirms that it considers it firmly within its scope for phase 2 to further review this purpose in the context of the System for Standardized Access / Disclosure (SSAD); • For recommendation #12, some additional context has been provided that may help explain the thinking behind the EPDP Team’s original recommendation. However, there is no agreement at this stage on whether or not the Board’s non-adoption should be supported.” During the Council’s June 2019 meeting, it continued to consider the next steps<https://mm.icann.org/pipermail/council/2019-May/022754.html>, taking into account a discussion with the ICANN Board at ICANN65. The reasoning and intent of the deletion part of recommendation #12 was explained to the Board, as well as the intent of purpose 2 and it was agreed that a letter should be drafted and sent to the ICANN Board as well as the EPDP Team to provide an update on the current thinking of the GNSO Council and likely next steps. Here, the Council will review the draft letter to be sent to the ICANN Board and the EPDP Team. See also Annex A-1, Section 6. Board Approval Process below for further details. Section 6. Board Approval Processes The Board will meet to discuss the EPDP recommendation(s) as soon as feasible, but preferably not later than the second meeting after receipt of the Recommendations Report from the Staff Manager. Board deliberation on the EPDP Recommendations contained within the Recommendations Report shall proceed as follows: a. Any EPDP Recommendations approved by a GNSO Supermajority Vote shall be adopted by the Board unless, by a vote of more than two-thirds (2/3) of the Board, the Board determines that such policy is not in the best interests of the ICANN community or ICANN. If the GNSO Council recommendation was approved by less than a GNSO Supermajority Vote, a majority vote of the Board will be sufficient to determine that such policy is not in the best interests of the ICANN community or ICANN. b. In the event that the Board determines, in accordance with paragraph a above, that the proposed EPDP Recommendations are not in the best interests of the ICANN community or ICANN (the Corporation), the Board shall (i) articulate the reasons for its determination in a report to the Council (the "Board Statement"); and (ii) submit the Board Statement to the Council. c. The Council shall review the Board Statement for discussion with the Board as soon as feasible after the Council's receipt of the Board Statement. The Board shall determine the method (e.g., by teleconference, email, or otherwise) by which the Council and Board will discuss the Board Statement. At the conclusion of the Council and Board discussions, the Council shall meet to affirm or modify its recommendation, and communicate that conclusion (the "Supplemental Recommendation") to the Board, including an explanation for the then-current recommendation. In the event that the Council is able to reach a GNSO Supermajority Vote on the Supplemental Recommendation, the Board shall adopt the recommendation unless more than two-thirds (2/3) of the Board determines that such guidance is not in the interests of the ICANN community or ICANN. For any Supplemental Recommendation approved by less than a GNSO Supermajority Vote, a majority vote of the Board shall be sufficient to determine that the guidance in the Supplemental Recommendation is not in the best interest of the ICANN community or ICANN. 4.1 – Introduction of topic (Council leadership) 4.2 – Council discussion 4.3 – Next steps Item 5: COUNCIL DISCUSSION – ICANN Org’s Request for Clarification on Data Accuracy and Phase-2 of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data (15 minutes) On 21 June 2019, the GNSO Council received a letter<https://gnso.icann.org/sites/default/files/file/field-file-attach/marby-to-…> from ICANN Org, which was seeking a better understanding of the Expedited Policy Development Process (EPDP) Team’s plans “to consider the subject of "data accuracy" as it relates to gTLD registration data and related services, such as the WHOIS Accuracy Reporting System (ARS)<https://whois.icann.org/en/whoisars>.” Further, “ICANN org notes that footnote #6 on page 7 of the EPDP Phase 1 Final Report states: “The topic of accuracy as related to GDPR compliance is expected to be considered further as well as the WHOIS Accuracy Reporting System.” However, it is not clear who would consider this topic and when. Therefore, ICANN org seeks the GNSO Council’s clarification on whether the Phase 2 EPDP Team will be considering the subject of data accuracy, including projects that utilize gTLD registration data, such as WHOIS ARS.” On 8 July 2019, GNSO Council Liaison to the EPDP Team, Rafik Dammak forwarded the letter to the EPDP Team seeking their input to better inform the Council in its preparation for a response to ICANN org. Here, the Council will take into consideration the questions and concerns from ICANN Org and input from the EPDP Team (if any) and seek to agree in principle on how to respond. 5.1 – Introduction of topic (Council leadership) 5.2 – Council discussion 5.3 – Next steps Item 6: COUNCIL DISCUSSION – PDP Updates on ICANN65 Activity (30 minutes) The GNSO Council, as the manager of the GNSO PDP, is seeking to ensure that it is staying current on the operations of the PDPs currently underway and to the extent that any assistance is needed from the Council, that it is considered in a timely manner. With ICANN65 recently concluded and all of the PDPs (1. PDP Review of All Rights Protection Mechanisms in All gTLDs; 2. PDP New gTLD Subsequent Procedures; and 3. Temporary Specification for gTLD Registration Data Expedited Policy Development Process Team, Phase 2) having held a number of sessions during the course of the meeting, the Council is seeking an update on each of the groups’ activities at ICANN65. Here, the Council, subject to availability, will receive an update from the respective leadership teams of the PDPs on the activities conducted at ICANN65. In addition, the Council and PDP leadership teams will have an opportunity to have a dialogue on the “asks” of Council raised during the pre-ICANN65 webinar<https://gnso.icann.org/sites/default/files/file/field-file-attach/presentat…> (see pages 7, 13, and 20). 6.1 – Introduction of topic (PDP Leadership Teams) 6.2 – Council discussion 6.3 – Next steps Item 7: COUNCIL DISCUSSION - Evolution of the Multistakeholder Model of Governance (15 minutes) At ICANN63, the ICANN Board asked the community, “How should ICANN’s multistakeholder model of governance and policy development process evolve to balance the increasing need for inclusivity, accountability and transparency, with the imperative of getting our work done and our policies developed in a more effective and timely manner, and with the efficient utilization of ICANN’s resources?” Based on community input to that question, as well as other input that resulted in the inclusion of Strategic Objective 2 in the Draft ICANN Strategic Plan for FY 2021-2025, “Improve the effectiveness of ICANN’s multistakeholder model of governance,” the ICANN Board organized a session at ICANN64, led by Brian Cute as an independent facilitator, to continue the conversation with the community. At ICANN65, the dialogue was continued, where the identified issues were consolidated and the work pivoted to developing a work plan. Here, recognizing the similar objectives within the Council’s own PDP 3.0, the Council would like to avoid duplicative or conflicting work, yet also seek to work together where synergies exist. 7.1 – Introduction of topic (Council leadership, Brian Cute) 7.2 – Council discussion 7.3 – Next steps Item 8: ANY OTHER BUSINESS (5 minutes) 8.1 - Public comment on the Fundamental Bylaw amendment<https://www.icann.org/public-comments/bylaws-amend-iana-naming-function-201…> and expected next steps for the GNSO as a member of the Empowered Community. 8.2 - Opportunity to ask any follow up questions after the webinar<https://icann.zoom.us/recording/play/bzuRFWWR-bEiVQen9_j_sWzEzcHf8-iJ2DU7ME…> on the Nominating Committee (NomCom) Review Implementation Planning Team (IPT). _______________________________ Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i)) See https://www.icann.org/resources/pages/governance/bylaws-en/#article11. Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4) See https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced… References for Coordinated Universal Time of 21:00 UTC Local time between March and October Summer in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 14:00 San José, Costa Rica (CST) UTC-6 15:00 New York/Washington DC, USA (EDT) UTC-4 17:00 Buenos Aires, Argentina (ART) UTC-3 18:00 Rio de Janeiro, Brazil (BRT) UTC-3 18:00 London, United Kingdom (GMT) UTC+1 22:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 22:00 Paris, France (CET) UTC+2 23:00 Moscow, Russia (MSK) UTC +3 (+1 day) 00:00 Islamabad, Pakistan (PKT) UTC+5 (+1 day) 02:00 Singapore (SGT) UTC+8 (+1 day) 05:00 Tokyo, Japan (JST) UTC+9 (+1 day) 06:00 Melbourne, Australia (AEDT) UTC+11 (+1 day) 07:00 ---------------------------------------------------------------------------- DST starts/ends on Sunday 27 of October 2019, 2:00 or 3:00 local time (with exceptions) for EU countries and on Sunday 03 of November 2019 for the US. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and https://tinyurl.com/y35nu9lu

1 0

REMINDER / Call for volunteers IRP-IOT and proposed Council endorsement process
by Terri Agnew July 9, 2019

July 9, 2019

**REMINDER: DUE 12 JULY 2019 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

Re: [council] Draft Motion GAC Communique
by Nathalie Peregrine July 8, 2019

July 8, 2019

Dear Michele, Thank you for your email. The motion has been posted on the Motion wiki page<https://community.icann.org/display/gnsocouncilmeetings/Motions+18+July+2019>. Kind regards, Nathalie On 7/8/19, 6:46 PM, "council on behalf of Michele Neylon - Blacknight" <council-bounces(a)gnso.icann.org on behalf of michele(a)blacknight.com> wrote: Please see attached -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://urldefense.proofpoint.com/v2/url?u=https-3A__www.blacknight.com&d=D… https://urldefense.proofpoint.com/v2/url?u=https-3A__blacknight.blog&d=DwIG… / https://urldefense.proofpoint.com/v2/url?u=http-3A__ceo.hosting_&d=DwIGaQ&c… Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow, R93 X265, Ireland Company No.: 370845

1 0

Draft Motion GAC Communique
by Michele Neylon - Blacknight July 8, 2019

July 8, 2019

Please see attached -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com https://blacknight.blog / http://ceo.hosting/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow, R93 X265, Ireland Company No.: 370845

1 0

[ICANN Community Leaders] 8 July Update
by Nathalie Peregrine July 8, 2019

July 8, 2019

[http://r20.rs6.net/on.jsp?ca=7568bc57-3063-41a9-86a4-e4cd0ba7f25d&a=1122025…] Monday, 8 July 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. TABLE OF CONTENTS Information Sharing · NEW: Update and Information on IRP IOT Re-Composition · REMINDER: Planning Assumptions for Subsequent Procedures for New gTLDs Public Comment · Process Proposal for Streamlining Organizational Reviews · Study on Technical Use of Root Zone Label Generation Rules · Fundamental Bylaws Amendment Proposal -- IANA Naming Function Review · Revisions to the ICANN Bylaws re SSAC and RSSAC Leadership · 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 Information Sharing NEW: 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. Public Comment Process Proposal for Streamlining Organizational Reviews [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Monday, 15 July 2019 Study on Technical Use of Root Zone Label Generation Rules [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 19 July 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-…> Close Date: 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-…> Close Date: 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-…> Close Date: 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: 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 30 | Archive [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> | Next Issue: Thursday, 11 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 [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

DEADLINE TODAY Reminder: Document and Motion deadline Monday 8 July 2019 at 23:59 UTC for GNSO Council Meeting 18 July 2019 at 21:00 UTC
by Nathalie Peregrine July 8, 2019

July 8, 2019

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

Action Items: ICANN65
by Nathalie Peregrine July 3, 2019

July 3, 2019

Dear Councilors, Please find the action items, as stated during the meetings, below arising from the following sessions held during ICANN65: GNSO Working Session, GNSO Council meeting, joint GNSO and ccNSO Councils meeting, and the GNSO Wrap up session. Please take note of the below action items and the proposed timing for delivery. Please ensure your wiki logins are up to date as all Action Items have been assigned to councilors and/or staff and posted on the Action Item wiki page here<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…>. If you are logged into the wiki when you go to that page, your name will be highlighted alongside the action item assigned to you. Please refer to this page for the recent status updates on the Action items. Please note that actions for all councilors are highlighted below. ICANN65 GNSO Council Working Session (24 June 2019) 1. GNSO Council to consider if/how to replace Erica Varlese on ATRT3. ICANN staff to investigate if there are any remaining GNSO candidates to consider. If not, determine if replacement is needed and if so, determine approach (e.g., call for volunteers, use SSC) 2. GNSO Chair to remind SG/Cs to discuss within its respective groups and respond directly (and/or inform Council if there is something within its purview) to the ATRT3 with a response to the following question: what types of improvements would the Community want to see implemented? ICANN65 GNSO Council Meeting (26 June) Item 4: COUNCIL DISCUSSION - Re-populating the Independent Review Process Implementation Oversight Team (IRP IOT) / GNSO Input to the Independent Review Process Standing Panel (15 minutes) Action Items: * Council to convene small team to review questions posed by ICANN org. (Volunteers: Flip as lead, Elsa) Item 5: COUNCIL DISCUSSION – IGO-INGO Access to Curative Rights Protection Mechanisms Next Steps (15 minutes) Action Items: * Small team to prepare draft RPMs charter amendments (which will likely include engagement with the IGOs/GAC afterwards) (Volunteers, Paul as lead, Martin, Elsa, Keith) Item 6: COUNCIL DISCUSSION – Next Steps For Internationalized Domain Names (15 minutes) Action Items: * GNSO Chair to send message to Council list to expand volunteer pool expertise beyond Council. Small team to consider and propose scope of holistic IDN review, prior to outreach with ccNSO. (Volunteers: Rubens, Maxim, Philippe, Edmon, Michele) Item 7: COUNCIL DISCUSSION - Board Consultation on the Expedited PDP on the Temporary Specification Phase 1 - Next Steps (15 minutes) Action Items: * Council to, in consultation with the EPDP team, write communication to ICANN Board and seek to secure board support for Rec #12. Item 8: COUNCIL DISCUSSION – Consideration of Updates From PDPs and Determination if Follow-Up or Council Action is Needed (10 minutes) Action Items: * ICANN Staff to consider timing for webinar (e.g., two weeks prior). ICANN Staff to consider suggested changes to slide format raised during meeting. Item 9: COUNCIL DISCUSSION – Consideration of Competition, Consumer Trust & Consumer Choice Review Team (CCT-RT) Recommendations Passed to the GNSO (10 minutes) Action Items: * Council to convene small team to consider CCT-RT recommendations referred to the GNSO and GNSO PDPs and determine next steps (Volunteers: Pam to lead, Carlos, Michele) ccNSO/GNSO Joint Meeting (26 June) * Evolution of MSM * Action Items * ccNSO and GNSO to form joint team to identify any commonalities or differences. Also look at budget and 5 year strategic plan. * ICANN staff to reach out to Maarten and Philippe to determine if they are willing to lead action item above. * IDNs and string similarity * Action Items: * GNSO Chair to email Katrina to inform her of immediate next steps and willingness determine the best coordination method between the GNSO and ccNSO. * Once GNSO small team is able to gain an understanding of the scope of effort and potential vehicle for resolution, ICANN staff to schedule call to identify structure for coordination between the GNSO and ccNSO. GNSO and ccNSO to identify where coordination is and is NOT needed. * ICANN staff to reach out to Maarten and Philippe to determine if they are willing to lead action items above. * ICANN staff to investigate format for JIG and see if it may be fit for purpose. Wrap-up Session (27 June 2019) * Review of ICANN65 GAC Advice * Action Item: * Council small team to determine if response is necessary. If so, small team to draft response (Volunteers: Julf, Paul, Martin, Michele, Tatiana.) * Marika to investigate when GAC/Board meeting will take place * Reminder of small team activities: * RPMs Charter amendments for Phase 2 (Volunteers: Paul, Martin) * Correspondence and proposed next steps for: * Request for Clarification on Data Accuracy and Phase-2 of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data * Action Item * Council’s liaison to the EPDP, Rafik to forward letter to EPDP Phase 2 Team and coordinate with them to determine what will be included in the response. * Council to add as a discussion item for future meeting. * ICANN org's preparation toward implementation of a new round of gTLDs * Action Item: * Council to Invite GDD to speak to Council on a future Council meeting. * ICANN66 Meeting Planning * Whether to have an informal dinner (and volunteer to organize if yes) * Yes. Choose the date earlier? Should be Saturday. * Action Item: Send schedule placeholder for informal dinner. * Input to leadership for planning purposes * Re-evaluate purpose, criteria and number of HITs/CCs * Aim to avoid GNSO Council conflicts with “major” things * Action Item: None * AOB * Council liaisons (IGO Red Cross) * Action Item: * ICANN staff to update relevant documentation to note change of liaison from Keith Drazek to Tatiana Tropina * Reminder - Attend EPDP Phase 1 Impacts at 15:15 * Action Item: ICANN staff to invite Brian Cute to a future Council meeting * Action Item: Rafik Dammak to invite Brian Cute to future PDP 3.0 meeting to make sure to not create overlapping work on the Evolution of the MSM * Action Item: Council leadership to ask SSR2 GNSO members to provide an update to the Council leadership initially. * Action Item: ICANN staff to review existing liaisons, determine who is termed out at the upcoming AGM, seek replacements and perform handover beforehand. Thank you, Kind regards, Nathalie -- Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

Draft minutes of the GNSO Council meeting 26 June 2019
by Nathalie Peregrine July 3, 2019

July 3, 2019

Dear Councilors, Attached, please find the draft minutes of the GNSO Council meeting Wednesday 26 June 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 13th July 2019. Thank you very much. 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

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

Reminder: Document and Motion deadline Monday 8 July 2019 at 23:59 UTC for GNSO Council Meeting 18 July 2019 at 21:00 UTC
by Nathalie Peregrine July 2, 2019

July 2, 2019

Dear all, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday 8 July 2019 at 23:59 UTC) of the GNSO Council Meeting on Thursday 18 July 2019 at 21:00 UTC. Motions should be sent to the Council mailing list by a councilor and will then be posted on the Wiki at: https://community.icann.org/x/g6OjBg Thank you very much. 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 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 1