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

**REMINDER** Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 18 November 2021 at 14:00 UTC
by Julie Bisland Nov. 17, 2021

Nov. 17, 2021

Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 18 November 2021 at 14:00 UTC for 90 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/94504686990?pwd=MWc2eXZE…> Passcode: Vc#0B7$pu8 For Audio only: Or One tap mobile : US: +13017158592,,94504686990#,,,,*4631547480# or +13126266799,,94504686990#,,,,*4631547480# Webinar ID: 945 0468 6990 Passcode: 4631547480 International numbers available: https://icann.zoom.us/u/akRu7JTFd [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/akRu7JTFd__;!!PtGJab4!pY…> If this is your first time with Zoom, please take a look here: Welcome to Zoom [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, alternates and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/3AC7Cg * Check your time zone: https://tinyurl.com/5ba4vsun [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/5ba4vsun__;!!PtGJab4!qI5d9D-…> ONLY for Members and Alternates * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Panelists and Attendees, or Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. * Alternate replacement confirmations – In order to keep track of alternate replacements, use the google form [forms.gle]<https://urldefense.com/v3/__https:/forms.gle/GZqMAi4kKDaVP5o66__;!!PtGJab4!…> to communicate who the alternate is replacing and for which period. This information will be publicly posted so that the Team is aware at any time who is active. Alternate Assignment –wiki page<https://community.icann.org/x/-wC7Cg>. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Terri

1 0

Notes and action items - RDA Scoping Team meeting #5 - 11 Nov 2021
by Caitlin Tubergen Nov. 12, 2021

Nov. 12, 2021

Dear RDA Scoping Team Members, Please find below the notes and action items from this week’s meeting. The next RDA Scoping Team meeting will be Thursday, 18 November at 14:00 UTC. Thank you. Best regards, Marika, Berry, and Caitlin -- Action Items 1. STILL OPEN: RDA Scoping Team members to populate questions to ICANN org in the dedicated Google Doc<https://docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit> over the coming weeks with a goal to finalize questions by Friday, 27 November. 2. By Thursday, 2 December, each group to identify their future explanation of Accuracy<https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit>, i.e., what should accuracy requirements look like and how should these be implemented and enforced by ICANN org in a future state? As part of this future explanation of accuracy, you are asked to identify what problem(s) this future explanation is expected to address, as well as provide your insights into how this problem has already been documented or how it can be documented as part of the team’s effort to scope the issue. Registration Data Accuracy Scoping Team – Meeting #5 Thursday 11 November at 14.00 UTC 1. Welcome & Chair Updates (5 minutes) * Project plan submitted to the GNSO Council (see https://mm.icann.org/pipermail/council/2021-November/025175.html) * The document reviewed by the Team last week was sent the GNSO Council this week. It will be included in the AOB agenda item at the Council’s upcoming meeting. * The meeting will remain at this time going forward; the only variable is whether the meeting will be 60 minutes or 90 minutes. The goal will be to conclude every meeting after 60 minutes. 1. Working definition of accuracy (10 minutes) From assignment #1: “The Scoping Team shall, with reference to the resources that will be included in the index of relevant resources cited below, consider whether there is an agreed definition of registration data accuracy and, if not, consider what working definitions should be used in the context of the Scoping Team's deliberations. Particular attention should be given to the definition that ICANN Compliance employs for “accuracy” in ICANN’s contracts. Note, this does not preclude any subsequent effort from formalising the definition(s) that should be applied in the context of any existing and/or new accuracy requirements that may be developed”. * Consider further input received on definition (see page 12 - https://docs.google.com/document/d/1k9fvA4gnb13bNbB8O4o72mXMZ8mQnJGC/edit[d…<https://urldefense.com/v3/__https:/docs.google.com/document/d/1k9fvA4gnb13b…>) * * Confirm working definition (current state) * During the last meeting, the group came close to rough consensus on a working definition. * Instead of a working definition, propose to refer to it as a working contractual construct * The assignment of the scoping team is to consider whether there is an agreed upon definition and what working definition to use in the context of the scoping team’s deliberations. Now it seems there is proposal to have a working construct. * Suggest that the team does away with the unvarnished meaning of accuracy. There are three kinds of accuracy: identity, syntactic, and operational. The language that should appear in contracts and policies should include the appropriate labels. It would be helpful to use the type of accuracy and then the discussion will be easier. * Accuracy is a loaded word and it means different things to different people in different contexts. Could live with the word definition – what some members are afraid of is that this definition will be set in stone and many are not OK with the current definition. * The group is starting with an explanation of the current state of affairs. Do members agree that this is an accurate capture of the current definition in existing contracts? If the group does not start with a shared point, it will be messy. Understand there are three types of accuracy defined by others, but that gets into questions 3 and 4. This assignment is – what is the current state, and can the group agree on it. * The words on the paper need to say current and have a disclaimer so that it is clear * There is a different level of checking for phone number and email then for names – it’s important to explain the different levels * Confirming that the group has viewed comments from Melina and Lori – does this belong here or in the aspirational discussion? Melina would like reference to purposes in ICANN Bylaws and purposes in EPDP Phase 1 1. Aspirational definition of accuracy (10 minutes) * Overview of homework assignment (see template - https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/11msexuoqWSUs…>) * Groups are now to work together to come up with their aspirational definition * The idea is that the group now has a current state definition. Many members have spoken about what the definition “should be”, which is why leadership is using the term aspirational. However, most have not provided why the definition should be changed. Groups are now asked to provide what the definition should be and then explain what problem this change is trying to address. Then, is there data that confirms that this problem exists? If there is no data currently, what data is necessary to gather to further understand the perceived problem? * The definition in the RAA only applies for new registrations and to certain fields. * To answer this question, the group should look at the final purposes of the EPDP Phase 1. * The EPDP team did not agree to the definition of accuracy vis-à-vis GDPR. The EPDP team was discussing purposes based on the RAA. This should not be the basis for going forward. * The definition used for accuracy was under dispute throughout the EPDP. The reason we have for accuracy is for contactability which does include third parties. * The work of this group for assignment 1 and 2 is not in scope to be relitigating or reopening the work in EPDP Phase 1, 2, or 2A. If the group identifies a problem, it could identify issues for the Council to reconsider. * Whatever the group is discussing in terms of accuracy must stay within the bounds of what was discussed in the EPDP. * In the third column, the word need has been added – what problems and/or needs is this future definition expected to address * Scoping team input * Aspirational is a loaded term. What is the need that accuracy is trying to fill – what goal is it trying to reach? Does the current definition meet that need? This is not a shopping list of items that we would like accuracy to do. The chart gets to this. * Looking at this as an aspirational definition could lead the group down a rabbit hole. Trying to agree to an aspirational definition could cause a lot of consternation. * Confirm next steps & deadline for input 1. Follow up questions to ICANN org regarding enforcement and Accuracy Reporting System (30 + minutes) * Note additional information added to the index of relevant resources from RDS-WHOIS2 RT, including responses to questions * Input received from scoping team to date: https://docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit[d…<https://urldefense.com/v3/__https:/docs.google.com/document/d/1arlKdQkbRkE1…> * Scoping team input * The document that staff prepared for Council is very thorough – referring specifically to the a26 Feb 2021 letter from Swinehart to Fouquart. This dovetails into the group’s first task nicely. After reading this document, did not come away with what definition ICANN uses. Perhaps this would be good fodder for a follow-up question with ICANN org. What does ICANN Compliance consider the current definition of accuracy and does that comply with the definition proposed by registrars? * Support the above * Important for the group to discuss these questions. * There is a Compliance blog post about enforcement – please read this document and determine if additional questions are necessary. Also review the question and additional information Sarah Wyld put into the document. * This work needs to take place intersessionally between the working calls; the calls cannot be used for the drafting of questions in order for the group to make progress. * Confirm deadline for submission of questions 1. Confirm action items & next meeting (Thursday 18 November at 14.00 UTC)

1 0

Registration Data Accuracy Scoping Team | Thursday, 11 November 2021
by Terri Agnew Nov. 11, 2021

Nov. 11, 2021

Dear all, All recordings for the Registration Data Accuracy Scoping Team held on Thursday, 11 November 2021 can be found on the agenda wiki page <https://community.icann.org/x/1AC7Cg> (attendance included) and the GNSO Master Calendar [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…>. These include: * Attendance (please let me know if your name has been left off the attendance list) * Audio recording * Zoom chat archive * Zoom recording (including audio, visual, rough transcript) * Transcript For additional information, you may consult the mailing list archives <https://mm.icann.org/pipermail/gnso-accuracy-st/> and the main wiki page<https://community.icann.org/x/hQIuCg>. Thank you! Kind Regards, Terri

1 0

**Starting in 15 minutes | Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 11 November 2021 at 14:00 UTC
by Terri Agnew Nov. 11, 2021

Nov. 11, 2021

**Starting in 15 minutes Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 11 November 2021 at 14:00 UTC for 90 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09 Passcode: Vc#0B7$pu8 For Audio only: Or One tap mobile : US: +13017158592,,94504686990#,,,,*4631547480# or +13126266799,,94504686990#,,,,*4631547480# Webinar ID: 945 0468 6990 Passcode: 4631547480 International numbers available: https://icann.zoom.us/u/akRu7JTFd [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/akRu7JTFd__;!!PtGJab4!pY…> If this is your first time with Zoom, please take a look here: Welcome to Zoom [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, alternates and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/1AC7Cg * Check your time zone: https://tinyurl.com/znz8kmf4 [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/znz8kmf4__;!!PtGJab4!psV4Gwm…> ONLY for Members and Alternates * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Panelists and Attendees, or Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. * Alternate replacement confirmations – In order to keep track of alternate replacements, use the google form [forms.gle]<https://urldefense.com/v3/__https:/forms.gle/GZqMAi4kKDaVP5o66__;!!PtGJab4!…> to communicate who the alternate is replacing and for which period. This information will be publicly posted so that the Team is aware at any time who is active. Alternate Assignment –wiki page<https://community.icann.org/x/-wC7Cg>. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Terri

2 1

Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 18 November 2021 at 14:00 UTC
by Terri Agnew Nov. 11, 2021

Nov. 11, 2021

Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 18 November 2021 at 14:00 UTC for 90 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09 Passcode: Vc#0B7$pu8 For Audio only: Or One tap mobile : US: +13017158592,,94504686990#,,,,*4631547480# or +13126266799,,94504686990#,,,,*4631547480# Webinar ID: 945 0468 6990 Passcode: 4631547480 International numbers available: https://icann.zoom.us/u/akRu7JTFd [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/akRu7JTFd__;!!PtGJab4!pY…> If this is your first time with Zoom, please take a look here: Welcome to Zoom [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, alternates and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/3AC7Cg * Check your time zone: https://tinyurl.com/5ba4vsun ONLY for Members and Alternates * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Panelists and Attendees, or Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. * Alternate replacement confirmations – In order to keep track of alternate replacements, use the google form [forms.gle]<https://urldefense.com/v3/__https:/forms.gle/GZqMAi4kKDaVP5o66__;!!PtGJab4!…> to communicate who the alternate is replacing and for which period. This information will be publicly posted so that the Team is aware at any time who is active. Alternate Assignment –wiki page<https://community.icann.org/x/-wC7Cg>. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Terri

1 0

Proposed Agenda - Accuracy Scoping Team meeting #5 - Thursday 11 November at 14.00 UTC
by Marika Konings Nov. 10, 2021

Nov. 10, 2021

Dear All, Please find below the proposed agenda for the next Registration Data Accuracy Scoping Team which is scheduled for Thursday 11 November at 14.00 UTC. As a reminder: 1. RDA Scoping Team members to review the most recent working definition for accuracy (p. 12 of the Assignment 1 background briefing doc [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1k9fvA4gnb13b…>) and provide proposed edits or alternate definitions by COB Wednesday, 10 November. Once the Team agrees to the baseline working definition, groups can begin working on their proposed “aspirational” or “desired future state” definitions. 2. RDA Scoping Team members to populate questions to ICANN org in the dedicated Google Doc [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1arlKdQkbRkE1…> over the coming weeks with a goal to finalize questions by Friday, 27 November. Best regards, Caitlin, Berry and Marika Registration Data Accuracy Scoping Team – Meeting #5 Thursday 11 November at 14.00 UTC 1. Welcome & Chair Updates (5 minutes) * Project plan submitted to the GNSO Council (see https://mm.icann.org/pipermail/council/2021-November/025175.html) 1. Working definition of accuracy (10 minutes) From assignment #1: “The Scoping Team shall, with reference to the resources that will be included in the index of relevant resources cited below, consider whether there is an agreed definition of registration data accuracy and, if not, consider what working definitions should be used in the context of the Scoping Team's deliberations. Particular attention should be given to the definition that ICANN Compliance employs for “accuracy” in ICANN’s contracts. Note, this does not preclude any subsequent effort from formalising the definition(s) that should be applied in the context of any existing and/or new accuracy requirements that may be developed”. * Consider further input received on definition (see page 12 - https://docs.google.com/document/d/1k9fvA4gnb13bNbB8O4o72mXMZ8mQnJGC/edit) * Confirm working definition (current state) 1. Aspirational definition of accuracy (10 minutes) * Overview of homework assignment (see template - https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit) * Scoping team input * Confirm next steps & deadline for input 1. Follow up questions to ICANN org regarding enforcement and Accuracy Reporting System (30 + minutes) * Note additional information added to the index of relevant resources from RDS-WHOIS2 RT, including responses to questions * Input received from scoping team to date: https://docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit * Scoping team input * Confirm deadline for submission of questions 1. Confirm action items & next meeting (Thursday 18 November at 14.00 UTC)

2 1

Re: [GNSO-Accuracy-ST] Proposed Agenda - Accuracy Scoping Team meeting #5 - Thursday 11 November at 14.00 UTC
by Marika Konings Nov. 10, 2021

Nov. 10, 2021

Dear All, To facilitate your input for agenda item #4, please find attached a compilation of the ICANN org answers to a number of accuracy related questions posed by the WHOIS-RDS2 Review Team back in 2018. Best regards, Caitlin, Berry and Marika From: GNSO-Accuracy-ST <gnso-accuracy-st-bounces(a)icann.org> on behalf of Marika Konings <marika.konings(a)icann.org> Date: Tuesday, 9 November 2021 at 14:52 To: "gnso-accuracy-st(a)icann.org" <gnso-accuracy-st(a)icann.org> Subject: [GNSO-Accuracy-ST] Proposed Agenda - Accuracy Scoping Team meeting #5 - Thursday 11 November at 14.00 UTC Dear All, Please find below the proposed agenda for the next Registration Data Accuracy Scoping Team which is scheduled for Thursday 11 November at 14.00 UTC. As a reminder: 1. RDA Scoping Team members to review the most recent working definition for accuracy (p. 12 of the Assignment 1 background briefing doc [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1k9fvA4gnb13b…>) and provide proposed edits or alternate definitions by COB Wednesday, 10 November. Once the Team agrees to the baseline working definition, groups can begin working on their proposed “aspirational” or “desired future state” definitions. 2. RDA Scoping Team members to populate questions to ICANN org in the dedicated Google Doc [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1arlKdQkbRkE1…> over the coming weeks with a goal to finalize questions by Friday, 27 November. Best regards, Caitlin, Berry and Marika Registration Data Accuracy Scoping Team – Meeting #5 Thursday 11 November at 14.00 UTC 1. Welcome & Chair Updates (5 minutes) * Project plan submitted to the GNSO Council (see https://mm.icann.org/pipermail/council/2021-November/025175.html) 1. Working definition of accuracy (10 minutes) From assignment #1: “The Scoping Team shall, with reference to the resources that will be included in the index of relevant resources cited below, consider whether there is an agreed definition of registration data accuracy and, if not, consider what working definitions should be used in the context of the Scoping Team's deliberations. Particular attention should be given to the definition that ICANN Compliance employs for “accuracy” in ICANN’s contracts. Note, this does not preclude any subsequent effort from formalising the definition(s) that should be applied in the context of any existing and/or new accuracy requirements that may be developed”. * Consider further input received on definition (see page 12 - https://docs.google.com/document/d/1k9fvA4gnb13bNbB8O4o72mXMZ8mQnJGC/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1k9fvA4gnb13b…>) * Confirm working definition (current state) 1. Aspirational definition of accuracy (10 minutes) * Overview of homework assignment (see template - https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/11msexuoqWSUs…>) * Scoping team input * Confirm next steps & deadline for input 1. Follow up questions to ICANN org regarding enforcement and Accuracy Reporting System (30 + minutes) * Note additional information added to the index of relevant resources from RDS-WHOIS2 RT, including responses to questions * Input received from scoping team to date: https://docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1arlKdQkbRkE1…> * Scoping team input * Confirm deadline for submission of questions 1. Confirm action items & next meeting (Thursday 18 November at 14.00 UTC)

2 2

**REMINDER** Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 11 November 2021 at 14:00 UTC
by Julie Bisland Nov. 10, 2021

Nov. 10, 2021

Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 11 November 2021 at 14:00 UTC for 90 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/94504686990?pwd=MWc2eXZE…> Passcode: Vc#0B7$pu8 For Audio only: Or One tap mobile : US: +13017158592,,94504686990#,,,,*4631547480# or +13126266799,,94504686990#,,,,*4631547480# Webinar ID: 945 0468 6990 Passcode: 4631547480 International numbers available: https://icann.zoom.us/u/akRu7JTFd [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/akRu7JTFd__;!!PtGJab4!pY…> If this is your first time with Zoom, please take a look here: Welcome to Zoom [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, alternates and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/1AC7Cg * Check your time zone: https://tinyurl.com/znz8kmf4 [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/znz8kmf4__;!!PtGJab4!psV4Gwm…> ONLY for Members and Alternates * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Panelists and Attendees, or Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. * Alternate replacement confirmations – In order to keep track of alternate replacements, use the google form [forms.gle]<https://urldefense.com/v3/__https:/forms.gle/GZqMAi4kKDaVP5o66__;!!PtGJab4!…> to communicate who the alternate is replacing and for which period. This information will be publicly posted so that the Team is aware at any time who is active. Alternate Assignment –wiki page<https://community.icann.org/x/-wC7Cg>. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Terri

1 0

Purpose
by Volker Greimann Nov. 5, 2021

Nov. 5, 2021

Hi all, during the last call, Steve asked about the purpose for the data, but I do not think that defining should concern for even a second of our work as the council was explicit in their instructions to that regard: "In carrying out its work above, *the Scoping Team is expected to take into account* the policy recommendations from the EPDP on gTLD Registration Data (EPDP) Team that have been adopted by the GNSO Council and the ICANN Board, including* the EPDP-identified purposes* and the related data processing activities. However, the scoping team *is not tasked to review these purposes or suggest changes*. If the scoping team finds that further review of these purposes is necessary, especially in the context of implementation and enforcement of existing requirements, it will identify this as an area of further work in its recommendations. " So let's just copy/paste the purposes as defined by the EPDP and be done with it. Best, -- Volker A. Greimann General Counsel and Policy Manager *KEY-SYSTEMS GMBH* T: +49 6894 9396901 M: +49 6894 9396851 F: +49 6894 9396851 W: www.key-systems.net Key-Systems GmbH is a company registered at the local court of Saarbruecken, Germany with the registration no. HR B 18835 CEO: Oliver Fries and Robert Birkner Part of the CentralNic Group PLC (LON: CNIC) a company registered in England and Wales with company number 8576358. This email and any files transmitted are confidential and intended only for the person(s) directly addressed. If you are not the intended recipient, any use, copying, transmission, distribution, or other forms of dissemination is strictly prohibited. If you have received this email in error, please notify the sender immediately and permanently delete this email with any files that may be attached.

3 6

Notes and action items - RDA Scoping Team meeting #4 - 4 Nov 2021
by Caitlin Tubergen Nov. 4, 2021

Nov. 4, 2021

Dear RDA Scoping Team members, Please find below the notes and action items from today’s meeting. The next RDA Scoping Team meeting will be Thursday, 11 November at 14:00 UTC. Best regards, Marika, Berry, and Caitlin -- Action Items 1. RDA Policy Support Team to distribute call for volunteers for alternates to SO/AC/C leadership. (complete) 2. RDA Scoping Team members to review the most recent working definition for accuracy (p. 12 of the Assignment 1 background briefing doc<https://docs.google.com/document/d/1k9fvA4gnb13bNbB8O4o72mXMZ8mQnJGC/edit>) and provide proposed edits or alternate definitions by COB Wednesday, 10 November. Once the Team agrees to the baseline working definition, groups can begin working on their proposed “aspirational” or “desired future state” definitions. 3. RDA Scoping Team members to populate questions to ICANN org in the dedicated Google Doc<https://docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit> over the coming weeks with a goal to finalize questions by Friday, 27 November. Registration Data Accuracy Scoping Team – Meeting #4 Thursday 4 November at 13.00 UTC 1. Welcome & Chair Updates * Council non-objection to appointing alternates and vice-chair * Groups can notify GNSO Support Staff if they intend to appoint an alternate * At this point in time, not going to undertake appointment of a vice-chair, but this has been approved * Appointment of Council liaison * Olga Cavalli has been appointed as the GNSO Council Liaison to the Scoping Team * Adjustment of call time & duration from next week onwards to accommodate for DST * Going forward, the meetings will take place on Thursdays at 14:00 UTC for 90 minutes, with the intent to end meetings after 60 minutes. * This schedule does include Thursday, Nov 25 (U.S. Thanksgiving) * Over the next couple of weeks, here is the plan: * Today – hope to reach rough consensus on the current definition of accuracy * Pending success on that, the Team will have four weeks to go back to their respective groups and produce what is called an “aspirational definition” on where they think the definition of accuracy should evolve to. * During these four weeks, the Team will use that intervening time to produce questions to ICANN org. * These questions need to be vetted before the ICANN org presentation, so please submit them by the last week of November 1. Proposed Work plan & timeline * Review proposed work plan & timeline * Many on this team are familiar with the PDP 3.0 principles for project management, i.e., defining and measuring the work ahead of us. * The Leadership Team was leaning toward an aspirational delivery of a report to the GNSO Council by ICANN75 (mid-September). * The Leadership Team will forward the project plan to the GNSO Council on Monday, 8 November (the motions and documents deadline). It will be an AOB item for the Council meeting. * Each month, we will produce a project package, including the dashboard currently shown on screen, the project plan, and the elements/topics the Team is discussing. * There are four assignments in front of the Team, per the Council’s instructions. The Team will work assignments 1 and 2 before working 3 and 4. Assignments 1 and 2 will be worked in parallel for 12 business weeks (roughly through the end of January). * One challenge in putting this plan together is that it is nebulous what the scope of work will look like; accordingly, February is planned to scope Assignment 3. The Council instructions provide a general direction, but the Team needs to drill own on defining the scope of Assignment 3 (for example, is a survey needed?) * The output of the deep dive into Assignment 3 will result in an update to the Council re: the sizing of the work ahead of the Team. * If necessary, the Team can communicate back to the Council if more or less time is needed. * If the group is on track after ICANN73, the Team will endeavor to deliver the report to the Council by September 2022. * The previous talking points will be included in the provision of the project plan to the Council. * The Group expressed concerns with how to account for the unknowns in Assignment 3, so the current plan includes some caveats and flexibility. * Scoping Team Input: * In looking at the whole process, there is a lot of emphasis regarding the criteria and measurement of accuracy. What are the purposes that are intended to be satisfied? In other words, if these requirements are satisfied, are the requirements fit for purpose? Does the group have an explicit and direct address to that issue? * As a Scoping Team, the Team is afforded latitude; however, the Team should be cautious about relitigating other aspects such as access. * If you called a phone number and it rang, is that accurate data? Most judges would probably say no. Is there a correlation? * For the purpose of today’s conversation, are there any concerns with the timeline? * Question about the tasks: different ideas of what we are putting out from this group. The Scoping Team is not something a PDP is doing. * Getting back to the timeline, what we have proposed here – over the next three months, the Team will be working concurrently on assignments 1 and 2. Today, the group will begin a substantive discussion on what the definition is today and get rough consensus on what that definition is today. From there, the Team will spend the next four weeks discussing within their groups on what the aspirational definition is. * Confirm next steps 1. Working definition of accuracy From assignment #1: “The Scoping Team shall, with reference to the resources that will be included in the index of relevant resources cited below, consider whether there is an agreed definition of registration data accuracy and, if not, consider what working definitions should be used in the context of the Scoping Team's deliberations. Particular attention should be given to the definition that ICANN Compliance employs for “accuracy” in ICANN’s contracts. Note, this does not preclude any subsequent effort from formalising the definition(s) that should be applied in the context of any existing and/or new accuracy requirements that may be developed”. * Review input received on definition (see page 12 - https://docs.google.com/document/d/1k9fvA4gnb13bNbB8O4o72mXMZ8mQnJGC/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1k9fvA4gnb13b…>) * Sarah and Michael had an exchange on the definition * The latest definition proposed by Sarah appears on p. 12 * The group’s task is to determine if contractual data accuracy obligations are effective at ensuring accuracy levels. The definition is one part of this and even if the definition is perfect, this does not address effectiveness or scope. * Subpart f of the Whois Accuracy Program Specification – there is a difference in technical and legal speak. Affirmative response means more than operational validation. * The requirements for operational validation discussed affirmative response; do not think the phone just ringing would not meet the current requirements. * Do not understand where the example of the phone just ringing comes from. Not sure what an affirmative response actually is – that is determined b/w ICANN compliance and the relevant registrar. The verification method is included in the RAA definition. Have hesitation about incorporating the specific examples because a definition should stand on its own without examples. Agree that it is important to have a common understanding of the difference between validation and verification. * Where is the relationship between the requirement and whether it serves the purpose? * Agree that it’s important to have a good foundation to begin on. Here is the definition, here is current enforcement, here is the scope of where the PDP will lie. * Question 3 could be reviewed before 1 and 2. * If there is a problem, that is what assignment 4 accounts for. One reason the group has been given some strong suggestive guidance is that after the analysis is undertaken, that will drive #4. * It is not just ensuring that the phone is ringing, it is communicating with the RNH. * What is the standard implementation of this requirement for operational accuracy. It is hard to answer that because have not done a survey of all registrars. Email verification is likely more common than a phone verification. Familiar with a text with a link to a webpage. It is, however, difficult to answer the standard overall method for registrars. If that is something the group determines is needed, this could be done via a survey of providers, but this may be out of scope. * Is there anyone who would like to update the definition as it appears now? * In the current definition, it may be helpful to reference the purpose of the definition by citing the relevant portion of the ICANN Bylaws. * In the group’s preparatory meeting, two of three elements of the definition are included. The third element (verification that there is a person at the end and that person is the RNH) is not – there is a third element that should be included. The third prong is not recognized anywhere; this should not be discarded. * The above appears to be identify verification – such as RNH being required to send in a photo ID and that being verified. * Text from ICANN org enforcement of accuracy pre and post-GDPR: “However, if the complaint is about identity (e.g., the registrant is not who they say they are), Contractual Compliance may ask the registrar to provide further information concerning their findings and the results of their investigation specific to the facts of the complaint.” * Registrars have been doing a lot of visible heavy lifting. Proposal to strike “shall strictly be defined” Instead, accuracy “is” syntactical accuracy of the registration data elements processed by Registrars. Also, in line with the text from the GAC Communique, proposal to add “and registries”. In other words, “Accuracy is syntactical accuracy of the registration data elements processed by Registrars and certain Registry Operators” provided by the Registered Name Holder or Account Holder as well as the operational accuracy of either the telephone number or the email address. * What is ICANN org’s authority for doing an identity check? * This is a question to address to compliance as this is confusing, even to registrars * Important to ensure this is a stable and clear definition * Text from ICANN72 GAC Communique: The GAC considers that assignments iii) and iv) are particularly important for the purpose of assessing possible improvements of accuracy of registration data. The GAC is looking forward to exchanging with other constituencies not only on the definition and measurement of accuracy but also on solutions on how to enhance accuracy. The GAC gives particular importance to the verification, validation and correction of all registration data by registrars, and certain registries, in line with their contractual obligations, and supports rigorous monitoring and enforcement of such contractual obligations by ICANN. The GAC stresses the importance of delivering on all four tasks in a timely and effective manner. * ICANN Compliance may ask for further information on the registrar’s findings – this is not asking the registrar to do something new * Compliance will see if registrar has taken reasonable steps * When the Team considers an aspirational definition, consider this as a future state/future solution. It is important not just to focus on the text of the aspirational definition, but also to accompany the text with (i) the problem or concern the aspirational definition is intended to address; and (ii) how that problem can be measured / confirmed. This can be included in clear bullet points. For example, some have suggested that identify verification needs to be included. * * Consider whether in addition to working definition focused on current application, input should be requested on aspirational definitions to identify perceived gap between current definition and aspirational definition * Scoping team input * Confirm next steps 1. Follow up questions to ICANN org regarding enforcement and Accuracy Reporting System * Note additional information added to the index of relevant resources from RDS-WHOIS2 RT, including responses to questions * Input received from scoping team to date: https://docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1arlKdQkbRkE1…> * Scoping team input * Confirm deadline for submission of questions 1. Confirm action items & next meeting (Thursday 11 November at 14.00 UTC)

1 0