Hello All,
Following the ALAC policy call today, there was a reference to a recent ICANN SSAD blog post toward the end of the call. I found it interesting that this blog post provides greater detail and insight on the issue of identity verification and ICANN Compliance’s potential future role, see https://www.icann.org/en/blogs/details/ssad-odp-update-contractual-compliance-and-identity-verification-methodology-2-11-2021-en
To be clear I am not proposing a change to our current working “definition” which I think we are pretty close to reaching consensus on. However, how ICANN defines “accuracy” becomes a little more interesting from this bigger perspective and could impact groups future aspirational definitions.
Melina, for one, I know has repeatedly referenced the term accuracy as it appears in the ICANN by-laws.
During the ALAC there was a separate discussion on the 60 day lock period after the registration of a domain name. I made a comment about how the original 60 day lock was a mechanism to allow Registrars to recoup any loses associated with credit card fraud, but then Jeff Neuman pointed out how that 60 day provision has evolved and has been linked to other policies/procedures.
I wanted to raise this point because I think it is important for us to not only be respectful of the past but to keep an eye toward the future and how things could evolve.
Just some food for thought. Please try and share your thoughts in advance of tomorrow’s call to make most efficient use of our time together.
Best regards,
Michael
From: GNSO-Accuracy-ST <gnso-accuracy-st-bounces@icann.org> On Behalf Of Michael Palage
Sent: Wednesday, November 10, 2021 8:17 AM
To: 'Marika Konings' <marika.konings@icann.org>; gnso-accuracy-st@icann.org
Subject: Re: [GNSO-Accuracy-ST] Proposed Agenda - Accuracy Scoping Team meeting #5 - Thursday 11 November at 14.00 UTC
Hello All,
I really encourage everyone to read this document which Marika just shared with the list. However, to help motivate everyone to read this document, I thought this little excerpt of “red meat” might help with this reading assignment.
5. What's the latest progress of WHOIS ARS Phase 3? Are there any means identified how to conduct identity validation?
ICANN org has looked into identity verification or validation as part of the phase 3 work of the ARS, but was not able to identify any services that would meet the intent of identity verification.
Happy reading.
Best regards,
Michael
From: GNSO-Accuracy-ST <gnso-accuracy-st-bounces@icann.org> On Behalf Of Marika Konings
Sent: Wednesday, November 10, 2021 7:49 AM
To: gnso-accuracy-st@icann.org
Subject: Re: [GNSO-Accuracy-ST] Proposed Agenda - Accuracy Scoping Team meeting #5 - Thursday 11 November at 14.00 UTC
Dear All,
To facilitate your input for agenda item #4, please find attached a compilation of the ICANN org answers to a number of accuracy related questions posed by the WHOIS-RDS2 Review Team back in 2018.
Best regards,
Caitlin, Berry and Marika
From: GNSO-Accuracy-ST <gnso-accuracy-st-bounces@icann.org> on behalf of Marika Konings <marika.konings@icann.org>
Date: Tuesday, 9 November 2021 at 14:52
To: "gnso-accuracy-st@icann.org" <gnso-accuracy-st@icann.org>
Subject: [GNSO-Accuracy-ST] Proposed Agenda - Accuracy Scoping Team meeting #5 - Thursday 11 November at 14.00 UTC
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:
Best regards,
Caitlin, Berry and Marika
Registration Data Accuracy Scoping Team – Meeting #5
Thursday 11 November at 14.00 UTC
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”.