June 2021 - council - lists.icann.org

Confirmed Agenda with GAC And Notes
by Jeff Neuman June 10, 2021

June 10, 2021

Dear Councilors, Please find below the confirmed agenda for the GNSO/GAC meeting on 16 June 2021. I have also enclosed some notes on each of the topics from the GAC perspective so that we can all prepare our thoughts for the meeting. Agenda (confirmed) * Follow-up to ICANN 70: * EPDP/SSAD and Phase 2A; * Accuracy; * DNS Abuse; * CCT-Review and GNSO take on pending recommendations (especially those passed by the Board to GNSO) and potential common ask to Board re common tracking tool of all Review Team recommendations * SubPro and/or issues coming out of GNSO Council * AOB Notes from the GAC 1. EPDP/SSAD * Regarding the SSAD, the GAC has asked ICANN Org to provide an update on the status of the ODP. * Regarding the implementation of the policy recommendations adopted by the GNSO in Phase 1 of the EPDP, the GAC is interested in the resumption of implementation of the Privacy/Proxy Accreditation policy recommendation (PPSAI). This is consistent with GAC Advice in the ICANN64 Kobe Communiqué, and subsequent follow-up on that advice in the ICANN65 Marrakech and ICANN66 Montréal Communiqués. 1. Phase 2A GAC representatives in the EPDP Phase 2A have raised several process observations following the recent publication of the Initial Report: * Timeline constraints have not been helpful in supporting the EPDP's work * There were too many substantive changes at the end of the drafting process of the Initial Report and not enough time for the EPDP team to review the proposed edits. Brand new questions, and changes with short turnaround times before publication, as low as 24 hours 24h, should not be allowed. * A document management system should be adopted to avoid too many documents being created too frequently. The number of documents should be reduced and their access centralized. This is deemed to directly impact the effectiveness of the EPDP Team's work. 1. Accuracy Scoping Effort As I have expressed within the small team efforts, the GAC is concerned with the accuracy of domain name information as opposed to the definition of accuracy under GDRP or any other potential legislation. Their interest is in ensuring that the information provided by a registrant allows that registrant to actually be identified and contacted as envisaged under the respective agreements. In that context, the focus of further studies on this matter, if any, should concentrate on the accuracy of the domain name information. 1. DNS Abuse The GAC would welcome an update from the GNSO about what Community work it envisions to conduct on these issues in light of the recent SAC115 Report and SSR2 Review Team Recommendations. 1. CCT Review Recommendations in GNSO Review of the ICANN70 Communiqué While the GAC appreciated our feedback in the response to the GAC Communique from ICANN70, they would like to know from us how the items identified in the CCT Review Team report will actually be addressed (as expressed in the GAC Communique from ICANN700. In particular on the issue of the CCT Review and Subsequent Rounds of New gTLD, according to the GAC, our response only reiterated previous GNSO Council positions and did not address the substantive issues identified by the GAC's advice, in terms of the adoptions of (relevant) CCT Review Recommendations ahead of the next round of New gTLDs. The GAC has presented some questions for us which are below (verbatim) Question 1: Given decisions not to address certain relevant issues in the SubPro work, does the GNSO intend to opine on those Recommendations that might require PDP processes, especially given the duration of such ? Question 2: The GAC asked the Board in its ICANN 70 Communique for a "a tracking tool that identifies the status of each Recommendation in terms of who is taking it forward, how it will be implemented and when it is expected to be completed, particularly in regard to Recommendations attributed to the Organisation and the ICANN Community (in addition to the Board)." - would the GNSO Council agree on such a tool being made available by ICANN Org on the CCT Review recommendations, and possibly also other review team recommendations? Personal note from GNSO Liaison to the GAC: This tracking tool seems like a no brainer for us to support along with the GAC. Not just for the CCT-Review Team Recommendations, but for all Review Team Recommendations as it is impossible to track the hundreds of recommendations and where they are in terms of Board Adoption, implementation planning, implementation, etc. 1. SubPro As we know, the GAC has filed a public comment to the SubPro Final Outputs put out for comment by the Board: [Comments-gnso-gtld-subsequent-procedures-final-outputs-22apr21] GAC Comment: GNSO New gTLD Subsequent Procedures Final Outputs for ICANN Board Consideration<https://mm.icann.org/pipermail/comments-gnso-gtld-subsequent-procedures-fin…>] Do we have any questions about those comments. Please let me know if you have any questions or concerns or whether you would like for me to get additional information to help the Council prepare for the meeting. Sincerely, Jeff Neuman GNSO Liaison to the GAC [cid:image001.png@01D75DDB.7906F8C0] Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC p: +1.202.549.5079 E: jeff(a)jjnsolutions.com<mailto:jeff@jjnsolutions.com> http://jjnsolutions.com

1 0

Re: [council] [gnso-secs] Reminder: Expected Participation GNSO Council Interactive Working Session Monday 14 June 2021 14:30 - !6:00 CET.
by Nathalie Peregrine June 9, 2021

June 9, 2021

With correct agenda page, apologies! From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Reply to: Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Wednesday, 9 June 2021 at 23:32 To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [gnso-secs] Reminder: Expected Participation GNSO Council Interactive Working Session Monday 14 June 2021 14:30 - !6:00 CET. Dear councilors, The GNSO Council Working Session is taking place on Monday 14 June 2021 from 14:30 CET to 16:00 CET. There will be no presentation nor slide deck, this session is geared towards interaction with the community. The Final Agenda has been posted here<https://community.icann.org/display/gnsocouncilmeetings/GNSO+Council+Workin…>. Please share it with your SG/C members so they can come adequately prepared. Please note that for the first topic on the Status of Implementation of GNSO Policy Recommendations, ICANN Org GDS staff will be joining the session. In order for them to prepare accordingly, as highlighted in the agenda, please be so kind as to share your questions ahead of time on the Council mailing list. For enhanced interaction, we kindly suggest you activate your video on the call! Please ensure you have the latest Zoom version (information as to how to update Zoom can be found here [support.zoom.us]<https://urldefense.com/v3/__https:/support.zoom.us/hc/en-us/articles/201362…>). Thank you! Nathalie

2 1

FW: [Gnso-epdp-team] EPDP Phase 2A Chair Update to GNSO Council -- Initial Report
by philippe.fouquart＠orange.com June 9, 2021

June 9, 2021

Dear Councillors, Please see the EPDP P2A chair's update to Council regarding the Initial Report of the EPDP. In particular, you will note Keith's characterisation of where the team is in terms of identifying new consensus policy elements, what is expected from the public comment in this regard along with the five areas where specific inputs are sought as they relate to their chartered goals. The WG remains on track for a Final Report end of August. An update is scheduled for our call next week on this. You will find the public comment page & initial report here https://www.icann.org/public-comments/epdp-phase-2a-initial-report-2021-06-…. Regards, Philippe From: Gnso-epdp-team [mailto:gnso-epdp-team-bounces@icann.org] On Behalf Of Drazek, Keith via Gnso-epdp-team Sent: Tuesday, June 8, 2021 12:35 AM To: gnso-chairs(a)icann.org Cc: gnso-secs(a)icann.org; gnso-epdp-team(a)icann.org Subject: [Gnso-epdp-team] EPDP Phase 2A Chair Update to GNSO Council -- Initial Report Dear GNSO Council Leadership Team, In my capacity as Chair of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data (Phase 2A), I am pleased to report to the GNSO Council that the Phase 2A team has finalized its Initial Report for public comment. The Initial Report includes a status update on the deliberations of the EPDP 2A team and primarily poses questions around five key issues and possible recommendations for community feedback. The public comment period will run for 45 days from 03 June to 19 July 2021. The EPDP 2A team has not yet reached consensus on whether there should be new consensus policy elements, amendments to the existing Phase 1 recommendations, or if the existing policies are sufficient at this time. This is a key area of focus for the community during the public comment period and the EPDP 2A team looks forward to considering all inputs, and especially new information, as we work to develop policy recommendations in a Final Report. The five key areas where new community input is requested are: 1. As the report indicates, there are substantially different views on the question of whether changes are needed to the Phase 1 recommendation which allows for differentiation between legal and natural person data, but does not require it. Some are of the view that changes are warranted, while others believe that the Phase 1 recommendation does not require changes at this time. 1. The EPDP Team has noted there are a number of potential relevant developments such as NIS2, decisions by pertinent tribunals and data protection authorities, as well as the possible adoption of the Phase 2 recommendations on a Standardized System for Access and Disclosure (SSAD) that may require, or benefit from, a renewed consideration of the question of whether any further policy changes are necessary. The EPDP Phase 2A preliminary recommendation included in the Initial Report suggests that the Council should monitor these developments to decide if/when (re)consideration is warranted, while others have suggested that this is already the responsibility of the Council and as such, neither monitoring nor specific triggering points need to be specifically called out. Community input is sought on if/how this recommendation is necessary for future GNSO Council consideration of any new policy work. Further information from the Council on how this monitoring suggestion is helpful is also welcomed. 1. As a possible new requirement, the EPDP Team has discussed the introduction of a standardized data element to facilitate and harmonize practices for those Contracted Parties who do choose to differentiate between legal and natural person data, but some important questions remain and are called out in the Initial Report, as follows: * Should a standardized data element be available for a Contracted Party to use? If yes, why? If no, why not? Why is harmonization of practices beneficial or problematic? * If yes, what field or fields should be used and what possible values should be included, if different from the ones identified in the Initial Report (Registrant Legal Person - Yes/No/Unspecified)? * If such a standardized data element is available, MUST a Contracted Party who decides to differentiate use this standardized data element or should supporting this standardized data element remain optional for a Contracted Party that implements this differentiation? 1. The EPDP Team has developed guidance for Contracted Parties who choose to differentiate but there are a number of questions that are put out for community input: * Does this guidance as written provide sufficient information and resources to Registrars and Registry Operators who wish to differentiate? If not, what is missing and why? * Are there additional elements that should be included? * Are there legal and regulatory considerations not yet considered in this Initial Report, that may inform Registries and Registrars in deciding whether and how to differentiate, and if so, how? * If a Registrar or Registry Operator decides to differentiate, should this guidance become a requirement that can be enforced if not followed ("MUST, if Contracted Party decides to differentiate")? 1. The EPDP Team has put forward a preliminary recommendation that Contracted Parties who choose to publish a registrant- or registration-based email address in the publicly accessible RDDS should ensure appropriate safeguards for the data subject in line with relevant guidance on anonymization techniques provided by their Data Protection Authority(ies) and the appended legal guidance in this recommendation. The EPDP Team asks: * Does this guidance as written provide sufficient information and resources to Registrars and Registry Operators who wish to publish a registrant- or registration-based email address? * If not, what is missing and why? In summary, irrespective of whether consensus is ultimately reached on the above issues, the EPDP 2A Team will continue working during the public comment period to ensure we remain on track for publication of a Final Report by the end of August 2021. The EPDP 2A Team appreciates the ongoing support of the GNSO Council as we conduct this important policy work, and we very much look forward to receiving, reviewing, and incorporating the community's feedback. Please advise if the GNSO Council has any follow-up questions for the EPDP Phase 2A team. Sincerely, Keith Drazek _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

1 0

EPDP-P2A // 03 Jun 2021 Milestone Project Package
by Berry Cobb June 9, 2021

June 9, 2021

Dear Councilors, On behalf of the EPDP-P2A leadership team, please find attached the EPDP-P2A’s 03 Jun 2021 milestone project package. 1. Page 01 – Summary timeline 2. Page 02 – Project Sitrep – an extract from the Council’s Project List 3. Page 03 – Group roster 4. Page 04 – Group attendance for plenary and legal committee 5. Page 05 – Work and activity metrics 6. Page 06 – Project Plan, Gannt chart 7. Pages 07-08 – Work plan & Action items for the period Please let us know if you have any questions. Thank you B Berry Cobb GNSO Policy Consultant Principal | BAC in Black Consulting<http://bacinblack.com/> Mob: +1 (720) 839-5735

1 0

RPM IGO CR WT May 2021 Project Package
by policy＠bacinblack.com June 9, 2021

June 9, 2021

Dear GNSO Council, On behalf of the IGO WT leadership team, please find attached the IGO WT's 31 May 2021 project package. 1. Page 01 - Summary timeline 2. Page 02 - Project Sitrep - an extract from the Council's Project List 3. Page 03 - Group roster 4. Page 04 - Group attendance for plenary 5. Page 05 - Work and activity metrics 6. Page 06 - Project Plan, Gannt chart 7. Page 07 - Work plan & Action items for the period Please let us know if you have any questions. Thank you B Berry Cobb GNSO Policy Consultant Principal | <http://bacinblack.com/> BAC in Black Consulting Mob: +1 (720) 839-5735 <https://twitter.com/berrycobb> <https://www.linkedin.com/in/berrycobb/>

2 1

GNSO Council Program Suite - 16 Jun 2021
by policy＠bacinblack.com June 8, 2021

June 8, 2021

Dear all, Please find attached links to the latest version of the GNSO Council's Program Suite for the meeting on 16 Jun 2021. Agenda: * https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+GNSO+ Council+Agenda+16+June+2021 Links to the Program Suite: * Program/Project Management Framework (PPMF): https://community.icann.org/x/0YvzC * Program Management Tool (PMT): https://community.icann.org/x/04vzC * Action/Decision Radar (ADR): https://community.icann.org/x/14vzC * Project List (PL): https://community.icann.org/x/1YvzC * Action Items (AIs): https://community.icann.org/x/RgZlAg * Council Small Teams (CSTs): https://community.icann.org/x/kwANCQ Key Project Changes for this Period: * ICANN71 (14-17 June 2021) * Initiation of the GNSO Framework for Continuous Improvement * EPDP-P2A Initial Report published for Public Comment <https://www.icann.org/public-comments/epdp-phase-2a-initial-report-2021-06- 03-en> * Continued discussions on Registration Data Accuracy Scoping Team * Continued discussions on IDNs Operational Track * Continued discussions on EPDP-P1 IRT Wave 1.5 relaunch for IRTs of PPSAI + T&T Key Project Activities for July 2021: * ICANN71 GNSO Council response to GAC Communique * Continued discussions on Registration Data Accuracy Scoping Team * EPDP-IDN 1st meeting expected * Confirmation of Transfer Policy Review PDP Work Plan * Close of Public Comment on EPDP-P2A * RPM IGO Curative Rights Work Track expected to deliver Initial Report for Public Comment * Continued discussions on EPDP-P1 IRT Wave 1.5 relaunch for IRTs of PPSAI + T&T Thank you. B Berry Cobb GNSO Policy Consultant Principal | <http://bacinblack.com/> BAC in Black Consulting Mob: +1 (720) 839-5735 <https://twitter.com/berrycobb> <https://www.linkedin.com/in/berrycobb/>

2 2

Reminder | Take the ICANN Public Meeting Survey!
by Terri Agnew June 7, 2021

June 7, 2021

**Reminder to take if you haven’t already. *** ICANN Public Meeting Survey: Community Interest in Face-to-Face Meetings ICANN org is now conducting a survey to determine individual comfort and tolerance for gatherings amongst ICANN Meeting participants and investigate the possibility of organizing ICANN72 as a hybrid meeting with virtual and in-person attendance in Seattle. We want to hear what you think. Please click below to participate in the survey. https://www.surveymonkey.com/r/7MBJPFY Thank you. Kind regards, Terri

1 0

FW: [Ext] Monday, 7 June 2021
by Julie Bisland June 7, 2021

June 7, 2021

FYI-- From: ICANN Community Leadership Digest <david.olive(a)icann.org> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Monday, June 7, 2021 at 10:00 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] Monday, 7 June 2021 [https://r20.rs6.net/on.jsp?ca=0e76ee4b-365a-4d8e-b927-3d02ba255cb4&a=112202…] Monday, 7 June 2021 ICANN Community Leadership Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] The ICANN org Policy Development Support function publishes this twice-weekly digest to help ICANN community leaders track requests and follow updates. Table of Contents ICANN71 Resources · Registration · Schedule · Participation Guides · Virtual Backgrounds · Policy Outlook Report · GNSO Briefing Information Sharing · NEW: ICANN Board Chair’s Blog: Preview of June Workshop · REMINDER: Call for Expressions of Interest: Chair of the EPDP on IDNs · REMINDER: Participate or Observe: EPDP on IDNs · REMINDER: Call for Expressions of Interest: ICANN 2022 NomCom Chair and Chair-Elect Public Comment · CLOSES TOMORROW: Maximal Starting Repertoire Version 5 (MSR-5) · Draft North America Engagement Plan FY21-25 · NEW: Initial Report of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data Team – Phase 2A ICANN71 Resources Registration [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001CYtvRUkEeOrhIJIT…> Participation Guides [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001CYtvRUkEeOrhIJIT…> Policy Outlook Report [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001CYtvRUkEeOrhIJIT…> Schedule [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001CYtvRUkEeOrhIJIT…> Virtual Backgrounds [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001CYtvRUkEeOrhIJIT…> GNSO Briefing [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001CYtvRUkEeOrhIJIT…> Information Sharing NEW: ICANN Board Chair’s Blog: Preview of June Workshop As part of the ICANN Board's commitment to transparency and accountability, I would like to share with you our focus for our upcoming workshop. It will take place from 10 to 12 June in between the ICANN71 Prep Week and the ICANN71 Virtual Policy Forum. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001CYtvRUkEeOrhIJIT…> REMINDER: Call for Expressions of Interest: Chair of the EPDP on IDNs The Generic Names Supporting Organization (GNSO) Council announced that it is seeking Expressions of Interest for a chair of the Expedited Policy Development Process (EPDP) team that will address issues related to Internationalized Domain Names (IDNs). Candidates interested in serving in this role should review the Expression of Interest document [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001CYtvRUkEeOrhIJIT…> before submission. The document details the role, required skills and experience, and the selection process. The deadline to submit an Expression of Interest is Friday, 25 June 2021 at 23:59 UTC. All submissions should be sent to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001CYtvRUkEeOrhIJIT…> REMINDER: Participate or Observe: EPDP on IDNs The Generic Names Supporting Organization (GNSO) Expedited Policy Development Process (EPDP) Team on Internationalized Domain Names (IDNs) welcomes anyone to join as a participant or an observer. Please contact gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> to sign up as a participant or an observer. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001CYtvRUkEeOrhIJIT…> REMINDER: Call for Expressions of Interest: ICANN 2022 NomCom Chair and Chair-Elect ICANN is seeking Expressions of Interest for the Chair and Chair-Elect of the 2022 Nominating Committee (NomCom). Expressions of Interest, which will be maintained as confidential, should be sent to nomcomchair2022(a)icann.org [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001CYtvRUkEeOrhIJIT…> no later than 23 June 2021. A suggested form for submitting an Expression of Interest is available here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001CYtvRUkEeOrhIJIT…>. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001CYtvRUkEeOrhIJIT…> Public Comment CLOSES TOMORROW: Maximal Starting Repertoire Version 5 (MSR-5) [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001CYtvRUkEeOrhIJIT…> Close Date: Tuesday, 8 June 2021 Draft North America Engagement Plan FY21-25 [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001CYtvRUkEeOrhIJIT…> Close Date: Friday, 2 July 2021 NEW: Initial Report of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data Team – Phase 2A [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001CYtvRUkEeOrhIJIT…> Close Date: Monday, 19 July 2021 Volume 3, Issue 42 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001CYtvRUkEeOrhIJIT…> | Next Issue: Thursday, 10 June 2021

1 0

Proposed Agenda GNSO Council Meeting - 16 June 2021 at 10:30 UTC
by Nathalie Peregrine June 6, 2021

June 6, 2021

Dear all, Please find below the final proposed agenda for the GNSO Council Meeting on 16 June 2021 at 10:30 UTC. Draft GNSO Council Agenda 16 June 2021 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/1YG1CQ This agenda was established according to the GNSO Operating Procedures<https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced…> v3.5, updated on 24 October 2019 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 10:30 UTC Coordinated Universal Time: 10:30 UTC: https://tinyurl.com/4wy66z7y 03:30 Los Angeles; 06:30 Washington; 11:30 London; 12:30 Paris; 13:30 Moscow; 20:30 Melbourne GNSO Council Meeting Remote Participation: 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/2021/minutes/minutes-gnso…> of the GNSO Council meeting on 22 April 2021 were posted on 06 May 2021. Minutes<https://gnso.icann.org/sites/default/files/policy/2021/minutes/minutes-gnso…> of the GNSO Council meeting on 20 May 2021 were posted on 03 June 2021. Item 2: Opening Remarks / Review of Projects & Action List (10 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 (0 minutes) * None Item 4: COUNCIL VOTE - Initiation of the GNSO Framework for Continuous Improvement Pilot Project (15 minutes) The GNSO Council has sought an approach to address work that focuses on GNSO structural, procedural and process improvement related work. Council leadership consulted with Stakeholder Group and Constituency Chairs on how to handle a number of items in the Council’s Action Decision Radar in the 0-1 month timeframe. Council leadership proposed the creation of a GNSO Framework for Continuous Improvement, to help provide structure to manage the numerous non-PDP related efforts. Based on initial feedback from Councilors and other GNSO stakeholders, a much more detailed draft document was prepared and shared<https://mm.icann.org/pipermail/council/2021-March/024508.html> on 2 March 2021, which provides additional information about the structure and potential work assignments. Input was sought from the Council and SG/C Chairs. Taking into account input, an updated proposal was circulated to the Council and SG/C Chairs on 26 May 2021 (see https://mm.icann.org/pipermail/council/2021-May/024730.html) This updated proposal<https://mm.icann.org/pipermail/council/attachments/20210526/8995c911/GNSOFr…> includes a proposed pilot (see section 4 of the proposal) which allows for a more limited roll out of the Framework from which lessons can be drawn and possible updates can be made, should the Council and GNSO community decide that it is worthwhile to continue. As a result of initiating the pilot, the items that are expected to be addressed as part of the Framework (including WS2, Policy & Implementation, PDP 3.0, Empowered Community, ATRT3, GNSO Review) will be moved to a section in the ADR with no timeframe associated with them, as the timing will be determined as a result of the pilot. However, this does not prevent the Council from determining that one or more of these items needs to be addressed in a different manner before the pilot concludes, for example, as a result of external factors or changes in the dependencies that were identified (see section 5<https://mm.icann.org/pipermail/council/attachments/20210526/8995c911/GNSOFr…>). Here, the Council will vote to initiate the GNSO Framework for Continuous Improvement as a pilot project, which also provides a near term path for items captured in the framework that also reside on the Council’s Action Decision Radar. 4.1 Presentation of motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+16+June+2021> (Tatiana Tropina, Council vice-chair) 4.2 Council discussion 4.3 Council vote (Voting Threshold: simple majority vote of each House) Item 5: COUNCIL DISCUSSION - Potential Next Steps for the Internationalized Domain Names (IDN) Operational Track (20 minutes) The IDN Implementation Guidelines are mainly directed at gTLD registries that offer IDN registrations, though there are contractual requirements for both registries (see Specification 6, 1.4 here https://www.icann.org/resources/pages/registries/registries-agreements-en) and registrars (see Additional Registrar Operation Specification, section 3 here: https://www.icann.org/resources/pages/approved-with-specs-2013-09-17-en) The contractual provisions in both agreements note that the Guidelines, “may be amended, modified, or superseded from time to time.” To develop v. 4.0 of the guidelines, similar to past revision processes, a community expert working group was convened in 2015, which was comprised of members from the ALAC, ccNSO, GNSO, and SSAC. The working group produced two draft versions for public comment and developed a Final Proposed Draft v. 4.0<https://www.icann.org/news/announcement-2018-05-10-en> in May of 2018 . The ICANN Board anticipated adopting the IDN Guidelines v. 4.0 as part of its consent agenda for the 3 May 2019 meeting, but the GNSO Council requested<https://gnso.icann.org/sites/default/files/file/field-file-attach/drazek-to…> that the vote be deferred, due in part to concerns around the process, as well as specific requirements within the guidelines (e.g.,“same entity” requirement on second level registrations, which are in both the guidelines and the Variant TLD Recommendations ). The ICANN Board agreed<https://www.icann.org/en/system/files/correspondence/chalaby-to-drazek-04ju…> to the deferral, allowing the GNSO Council additional time to consider the matter. In August of 2020, the Council approved as part of its consent agenda that the Contracted Parties House (CPH) should work with ICANN org to propose potential changes to IDN Guidelines. It was later determined that ICANN org was not the proper party to negotiate amendments to the IDN Guidelines 4.0. The CPH has considered the best approach for the guidelines, taking into account the overlap in subject matter between the guidelines and the IDNs EPDP that the Council initiated in May of 2021. The Councilors from the CPH provided a letter [INSERT LINK WHEN AVAILABLE] to Council on 4 June 2021 suggesting a path forward, as well as rationale for why the Council should follow that path. In addition, a draft letter [INSERT LINK WHEN AVAILABLE] from the Council to the Board was shared, that could be used as a starting point if the Council agrees to the suggested path forward. Here, the Council will receive a briefing from the CPH Councilors on the proposed path forward for addressing the IDN Guidelines 4.0. 5.1 - Introduction of the topic (Kurt Pritz) 5.2 – Council discussion 5.3 – Next steps Item 6: COUNCIL DISCUSSION - Accuracy Scoping Team (5 minutes) During its October 2020 meeting, the GNSO Council confirmed its intent to launch a scoping team on the topic of accuracy based on a proposal from the previous Council leadership team (see here <https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-2-pr…> for the proposal). On 4 November 2020, the GNSO Council wrote<https://www.icann.org/en/system/files/correspondence/fouquart-to-swinehart-…> to ICANN org, requesting the preparation of a briefing document outlining both the existing accuracy requirements and programs as well as the impact that GDPR has had on implementing and enforcing the identified requirements and programs. This briefing is intended to inform an accuracy scoping team that the GNSO Council envisioned initiating, which would be tasked with furthering the community’s understanding of the issue and assist in scoping and defining the issue (see here<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-2-pr…>). On 10 December 2020, ICANN org responded<https://www.icann.org/en/system/files/correspondence/swinehart-to-fouquart-…> to confirm its understanding of the request and to commit to delivering that briefing by 26 February 2021. ICANN org timely delivered the briefing<https://www.icann.org/en/system/files/correspondence/swinehart-to-fouquart-…>. In addition to the briefing providing an overview of accuracy requirements and programs and the impact of GDPR on these, ICANN org also included a suggestion that a study to measure accuracy of registration data might be beneficial. In parallel to the request for the briefing, ICANN SO/AC/SG/Cs were requested to start thinking about whether their groups would be interested to participate in a scoping team once created. To date, the BC, ISPCP, RySG, IPC and GAC have expressed an interest and identified potential volunteers with relevant knowledge and expertise. The Council discussed this briefing and potential next steps during its Extraordinary Meeting on 08 April 2021. Following the meeting, Council leadership, with the support of the GNSO Support Staff, worked together to develop a set of proposed next steps<https://mm.icann.org/pipermail/council/2021-April/024662.html> for dealing with the topic of accuracy, which was shared on 23 April 2021. Feedback was sought from Councilors by 07 May 2021 and the topic was discussed again during the Council’s May meeting. The Council agreed to convene a small team to refine the proposed next steps, particularly around clarifying the remit of the eventual scoping team. Here, the Council will receive an update from that small team on progress made. 6.1 – Introduction of topic (Pam Little, Council vice-chair) 6.2 – Council discussion 6.3 – Next steps Item 7: COUNCIL DISCUSSION - Interactions With the GAC (20 minutes) In their respective roles, the Generic Names Supporting Organization (GNSO) responsible for developing gTLD policy and the Governmental Advisory Committee (GAC) providing input to the ICANN Board on issues of public policy, the two groups determined that there was an opportunity to improve coordination and cooperation. In recognition of that opportunity, the GAC and GNSO jointly established a consultation group to explore ways for the GAC to engage early in the GNSO Policy Development Processes (PDP) and to improve overall cooperation between the two bodies, commencing that work in December 2013. That group delivered its Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/2016-12/g…> on 10 October 2016 and its recommendations have since been integrated into the processes of both of the groups (e.g., early engagement, GNSO liaison to the GAC). Beyond these specific improvements, the GNSO and GAC engage on a periodic basis, at every ICANN meeting. As the former GNSO Council liaison to the GAC indicated in his annual report<https://mm.icann.org/pipermail/council/2020-October/024148.html> from 2020, it may be timely to evaluate the effectiveness of the recommendations as well as the changed dynamic in the way that GNSO and the GAC interact, as well as the way the GAC engages in GNSO processes. For instance, the GAC now participates directly in PDPs and in some limited instances, PDP leaders have engaged directly with the GAC. Does this change in engagement impact the need or the nature of the role of the GNSO liaison to the GAC? Additionally, how can the bilateral meetings between the GNSO and GAC be made more productive? The former liaison recommended that the incoming liaison be allowed some time to form an informed view of what works, what does not work, and what the challenges are (to be covered under 7.2). Here, the Council will receive an update from the current GNSO liaison to the GAC and reflect and discuss ways in which the interactions with the GAC work well or could be improved. 7.1 – Introduction of topic (Council leadership) 7.2 - Update and input from the GNSO Council liaison to the GAC 7.3 – Council discussion 7.4 – Next steps Item 8: COUNCIL UPDATE - Status Update Regarding EPDP Phase 2A (5 minutes) On 21 October 2020, the GNSO Council approved the initiation<https://gnso.icann.org/en/council/resolutions/2020#202010> of EPDP Phase 2A, to examine the topics of legal/natural and feasibility of unique contacts. In doing so, the Council required that: "[a]t the latest 3 months after reconvening, the Chair of the EPDP Team and GNSO Council Liaison to the EPDP will report back to the GNSO Council on the status of deliberations. Based on this report, which is expected to include an update on progress made and the expected likelihood of consensus recommendations, the GNSO Council will decide on next steps, which could include providing additional time for the EPDP to finalize its recommendations or termination of the EPDP if it is clear that no progress is being made or consensus is unlikely).” During the March Council meeting, the Chair of the EPDP Team and GNSO Council Liaison to the EPDP shared a presentation<https://community.icann.org/download/attachments/155192465/EPDP%20Phase%202…> and provided an update to the Council. The Council agreed that more time should be afforded to continue to make progress. The EPDP Team has since received responses from Bird & Bird to the EPDP Team’s Legal Committee’s questions and considered that feedback in progressing its work. The EPDP Team published its Initial Report for public comment<https://www.icann.org/public-comments/epdp-phase-2a-initial-report-2021-06-…> on 3 June 2021, which includes preliminary recommendations as well as questions for community input. Here, the GNSO Council Liaison to the EPDP will provide a brief update on the EPDP Team’s progress. 8.1 – Introduction of topic (Philippe Fouquart, GNSO Council liaison) 8.2 – Council discussion 8.3 – Next steps Item 9: COUNCIL DISCUSSION - EPDP Phase 1 Rec 27 (Wave 1.5) (10 minutes) Recommendation 27 from the EPDP Phase 1 Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-gtld…>, “... recommends that as part of the implementation of these policy recommendations, updates are made to the following existing policies / procedures, and any others that may have been omitted, to ensure consistency with these policy recommendations as, for example, a number of these refer to administrative and/or technical contact which will no longer be required data elements.” In support of this recommendation, ICANN org prepared the Wave 1 report, an updated version of which was shared with the Council on 19 February 2020. ICANN org has performed additional analysis for recommendation 27, resulting in the Wave 1.5 Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/draft-epd…> that focuses on Privacy and Proxy Services Accreditation Issues (PPSAI) and Translation and Transliteration of Contact Information (T/T) policy recommendations, for which implementation has been started but not completed. For the Wave 1 Report, the staff support team conducted a first analysis of the report, identifying possible next steps for Council consideration that the Council subsequently reviewed to determine next steps. After discussing during the Council’s Extraordinary Meeting in April of 2020, the Council agreed to seek input from ICANN’s Global Domains Division (GDS) staff to determine the estimated level of effort to complete the implementation of the PPSAI IRT and the interest and availability to reconvene the IRT. Here, the Council will discuss the input from GDS staff to help determine next steps. 9.1 – Introduction of topic (Council Leadership) 9.2 – Council discussion 9.3 – Next steps Item 10: ANY OTHER BUSINESS (15 minutes) 10.1 - Review of topics to discuss with the ICANN Board 10.2 - Open Microphone _______________________________ 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 12:30 UTC Local time between November and March Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 03:30 San José, Costa Rica (CST) UTC-6 04:30 New York/Washington DC, USA (EDT) UTC-4 06:30 Buenos Aires, Argentina (ART) UTC-3 07:30 Rio de Janeiro, Brazil (BRST) UTC-3 07:30 London, United Kingdom (GMT) UTC+1 11:30 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 11:30 Paris, France (CEST) UTC+2 12:30 Moscow, Russia (MST) UTC+3 13:30 Singapore (SGT) UTC+8 18:30 Melbourne, Australia (AEDT) UTC+11 20:30 ---------------------------------------------------------------------------- DST starts/ends on Sunday 31 October 2021, 2:00 or 3:00 local time (with exceptions) for EU countries and on Sunday 7 November 2021 for the US. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and https://tinyurl.com/4wy66z7y

1 0

Deadline today: Document and Motion deadline Sunday, 06 June 2021 at 23:59 UTC for GNSO Council Meeting 16 June 2021 at 10:30 UTC
by Nathalie Peregrine June 6, 2021

June 6, 2021

Dear all, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Sunday, 06 June 2021 at 23:59 UTC) of the GNSO Council Meeting on Wednesday,16 June 2021 at 10:30 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/2YG1CQ Thank you. Nathalie _______________________________________________ liaison6c mailing list liaison6c(a)gnso.icann.org https://mm.icann.org/mailman/listinfo/liaison6c _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

1 0