January 2022 - GNSO-Accuracy-ST

Proposed Agenda - Registration Data Accuracy Scoping Team meeting #13 on Thursday 13 January at 14.00 UTC
by Marika Konings Jan. 11, 2022

Jan. 11, 2022

Dear All, Please find below the proposed agenda for the next Registration Data Accuracy Scoping Team meeting which is scheduled for Thursday 13 January at 14.00 UTC. Best regards, Caitlin, Berry and Marika Registration Data Accuracy Scoping Team – Meeting #13 Thursday 13 January at 14.00 UTC 1. Welcome & Chair Updates (5 minutes) * Vice-chair – volunteers? Proposed deadline for expressions of interest Wednesday 19 January. 1. ICANN org responses to Scoping Team questions (30 minutes) * High level overview * Scoping team follow up questions / comments * Next steps 1. Gap Analysis (20 minutes) * Responses to questions raised in relation to GAC input during meeting #11 * Continue review of remaining input (ISPCP, still missing BC): https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit * Scoping team input * Confirm next steps 1. Measurement of current goals identified (20 minutes) – see page 25 https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit (20 minutes) * EPDP Team to consider what is needed and from whom to obtain information identified as necessary to measure whether current goals are met * Confirm next steps 1. Confirm action items & next meeting (Thursday 20 January at 14.00 UTC)

2 1

RDA_ST // 31 Dec 2021 Project Package
by Berry Cobb Jan. 6, 2022

Jan. 6, 2022

Dear Scoping Team, Please find a link below to project package for the RDA_ST (31 Dec 2021). This package is a snap-shot at the close of each month and developed by the leadership team to report on the working group’s activities and status of the project. It is also distributed to the GNSO Council to keep them informed as managers of the PDP. The package is deposited on the wiki so that we can track access statistics. Link: https://community.icann.org/x/PQ2HCg 1. Page 01 – Summary dashboard 2. Page 02 – Project Sitrep – an extract from the Council’s Project List 3. Page 03 – Group roster 4. Page 04,05 – Work and activity metrics 5. Page 06,07 – Project Plan, Gantt chart 6. Page 08 – Work plan & Action items for the period Please let us know if you have questions. Thank you. B Berry Cobb Policy Development - Portfolio Manager Internet Corporation for Assigned Names and Numbers (ICANN) berry.cobb(a)icann.org

1 0

Notes and action items - RDA Scoping Team Meeting #12 - 6 January 2021
by Caitlin Tubergen Jan. 6, 2022

Jan. 6, 2022

Dear RDA Scoping Team, Please find below the notes and action items from today’s meeting. The next meeting will be Thursday, 13 January at 14:00 UTC. Best regards, Marika, Berry, and Caitlin -- Action Items 1. GAC colleagues to come prepared to respond to questions raised during 23 December call. (Please refer to meeting transcript and notes: https://community.icann.org/pages/viewpage.action?pageId=180027627 2. Scoping Team to consider what is needed and from whom to obtain information identified as necessary to measure whether current goals are met. Additionally, scoping team members to begin identifying specific ways in which measurement can be undertaken. As noted during today’s meeting, Support Staff has begun inputting the responses received from the Gap Analysis here: https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit?p… 3. OUTSTANDING: BC colleagues to input feedback into Gap Analysis as soon as possible. Registration Data Accuracy Scoping Team – Meeting #12 Thursday 6 January at 14.00 UTC 1. Welcome & Chair Updates (5 minutes) * Status of questions to ICANN org * Expect the ICANN org answers to come back by mid-next week, hopefully before the next meeting * Relevant subject matter experts have expressed willingness to attend the meeting and answer follow-up questions * Vice-chair – proposed next steps * Propose to open the floor for the vice-chair position – interested members can speak up now on the call or write to the list if interested in the position * Is the vice-chair open to the entire community, or just members/alternates? * Members/alternates should be given the first chance to express interest; however, members and alternates may not wish to give up their neutrality. It may have to be opened to everyone if no members or alternates steps forward. 1. Gap Analysis (50 minutes) * Responses to questions raised in relation to GAC input during meeting #11 * Postponed until next meeting to allow sufficient time for GAC colleagues to collaborate * Note: the notes and transcript of the last meeting will provide the specific questions that arose during the meeting * Continue review of remaining input (SSAC, still missing: BC, ISPCP, NCSG):https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/…<https://urldefense.com/v3/__https:/docs.google.com/document/d/11msexuoqWSUs…> * SSAC sent additional input to the group earlier this week * SSAC input: * There appears to be a fundamental split in the discussion. There is a distinction b/w stated purposes from EPDP vs. what are felt to be legitimate needs felt by various users. * When the group is finished, it will need to communicate what is done and what is not done. * What are the operational requirements imposed on CPs? This is intended to implement these purposes, but the question remains – do they effectively implement these purposes * Understand it is important to stick to Council instructions, but it’s important to identify problems if the group observes them * Important not to conflate purposes and uses – purposes were settled under EPDP; subsequent use of information is what the group can discuss. * Believe the EPDP Team was approaching the problem in the wrong way - engineers, lawyers, and policy folks have a different approach to scope * The picket fence does limit what can be put in contracts and made binding on contracted parties. The issue of maintenance of accurate and up-to-date registration data is squarely within the picket fence. * ICANN should regain access to reg data and resume ARS * ICANN access to registration data is a basic example of a GDPR-compliant service * Oversight of accuracy – this should be spelled out in a co-controller agreement of some kind – this group needs to see the agreement * The agreement is a subordinate matter * How exactly does SSAC anticipate that ICANN can check the accuracy of data? It seems it was suggested that it could work with a third party on this. * The current rules are vague on two points: which data elements needs to be validated at which levels. The actual validation that is carried out should be disclosed. If there is a choice to verify the email or phone number – the verification level should be returned. When was the validation/verification done? * (per element accuracy requirement) – which elements do not have any requirements? * Name and org * These have validation requirements – they are in the appropriate format, but not verification requirements, so they should fall under V1 * Syntactic requirements are pretty weak. What they ultimately should fall under is a policy issue. * Believe V1 is the appropriate level for name and org * Both RDAP and EPP are extensible with respect to what fields are included – that is different than a new platform * When verification request is sent to a phone or email, the registrant is asked to confirm that all fields are accurate (and this is additionally confirmed on an annual basis under the WDRP) * NCSG Input * Goals: operational and syntactic accuracy (contactability) * Registrars are in the best position to measure these goals since they hold the data * No additional goals identified – the registrar has requirement to ensure data is accurate throughout its lifecycle * BC’s input is forthcoming * Scoping team input * Confirm next steps * BC’s input is forthcoming 1. Measurement of current goals identified (30 minutes) * EPDP Team to consider what is needed and from whom to obtain information identified as necessary to measure whether current goals are met * Within the table, Support Staff has input the responses from groups * The idea is to start having a practical conversation around confirming if these goals are met, and, further, what is needed to confirm this? * Does further research need to be undertaken? Do additional parties need to be involved? How much time would be needed for this? Steve’s Document: * There is a tremendous amount of repeating points that have been made in the past. Keep track of these to shorten repetition and be forthright about what the group is doing and NOT doing. * This is now in a google doc format to allow collaboration * Some items in this document were discussed earlier via the SSAC input * EPDP2A recommended no change because of no consensus, but there were a substantial number of minority views – this can be recorded here. * It would be helpful to identify who the user is, as not all users have a need to identify the registrant * Security researchers do not have delegated authority to act as if they are law enforcers * Confirm next steps 1. Confirm action items & next meeting (Thursday 13 January at 14.00 UTC)

1 0

Post call | Registration Data Accuracy Scoping Team | Thursday, 06 January 2022
by Terri Agnew Jan. 6, 2022

Jan. 6, 2022

Dear all, All recordings for the Registration Data Accuracy Scoping Team held on Thursday, 06 January 2022 can be found on the agenda wiki page <https://community.icann.org/x/7oD3Cg> (attendance included) and the GNSO Master Calendar<https://gnso.icann.org/en/group-activities/calendar/2022>. 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

Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 13 January 2022 at 14:00 UTC
by Terri Agnew Jan. 6, 2022

Jan. 6, 2022

Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 13 January 2022 at 14:00 UTC for 90 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09<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 <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 <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/8ID3Cg * Check your time zone: https://tinyurl.com/2p8b55v7 ONLY for Members and Alternates * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select 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 <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

**Starting in 15 minutes | Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 06 January 2022 at 14:00 UTC
by Terri Agnew Jan. 6, 2022

Jan. 6, 2022

**Starting in 15 minutes Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 06 January 2022 at 14:00 UTC for 90 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09<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 <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 <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/7oD3Cg * Check your time zone: https://tinyurl.com/y732rcak [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/y732rcak__;!!PtGJab4!r32uzcM…> ONLY for Members and Alternates * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select 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 <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

**REMINDER** Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 06 January 2022 at 14:00 UTC
by Julie Bisland Jan. 5, 2022

Jan. 5, 2022

Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 06 January 2022 at 14:00 UTC for 90 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09<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 <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 <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/7oD3Cg * Check your time zone: https://tinyurl.com/y732rcak [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/y732rcak__;!!PtGJab4!r32uzcM…> ONLY for Members and Alternates * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select 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 <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 - Registration Data Accuracy Scoping team meeting #12 on Thursday 6 January at 14.00 UTC
by Marika Konings Jan. 4, 2022

Jan. 4, 2022

Dear all, First of all, best wishes for 2022! Please find below the proposed agenda for the next Registration Data Accuracy Scoping Team meeting which is scheduled for Thursday 6 January at 14.00 UTC. Best regards, Caitlin, Berry and Marika Registration Data Accuracy Scoping Team – Meeting #12 Thursday 6 January at 14.00 UTC 1. Welcome & Chair Updates (5 minutes) * Status of questions to ICANN org * Vice-chair – proposed next steps 1. Gap Analysis (50 minutes) * Responses to questions raised in relation to GAC input during meeting #11 * Continue review of remaining input (SSAC, still missing: BC, ISPCP, NCSG): https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit * Scoping team input * Confirm next steps 1. Measurement of current goals identified (30 minutes) * EPDP Team to consider what is needed and from whom to obtain information identified as necessary to measure whether current goals are met * Confirm next steps 1. Confirm action items & next meeting (Thursday 13 January at 14.00 UTC)

1 0

Notes and action items - RDA Scoping Team Meeting #11 - 23 December 2021
by Caitlin Tubergen Jan. 3, 2022

Jan. 3, 2022

Dear RDA Scoping Team Members, Please find below the notes and action items from the last meeting on Thursday, December 23 at 14:00 UTC. Happy New Year to all! Best regards, Marika, Berry, and Caitlin -- Action Items 1. GAC Representatives to come prepared to answer questions raised during the meeting on Thursday, 23 December. 2. Question for ICANN org: Is the list provided at this link (https://whois.icann.org/en/what-registration-data-used) still relevant? 3. STILL OUTSTANDING: Groups who have not provided input for the Gap Analysis (ISPCP, NCSG, SSAC) to do so ASAP or inform Leadership if their group does not intend to do so. Registration Data Accuracy Scoping Team – Meeting #11 Thursday 23 December at 14.00 UTC 1. Welcome & Chair Updates (5 minutes) * Status of questions to ICANN org * Questions have been transmitted to the appropriate subject matter experts, including compliance, legal, etc. Org will endeavor to provide responses to questions by 13 January (the second scoping team meeting in the new year). * Vice-chair appointment – any further input? * In response to Marc A’s message, Rafik served as vice chair and GNSO Council liaison during Phase 1 and Phase 2. Additionally, the role of chair for this scoping team was not heavily sought after. Unlike EPDP Phase 1 and 2, which delivered binding policy recommendations, this group will not. * Response: With respect to Rafik as vice-chair in EPDP, others had concerns with that also, particularly because Rafik ultimately had to step into the role of chair, and it’s not ideal to wear the hats of chair and liaison simultaneously. There are other options the group should consider, including requesting a vice chair from the GNSO Council. 1. Gap Analysis (50 minutes) * Continue review of input received from scoping team: https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit[d…<https://urldefense.com/v3/__https:/docs.google.com/document/d/11msexuoqWSUs…> * ALAC Gap Analysis: * The current goal of accuracy is the one embodied in the RAA, and this has a long history associated with it. The goal going into the discussion of the accuracy specification is to improve accuracy. Both the NORC and the accuracy study showed there was a significant accuracy issue that needed to be fixed. * The RAA is a bilateral negotiation between ICANN and registrars, and what came out of it was – “we agree to do some, but not all”. For example, the AFAV requirements have still not been implemented. * This is only a partial solution, and the original goal was not met, and the requirements detailed in the Whois Accuracy Spec are still not being enforced today. * In terms of the goals that were not met, could ALAC articulate the goals that were laid out and not met? * To make something accurate, is to make something useful and facilitate contact. Some level of verification that this will facilitate contact should be required. * Concerned about claims of no accuracy, while the WAPS did provide improvements. * Indeed, there was an improvement with the introduction of the WAPS. By way of example of something the WAPS did not do: registrars are required to verify either the phone or email address, but there is no flag added to RDDS to indicate which field was ultimately verified/usable. * Dispute that the WAPS was not effective; if you were to review the ARS reports, it showed accuracy levels significantly improve. Over 90% of domain names were contactable by at least one field (phone, email, postal address), and a majority were contactable in all three. Adding a flag in the RDDS would be a gargantuan task and a large expense. * Did not say that the WAPS was not effective at doing something. Believe for 70-80% of domain names at least one field that was not accurate. While 95% of names had an accurate field, it was unclear to others which field was actually accurate. Understand that information is maintained in terms of which field was actually verified. * The primary goal of this group is to gather objective facts. Could Rys or Rrs document changes to their systems, for example, the Chinese real name verification – could CPs give an idea of the magnitude of what was done for these changing requirements? This could be helpful for the Council to make an informed determination. * Request to put specific questions to stakeholder groups in writing. When it comes to costing, it is very unlikely that registries will share costing. * The 2013 RAA is almost 9 years old, and the cybercrime world has changed very significantly since 2013. * The RAA requires all contact details to be validated at some degree. * Believe that this verification should be done by an external body. * GAC Gap Analysis<https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit>: read into the record * May be worth more follow-up when GAC colleagues have returned – the goal in the group’s charter is to fully capture the current state. It’s difficult to go forward with work without a firm understanding of what accuracy is. This is a red flag that requires further work – the group should be convinced of what the current state is. * The purposes for processing listed here is not the same as the EPDP Phase 1 approved purposes * Question to ICANN org – Is the list provided at this link (https://whois.icann.org/en/what-registration-data-used) still relevant? * Citing SAC 058, which predates the 2013 RAA, may not be relevant anymore. * Any study that samples data, whether a SAC report or another report, raises the question of what it looks like today. Perhaps putting forward a nomenclature for accuracy, whether it is recognized as coming from this paper or not, would be helpful. * The question the scoping team should ask – whether this is being met, rather than it is unclear that it is being met. Need to look at this from a perspective: it is not being met, and here is the evidence to show this. Or, there is nothing showing it is not being met. It’s easier to prove a positive rather than a negative. * A significant part of ICANN’s ability to check accuracy, except on a case-by-case complaint basis, is that ICANN does not have access to the data. * 7.3.2 of the RAA – registrars shall abide by applicable laws and governmental regulations – the only time this was seen by ICANN is when registrars would say that something could not be done because it was prohibited by local law * Can GAC reps please explain what they mean by “a more holistic interpretation of the RAA”? * Without looking at new data, cannot verify that this conjecture is correct * Where numbers are cited, the source should also be cited. * Call into question the InterIsle numbers * The claim that there is a large amount of data that is not validated is simply incorrect. Would like to see numbers that showcase an interest in domain name registered more than ten years ago. * Next steps: With respect to the first part of the Gap Analysis, specifically questions 1 and 2, the ways in which data can or should be gathered to demonstrate whether or not certain requirements are being met. Some have claimed CPs should provide data, some said ICANN org or a third party should obtain the data. Through some of this data gathering, the team already receive information that could inform 3 and 4. * Scoping team input * Confirm next steps 1. Confirm action items & next meeting (Thursday 6 January at 14.00 UTC)

2 3