December 2019 - council - lists.icann.org

FYI: [ICANN Community Leaders] 19 December Update
by Michelle DeSmyter 19 Dec '19

19 Dec '19

FYI: [http://r20.rs6.net/on.jsp?ca=993ac9e6-a0b3-4227-8de6-262f88ae0132&a=1122025…] Thursday, 19 December 2019 ICANN Community Leadership Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] The ICANN org Policy Development Support team publishes this twice-weekly digest to help ICANN community leaders track requests and updates. The ICANN Community Leadership Digest will return on Monday, 6 January 2020. Table of Contents Information Sharing · REMINDER: Revised Schedule for Public Comment on Two Key ICANN Plans · REMINDER: Opportunity for Strategic Outlook Trends Identification Sessions at ICANN67 · REMINDER: FY21 SO/AC Additional Budget Request Process · REMINDER: ICANN Fellowship Program Mentors ICANN67 Planning · REMINDER: ICANN67 Publication Support · REMINDER: CROP Deadline for ICANN67 Public Comment · Registration Directory Service (WHOIS2) Review Team Final Report · Proposal for Future Root Zone KSK Rollovers · NEW: Third Accountability and Transparency Review Team (ATRT3) Draft Report Information Sharing REMINDER: Revised Schedule for Public Comment on Two Key ICANN Plans ICANN org Announcement [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> FOR: All Community Leaders INFORMATION SHARING The Public Comment proceeding for the Draft FY21-FY25 Operating and Financial Plan and Draft FY21 Operating Plan and Budget has changed. Originally scheduled for Tuesday, 17 December 2019, drafts of the two plans will now be available beginning Friday, 20 December 2019. This date change may impact previously scheduled meetings intended for the Supporting Organizations and Advisory Committees to begin their review. ICANN org is prepared to provide those groups with the table of contents of the documents and other information that may be helpful prior to the release of the complete drafts. Please email planning(a)icann.org<mailto:planning@icann.org> to request. Information also will be published on the Finance community wiki page [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. In addition, the Public Comment proceeding has been extended by 7 days to 58 days (excluding holidays) to give the community more time to review the documents. To learn more and ask questions during the Public Comment window, webinars will be held on: · Thursday, 9 January 2020 at 01:00 UTC https://icann.zoom.us/j/935036343 [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> · Thursday, 9 January 2020 at 16:00 UTC https://icann.zoom.us/j/506858960 [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> · Monday, 14 January 2020 at 16:00 UTC https://icann.zoom.us/j/257109807 [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> More details about how to join these webinars will be available in January. ICANN org staff is available to meet with individual community groups to answer questions and help increase understanding about the plans. Please email planning(a)icann.org<mailto:planning@icann.org> to request a meeting. REMINDER: Opportunity for Strategic Outlook Trends Identification Sessions at ICANN67 Executive: Theresa Swinehart, Senior Vice President, Multistakeholder Strategy and Strategic Initiatives FOR: All Community Leaders INFORMATION SHARING ICANN org will hold Strategic Outlook Trends Identification sessions with the community at ICANN67. To prepare for that exercise, ICANN org will be seeking community feedback on possible formats and arrangements which will be sent through each community group’s leadership. The Strategic Outlook program [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> is a joint effort among ICANN org, the community, and ICANN Board to identify and track trends that relate to ICANN and its mission and to make sure that relating opportunities and challenges are incorporated into ICANN's current and future strategy. New trends or shifts in existing trends impacting the operating plans (five-year or annual), and/or budget, will be factored into the annual iteration of those plans as appropriate. Significant shifts could also result in adjustments to the strategic plan. REMINDER: FY21 SO/AC Additional Budget Request Process Executive: Xavier Calvez, Chief Financial Officer FOR: All Community Leaders INFORMATION SHARING The Fiscal Year 2021 (FY21) Supporting Organization and Advisory Committee (SO/AC) Additional Budget Request process has begun. This additional budget approval process is part of the overall ICANN annual budgeting process that is for the review of specific requests from the community that are not already included in the budget but serve to further the key objectives of the requesting community group. Your active participation and adherence to procedural guidelines is greatly appreciated. Information concerning the FY21 SO/AC Additional Budget Request process, including timeline and request template can be found on the finance community wiki [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. Additional Budget Requests are due Friday, 31 January 2020. Please email any questions that you may have to planning(a)icann.org<mailto:planning@icann.org>. We look forward to your continued engagement on the SO/AC Additional Budget Request process for FY21. REMINDER: ICANN Fellowship Program Mentors From: Sally Costerton, Senior Vice President, Global Stakeholder Engagement FOR: All Community Leaders INFORMATION SHARING ICANN's Supporting Organizations (SOs) and Advisory Committees (ACs) are invited to nominate [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> one individual each (total of seven) to serve as a mentor in the ICANN Fellowship Program. Mentors will serve a term that includes three consecutive ICANN Public Meetings, beginning with ICANN68. They will provide extensive pre-meeting preparation and on-site support for their assigned fellows, as well as complete a survey after each meeting. Mentors are expected to follow Fellowship Program guidelines to help ensure consistency in capacity development opportunities for fellows. They also play an important role to help fellows actively participate in ICANN's work. Mentors will receive travel funding support. Mentors cannot serve on the Fellowship Program Selection Committee [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> at the same time they are serving as mentors. For more information on the guidelines and expectations for mentors, please read about the program here [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. SOs/ACs should first select their respective Fellowship Program mentor by Friday, 31 January 2020, and notify fellowshipconsultation(a)icann.org. Individual self-nominations will not be considered. ICANN67 Planning REMINDER: ICANN67 Publication Support From: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING Design Deadline If you require design assistance for an ICANN67 publication, all text, images, layout, and publication type/size requirements (i.e. newsletter, 1-pager, tri-fold, etc.) are due Friday, 3 January 2020. Please ensure that all materials, new or updated, are evergreen. Translation Deadline If your ICANN67 publication requires translation, please provide the final material(s) by Monday, 27 January 2020. This ensures that there is enough time to translate the publication by the print deadline. If your materials require design assistance (outlined above), please note that the final materials will have to be complete, including the edit/approval process, by this deadline in order to be translated. Print-Only Deadline If you only need your ICANN67 publication printed (meaning your publication is ready to send directly to the printer and needs no translation or design/layout modifications), please provide the file along with the quantity you want printed and dimensions of the publication by Friday, 7 February 2020. Please work directly with your support staff to submit these requests to chantelle.doerksen(a)icann.org and liana.teo(a)icann.org. REMINDER: CROP Deadline for ICANN67 From: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING For eligible groups planning to use Community Regional Outreach Program (CROP) funds to conduct outreach during ICANN67, requests must be submitted no later than Friday, 17 January 2020. No exceptions will be made. When submitting a CROP travel request, please keep in mind the following: Trip requests must be approved by the respective community leadership team. For FY20, the trip request must be filled in by the CROP participant via the CROP workspace [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. In order to access it, applicants must first have an account; please let the CROP coordinator know if you need an account. All individuals requesting CROP funding must also review the CROP Guidelines [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> prior to submitting a request. Please contact crop-staff(a)icann.org with any questions. Public Comment Registration Directory Service (WHOIS2) Review Team Final Report [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Monday, 23 December 2019 Proposal for Future Root Zone KSK Rollover [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 31 January 2020 NEW: Third Accountability and Transparency Review Team (ATRT3) Draft Report [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 31 January 2020 Volume 1, Issue 75 | Archive [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> | Next Issue: Monday, 6 January 2020 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

GNSO Council Meeting / Supplemental Recommendation re EPDP - 19 December 2019
by Marie Pattullo 19 Dec '19

19 Dec '19

Dear all, The BC appreciates all of the discussions to date on the non-adopted EPDP Phase 1 Recommendations, and thanks Rafik for the drafting of the Supplemental Recommendation. May we suggest a small amendment Resolved... 2. In relation to Recommendation 12, with respect to the option to delete data in the Organization field, the GNSO Council adopts the following Supplemental Recommendation reaffirming the part of the original Recommendation #12 and the Implementation Advice which stated that: “b) If the registrant declines, or does not respond to the query, the Registrar may redact the Organization field, or delete the field contents.” (emphasis added) but hereby providing additional implementation guidance: similar to what was recommended in Recommendation 29 in the context of the deletion of administrative contact, prior to eliminating Organization Contact fields, all Registrars MUST ensure that each registration contains Registered Name Holder contact information. Rationale: the original wording would lead to deletion based not on data inaccuracy, but on registrants’ failure to respond. If the data is inaccurate (reference Section 4 of the WAPS, https://www.icann.org/resources/pages/approved-with-specs-2013-09-17-en#who…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>) the Contracted Parties should already seek to correct the inaccuracy. We could also agree that historical circumstances have resulted in different uses of that field, and therefore WHOIS inaccuracy complaints should not be based on inconsistencies or syntactical errors with Org field data, at least for some period of time. With this change the BC will be happy to vote in favour of the motion on Thursday. Best to all, Marie From: council <council-bounces(a)gnso.icann.org> On Behalf Of Andrea Glandon Sent: Tuesday, December 10, 2019 7:56 PM To: council(a)gnso.icann.org Cc: gnso-secs(a)icann.org Subject: [council] Final Proposed Agenda GNSO Council Meeting - 19 December 2019 at 21:00 UTC Dear all, Please find below the final proposed agenda for the GNSO Council Meeting on 19 December 2019 at 21:00 UTC. Draft GNSO Council Agenda 19 December 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/D5IzBw 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/w82k6rn 13:00 Los Angeles; 13:00 Washington; 21:00 London; (Friday) 02:00 Islamabad; (Friday) 06:00 Tokyo; (Friday) 08:00 Melbourne GNSO Council Meeting Audio Cast Listen in browser: http://stream.icann.org:8000/stream0<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…>1 Listen in application such as iTunes: http://stream.icann.org:8000/stream01.m3u 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/minutes-coun…> of the GNSO Council meeting on the 24 October 2019 were posted on 13 November 2019 Minutes Part 1<https://gnso.icann.org/sites/default/files/policy/2019/minutes/minutes-gnso…> Part 2 <https://gnso.icann.org/sites/default/files/policy/2019/minutes/minutes-gnso…> of the GNSO Council meetings on the 06 November 2019 were posted on 26 November 2019 Item 2: Opening Remarks / Review of Projects & Action List (20 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/x/DZIzBw> to adopt the GNSO Council response to the GAC Communique. * Motion<https://community.icann.org/x/DZIzBw> for the confirmation of GNSO representative to the Empowered Community Administration * Confirmation of Anne Aikman-Scalese as one of the GNSO appointees to the CCWG Auction Proceeds Item 4: COUNCIL VOTE - Approval of the Supplemental Recommendation Related to the Non-Adopted EPDP Phase 1 Recommendations (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 1 policy 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. The Council discussed a draft response on its 18 July 2019 meeting, subsequent discussion on the mailing list, and additional dialogue on the 22 August 2019 meeting. On 9 September 2019, the GNSO Council sent its response<https://gnso.icann.org/sites/default/files/file/field-file-attach/gnso-coun…> to the ICANN Board. On 14 October 2019, the ICANN Board provided its response<https://gnso.icann.org/sites/default/files/file/field-file-attach/chalaby-t…> to the GNSO Council’s update. On the Council’s October 2019 meeting, the Council considered the Board’s response and discussed next steps. The Council consulted with the EPDP Team regarding some potential ways of addressing Board’s concerns (i.e., including implementation guidance), in preparation for discussions with the ICANN Board at ICANN66. At ICANN66, the GNSO Council conducted dialogue with the ICANN Board to share the proposed approach. Here, the Council will vote to approve Supplemental Recommendation reaffirming the part of the original Recommendation #12 and the Implementation Advice. 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 – Presentation of motion (Council leadership) 4.2 – Council discussion 4.3 – Council vote (voting threshold: Supermajority) Taking this action is within the GNSO’s remit as outlined in ICANN’s Bylaws as the GNSO ‘shall be responsible for developing and recommending to the Board substantive policies relating to generic top-level domains and other responsibilities of the GNSO as set forth in these Bylaws’ (Art.11.1). Furthermore, this action complies with the requirements set out in Annex A: GNSO Policy Development Process of the ICANN Bylaws. Item 5: COUNCIL DISCUSSION – Discussion on the Addendum to the Review of All Rights Protection Mechanisms in All gTLDs Charter to Integrate Recommendation 5 From IGO-INGO Access to Curative Rights Protection Mechanisms Final Report (20 minutes) On 18 April 2019, the Council voted<https://community.icann.org/display/gnsocouncilmeetings/Motions+18+April+20…> to approve recommendations 1-4 of Final Report from the IGO-INGO Access to Curative Rights Protection Mechanisms PDP WG. The Council also resolved to not approve Recommendation 5 and, ” directs the Review of All Rights Protection Mechanisms in All gTLDs (RPM) PDP to consider, as part of its Phase 2 work, whether an appropriate policy solution can be developed that is generally consistent with Recommendations 1, 2, 3 & 4 of the PDP Final Report and: * accounts for the possibility that an IGO may enjoy jurisdictional immunity in certain circumstances; * does not affect the right and ability of registrants to file judicial proceedings in a court of competent jurisdiction; * preserves registrants’ rights to judicial review of an initial UDRP or URS decision; and * recognizes that the existence and scope of IGO jurisdictional immunity in any particular situation is a legal issue to be determined by a court of competent jurisdiction.” The GNSO Council resolved also to, “amend the charter for the RPMs PDP Working Group to reflect this new instruction accordingly.” Some members of the GNSO Council met with certain members of the GAC and IGOs at ICANN65, where there appeared to be agreement from the GAC/IGOs to support the chartering of this separate work. A small team of Councilors was convened to prepare a draft Addendum to the RPMs PDP charter, which was discussed during the Council’s September 2019 meeting. After integrating Councilor feedback, the revised Addendum<https://gnso.icann.org/en/drafts/rpms-charter-addendum-09oct19-en.pdf> was shared with the GAC and IGOs for their consideration. The Council considered GAC/IGO feedback<https://gnso.icann.org/sites/default/files/file/field-file-attach/ismail-to…> received on 1 November 2019, as well as feedback from the meeting with the GAC at ICANN66. Taking into account GAC and IGO feedback received and balancing with the goals of the GNSO Council, leadership prepared a revised draft for GNSO Council consideration. Here, the Council will discuss the draft revisions to the Addendum to the RPMs PDP charter, as well as additional steps that need to be taken prior to Council consideration for adoption. 5.1 – Introduction of topic (Council leadership) 5.2 – Council discussion 5.3 – Next steps Item 6: COUNCIL UPDATE - Expedited PDP on the Temporary Specification for gTLD Registration Data - Phase 2 Work (15 minutes) As noted in the charter<https://community.icann.org/display/EOTSFGRD/EPDP+Team+Charter> for the Expedited PDP on the Temporary Specification for gTLD Registration Data, work on a System for Standardized Access to Non-Public Registration Data (SSAD) commenced after the work on a series of gating questions are complete. With the EPDP Team’s delivery of its Final Report to the GNSO Council, the work on the gating questions was considered completed and the work on the SSAD, or otherwise known as phase 2 of the EPDP, commenced. In March of 2019, the GNSO Council resolved to indicate its non-objection to the EPDP Phase 2 work beginning; the Team commenced its Phase 2 deliberations on 2 May 2019. The Team has worked diligently in developing draft “building blocks” and policy principles that can serve as components of the SSAD. Leveraging ICANN meetings and a dedicated face-to-face meeting in September 2019, as well as remote meetings twice a week, the Team has made substantial progress towards its goal of publishing its Initial Report for public comment by mid-December of 2019. However, the EPDP Team collectively agreed to delay publication from December until a target date of 7 February 2020, noting it would prefer more time to ensure the overall quality and comprehensiveness of its draft recommendations; accordingly, the Team submitted a Project Change Request (PCR<https://community.icann.org/download/attachments/105388008/EPDP-P2_Project_…>) to the GNSO Council. The EPDP Leadership presented the ramifications of delayed publication to the EPDP Team, noting, specifically, if the EPDP Team delays publication at this stage, no slack remains in the project plan to deliver a Final Report by June. In the event the EPDP Team does not meet the June deadline, any remaining resources allocated will be returned to conclude fiscal year 2020. Therefore, if the EPDP were to determine additional resources will be necessary to complete its work, the GNSO Council will be required to request more resources from the Board. Here, the Council will receive an update on the status of the EPDP Phase 2. 6.1 – Introduction of topic (Council leadership; Rafik Dammak - Council Liaison) 6.2 – Council discussion 6.3 – Next steps Item 7: COUNCIL DISCUSSION - GNSO Council Strategic Planning Session (15 minutes) From 22-24 January of 2020, the GNSO Council will hold its third Strategic Planning Session (SPS), which is a result of previous GNSO Councils realizing the benefit of holding dedicated sessions to plan and prepare for the coming year of work; the primary objective of these sessions is to develop a work plan for the year ahead and beyond. However, the sessions also help the GNSO Council to better understand its responsibilities and remit and how to more effectively perform its role. Council leadership and staff have collaborated on planning the upcoming SPS. Here, the Council will discuss the draft agenda, expectations for Councilors, and review action items from previous SPSs. 7.1 - Introduction of topic (Council leadership) 7.2 - Council discussion 7.3 - Next steps Item 8: ANY OTHER BUSINESS (10 minutes) 8.1 - Consideration of previous GNSO Council Additional Budget Requests (ABRs) and whether they should be pursued in the future, as well as if other ABRs should be submitted. FY20 ABRs included: * GNSO Council Strategic Planning Session<https://community.icann.org/download/attachments/102146823/FY20%20ABR_SPS.p…> (similar ABRs submitted in FY18, FY19, and FY20) * PDP Leadership Travel Pilot<https://community.icann.org/download/attachments/102146823/FY20%20ABR_Trave…> (similar ABRs submitted submitted in FY18, FY19, and FY20) * Consensus Building Playbook<https://community.icann.org/download/attachments/102146823/FY20%20ABR_Conse…> (submitted in FY20 only, as an element of PDP 3.0) _______________________________ 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 October and March Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PST) UTC-8 13:00 San José, Costa Rica (CST) UTC-6 15:00 New York/Washington DC, USA (EST) UTC-5 16:00 Buenos Aires, Argentina (ART) UTC-3 18:00 Rio de Janeiro, Brazil (BRST) UTC-2 20:00 London, United Kingdom (GMT) UTC+0 21:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 22:00 Paris, France (CET) UTC+1 22:00 Islamabad, Pakistan (PKT) (+1 day) UTC+5 02:00 Singapore (SGT) (+1 day) UTC+8 05:00 Tokyo, Japan (JST) (+1 day) UTC+9 06:00 Melbourne, Australia (AEDT) (+1 day) UTC+11 08:00 ---------------------------------------------------------------------------- DST starts/ends on Sunday 29 of March 2020, 2:00 or 3:00 local time (with exceptions) for EU countries and on Sunday 08 of March 2020 for the US. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and https://tinyurl.com/w82k6rn

3 3

DRAFT ADDENDUM TO THE CHARTER FOR THE REVIEW OF ALL RPMS PDP
by Steve Chan 19 Dec '19

19 Dec '19

Dear Councilors, On behalf of the small team and Council leadership, please find the latest draft of the Addendum to the RPMs Charter to incorporate recommendation 5 from the IGO Curative Rights Protection Mechanisms Final Report. This draft will be discussed during the 19 December Council meeting under agenda item 5. Best, Steve Steven Chan  Policy Director, GNSO Support Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Email: steve.chan(a)icann.org Skype: steve.chan55 Mobile: +1.310.339.4410 Find out more about the GNSO by visiting: https://learn.icann.org/ Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar

3 2

GNSO Council Absence Notification Form [#339]
by ICANN 18 Dec '19

18 Dec '19

1 0

FW: EPDP Phase 1 Recommendation 28
by Drazek, Keith 18 Dec '19

18 Dec '19

Hi all, Please see the attached letter from Goran related to timing of the EPDP Phase 1 IRT. We will have a Council action item to affirm our support for ICANN’s continued work with the community on implementing the Phase 1 recommendations, while acknowledging the original target date of February 29, 2020 will not be met. Thanks, and we can discuss further during tomorrow’s Council call. Regards, Keith From: Tina Shelebian <tina.shelebian(a)icann.org> Sent: Wednesday, December 18, 2019 12:30 PM To: Drazek, Keith <kdrazek(a)verisign.com> Cc: karklinsj(a)gmail.com; Correspondence <Correspondence(a)icann.org> Subject: [EXTERNAL] EPDP Phase 1 Recommendation 28 Tina Shelebian on behalf of Goran Marby Dear Keith, Attached please find letter from Göran with Information regarding EPDP Phase 1 Recommendation 28. Please note that I’ve copied Janis Karklins as a courtesy. Best regards, Tina Shelebian Executive Assistant, Office of the President & CEO Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 Direct: (310) 578-8906 tina.shelebian(a)icann.org<mailto:tina.shelebian@icann.org>

1 0

Reading Materials GNSO Council meeting 19 December 2019 at 21:00 UTC
by Nathalie Peregrine 18 Dec '19

18 Dec '19

Dear all, In order to prepare for the GNSO Council meeting on Thursday 19 December 2019 at 21:00 UTC, please find links below to reading materials. * GNSO Council meeting agenda: https://community.icann.org/x/C5IzBw * GNSO Council Action Items: https://community.icann.org/x/RgZlAg * GNSO Project List: https://gnso.icann.org/en/council/project * GNSO Council meeting motions: https://community.icann.org/x/DZIzBw * GNSO Council Documents for Council meeting: https://community.icann.org/x/D5IzBw * Documents for GNSO Council input: https://community.icann.org/x/zIAzBw Please note that the Small Group on RPM Charter Amendment for IGO Addendum will be circulating an updated document to the Council mailing list later today, this will then be added to the corresponding pages listed above. 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 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…>

1 0

FW: NomComRIWG: Outreach questions
by Drazek, Keith 16 Dec '19

16 Dec '19

Hi all, Please see the email below from the NomCom Review Implementation Working Group. They have posed a set of questions to the GNSO Council, with a response deadline of January 31. I suggest we form a small team to coordinate the Council’s answers and reply. If anyone would like to volunteer, please let me know. Best, Keith From: Jean-Baptiste Deroulez <jean-baptiste.deroulez(a)icann.org> Sent: Friday, December 13, 2019 8:13 AM To: Drazek, Keith <kdrazek(a)verisign.com>; pam.little(a)alibaba-inc.com; rafik.dammak(a)gmail.com Cc: Tom Barrett <tbarrett(a)encirca.com>; Cheryl Langdon-Orr <langdonorr(a)gmail.com>; Zahid Jamil-IG <internet(a)jamilandjamil.com>; Lars Hoffmann <lars.hoffmann(a)icann.org>; Steve Chan <steve.chan(a)icann.org>; gnso-secs(a)icann.org Subject: [EXTERNAL] NomComRIWG: Outreach questions Dear Keith, Dear Pam, Dear Rafik, As the leaders of the NomCom Review Implementation Working Group (NomComRIWG), we are contacting you following the ICANN Board’s acceptance of our Detailed Implementation Plan<https://www.icann.org/resources/board-material/resolutions-2019-11-07-en#2.b>. The NomComRIWG has been directed to commence implementation of the twenty-seven (27) recommendations, and we are seeking the GNSO Council’s responses to a number of questions via the following google form: https://forms.gle/vrs95jrp9akK5sSRA by 31 January 2020. Feel free to also seek input from the GNSO Council’s supporting staff if you believe this might add value to the implementation. If we have not received the GNSO Council’s response or a request for an extension by the deadline, we will proceed with the implementation without your input. If you prefer, feel free to respond separately to individual questions that you are able to answer, rather than wait until you are able to answer all of the questions at once. Please note this is the first round of several outreaches, we will be continuously outreaching to you throughout the implementation phase (over the next twenty-four to thirty-six months) due to the nature of this review. In particular, many members of the NomComRIWG will attend ICANN67 and plan to hold an update session for the entire community. If your group has time on your internal agenda and would like to meet with us for a short in-person update, do not hesitate to reach out to us via mssi-secretariat(a)icann.org<mailto:mssi-secretariat@icann.org> and we will happily coordinate. Finally, if you have any questions or concerns, either about the questions, or about any other aspect of the NomCom Review implementation, please, do not hesitate to reach out to us. Many thanks and best wishes, Tom Barrett, Chair NomComRIWG Cheryl Langdon-Orr, Vice-Chair NomComRIWG Zahid Jamal, Vice-Chair NomComRIWG NomComRIWG wiki: https://community.icann.org/x/aBpIBg Detailed Implementation Plan: PDF<https://www.icann.org/en/system/files/files/nomcom-implementation-plan-15se…> Rec. 14: Formalize communication between the NomCom and the Board, SOs/ACs, and the PTI Board to understand needed competencies and experience. * Is there additional information that could be shared between the NomCom and the GNSO so that the NomCom can better target its selection to the needs of the GNSO Council? Rec. 16: Implement and codify a system for providing feedback to the NomCom regarding the contributions and participation of members up for re-appointment by the NomCom. * What information do you currently share with the NomCom about its NomCom appointees, and what is the timing of these communications? * In your opinion, what additional information should be shared between you and the NomCom? Rec. 21: The NomCom should use a standardized tool to evaluate and prioritize candidates, based on desired competencies and experience as determined annually. This tool will not replace qualitative assessments of candidates. * In your opinion, what tools, assessments and skills analysis should be used by the NomCom to make the best possible selection. Rec. 22: The NomCom should provide consistent interview questions and an interviewer evaluation form for the candidates interviewed during the deep-dive phase and the final face-to-face interviews. * In your opinion, which questions should be part of the "interview question library" and which would then be used by every NomCom? Rec. 25: Improve NomCom selection decisions by assessing the performance and needs of all bodies receiving NomCom appointees. * Is the GNSO Council performing any self-assessments, or third-party assessments? * If yes, are there any identified skills needed for future NomCom appointees to your organization? * If applicable, how do you communicate this to the NomCom? * What performance assessment, if any, do you think is feasible by the GNSO Council to improve future NomCom selection decisions.

3 2

GNSO Council Absence Notification Form [#338]
by ICANN 16 Dec '19

16 Dec '19

1 0

[ICANN Community Leaders] 16 December Update
by Andrea Glandon 16 Dec '19

16 Dec '19

[http://r20.rs6.net/on.jsp?ca=dc185dc3-c8ad-458b-9de2-3a124e15fac4&a=1122025…] Monday, 16 December 2019 ICANN Community Leadership Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] The ICANN org Policy Development Support team publishes this twice-weekly digest to help ICANN community leaders track requests and updates. Table of Contents Information Sharing · NEW: Revised Schedule for Public Comment on Two Key ICANN Plans · DUE TODAY: NextGen@ICANN Community Consultation · REMINDER: Opportunity for Strategic Outlook Trends Identification Sessions at ICANN67 · REMINDER: FY21 SO/AC Additional Budget Request Process · REMINDER: ICANN Fellowship Program Mentors ICANN67 Planning · REMINDER: ICANN67 Publication Support · REMINDER: CROP Deadline for ICANN67 Public Comment · Registration Directory Service (WHOIS2) Review Team Final Report · Proposal for Future Root Zone KSK Rollovers Information Sharing NEW: Revised Schedule for Public Comment on Two Key ICANN Plans ICANN org Announcement [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> FOR: All Community Leaders INFORMATION SHARING The Public Comment proceeding for the Draft FY21-FY25 Operating and Financial Plan and Draft FY21 Operating Plan and Budget has changed. Originally scheduled for Tuesday, 17 December 2019, drafts of the two plans will now be available beginning Friday, 20 December 2019. This date change may impact previously scheduled meetings intended for the Supporting Organizations and Advisory Committees to begin their review. ICANN org is prepared to provide those groups with the table of contents of the documents and other information that may be helpful prior to the release of the complete drafts. Please email planning(a)icann.org<mailto:planning@icann.org> to request. Information also will be published on the Finance community wiki page [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. In addition, the Public Comment proceeding has been extended by 7 days to 58 days (excluding holidays) to give the community more time to review the documents. To learn more and ask questions during the Public Comment window, webinars will be held on: · Thursday, 9 January 2020 at 01:00 UTC https://icann.zoom.us/j/935036343 [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> · Thursday, 9 January 2020 at 16:00 UTC https://icann.zoom.us/j/506858960 [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> · Monday, 14 January 2020 at 16:00 UTC https://icann.zoom.us/j/25710980 [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>7 [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> More details about how to join these webinars will be available in January. ICANN org staff is available to meet with individual community groups to answer questions and help increase understanding about the plans. Please email planning(a)icann.org<mailto:planning@icann.org> to request a meeting. DUE TODAY: NextGen@ICANN Community Consultation Executive: Sally Costerton, Senior Vice President, Global Stakeholder Engagement FOR: All Community Leaders INFORMATION SHARING The NextGen@ICANN program is currently undergoing a community consultation [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. One request from the preliminary feedback received to-date was for ICANN org to explore the feasibility of having community volunteer representatives from Supporting Organizations (SOs), Advisory Committees (ACs), Stakeholder Groups (SGs), and Constituencies (Cs) to nominate individuals for the following two roles: 1. NextGen Selection Committee members 2. NextGen mentors For the Selection Committee, a time commitment of approximately 20 hours over three weeks is required (for each application round). Selection Committee members will typically serve for two years (or six application rounds). Mentors are expected to devote approximately 24 hours to pre-ICANN Public Meeting preparation with their mentees, to offer advice, networking support, and regular check-ins on-site, and to complete evaluations following the ICANN Public Meeting. Based on previous estimates, mentors spend about two hours per week during the six-week preparation period in advance of the meeting and about two hours per day providing on-site support at the ICANN Public Meeting. Mentors will typically serve for one year (or three meetings). Is your group interested in nominating individuals for either of these roles? By Monday, 16 December 2019, please take the following poll [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> to help ICANN org can gauge the level of community interest. The findings of this poll will inform the proposed NextGen program approach that will be published for Public Comment. Note: You will not be asked to submit the names of potential volunteers for roles at this time. REMINDER: Opportunity for Strategic Outlook Trends Identification Sessions at ICANN67 Executive: Theresa Swinehart, Senior Vice President, Multistakeholder Strategy and Strategic Initiatives FOR: All Community Leaders INFORMATION SHARING ICANN org will hold Strategic Outlook Trends Identification sessions with the community at ICANN67. To prepare for that exercise, ICANN org will be seeking community feedback on possible formats and arrangements which will be sent through each community group’s leadership. The Strategic Outlook program [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> is a joint effort among ICANN org, the community, and ICANN Board to identify and track trends that relate to ICANN and its mission and to make sure that relating opportunities and challenges are incorporated into ICANN's current and future strategy. New trends or shifts in existing trends impacting the operating plans (five-year or annual), and/or budget, will be factored into the annual iteration of those plans as appropriate. Significant shifts could also result in adjustments to the strategic plan. REMINDER: FY21 SO/AC Additional Budget Request Process Executive: Xavier Calvez, Chief Financial Officer FOR: All Community Leaders INFORMATION SHARING The Fiscal Year 2021 (FY21) Supporting Organization and Advisory Committee (SO/AC) Additional Budget Request process has begun. This additional budget approval process is part of the overall ICANN annual budgeting process that is for the review of specific requests from the community that are not already included in the budget but serve to further the key objectives of the requesting community group. Your active participation and adherence to procedural guidelines is greatly appreciated. Information concerning the FY21 SO/AC Additional Budget Request process, including timeline and request template can be found on the finance community wiki [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. Additional Budget Requests are due Friday, 31 January 2020. Please email any questions that you may have to planning(a)icann.org<mailto:planning@icann.org>. We look forward to your continued engagement on the SO/AC Additional Budget Request process for FY21. REMINDER: ICANN Fellowship Program Mentors From: Sally Costerton, Senior Vice President, Global Stakeholder Engagement FOR: All Community Leaders INFORMATION SHARING ICANN's Supporting Organizations (SOs) and Advisory Committees (ACs) are invited to nominate [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> one individual each (total of seven) to serve as a mentor in the ICANN Fellowship Program. Mentors will serve a term that includes three consecutive ICANN Public Meetings, beginning with ICANN68. They will provide extensive pre-meeting preparation and on-site support for their assigned fellows, as well as complete a survey after each meeting. Mentors are expected to follow Fellowship Program guidelines to help ensure consistency in capacity development opportunities for fellows. They also play an important role to help fellows actively participate in ICANN's work. Mentors will receive travel funding support. Mentors cannot serve on the Fellowship Program Selection Committee [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> at the same time they are serving as mentors. For more information on the guidelines and expectations for mentors, please read about the program here [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. SOs/ACs should first select their respective Fellowship Program mentor by Friday, 31 January 2020, and notify fellowshipconsultation(a)icann.org. Individual self-nominations will not be considered. ICANN67 Planning REMINDER: ICANN67 Publication Support From: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING Design Deadline If you require design assistance for an ICANN67 publication, all text, images, layout, and publication type/size requirements (i.e. newsletter, 1-pager, tri-fold, etc.) are due Friday, 3 January 2020. Please ensure that all materials, new or updated, are evergreen. Translation Deadline If your ICANN67 publication requires translation, please provide the final material(s) by Monday, 27 January 2020. This ensures that there is enough time to translate the publication by the print deadline. If your materials require design assistance (outlined above), please note that the final materials will have to be complete, including the edit/approval process, by this deadline in order to be translated. Print-Only Deadline If you only need your ICANN67 publication printed (meaning your publication is ready to send directly to the printer and needs no translation or design/layout modifications), please provide the file along with the quantity you want printed and dimensions of the publication by Friday, 7 February 2020. Please work directly with your support staff to submit these requests to chantelle.doerksen(a)icann.org and liana.teo(a)icann.org. REMINDER: CROP Deadline for ICANN67 From: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING For eligible groups planning to use Community Regional Outreach Program (CROP) funds to conduct outreach during ICANN67, requests must be submitted no later than Friday, 17 January 2020. No exceptions will be made. When submitting a CROP travel request, please keep in mind the following: Trip requests must be approved by the respective community leadership team. For FY20, the trip request must be filled in by the CROP participant via the CROP workspace [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. In order to access it, applicants must first have an account; please let the CROP coordinator know if you need an account. All individuals requesting CROP funding must also review the CROP Guidelines [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> prior to submitting a request. Please contact crop-staff(a)icann.org with any questions. Public Comment Registration Directory Service (WHOIS2) Review Team Final Report [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Monday, 23 December 2019 Proposal for Future Root Zone KSK Rollover [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 31 January 2020 Volume 1, Issue 74 | Archive [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> | Next Issue: Thursday, 19 December 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

Motion on Confirmation of GNSO Representative to the Empowered Community Administration
by Pam Little 16 Dec '19

16 Dec '19

Dear Councilors, Please find the attached motion for consideration at our next Council meeting regarding the Confirmation of GNSO Representative to the Empowered Community Administration. Kind regards Pam Little

4 3