Page History
...
For other places see: https://tinyurl.com/znz8kmf4
Info |
---|
PROPOSED AGENDA
2. 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”.
3. Aspirational definition of accuracy (10 minutes) a. Overview of homework assignment (see template - https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit [docs.google.com]) b. Scoping team input c. Confirm next steps & deadline for input 4. Follow up questions to ICANN org regarding enforcement and Accuracy Reporting System (30 + minutes) a. Note additional information added to the index of relevant resources from RDS-WHOIS2 RT, including responses to questions b. input received from scoping team to date: https://docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit[docs.google.com] c. Scoping team input d. Confirm deadline for submission of questions 5. Confirm action items & next meeting (Thursday 18 November at 14.00 UTC)
BACKGROUND DOCUMENTS As a reminder:
|
Info | ||
---|---|---|
| ||
GNSO transcripts are located on the GNSO Calendar |
Tip | ||
---|---|---|
| ||
Apologies: Sarah Wyld, Melina Stroungi Alternate: Owen Smigelski |
Note |
---|
Notes/ Action Items Action Items
2. By Thursday, 2 December, each group to identify their future explanation of Accuracy [docs.google.com], 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
2. 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”.
b. Confirm working definition (current state)
3. Aspirational definition of accuracy (10 minutes) a. Overview of homework assignment (see template - https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit [docs.google.com])
b. Scoping team input
c. Confirm next steps & deadline for input 4. Follow up questions to ICANN org regarding enforcement and Accuracy Reporting System (30 + minutes) a. Note additional information added to the index of relevant resources from RDS-WHOIS2 RT, including responses to questions b. Input received from scoping team to date: https://docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit[docs.google.com] c. Scoping team input
c. Confirm deadline for submission of questions 5. Confirm action items & next meeting (Thursday 18 November at 14.00 UTC) |