October 2021 - GNSO-Accuracy-ST

Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 04 November 2021 at 13:00 UTC
by Terri Agnew Oct. 21, 2021

Oct. 21, 2021

Reminder: The next call will be during ICANN72, Tuesday, 26 October at 12:30 local time (19:30 UTC). The zoom URL will be posted here<https://72.schedule.icann.org/meetings/LfJ22fzQsPhhFMPDD#/?limit=10&sortByF…> shortly before the meeting. Be sure you have registered<https://account.icann.org/login>! Below is the next call taking place after the ICANN72 meeting. Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 04 November 2021 at 13: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, 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/Lg2HCg * Check your time zone: https://tinyurl.com/5zkn6vmc ONLY for Members and Participants * 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. 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, 21 October 2021 at 13:00 UTC
by Terri Agnew Oct. 21, 2021

Oct. 21, 2021

**starting in 15 minutes Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 21 October 2021 at 13: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, 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/Kg2HCg * Check your time zone: https://tinyurl.com/u4nvazuh [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/u4nvazuh__;!!PtGJab4!q_jGr3P…> ONLY for Members and Participants * 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. 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

Registration Data Accuracy Scoping Team meeting
by ICANN Policy Calendar Oct. 21, 2021

Oct. 21, 2021

Meeting: Registration Data Accuracy Scoping Team meeting Date/time: Thursday, 21 October 2021 at 13: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, 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/Kg2HCg * Check your time zone: https://tinyurl.com/u4nvazuh ONLY for Members and Participants * 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. 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

**REMINDER** Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 21 October 2021 at 13:00 UTC
by Julie Bisland Oct. 20, 2021

Oct. 20, 2021

Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 21 October 2021 at 13: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, 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/Kg2HCg * Check your time zone: https://tinyurl.com/u4nvazuh [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/u4nvazuh__;!!PtGJab4!q_jGr3P…> ONLY for Members and Participants * 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. 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

Request
by Michael Palage Oct. 19, 2021

Oct. 19, 2021

Hello All, I would like to thank our RrSG colleagues for their contribution on a proposed definition of accuracy, and Steve’s contribution that has help tee up some material for our Thursday call. As I have previously stated I would really value all Working Group members contributing their thoughts via the mailing list or mark-ups on the Google Docs during the week to help tee up discussion points in advance of our weekly calls. I believe this approach is the best way to make most efficient use of our time. Over the past month I have discussed/reviewed a number of Stakeholder groups statements submitted to Brussels in connection with NIS 2.0. LET ME VERY CLEAR I AM NOT interjecting a substantive discussion of NIS 2.0. However, I have found these various communications informative to better understand how ICANN’s various stakeholder groups have articulated their version of ICANN’s existing contractual obligations with contracting parties. Therefore, I would respectfully request that these stakeholder groups share these communications via the list to allow us to better understand the respective viewpoints of these groups. Keep up the constructive dialog and please contribute. Best regards, Michael

1 0

**REMINDER TO REGISTER** ICANN72 GNSO Sessions - How to Get Organized / Remote Participation Details
by Julie Bisland Oct. 19, 2021

Oct. 19, 2021

Dear all, ICANN72 is right around the corner! This email provides some information to help you prepare and organize. Please note: You will need to register for ICANN72 to access the meeting schedule. Mandatory Registration for ICANN72 * Sign into your ICANN Account, or create an account here [account.icann.org]<https://urldefense.com/v3/__https:/account.icann.org/login__;!!PtGJab4!p_nH…>. * Register for ICANN72 by selecting Meeting Registration and click on the ICANN72 Registration link. Click here [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> for detailed instructions. Access the ICANN72 Schedule * ICANN72 schedule: https://72.schedule.icann.org/ [72.schedule.icann.org]<https://urldefense.com/v3/__https:/72.schedule.icann.org/__;!!PtGJab4!p_nHN…> For security purposes, participation links will be posted 24-hours prior to the session start times. * ICANN72 GNSO Sessions have been grouped on the ICANN72 GNSO wiki page<https://community.icann.org/x/CAFmCg>. Create your own schedule: * The ICANN Meeting website allows you to download all GNSO-related meetings to your inbox calendar in one go. For detailed instructions on how to create your personalized ICANN72 schedule and import your schedule to your calendar, click here [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…>. Review the Participation Tools and update Zoom * All sessions will use Zoom rooms. Access details are available 24hrs prior on the ICANN72 Meeting Schedule [72.schedule.icann.org]<https://urldefense.com/v3/__https:/72.schedule.icann.org/__;!!PtGJab4!p_nHN…>. * Visit the Participation Tools page [72.schedule.icann.org]<https://urldefense.com/v3/__https:/72.schedule.icann.org/participation-tool…> for links to download the latest version of Zoom for access to the ICANN72 sessions. * Please see the ICANN Meeting Virtual Participation How-To Guide [72.schedule.icann.org]<https://urldefense.com/v3/__https:/72.schedule.icann.org/attend*:*:text=vir…> for more information on how to get the most out of the virtual meeting tools. Links to Bookmark ICANN72 Meeting Schedule [72.schedule.icann.org]<https://urldefense.com/v3/__https:/72.schedule.icann.org/__;!!PtGJab4!p_nHN…> GNSO ICANN72 Wiki Page<https://community.icann.org/x/CAFmCg> GNSO Session agendas<https://community.icann.org/x/iIH8CQ> For all GNSO meeting-related queries (RP or others), please email us at: gnso-secs(a)icann.org and we will be more than happy to assist! Kind regards, GNSO SO/AC Support team -- 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

Re: [GNSO-Accuracy-ST] RrSG-Proposed Definition of Accuracy
by Steve Crocker Oct. 19, 2021

Oct. 19, 2021

Sarah, Doesn't section f of the Whois Accuracy Specification require *identity validation*, not just *operational (operable) validation*? If the RrSG is proposing *operational validation*, this seems to me a weakening of the current validation requirement and would not be consistent with section f. On the other hand, if the RrSG is proposing validation consistent with section f, the terminology *identity validation* would be consistent. Here's the text of section f: f. Verify: 1. the email address of the Registered Name Holder (and, if different, the Account Holder) by sending an email requiring an affirmative response through a tool-based authentication method such as providing a unique code that must be returned in a manner designated by the Registrar, or 2. the telephone number of the Registered Name Holder (and, if different, the Account Holder) by either (A) calling or sending an SMS to the Registered Name Holder's telephone number providing a unique code that must be returned in a manner designated by the Registrar, or (B) calling the Registered Name Holder's telephone number and requiring the Registered Name Holder to provide a unique code that was sent to the Registered Name Holder via web, email or postal mail. In either case, if Registrar does not receive an affirmative response from the Registered Name Holder, Registrar shall either verify the applicable contact information manually or suspend the registration, until such time as Registrar has verified the applicable contact information. If Registrar does not receive an affirmative response from the Account Holder, Registrar shall verify the applicable contact information manually, but is not required to suspend any registration. In SAC 058, the following definitions are provided: *Operational Validation* refers to the assessment of data for their intended use in their routine functions. Examples of operational validation include 1) checking that an email address or phone number can receive email or phone calls; 2) checking that a postal address can receive postal mail; 3) checking that the data entered are self-consistent, i.e. that all data are logically consistent with all other data. It is expected that many operational validation checks would be automated and some could be executed inline with a registration process. *Identity validation* refers to the assessment that the data corresponds to the real world identity of the entity. It involves checking that a data item correctly represents the real world identity for the registrant. In general, identity validation checks are expected to require some manual intervention. Thanks, Steve On Tue, Oct 19, 2021 at 8:50 AM Sarah Wyld <swyld(a)tucows.com> wrote: > Hello all, > > The RrSG members of the Accuracy Scoping team propose the following > definition of “accuracy” for domain name registration data, as per our > homework assignment: > > *"Accuracy shall be strictly defined as syntactical accuracy of the > registration data elements provided by the Registered Name Holder as well > as the operational accuracy of either the telephone number or the email > address."* > > To be determined to be *syntactically accurate*, the contact must satisfy > all requirements for validity (see Whois Accuracy Program Specification > <https://www.icann.org/resources/pages/approved-with-specs-2013-09-17-en#who…> > Sections 1b-d). E.g. for email addresses, all characters must be > permissible, the “@” symbol is required, there must be characters before > the “@” symbol (the “local” component), there must be a valid top-level > domain at the end, and there must be a valid domain after the “@” symbol, > but before a “.” and the valid top-level domain. > > To be determined to be *operably accurate*, the contact must be operable > as defined in the Whois Accuracy Program Specification > <https://www.icann.org/resources/pages/approved-with-specs-2013-09-17-en#who…> > Section f; in other words, the email must be deliverable, the telephone > number has to connect without an error message such as that the number is > invalid or disconnected, and the postal address must be mailable. > > The RAA currently requires validation of syntactical accuracy and > verification of operational accuracy for either email or phone. > > Thank you, > > > > -- > > *Sarah Wyld*, CIPP/E > > > > Policy & Privacy Manager > > Pronouns: she/they > > > > swyld(a)tucows.com > > +1.416 535 0123 Ext. 1392 > > > > > _______________________________________________ > GNSO-Accuracy-ST mailing list > GNSO-Accuracy-ST(a)icann.org > https://mm.icann.org/mailman/listinfo/gnso-accuracy-st > > _______________________________________________ > By submitting your personal data, you consent to the processing of your > personal data for purposes of subscribing to this mailing list accordance > with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and > the website Terms of Service (https://www.icann.org/privacy/tos) You can > visit the Mailman link above to change your membership status or > configuration, including unsubscribing, setting digest-style delivery or > disabling delivery altogether (e.g., for a vacation), and so on.

3 6

RrSG-Proposed Definition of Accuracy
by Sarah Wyld Oct. 19, 2021

Oct. 19, 2021

Hello all, The RrSG members of the Accuracy Scoping team propose the following definition of “accuracy” for domain name registration data, as per our homework assignment: "Accuracy shall be strictly defined as syntactical accuracy of the registration data elements provided by the Registered Name Holder as well as the operational accuracy of either the telephone number or the email address." To be determined to be syntactically accurate, the contact must satisfy all requirements for validity (see Whois Accuracy Program Specification Sections 1b-d). E.g. for email addresses, all characters must be permissible, the “@” symbol is required, there must be characters before the “@” symbol (the “local” component), there must be a valid top-level domain at the end, and there must be a valid domain after the “@” symbol, but before a “.” and the valid top-level domain. To be determined to be operably accurate, the contact must be operable as defined in the Whois Accuracy Program Specification Section f; in other words, the email must be deliverable, the telephone number has to connect without an error message such as that the number is invalid or disconnected, and the postal address must be mailable. The RAA currently requires validation of syntactical accuracy and verification of operational accuracy for either email or phone. Thank you, -- Sarah Wyld, CIPP/E Policy & Privacy Manager Pronouns: she/they swyld(a)tucows.com +1.416 535 0123 Ext. 1392

1 0

RrSG-Proposed Definition of Accuracy
by Sarah Wyld Oct. 19, 2021

Oct. 19, 2021

Hello all, The RrSG members of the Accuracy Scoping team propose the following definition of “accuracy” for domain name registration data, as per our homework assignment: "Accuracy shall be strictly defined as syntactical accuracy of the registration data elements provided by the Registered Name Holder as well as the operational accuracy of either the telephone number or the email address." To be determined to be syntactically accurate, the contact must satisfy all requirements for validity (see Whois Accuracy Program Specification Sections 1b-d). E.g. for email addresses, all characters must be permissible, the “@” symbol is required, there must be characters before the “@” symbol (the “local” component), there must be a valid top-level domain at the end, and there must be a valid domain after the “@” symbol, but before a “.” and the valid top-level domain. To be determined to be operably accurate, the contact must be operable as defined in the Whois Accuracy Program Specification Section f; in other words, the email must be deliverable, the telephone number has to connect without an error message such as that the number is invalid or disconnected, and the postal address must be mailable. The RAA currently requires validation of syntactical accuracy and verification of operational accuracy for either email or phone. Thank you, -- Sarah Wyld, CIPP/E Policy & Privacy Manager Pronouns: she/they swyld(a)tucows.com +1.416 535 0123 Ext. 1392

1 0

Proposed Agenda - Accuracy Scoping Team meeting on 18 October 2021
by Marika Konings Oct. 18, 2021

Oct. 18, 2021

Dear All, Please find below the proposed agenda for the next Registration Data Accuracy Scoping Team meeting which has been scheduled for Thursday 21 October at 13.00 UTC. As a reminder, please review the background briefings and provide your input on the remaining questions for discussion by COB today (18 October): * Background briefing assignment #2: https://docs.google.com/document/d/1LvqM6KlNGyTVQxe_l5v03-UWlsxo4AAl/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1LvqM6KlNGyTV…> * Background briefing assignment #3: https://docs.google.com/document/d/1S-bBG75O6VsGg4mhGgIsKKoUK7lDMO-w/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1S-bBG75O6VsG…> * Background briefing assignment #4: https://docs.google.com/document/d/1gvVN4IQjrkinQom0Xj_QGjTBTO-XkMri/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1gvVN4IQjrkin…> Also, please don’t forget to add your proposed follow up questions for ICANN org to the following document: * https://docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit Best regards, Caitlin, Berry and Marika Registration Data Accuracy Scoping Team – Meeting #3 Thursday 21 October at 13.00 UTC 1. Welcome & Chair Updates (10 minutes) * Miscellaneous administrative issues * ICANN72 session – Tuesday Tuesday 26 October (19.30 – 21.00 UTC). Proposed agenda: * Welcome & Introduction * High level overview of workplan * Open microphone * Confirm action items & next meeting (Thursday 4 November at 13.00 UTC) 1. Background briefing assignment #2 – see https://docs.google.c‌om/document/d/1OyzzAjZgvNkfZ5EekUvJ7PQg80vNZvJ3/edit<https://docs.google.com/document/d/1OyzzAjZgvNkfZ5EekUvJ7PQg80vNZvJ3/edit> * Review assignment #2 * Consider questions and team input received: * What information, if any, is missing to support the team’s deliberations on whether ARS needs a revamp or whether there are other ways in which accuracy levels can/should be measured? * What approach should the team take to develop these recommendations? * How much time and resources are expected to be needed to either revamp ARS or implement other ways in which accuracy levels can/should be measured? * Confirm next steps 1. Background briefing assignment #3 – see https://docs.google.com/document/‌d/1NiwMk6qHOQRn7VdcW0Paj5OoC3tWAQpm/edit<https://docs.google.com/document/d/1NiwMk6qHOQRn7VdcW0Paj5OoC3tWAQpm/edit> * Review assignment #3 * Consider questions and team input received: * What is necessary to undertake such an analysis? * What is the definition of “effective”? * How are “accurate and reliable” to be interpreted (see also assignment #1 re. working definitions)? * What next steps and approach should the team take to address this assignment? * Confirm next steps 1. Background briefing assignment #4 - see https://docs.google.com/document/d/1Z8t-uH4gRqXytHOGnIkZ2qMSJctgR_kD/edit * Review assignment #4 * Consider questions and team input received: * When & how are estimates of benefits and costs expected to be developed? * In addition to outcome of assignment #1-3 and cost/benefit analysis, is there anything further that is needed for the scoping team to deliberate on whether any changes are needed to improve accuracy levels? * Based on response to previous question, what are the options the team can consider for how and by whom these changes would need to be developed? * What next steps and approach should the team take to address this assignment? * Confirm next steps 1. Confirm action items & next meeting (ICANN72 session on Tuesday 26 October at 19.30 UTC)

1 0