[GNSO-Accuracy-ST] Proposed Agenda - Registration Data Accuracy Scoping Team Meeting #1 - Tuesday 5 October at 14.00 UTC
steve at shinkuro.com
Tue Oct 5 01:22:54 UTC 2021
Attached is a rough attempt at capturing the validation requirements listed
in the first few pages of assignment 1. The validation settings are in the
column labeled VAL. The settings V0, V1, V2 and V3 align with the
definitions in SAC 058, which are repeated on the first page of assignment
2. V0 indicates no validation, i.e. accept whatever the registrant
supplies. V1 indicates syntactic validation, V2 indicates operational
validation, and V3 indicates identity validation.
The COLL column indicates whether the data element is required (Collect),
optional (Optional), or left up to the registrar (Any). The SENS column
indicates the sensitivity of the data element. S0 indicates "public." In
other cases, the degree of sensitivity or a range of possible sensitivity
settings is indicated. (There is more to explain about this part of the
system, but the focus of this message is only to capture the accuracy
The STORE column indicates whether ICANN stores the data element. Since
ICANN does require escrow of data, it can be argued these data elements
should be set to STORE. As with the sensitivity settings, this is subject
to further discussion but is outside the scope of this message.)
Are the validation settings shown here an accurate expression of the policy
and contractual requirements?
Regarding the meeting tomorrow, I have a conflict after 30 minutes. Going
forward, this time slot will generally be ok for me, although the conflict
I have tomorrow may occur every three months. I'm also open to other time
On Mon, Oct 4, 2021 at 9:57 AM Marika Konings <marika.konings at icann.org>
> Dear All,
> Please find below the proposed agenda for the first meeting of the
> Registration Data Accuracy Scoping Team.
> Best regards,
> Caitlin, Berry and Marika
> *Registration Data Accuracy Scoping Team – Meeting #1*
> Tuesday 5 October at 14.00 UTC
> 1. Welcome and introductions (30 minutes)
> 1. Each team member to introduce themselves and share objectives
> for this effort (results of survey to be shared in advance of the meeting)
> 2. Consider how objectives align and how obstacles can be avoided.
> 2. Required documents for review by Scoping Team (10 minutes)
> 1. Council instructions and assignments (see
> 2. Index of relevant resources (see
> 3. Assignment Background briefings:
> - Assignment #1 -
> - Assignment #2 -
> - Assignment #3 -
> - Assignment #4 -
> 1. Discuss proposed next steps (15 minutes)
> 1. Diversity and inclusiveness
> 2. Meeting frequency / timing: proposal is to start with weekly
> plenary sessions to go through background briefings and develop work plan.
> Following that, try agile approach and have small teams make progress on
> work items.
> 3. All team members are expected to have reviewed the items under
> #2 by the next meeting.
> 4. All team members to provide input on the questions identified in
> assignment background briefing #1 - 4 by the next meeting – walk through of
> assignment background briefings and related questions will commence during
> next week’s meeting.
> 2. Confirm action items & next meeting (Tuesday 12 October at 14.00
> GNSO-Accuracy-ST mailing list
> GNSO-Accuracy-ST at icann.org
> By submitting your personal data, you consent to the processing of your
> personal data for purposes of subscribing to this mailing list accordance
> 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...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Accuracy 2021-10-04.pdf
Size: 194628 bytes
Desc: not available
More information about the GNSO-Accuracy-ST