- GNSO-Accuracy-ST - lists.icann.org

Council resolution on Registration Data Accuracy Scoping Team Recommendations #1 and #2 – extending deferral of consideration by six months
by Terri Agnew July 26, 2023

July 26, 2023

Dear All, For your information, please find below the resolution that was adopted by the GNSO Council on Thursday, 20 July in relation to the Scoping Team’s recommendations. Please pay specific attention to resolved clauses #1-3, which confirm the Scoping Team’s recommendation to pause work on the proposals that require access to registration data and defer consideration of recommendations #1 (registrar survey) and #2 (registrar audit) “until such time the DPA negotiations between ICANN org and Contracted Parties have completed and there is feedback from ICANN org on if/how it anticipates the requesting and processing of registration data will be undertaken in the context of measuring accuracy, or for six months, whichever is the shorter”. Furthermore, once those conditions are met, the Council will review the Scoping Team’s formation and instructions to make sure these are still fit for purpose. As a result, we will not be scheduling any meetings or further work for now, but we will keep you posted when there are updates in relation to the conditions identified in the resolution. Best regards, Terri 20230720-1 CONSENT AGENDA Data Accuracy Scoping Team Recommendations #1 and #2 – extending deferral of consideration by six months Submitted by Greg DiBiase Seconded by Paul McGrady Whereas, The GNSO Council <https://gnso.icann.org/en/council/resolutions/2020-current#20221117-4> resolved<https://gnso.icann.org/en/council/resolutions/2020-current#20221117-4> on 17 November 2022 to defer consideration of recommendations #1 and #2 of the Registration Data Accuracy Scoping Team <https://gnso.icann.org/sites/default/files/policy/2022/correspondence/palag…> write up<https://gnso.icann.org/sites/default/files/policy/2022/correspondence/palag…> until such time the Data Processing Agreement (DPA) negotiations between ICANN org and Contracted Parties have completed and there is feedback from ICANN org on if/how it anticipates the requesting and processing of registration data will be undertaken in the context of measuring accuracy, or for six months, whichever is the shorter; 1. The GNSO Council <https://gnso.icann.org/sites/default/files/policy/2022/correspondence/gnso-…> wrote<https://gnso.icann.org/sites/default/files/policy/2022/correspondence/gnso-…> to ICANN org to obtain this feedback and received a <https://gnso.icann.org/sites/default/files/policy/2023/correspondence/gutte…> response<https://gnso.icann.org/sites/default/files/policy/2023/correspondence/gutte…> providing a status update on 14 March 2023 which was also presented during its April 2023 meeting; 2. ICANN org’s work on the scenarios that have been identified to review the accuracy of registration data and the data protection questions that arise from these scenarios is still ongoing; 3. Negotiations between ICANN org and Contracted Parties on a DPA have not completed yet. Resolved, 1. The GNSO Council extends the deferral of consideration of recommendations #1 and #2 of the Registration Data Accuracy Scoping Team <https://gnso.icann.org/sites/default/files/policy/2022/correspondence/palag…> write up<https://gnso.icann.org/sites/default/files/policy/2022/correspondence/palag…> for another six months. 2. The GNSO Council commits to considering the Scoping Team recommendations at an earlier date if the DPA negotiations have been completed before six months have passed and/or there is feedback from ICANN org if/how it anticipates the requesting and processing of registration data will be undertaken in the context of measuring accuracy. Vote results<https://gnso.icann.org/sites/default/files/policy/2023/vote-result/gnso-cou…>

1 0

FW: [council] FW: [Ext] Registration Accuracy Data Scoping Team Request [ ref:_00D1aY7OU._5001P1VAdzl:ref ]
by Brian Gutterman March 21, 2023

March 21, 2023

Dear All, FYI – Please see attached the response letter from ICANN org to the GNSO Council in response to the 1 December 2022<https://www.icann.org/en/system/files/correspondence/ducos-to-gutterman-01d…> letter requesting updates from ICANN org on outstanding issues related to registration data accuracy and the pending work of our group, the Accuracy Scoping Team. Best, Brian From: council <council-bounces(a)gnso.icann.org> on behalf of Nathalie Peregrine via council <council(a)gnso.icann.org> Reply to: Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Wednesday, 15 March 2023 at 08:58 To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [council] FW: [Ext] Registration Accuracy Data Scoping Team Request [ ref:_00D1aY7OU._5001P1VAdzl:ref ] Dear councilors, Please find attached the correspondence from ICANN org to Sebastien in response to his letter dated 1 December 2022 requesting updates from ICANN org on outstanding issues related to registration data accuracy and the pending work of the Registration Data Accuracy Scoping Team. This will be posted shortly on the GNSO Correspondence page. Thank you! Nathalie From: Correspondence <correspondence(a)icann.org> Date: Tuesday, 14 March 2023 at 17:01 To: "Sebastien(a)registry.godaddy" <Sebastien(a)registry.godaddy> Cc: Brian Gutterman <brian.gutterman(a)icann.org>, Amy Bivins <amy.bivins(a)icann.org>, Nathalie Peregrine <nathalie.peregrine(a)icann.org> Subject: [Ext] Registration Accuracy Data Scoping Team Request [ ref:_00D1aY7OU._5001P1VAdzl:ref ] [Image removed by sender.] Dear Sebastien Ducos, Please find attached a letter from Brian Gutterman at ICANN. This letter will be posted shortly to the ICANN Correspondence page (https://www.icann.org/resources/pages/correspondence) Please submit any questions you may have about this message to correspondence(a)icann.org<mailto:correspondence@icann.org>. Best Regards, Michael Kovach The Correspondence Team Internet Corporation for Assigned Names and Numbers (ICANN) correspondence(a)icann.org www.icann.org ref:_00D1aY7OU._5001P1VAdzl:ref [Image removed by sender.]

2 2

FYI - New Data Accuracy Data Points
by michael palage.com Jan. 31, 2023

Jan. 31, 2023

Hello Accuracy Scoping Team Members, While the Accuracy Scoping Team is on hiatus, I thought I would share a couple of interesting data points that the group may find of interest. At the top of the hour, DomainCrawler will be doing a webinar on KYC Practices for Registrars and Registries. For those interested here is a link to the sign-up page, see https://domaincrawler.clickmeeting.com/kyc-practices-for-registries-and-reg… The EC has also issued a call for a study on domain name registration data https://digital-strategy.ec.europa.eu/en/funding/call-tender-study-domain-n… Hopefully, when the Scoping Team is re-engaged we will have some additional data to consider. Best regards, Michael

1 0

Council resolution on Registration Data Accuracy Scoping Team's write up and recommendations
by Marika Konings Nov. 17, 2022

Nov. 17, 2022

Dear All, For your information, please find below the resolution that was adopted by the GNSO Council earlier today in relation to the Scoping Team’s recommendations. Please pay specific attention to resolved clauses #1-3 which in summary confirm the Scoping Team’s recommendation to pause work on the proposals that require access to registration data and defer consideration of recommendations #1 (registrar survey) and #2 (registrar audit) “until such time the DPA negotiations between ICANN org and Contracted Parties have completed and there is feedback from ICANN org on if/how it anticipates the requesting and processing of registration data will be undertaken in the context of measuring accuracy, or for six months, whichever is the shorter”. Furthermore, once those conditions are met, the Council will review the Scoping Team’s formation and instructions to make sure these are still fit for purpose. As a result, we will not be scheduling any meetings or further work for now, but we will keep you posted when there are updates in relation to the conditions identified in the resolution. Best regards, Caitlin, Berry and Marika 20221117-4 Motion - Registration Data Accuracy Scoping Team write up for assignments #1 and #2 recommendations Submitted by: Greg DiBiase Seconded by: Thomas Rickert WHEREAS, 1. The GNSO Council adopted a proposal [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> on 21 October 2020 which recommended that a Scoping Team addresses the effects of GDPR on Registration Data accuracy requirements and the Whois Accuracy Reporting System (ARS), stating, "a scoping team would be tasked to, 'facilitate community understanding of the issue; assist in scoping and defining the issue; gather support for the request of an Issue Report, and/or; serve as a means to gather additional data and/or information before a request [for an Issue Report] is submitted'. 2. On 4 November 2020, GNSO SG/Cs as well as ICANN SO/ACs were informed of the Council's intent to form a Registration Data Accuracy Scoping Team and were requested to indicate if they would be interested in sending representatives to this effort. 3. At the same time, the GNSO Council also requested that ICANN org develop a briefing document that outlines both (i) existing accuracy requirements and programs and (ii) the corresponding impact that GDPR has had on implementing / enforcing these requirements and programs. This briefing paper<https://www.icann.org/en/system/files/correspondence/swinehart-to-fouquart-…>was delivered to the Council in February 2021. 4. Following the Council discussion of the ICANN org briefing paper in April 2021, Council leadership put together a first proposal outlining possible instructions to the Registration Data Accuracy Scoping Team. 5. As a result of input that was provided by different Council members on the first proposal, the Council decided at its May 2021 meeting to form a small team to further review and revise the instructions to the scoping team. 6. The small team, consisting of one Council member from each GNSO Stakeholder Group or Constituency, two NomCom appointed Council members and the GNSO Liaison to the GAC (as an observer), submitted its recommendations in relation to the formation as well as the instructions for the Registration Data Accuracy Scoping Team to the Council on9 July 2021<https://mm.icann.org/pipermail/council/2021-July/024851.html> for Council's consideration. 7. The GNSO Council confirmed the formation of the Registration Data Accuracy Scoping Team and its instructions during its meeting on 22 July 2021. 8. The GNSO Council confirmed the Chair for the Scoping Team during its meeting on 23 September 2021. 9. The Scoping Team started its deliberations on 5 October 2021 focusing its efforts on assignments #1 (enforcement and reporting) and #2 (measurement of accuracy). 10. The Scoping Team delivered its write up [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> for assignments #1 and #2 to the GNSO Council on 5 September 2022. 11. The GNSO Council was briefed on the write up and its recommendations during the Council meeting [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/rec/share/BYAKGwD2U4PMV6Rs…> at ICANN75 and continued its deliberations during its October Council meeting [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/rec/share/y26ROY5NZSLyfZj1…>. RESOLVED, 1. The GNSO Council adopts recommendation #3 of the write up which recommends 1) pausing the work in relation to proposals that require access to registration data, 2) encouraging ICANN org to proceed with their outreach to the EDPB as well as the Data Protection Impact Assessment in connection with the scenario(s) in which the request and processing of registration data takes place as a matter of urgency, and 3) requests that ICANN org and Contracted Parties finalize the negotiations on the Data Processing Agreement (DPA) as soon as practicable as the absence of a completed DPA may act as a roadblock for policy work before Council. 2. The GNSO Council defers consideration of recommendations #1 and #2 until such time the DPA negotiations between ICANN org and Contracted Parties have completed and there is feedback from ICANN org on if/how it anticipates the requesting and processing of registration data will be undertaken in the context of measuring accuracy, or for six months, whichever is the shorter. 3. Once the DPA negotiations are completed and the feedback referred to at paragraph 2 is received from ICANN org, the GNSO Council will review the formation and instructions<https://community.icann.org/x/QoFaCg> to the Scoping Team to ensure these are still fit for purpose and request the Scoping Team to further consider potential proposals that require access to registration data as well as how these impact the existing recommendations #1 and #2 (e.g. should these still be considered by the GNSO Council for adoption, or in the context of proposals that require access to registration data these may no longer be relevant or a priority?). If, after 6 months from this resolution, the DPA negotiations are not completed and/or the required feedback referred to at paragraph 2 has not been provided by ICANN org, Council will discuss and determine whether or not to continue deferring the consideration of recommendations #1 and #2. 4. Taking into account the delay with which the write up was delivered, as well as some of the challenges that were shared with the Scoping Team’s Chair during his briefing to the Council, Council leadership will reach out informally to Scoping Team members to better understand the issues encountered to help inform the Council’s review of the formation and instructions. 5. Council leadership is requested to send a communication to ICANN org in relation to recommendation #3 (as well as Contracted Parties in relation to the DPA) as well as communicate the Council’s decision to non-GNSO groups participating in this effort (ALAC, GAC and SSAC) as well as the Scoping Team. 6. The GNSO Council thanks Michael Palage, outgoing Chair, and Olga Cavalli, outgoing Council liaison, for their efforts. As part of its review of the formation and instructions to the Scoping Team, the Council will consider next steps for finding new leadership for this effort. Vote results [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…>

1 0

ICANN75 Policy Outcomes Report is now available for Download
by Terri Agnew Oct. 20, 2022

Oct. 20, 2022

Dear all, As announced in the ICANN Community Digest, the ICANN75 Policy Outcomes Report is now available for download: https://go.icann.org/outcomes75 Happy reading! Kindest regards, Terri

1 0

Notes - ICANN75 Registration Data Accuracy Scoping Team - 17 September 2022
by Chantelle Doerksen Sept. 28, 2022

Sept. 28, 2022

Dear RDA Scoping Team Members, Please find below the notes from the ICANN75 session held on Saturday, 17 September 2022. Best, Marika, Berry, and Chantelle --------- Action Items None, until such time when the GNSO Council has considered the write up for assignments #1 and #2 and approved the related recommendations. Notes Welcome Olga Cavalli reviewed the agenda and provided a brief explanation of work to date. Write up for assignments #1 (Enforcement & Reporting) and #2 (Measurement of Accuracy) – high level overview & expected next steps Olga Cavalli provided a high level overview of the purpose of the write-up. Registrar Survey Introduction Review staff support team document Marika Konings introduced the draft survey that was shared with the Scoping Team for review. She highlighted that the draft survey was based on the questions that the Scoping Team had previously identified and which are included in Annex D to the write up. Furthermore, she noted that a number of questions had been highlighted for Scoping Team review. In order to take advantage of the face-to-face time during ICANN75, informal conversations about the registrar survey would take place as part of this meeting, but any formal work would only commence after the GNSO Council’s approval of the Scoping Team’s recommendations included in the write up. Scoping Team input Input received from Scoping Team Members: Group needs to decide if an audit would duplicate efforts of the survey. Staff reviewed the draft questions in the registrant survey with the scoping team. Scoping Team members provided input. Ask registrars if they can identify which of these cases applies to each registration, and then give you the counts and the substantive information about validation for each of those. Privacy/Proxy - underlying data does not matter because they are not the registrant. Only the proxy service would need to be verified. For question five on completion of verification, we need to be more precise. We should clarify if we are looking for a positive outcome on verification or a negative outcome; or if we don't care about verification and just want to know the percentage attempted to be verified either positive or negative. As the survey is voluntary, we need to make sure the questions stay within scope to ensure participation from registrars. Staff: For question five, the group may do more to understand what data is useful to inform conversations. If/when the GNSO Council supports moving forward with the Registrar Survey, Scoping Team members are to review the survey and provide input. The GNSO Council received the write-ups prior to ICANN75, and will commence its review during the GNSO Council meeting on Wednesday, 21 September. The Scoping Team thanked Michael Palage for his service as chair. The GNSO Council will need to identify a new chair as well as a GNSO Council liaison to lead future meetings. Q&A Confirm next steps and wrap up

1 0

FW: You are Cordially Invited to the ICANN75 INTA/IPC Reception on Tuesday Evening
by Lori Schulman Sept. 15, 2022

Sept. 15, 2022

We have to have fun some time! Looking forward to the meeting on Satuday and hope that you can make it to our cocktail event on Tuesday. [cid:image003.jpg@01D8C453.8BC39510] You Are Cordially Invited to a Reception at ICANN75! On the occasion of the International Corporation for Assigned Names and Numbers (ICANN) 75th meeting in Kuala Lumpur, we are pleased to invite you to a reception for INTA and IPC members, prospective members, friends and colleagues. Catch up with what is happening in the domain name space, see old friends, make new friends and learn about INTA's upcoming Annual Meeting in Singapore in Spring 2023. Date: Tuesday, September 20, 2022 Time: 6:00 pm-8:00 pm Where: Traders Hotel SkyBar Kuala Lumpur City Centre 50088 Malaysia RSVP: Rose Davis, RDavis(a)inta.org<mailto:RDavis@inta.org> Hosted by: [cid:image001.jpg@01D8C453.79CAC090] [cid:image002.jpg@01D8C453.79CAC090]

1 0

Guidelines for speakers ICANN75
by Nathalie Peregrine Sept. 14, 2022

Sept. 14, 2022

Dear all, ICANN75 will begin in a few days. For all those joining, be it on-site or remotely, please take a few moments to review the attached guidelines. Whether you are a scheduled speaker, or planning to attend sessions, these guidelines ensure your audio will be loud and clear, and that meetings can run smoothly. Thank you all! Kind regards, Nathalie

1 0

Proposed Agenda - Registration Data Accuracy Scoping Team session at ICANN75 on Saturday 17 September
by Marika Konings Sept. 9, 2022

Sept. 9, 2022

Dear All, Please find hereby the proposed agenda for the Registration Data Accuracy Scoping Team session at ICANN75 (see https://75.schedule.icann.org/meetings/mLgjoa3GEzrYfnKba) Olga, as the GNSO Liaison to the Scoping Team, has kindly volunteered to chair this session as Michael is in the process of stepping down, but she has indicated that if someone else prefers to take on this role for this specific meeting you can indicate so on the mailing list. The GNSO Council is expected to commence its review of the write up during its meeting at ICANN75 as well as consider next steps to identify a new Chair for the Scoping Team (as well as a GNSO Liaison as Olga will be stepping down from the GNSO Council at the AGM). Also, as a reminder, the discussion on the Registrar Survey is an informal discussion as the GNSO Council will still need to review the team’s write up and endorse the recommendations before the team can formally proceed. The staff support team has taken the liberty to do some further work on the questions identified in Annex D of the write up and identified a number of follow up questions that we hope to go through during the session (see link to the document in the agenda below). Proposed Agenda – Registration Data Accuracy Scoping Team meeting at ICANN75 on Saturday 17 September 2022 1. Welcome 2. Write up for assignments #1 (Enforcement & Reporting) and #2 (Measurement of Accuracy) – high level overview & expected next steps 3. Registrar Survey * Introduction * Review staff support team document (see https://docs.google.com/document/d/1q6FzBaANgXl8gW-qPr-5AYlzj47TrwPe/edit) * Scoping Team input 4. Q & A 5. Confirm next steps and wrap up We look forward to seeing you in person or virtually at ICANN75. Best regards, Chantelle, Berry and Marika

1 0

ICANN75 GNSO Policy Briefing Available for Download
by Julie Bisland Sept. 7, 2022

Sept. 7, 2022

Dear All, On behalf of the GNSO Team, I am happy to report that the GNSO Policy Briefing for ICANN75 is now available for download at https://go.icann.org/gnsobriefing [go.icann.org]<https://urldefense.com/v3/__https:/go.icann.org/gnsobriefing__;!!PtGJab4!6U…>. Happy reading! Best Regards, Julie -- Julie Bisland Policy Operations Sr. Coordinator (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Skype ID: 79613b691cb8a6c1 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