Page History
...
For other places see: https://tinyurl.com/5zkn6vmc
Info |
---|
PROPOSED AGENDA
2. Proposed Work plan & timeline a. Review proposed work plan & timeline b. Confirm next steps 3. Working definition of accuracy 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”.
4. Follow up questions to ICANN org regarding enforcement and Accuracy Reporting System 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 11 November at 14.00 UTC) BACKGROUND DOCUMENTS |
Info | ||
---|---|---|
| ||
GNSO transcripts are located on the GNSO Calendar |
Tip | ||
---|---|---|
| ||
Apologies: Toba Obaniyi |
Note |
---|
Notes/ Action Items Action Items
Registration Data Accuracy Scoping Team – Meeting #4 Thursday 4 November at 13.00 UTC
2. Proposed Work plan & timeline a. Review proposed work plan & timeline
b. Confirm next steps
3. Working definition of accuracy 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”.
4. Follow up questions to ICANN org regarding enforcement and Accuracy Reporting System 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 11 November at 14.00 UTC)
|