[GNSO-Accuracy-ST] Proposed Agenda - Registration Data Accuracy Scoping Team Meeting #1 - Tuesday 5 October at 14.00 UTC
michael at palage.com
Tue Oct 5 02:28:55 UTC 2021
First thanks for completing the survey and getting a head start on some of our future work – you get the Chair’s first Gold Star for Working Group Participation😊
One of the questions I would like to pose to you, Jeff and the rest of your SSAC colleagues is the following. SAC 058 was written in 2013 - over 8 years ago. Since that time there has been a substantial amount of work done internationally on identity/accuracy proofing standards. Has SSAC ever revised a previously published SAC document to make sure that it is still up to date with current international and industry best practices?
Specifically, I would like to address your validation levels V0, V1, V2, and V3. Under older NIST Guidelines (Version 1.0.2. -2011) I believe there were 4 recognized assurance levels. However, under the current NIST SP 800-63a Digital Identity Guidelines (https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-63a.pdf) there are now 3 Identity Assurance Levels (IAL) NOT 4. These three assurance levels also align with the levels in the current EU eIDAS Regulation (2016) (low, substantial and high), see https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eIDAS+Levels+of+assurance
So please keep up the excellent work and I look forward to hearing any additional feedback from you and Jeff.
From: GNSO-Accuracy-ST <gnso-accuracy-st-bounces at icann.org> On Behalf Of Steve Crocker
Sent: Monday, October 4, 2021 9:23 PM
To: gnso-accuracy-st at icann.org
Subject: Re: [GNSO-Accuracy-ST] Proposed Agenda - Registration Data Accuracy Scoping Team Meeting #1 - Tuesday 5 October at 14.00 UTC
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 requirement.)
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 slots.
On Mon, Oct 4, 2021 at 9:57 AM Marika Konings <marika.konings at icann.org <mailto:marika.konings at icann.org> > wrote:
Please find below the proposed agenda for the first meeting of the Registration Data Accuracy Scoping Team.
Caitlin, Berry and Marika
Registration Data Accuracy Scoping Team – Meeting #1
Tuesday 5 October at 14.00 UTC
1. Welcome and introductions (30 minutes)
a. Each team member to introduce themselves and share objectives for this effort (results of survey to be shared in advance of the meeting)
b. Consider how objectives align and how obstacles can be avoided.
2. Required documents for review by Scoping Team (10 minutes)
a. Council instructions and assignments (see https://community.icann.org/x/QoFaCg)
b. Index of relevant resources (see https://community.icann.org/x/SoFaCg)
c. Assignment Background briefings:
* Assignment #1 - <https://docs.google.com/document/d/16mFQkzM4tTj84736J-tlZ8T7tFeiFwfx/edit> https://docs.google.com/document/d/16mFQkzM4tTj84736J-tlZ8T7tFeiFwfx/edit
* Assignment #2 - <https://docs.google.com/document/d/1OyzzAjZgvNkfZ5EekUvJ7PQg80vNZvJ3/edit> https://docs.google.com/document/d/1OyzzAjZgvNkfZ5EekUvJ7PQg80vNZvJ3/edit
* Assignment #3 - <https://docs.google.com/document/d/1NiwMk6qHOQRn7VdcW0Paj5OoC3tWAQpm/edit> https://docs.google.com/document/d/1NiwMk6qHOQRn7VdcW0Paj5OoC3tWAQpm/edit
* Assignment #4 - <https://docs.google.com/document/d/1Z8t-uH4gRqXytHOGnIkZ2qMSJctgR_kD/edit> https://docs.google.com/document/d/1Z8t-uH4gRqXytHOGnIkZ2qMSJctgR_kD/edit
3. Discuss proposed next steps (15 minutes)
a. Diversity and inclusiveness
b. 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.
c. All team members are expected to have reviewed the items under #2 by the next meeting.
d. 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.
4. Confirm action items & next meeting (Tuesday 12 October at 14.00 UTC)
GNSO-Accuracy-ST mailing list
GNSO-Accuracy-ST at icann.org <mailto:GNSO-Accuracy-ST at icann.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the GNSO-Accuracy-ST