Dear colleages, I may be joining later to this call, due to unexpected issues I must attend. Please note my apologies for this inconvenience. Best regards Olga El mar, 9 nov 2021 a las 10:52, Marika Konings (<marika.konings@icann.org>) escribió:

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/1k9fvA4gnb13bN...>) 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/1arlKdQkbRkE1L...> 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) 1. 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**”**.*

1. Consider further input received on definition (see page 12 - https://docs.google.com/document/d/1k9fvA4gnb13bNbB8O4o72mXMZ8mQnJGC/edit)

2. Confirm working definition (current state)

1. Aspirational definition of accuracy (10 minutes) 1. Overview of homework assignment (see template - https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit ) 2. Scoping team input 3. Confirm next steps & deadline for input

1. Follow up questions to ICANN org regarding enforcement and Accuracy Reporting System (30 + minutes) 1. Note additional information added to the index of relevant resources from RDS-WHOIS2 RT, including responses to questions 2. Input received from scoping team to date: https://docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit 3. Scoping team input 4. Confirm deadline for submission of questions

1. Confirm action items & next meeting (Thursday 18 November at 14.00 UTC)

_______________________________________________ GNSO-Accuracy-ST mailing list GNSO-Accuracy-ST@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.