March 2022 - GNSO-Accuracy-ST

April, May and June 2022 | Registration Data Accuracy Scoping Team
by Terri Agnew March 31, 2022

March 31, 2022

Dear all, Please find the recurring .ics attachment and dates listed below for the Registration Data Accuracy Scoping Team calls taking place in April, May and June 2022. Please download them to your calendar. Depending on your calendar, you may need to select recurring on the .ics attachment. Calls take place at 14:00 UTC for 90 minutes. The dates are as follows: · Thursday, 07 April 2022 - email invite sent as this is the next meeting · Thursday, 14 April 2022 - (call time TBD, once determined a stand-alone invite will be sent) · Thursday, 21 April 2022 - recurring ics attachment is 21 April – 02 June 2022 · Thursday, 28 April 2022 · Thursday, 05 May 2022 · Thursday, 12 May 2022 · Thursday, 19 May 2022 · Thursday, 26 May 2022 · Thursday, 02 June 2022 · Thursday, 09 June 2022 The email invitation for each call will be sent out closer to the date of the meeting. The next call takes place on 07 April 2022 and the invitation has been sent out. Thank you. Kind regards, Terri

1 0

Registration Data Accuracy Scoping Team meeting
by ICANN Policy Calendar March 31, 2022

March 31, 2022

Meeting: Registration Data Accuracy Scoping Team meeting Date/time: Recurring weekly on Thursdays at 14:00 UTC for 90 minutes, 21 April – 02 June 2022 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 2022 Wiki agenda pages: https://community.icann.org/x/7ID3Cg (see dates on the left column) * Check your time zone: https://tinyurl.com/staz76cv 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://forms.gle/GZqMAi4kKDaVP5o66> 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.

1 0

Question to the team | Adjustment of 14 April 2022 start time | Registration Data Accuracy Scoping Team
by Terri Agnew March 31, 2022

March 31, 2022

Dear all, At this time Registration Data Accuracy Scoping Team calls are only scheduled out until Thursday, 07 April 2022, we are in the process of scheduling them weekly on Thursdays (14:00 UTC) until June 2022 (ICANN74). There will be a conflict with the GNSO Council call (13:00-15:00 UTC) on Thursday, 14 April 2022. Moving the team call to Friday, 15 April 2022 would conflict with a holiday for many countries. Question to the team: Would it be possible to move Thursday, 14 April RDA ST Team call time from 14:00-15:30 UTC to 15:00-16:30 UTC ( to start after the GNSO Council call)? Thank you for this consideration in advance, Terri

2 2

Registration Data Accuracy Scoping Team | Thursday, 31 March 2022
by Terri Agnew March 31, 2022

March 31, 2022

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

Please complete | poll | ICANN74 RDA ST Team meeting
by Terri Agnew March 31, 2022

March 31, 2022

Dear RDA ST Team members and alternate, As discussed on today’s call, please complete the google poll to help us determine a team meeting during ICANN74 (13-16 June 2022). Google poll: https://forms.gle/wt5jeA6VgY6iKTYo7 Thank you. Kind regards, Terri

1 0

Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 07 April 2022 at 14:00 UTC
by Terri Agnew March 31, 2022

March 31, 2022

Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 07 April 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<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/0Ad1Cw * Check your time zone: https://tinyurl.com/5n9a3266 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, 31 March 2022 at 14:00 UTC
by Terri Agnew March 31, 2022

March 31, 2022

**Starting in 15 minutes Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 31 March 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<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/7hQiCw * Check your time zone: https://tinyurl.com/mr2usskt [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/mr2usskt__;!!PtGJab4!rurDBKF…> 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

3 2

**REMINDER** Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 31 March 2022 at 14:00 UTC
by Julie Bisland March 30, 2022

March 30, 2022

Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 31 March 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<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/7hQiCw * Check your time zone: https://tinyurl.com/mr2usskt [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/mr2usskt__;!!PtGJab4!rurDBKF…> 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 #23 on Thursday 31 March at 14.00 UTC
by Marika Konings March 29, 2022

March 29, 2022

Dear All, Please find below the proposed agenda for the next Registration Data Accuracy Scoping Team meeting which is scheduled for Thursday 31 March at 14.00 UTC. As a reminder: 1. Scoping Team members to review the updates to the Accuracy working description [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1e5rUm-AFFDgN…> and propose FINAL edits by Wednesday, 30 March. Support Staff will lock the document after the deadline. 2. Scoping Team members to consider the Gap Analysis [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1sScP8MwgDCg4…> and specifically review the “next steps” column of each proposal by Wednesday, 30 March. The group will begin by discussing the potential next steps for Proposal A during the next meeting on 31 March, so please come prepared for this discussion. 3. STILL OUTSTANDING: IPC Reps to respond to the comments directed to IPC in Proposal H of the Gap Analysis [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1sScP8MwgDCg4…>. Best regards, Caitlin, Berry and Marika Registration Data Accuracy Scoping Team – Meeting #23 Thursday 31 March at 14.00 UTC 1. Welcome & Chair Updates (5 minutes) 2. Commence deep dive of Gap Analysis Data Collection Proposals (60 minutes) (see https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit) a. Proposal A – Survey Registrars b. Proposal B – Third Party Assessment (if time allows) c. Proposal D – ICANN org Registrar Audit (if time allows) d. Proposal E – Review of Accuracy Complaints (if time allows) e. Confirm next steps 1. Accuracy description of current requirements and enforcements (15 minutes) * Review input received on proposed description of current accuracy requirements and enforcement (see https://docs.google.com/document/d/1e5rUm-AFFDgNOU3OcT7ABu4InGwPiUyb/edit) * Confirm next steps 1. Confirm action items & next meeting (Thursday 7 April at 14.00 UTC)

1 0

Notes and action items: RDA Scoping Team Meeting #22
by Caitlin Tubergen March 25, 2022

March 25, 2022

Dear RDA Scoping Team Members, Please find below the notes and action items from today’s call. The next meeting will be Thursday, 31 March at 14:00 UTC. Best regards, Marika, Berry, and Caitlin -- Action Items 1. Scoping Team members to review the updates to the Accuracy working description<https://docs.google.com/document/d/1e5rUm-AFFDgNOU3OcT7ABu4InGwPiUyb/edit> and propose FINAL edits by Wednesday, 30 March. Support Staff will lock the document after the deadline. 2. Scoping Team members to consider the Gap Analysis<https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit> and specifically review the “next steps” column of each proposal by Wednesday, 30 March. The group will begin by discussing the potential next steps for Proposal A during the next meeting on 31 March, so please come prepared for this discussion. 3. STILL OUTSTANDING: IPC Reps to respond to the comments directed to IPC in Proposal H of the Gap Analysis<https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit>. Registration Data Accuracy Scoping Team – Meeting #22 Thursday 24 March at 14.00 UTC 1. Welcome & Chair Updates (5 minutes) 1. Accuracy working definition / construct (30 minutes) * Consider input received on proposed description of current accuracy requirements and enforcement (see https://docs.google.com/document/d/1e5rUm-AFFDgNOU3OcT7ABu4InGwPiUyb/edit) * RySG proposed edits to the definition * First change: updating the introduction, which now includes “measured against a specified standard” – believe this inclusion is imperative for the work on Question 2 * Also proposed alternative text re: the base registry agreement (additional context was provided over the list for those who are interested on 23 March) – the new text notes that there are no explicit provisions in the base registry agreement that refer to accuracy. * Question: is the position that Spec 13 does not apply? * Spec 13 is about eligibility criteria – maybe the annual audits on Spec 13 could be useful * Agree with this proposed language – only proposed edit is to include the auditing * If this is a specific registry requirement – that does not seem to be a good analog to regular domain names; accordingly, would support these changes to the definition * No reference to auditing here b/c consider Spec 13 is not included in the base registry agreement. The audit reference is included in the background information on the list. If we did want to include the auditing information, could include the references to Spec 11 and Spec 12 * A unique use case may not be applicable to the general standard * It’s the view of the group that the definition should represent the baseline from which to measure. Spec 13 does not represent the baseline requirements * Find it helpful to go back to the Council assignment, particularly: “The Scoping Team will assess the measures, including proactive measures, used by ICANN Compliance to monitor, measure, enforce and report on the accuracy obligations as specified in the Registry Agreements (RAs) and Registrar Accreditation Agreement (RAA). This assessment will include consideration of what compliance with the existing contractual data accuracy obligations means.” Find it interesting that the proposed definition is currently trying to include every possible thing a contracted party may include with respect to accuracy. This group should be focusing on the baseline obligation that is required by everyone. * Are contracted parties required to comply with national law? CPs are required to comply with applicable law. * Reason this question is being raised – aware of NIS2, it would be helpful for this group to look at existing accuracy requirements. If ICANN Compliance is not going to look at national law, it would be helpful to know that. * Perhaps could include something like, “which are applicable to those TLDs” – not sure that we need to be more specific about the current requirements other than referencing that some registries may have additional requirements * Agree with this. Have a concern with the newly-added language (during the meeting) regarding “patently inaccurate” * The assignment is to document the current enforcement * There seems to be in, principle agreement, to Sophie’s edits; accept the changes and then go back to other changes * The second paragraph includes changes from Melina made during this call, and a question posed from Alan Greenberg. * Concerned as additional paragraphs are layered on – this group is setting itself up for a contradiction. Something can be operable, but not be true – for example, if someone moves and forgets to update their address at their registrar. Believe the group should tone down the use of “accuracy of registration data” as accuracy has never applied in its pure form to registration data. * Cannot put a pure definition of accuracy into a registration system if meeting that term will cost money and price us out of business * The reference to “specified standard” references the later paragraphs that go into detail about what the RAA says * Accurate, reliable, and up-to-date comes directly from the RAA * Recommend using the mailing list to wrap up the definition discussion * This is meant to be used to describe what accuracy currently means and how it is enforced so the group can begin assignment 2 – we will propose a firm deadline for when suggestions are due * Review survey responses – see https://docs.google.com/forms/d/e/1FAIpQLSdL-R4Tk7pP86bMIRMX1tH1IA9-UgbHFYV… * 10 responses, and it is pretty 50/50 in terms of responses * Confirm next steps 3. Continue review of Gap Analysis Data Collection Proposals (30 minutes) (see https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit) a. Review Scoping Team input on proposals (upside, downside and possible next steps) * No further input has been received from groups – not sure if that means everyone is OK with what is currently in the document. * A specific question was posed to IPC regarding proposal H * Regarding the RDS 2 recommendations: LE.1 is included in the prioritization exercise that is currently ongoing. CC.1 was referred to the GNSO Council by the ICANN Board – one was considered addressed, but for this one specifically – the Council did indicate that further consideration needs to be given to that item. This does need to be considered, but perhaps not in the context of these proposals. * BC wanted to make sure these recommendations were noted. Felt these recommendations would contribute to the accuracy of the data. For example, with CC.1 there is no indication why a domain name is suspended. A lot of work was done by the review team, but none of it has been implemented b. Confirm next steps * Too close to call an end to assignment 2 – the group has noted areas where additional gather could be gathered, but more information is needed – who needs to gather, who needs to be involved * Once the group looks at what is in the realm of possibilities, it would be helpful to note a ranking – what should be done first or in parallel? Are there other things the group can work on in parallel? * This document warrants more discussion * Could start thinking through the next steps from Proposal A and work way down * In terms of next call, would encourage the group to take a look at CC.1 recommendation – in reaction to comments not being implemented – this specific recommendation has direct implications to an existing consensus policy. Would be helpful for this group to review this in detail – would this, in fact, require additional policy development so that it can be implemented? This has been an item on the program management tool that needs to be resolved. * There are two ways to affect this: (1) updates to consensus policy; (2) RAA updates * The extent to which we can address this is to recommend additional action, but need to consider this in more detail 1. Confirm action items & next meeting (Thursday 31 March at 14.00 UTC)

1 0