[GNSO-Accuracy-ST] RrSG-Proposed Definition of Accuracy

[Steve Crocker]

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 at 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#whois-accuracy>
> 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#whois-accuracy>
> 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 at tucows.com
>
> +1.416 535 0123 Ext. 1392
>
>
>
>
> _______________________________________________
> GNSO-Accuracy-ST mailing list
> GNSO-Accuracy-ST at 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/gnso-accuracy-st/attachments/20211019/b841572a/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 66DD891F1CD140B8B082E775A55F2328[15001114917].png
Type: image/png
Size: 3031 bytes
Desc: not available
URL: <https://mm.icann.org/pipermail/gnso-accuracy-st/attachments/20211019/b841572a/66DD891F1CD140B8B082E775A55F232815001114917-0001.png>