December 2021 - GNSO-Accuracy-ST

Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 23 December 2021 at 14:00 UTC
by Julie Bisland Dec. 16, 2021

Dec. 16, 2021

Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 23 December 2021 at 14:00 UTC for 90 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09<https://urldefense.com/v3/__https:/icann.zoom.us/j/94504686990?pwd=MWc2eXZE…> Passcode: Vc#0B7$pu8 For Audio only: Or One tap mobile : US: +13017158592,,94504686990#,,,,*4631547480# or +13126266799,,94504686990#,,,,*4631547480# Webinar ID: 945 0468 6990 Passcode: 4631547480 International numbers available: https://icann.zoom.us/u/akRu7JTFd <https://urldefense.com/v3/__https:/icann.zoom.us/u/akRu7JTFd__;!!PtGJab4!pY…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, alternates and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/6wC7Cg * Check your time zone: https://tinyurl.com/86rd6h57 ONLY for Members and Alternates * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. * Alternate replacement confirmations – In order to keep track of alternate replacements, use the google form <https://urldefense.com/v3/__https:/forms.gle/GZqMAi4kKDaVP5o66__;!!PtGJab4!…> to communicate who the alternate is replacing and for which period. This information will be publicly posted so that the Team is aware at any time who is active. Alternate Assignment –wiki page<https://community.icann.org/x/-wC7Cg>. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Julie

1 0

**ON IN 2 MINUTES** Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 16 December 2021 at 13:00 UTC
by Julie Bisland Dec. 16, 2021

Dec. 16, 2021

**ON IN 2 MINUTES** Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 16 December 2021 at 13:00 UTC for 60 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09<https://urldefense.com/v3/__https:/icann.zoom.us/j/94504686990?pwd=MWc2eXZE…> Passcode: Vc#0B7$pu8 For Audio only: Or One tap mobile : US: +13017158592,,94504686990#,,,,*4631547480# or +13126266799,,94504686990#,,,,*4631547480# Webinar ID: 945 0468 6990 Passcode: 4631547480 International numbers available: https://icann.zoom.us/u/akRu7JTFd <https://urldefense.com/v3/__https:/icann.zoom.us/u/akRu7JTFd__;!!PtGJab4!pY…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, alternates and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/6AC7Cg * Check your time zone: https://tinyurl.com/46r8k6yt [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/46r8k6yt__;!!PtGJab4!rEPOexg…> ONLY for Members and Alternates * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Panelists and Attendees, or Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. * Alternate replacement confirmations – In order to keep track of alternate replacements, use the google form <https://urldefense.com/v3/__https:/forms.gle/GZqMAi4kKDaVP5o66__;!!PtGJab4!…> to communicate who the alternate is replacing and for which period. This information will be publicly posted so that the Team is aware at any time who is active. Alternate Assignment –wiki page<https://community.icann.org/x/-wC7Cg>. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Terri

1 0

Re: [GNSO-Accuracy-ST] [Ext] RE: Proposed Agenda - Registration Data Accuracy Scoping Team meeting #10 on Thursday 16 December at 13.00 UTC
by Marika Konings Dec. 16, 2021

Dec. 16, 2021

Thanks, Marc. To respond to your comment “I’m not sure where those edits came from”, we thought it might be helpful to clarify why this proposed change was made. On several calls representatives from the RrSG have indicated that what they put forward is not necessarily a “working definition” but more like a description of what Contracted Parties are currently required to do. As such, we thought it might be better to refer to it in that way as in the question it is attributed to the RrSG. Of course, if the RrSG has no issues with it being referred to as a “working definition” we can easily make the update as you suggested below. We hope this background is helpful. Best regards, Caitlin, Berry and Marika From: "Anderson, Marc" <mcanderson(a)verisign.com> Date: Thursday, 16 December 2021 at 03:45 To: Marika Konings <marika.konings(a)icann.org>, "gnso-accuracy-st(a)icann.org" <gnso-accuracy-st(a)icann.org> Subject: [Ext] RE: Proposed Agenda - Registration Data Accuracy Scoping Team meeting #10 on Thursday 16 December at 13.00 UTC Accuracy scoping team, Apologies for sending this so late. For question 21 in the reorganized questions to ICANN org, I don’t provide the complete text of the current definition that registrars proposed on accuracy. It has been pointed out to me by a couple of people that this loses some important context. I am suggesting edits to include the entirety of the registrar proposal. I also note that there have been some edits to my original text. I’m not sure where those edits came from but the seeming intent is to remove the word definition from the text. As I recall, on a previous call there was concern raised about calling the registrars proposed current definition of accuracy a “working definition” as that working definition might become the permanent definition. I thought registrars made it clear on that call they did not propose this as what the accuracy definition should be, but rather to capture their current understanding of accuracy obligations under the RAA. The entire text of the first charge to the scoping team in our instructions from council is: 1. Enforcement and reporting: The Scoping Team will assess the measures, including proactive measures, used by ICANN Compliance to monitor, measure, enforce and report on the accuracy obligations as specified in the Registry Agreements (RAs) and Registrar Accreditation Agreement (RAA). This assessment will include consideration of what compliance with the existing contractual data accuracy obligations means. 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. In proposing my question, I am trying to understand the definition that ICANN Compliance employs for accuracy in ICANN’s contracts, as we have been instructed by council. I would also like to understand if ICANN compliance agrees with the current definition provided by registrars, thus the question. I don’t know how we can understand the current definition ICANN compliance employs for accuracy without using the word definition. I have added language to hopefully clarify that this is an effort to understand the current state of accuracy, not an attempt to suggest what the definition of accuracy should be. I hope that addresses concern over the use of the word definition. Updated question to ICANN org: As part of the accuracy scoping team’s effort to undertake a fact based survey of the current state of accuracy in the ICANN context, registrars proposed the following working definition of accuracy based on current contractual and consensus policy requirements (https://mm.icann.org/pipermail/gnso-accuracy-st/2021-October/000086.html) Accuracy shall be strictly defined as syntactical accuracy of the registration data elements provided by the Registered Name Holder or Account 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 Sections 1b-d). For example, for email addresses all characters must be permissible, the “@” symbol is required, and there must be characters before the “@” symbol. To be determined to be operably accurate, the contact must be operable as defined in the Whois Accuracy Program Specification Section f. The RAA currently requires validation of syntactical accuracy and verification of operational accuracy including an affirmative response from the Registered Name Holder for either email or phone. In proposing this working definition registrars are not suggesting that this is what the definition of accuracy should be, but rather capturing what it currently is to inform the work of the scoping team. The council instructions to the scoping team (https://community.icann.org/display/AST/2.+Council+Instructions+to+Scoping+…) include the following charge: 1. Enforcement and reporting: The Scoping Team will assess the measures, including proactive measures, used by ICANN Compliance to monitor, measure, enforce and report on the accuracy obligations as specified in the Registry Agreements (RAs) and Registrar Accreditation Agreement (RAA). This assessment will include consideration of what compliance with the existing contractual data accuracy obligations means. 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. Does ICANN Compliance agree with the working definition proposed by registrars? What definition does ICANN compliance employ for “accuracy” in ICANN’s contracts? Given the above instructions from council, the scoping team is attempting to understand ICANN compliance’s definition of accuracy, and what compliance with existing contractual data accuracy obligations means to better inform our work. From: GNSO-Accuracy-ST <gnso-accuracy-st-bounces(a)icann.org> On Behalf Of Marika Konings Sent: Tuesday, December 14, 2021 8:27 AM To: gnso-accuracy-st(a)icann.org Subject: [EXTERNAL] [GNSO-Accuracy-ST] Proposed Agenda - Registration Data Accuracy Scoping Team meeting #10 on Thursday 16 December at 13.00 UTC Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Dear All, Please find below the proposed agenda for the next Registration Data Accuracy Scoping Team meeting which is scheduled for Thursday 16 December at 13.00 UTC. You will find attached for your review the reorganized questions for ICANN org (see agenda item #2). As discussed, we’ve aimed to group similar questions together to facilitate the development of responses. In redline you will find some edits that we are proposing to make, mainly for clarity, consistency and/or referencing. If you have any comments or concerns about this reorganization and/or proposed edits, please flag these on the mailing list in advance of the meeting. As a reminder: * Groups who have not provided inputs for the Gap Analysis (BC, GAC, ISPCP, NCSG) to do so in advance of the Team's next meeting on Thursday, 16 December. Best regards, Caitlin, Berry and Marika Registration Data Accuracy Scoping Team – Meeting #10 Thursday 16 December at 13.00 UTC 1. Welcome & Chair Updates (5 minutes) * Vice-chair * Communication to Council 1. Finalize questions to ICANN org regarding enforcement and Accuracy Reporting System (10 minutes) * See cleaned up version developed by staff support team (see attached) * Scoping team input * Confirm final questions for submission to ICANN org 1. Gap Analysis (40 minutes) * Review input received from scoping team: https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/11msexuoqWSUs…> * Scoping team input * Confirm next steps 1. Confirm action items & next meeting (Thursday 23 December at 14.00 UTC)

2 2

**15-minute reminder** Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 16 December 2021 at 13:00 UTC
by Julie Bisland Dec. 16, 2021

Dec. 16, 2021

**15-minute reminder** Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 16 December 2021 at 13:00 UTC for 60 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09<https://urldefense.com/v3/__https:/icann.zoom.us/j/94504686990?pwd=MWc2eXZE…> Passcode: Vc#0B7$pu8 For Audio only: Or One tap mobile : US: +13017158592,,94504686990#,,,,*4631547480# or +13126266799,,94504686990#,,,,*4631547480# Webinar ID: 945 0468 6990 Passcode: 4631547480 International numbers available: https://icann.zoom.us/u/akRu7JTFd <https://urldefense.com/v3/__https:/icann.zoom.us/u/akRu7JTFd__;!!PtGJab4!pY…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, alternates and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/6AC7Cg * Check your time zone: https://tinyurl.com/46r8k6yt [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/46r8k6yt__;!!PtGJab4!rEPOexg…> ONLY for Members and Alternates * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Panelists and Attendees, or Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. * Alternate replacement confirmations – In order to keep track of alternate replacements, use the google form <https://urldefense.com/v3/__https:/forms.gle/GZqMAi4kKDaVP5o66__;!!PtGJab4!…> to communicate who the alternate is replacing and for which period. This information will be publicly posted so that the Team is aware at any time who is active. Alternate Assignment –wiki page<https://community.icann.org/x/-wC7Cg>. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Terri

1 0

Proposed Agenda - Registration Data Accuracy Scoping Team meeting #10 on Thursday 16 December at 13.00 UTC
by Marika Konings Dec. 16, 2021

Dec. 16, 2021

Dear All, Please find below the proposed agenda for the next Registration Data Accuracy Scoping Team meeting which is scheduled for Thursday 16 December at 13.00 UTC. You will find attached for your review the reorganized questions for ICANN org (see agenda item #2). As discussed, we’ve aimed to group similar questions together to facilitate the development of responses. In redline you will find some edits that we are proposing to make, mainly for clarity, consistency and/or referencing. If you have any comments or concerns about this reorganization and/or proposed edits, please flag these on the mailing list in advance of the meeting. As a reminder: * Groups who have not provided inputs for the Gap Analysis (BC, GAC, ISPCP, NCSG) to do so in advance of the Team's next meeting on Thursday, 16 December. Best regards, Caitlin, Berry and Marika Registration Data Accuracy Scoping Team – Meeting #10 Thursday 16 December at 13.00 UTC 1. Welcome & Chair Updates (5 minutes) * Vice-chair * Communication to Council 1. Finalize questions to ICANN org regarding enforcement and Accuracy Reporting System (10 minutes) * See cleaned up version developed by staff support team (see attached) * Scoping team input * Confirm final questions for submission to ICANN org 1. Gap Analysis (40 minutes) * Review input received from scoping team: https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit * Scoping team input * Confirm next steps 1. Confirm action items & next meeting (Thursday 23 December at 14.00 UTC)

2 1

Re: [GNSO-Accuracy-ST] Proposed Agenda - Registration Data Accuracy Scoping Team meeting #10 on Thursday 16 December at 13.00 UTC
by Brian Gutterman Dec. 15, 2021

Dec. 15, 2021

Hi all, Apologies but I won’t be able to make tomorrow’s meeting. I’ll be sure to listen to the recording and catch up on the notes. Dear Michael, all, FYI -With respect to the still-developing final list of questions for Org, after consulting with some of the relevant SMEs internally we do think it might be difficult to meet the original timeline/deadline for getting answers back to the group by the Dec 23rd (some important SMEs have previously scheduled Holiday time off next week); with that being said, we’re of course going to do everything we can to provide answers in a timely fashion to keep the work moving along. Policy team colleagues can provide more info if needed during the call tomorrow, and I’ll be back to join the following weeks’ meeting on the 23rd. Best, Brian From: GNSO-Accuracy-ST <gnso-accuracy-st-bounces(a)icann.org> on behalf of Marika Konings <marika.konings(a)icann.org> Date: Tuesday, December 14, 2021 at 5:28 AM To: "gnso-accuracy-st(a)icann.org" <gnso-accuracy-st(a)icann.org> Subject: [GNSO-Accuracy-ST] Proposed Agenda - Registration Data Accuracy Scoping Team meeting #10 on Thursday 16 December at 13.00 UTC Dear All, Please find below the proposed agenda for the next Registration Data Accuracy Scoping Team meeting which is scheduled for Thursday 16 December at 13.00 UTC. You will find attached for your review the reorganized questions for ICANN org (see agenda item #2). As discussed, we’ve aimed to group similar questions together to facilitate the development of responses. In redline you will find some edits that we are proposing to make, mainly for clarity, consistency and/or referencing. If you have any comments or concerns about this reorganization and/or proposed edits, please flag these on the mailing list in advance of the meeting. As a reminder: * Groups who have not provided inputs for the Gap Analysis (BC, GAC, ISPCP, NCSG) to do so in advance of the Team's next meeting on Thursday, 16 December. Best regards, Caitlin, Berry and Marika Registration Data Accuracy Scoping Team – Meeting #10 Thursday 16 December at 13.00 UTC 1. Welcome & Chair Updates (5 minutes) * Vice-chair * Communication to Council 1. Finalize questions to ICANN org regarding enforcement and Accuracy Reporting System (10 minutes) * See cleaned up version developed by staff support team (see attached) * Scoping team input * Confirm final questions for submission to ICANN org 1. Gap Analysis (40 minutes) * Review input received from scoping team: https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/11msexuoqWSUs…> * Scoping team input * Confirm next steps 1. Confirm action items & next meeting (Thursday 23 December at 14.00 UTC)

1 0

**REMINDER** Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 16 December 2021 at 13:00 UTC
by Julie Bisland Dec. 15, 2021

Dec. 15, 2021

**Note start time and duration update below, please make sure to adjust your calendars for 16 December 2021 meeting only from 14:00 UTC 90 minutes to 13:00 UTC 60 minutes. Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 16 December 2021 at 13:00 UTC for 60 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09<https://urldefense.com/v3/__https:/icann.zoom.us/j/94504686990?pwd=MWc2eXZE…> Passcode: Vc#0B7$pu8 For Audio only: Or One tap mobile : US: +13017158592,,94504686990#,,,,*4631547480# or +13126266799,,94504686990#,,,,*4631547480# Webinar ID: 945 0468 6990 Passcode: 4631547480 International numbers available: https://icann.zoom.us/u/akRu7JTFd <https://urldefense.com/v3/__https:/icann.zoom.us/u/akRu7JTFd__;!!PtGJab4!pY…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, alternates and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/6AC7Cg * Check your time zone: https://tinyurl.com/46r8k6yt [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/46r8k6yt__;!!PtGJab4!rEPOexg…> ONLY for Members and Alternates * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Panelists and Attendees, or Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. * Alternate replacement confirmations – In order to keep track of alternate replacements, use the google form <https://urldefense.com/v3/__https:/forms.gle/GZqMAi4kKDaVP5o66__;!!PtGJab4!…> to communicate who the alternate is replacing and for which period. This information will be publicly posted so that the Team is aware at any time who is active. Alternate Assignment –wiki page<https://community.icann.org/x/-wC7Cg>. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Terri

1 0

Re: [GNSO-Accuracy-ST] Update - Working Accuracy Contractual Construct/ Definition
by Lori Schulman Dec. 11, 2021

Dec. 11, 2021

Hi, The changes were definitely tracked. I was under the impression that we agreed to those changes. If so, then they should be reinserted as a compromise that we can live with for the purposes of the scoping exercise. Any binding definitions will be negotiated by the eventual PDP. With kind regards, Lori S. Schulman Senior Director, Internet Policy International Trademark Association (INTA) +1-202-704-0408, Skype: LSSchulman lschulman(a)inta.org<mailto:lschulman@inta.org>, www.inta.org<blocked::http://www.inta.org> From: GNSO-Accuracy-ST <gnso-accuracy-st-bounces(a)icann.org> On Behalf Of Sarah Wyld Sent: Monday, November 29, 2021 3:27 PM To: michael(a)palage.com; gnso-accuracy-st(a)icann.org Subject: Re: [GNSO-Accuracy-ST] Update - Working Accuracy Contractual Construct/ Definition Hi team, I (of course) can’t speak for the registries or answer this question, but I do want to say, I’m glad the text in the screenshot was not updated. The definition in that section of the document should remain as we had proposed it back on Oct 29, and any changes should be tracked elsewhere. Maybe that’s why the changes were removed? See you tomorrow, thanks! Sarah -- Sarah Wyld, CIPP/E Policy & Privacy Manager Pronouns: she/they swyld(a)tucows.com<mailto:swyld@tucows.com> +1.416 535 0123 Ext. 1392 [cid:image001.png@01D7E5EA.FDD631A0] From: Michael Palage<mailto:michael@palage.com> Sent: November 26, 2021 12:02 PM To: gnso-accuracy-st(a)icann.org<mailto:gnso-accuracy-st@icann.org> Subject: [GNSO-Accuracy-ST] Update - Working Accuracy Contractual Construct/ Definition Hello All, For those colleagues that celebrated the Thanksgiving holiday yesterday, I hope you had an enjoyable time with your family and friends and did not eat too much. I would also like to thanks those team members that showed up for our brief Administrative Call yesterday. In preparing for the call yesterday I noted some of the new additions added by the RySG to the questions for ICANN staff. Thank you for these additions Roger. This flagged a previous issue which I had raised with our ICANN colleagues last weekend and it involves the current working contractual construct / definition. In the RySG questions they cited to the proposed RrSG accuracy “definition” (aka contractual construct): "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." Last week when I was looking for the latest and greatest contractual construct/definition I noted that there was a technical glitch when reviewing the Zoom recording which I will summarize below. If you go to the Zoom recording from the Nov 4th call you will see that the red lined version of the contractual construct/definition which was agreed to during the call and which is reflected below. [cid:image001.png@01D7E2BD.34B4CF00] However, at the conclusion of the call as we were wrapping up the session, these edits were lost [cid:image002.png@01D7E2BD.34B4CF00] Therefore, I would like clarification from the RySG do they wish to cite the group’s current working contractual construct/definition that was agreed to during the Nov 4th call, or do they intend to cite to the RrSG pre November 4th call contractual construct/definition? I know these technical glitches, e.g. delta in Google Doc, Alan receiving emails, and the unavailability email archives makes things a little more challenging. However, I know our ICANN colleagues are working on the email issues, and I am sure we will be able to achieve most of our work asynchronously if we put our minds to it. Best regards, Michael

5 6

Notes and action items - RDA Scoping Team Meeting #9 - 9 December 2021
by Caitlin Tubergen Dec. 9, 2021

Dec. 9, 2021

Dear RDA Scoping Team Members, Please find below the notes and action items from today’s meeting. The next RDA Scoping Team meeting will be Thursday, 16 December at 13:00 UTC. Best regards, Marika, Berry, and Caitlin -- Action Items 1. By the COB Friday, 10 December, Scoping Team members who submitted questions to review questions, in light of meeting discussions and other questions submitted, and determine if questions should be deleted, modified, or retained. Deletions and modifications to be applied by COB, Friday, 10 December. (https://docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit) 2. Beginning 13 December, Support Staff to review the list of questions and group similar questions together and consolidate where possible. Support Staff to share updated list of questions with the Scoping Team by Tuesday, 14 December for the Team to provide any objections by Thursday, 16 December. 3. Groups who have not provided inputs for the Gap Analysis (BC, GAC, ISPCP, NCSG, SSAC) to do so in advance of the Team's next meeting on Thursday, 16 December. Registration Data Accuracy Scoping Team – Meeting #9 Thursday 9 December at 14.00 UTC 1. Welcome & Chair Updates (5 minutes) * Next week’s meeting will be Thursday, 16 December at 13:00 UTC. * Once the Team goes through the entire list of submitted questions, Support Staff will group similar questions together 1. Finalize questions to ICANN org regarding enforcement and Accuracy Reporting System (30 minutes) * Input received from scoping team to date: https://docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit[d…<https://urldefense.com/v3/__https:/docs.google.com/document/d/1arlKdQkbRkE1…> * The process of Registration Data Complaints is still in use – this will be conveyed back to IPC membership * Encourage everyone to listen to the one-hour Compliance update session from ICANN72: https://72.schedule.icann.org/meetings/xGs2HynAJKdXvN36G * Is there any self-policing going on for registrars that could be used for best practices? * The question re: due diligence for data accuracy – believe this is covered under existing contractual obligations – for example, all new data sets are verified. On an annual basis, there is a confirmation sent to the registrant that the data is still accurate. * Paragraph 4 from the Whois Accuracy Spec provides that if registrar has any received any information that the information is inaccurate, additional requirements apply. * In terms of suspending the ARS because the data is unavailable seems incorrect – there should be a legitimate ICANN purpose for processing the data. * Have been told that registrars are not obliged to chase bounced emails – good to know this language exists. The WDRP notice is not a confirmation – it’s a reminder. * With respect to ARS, it was suspended because ICANN could not perform its current process * Registrars must annually self-certify that they are in compliance with the RAA. ICANN can audit registrars, which is a great way to monitor and check for compliance. A DPA is not currently in place for ICANN. There is no way to prove that a registrant has read the WDRP notice; the same issue comes about with terms of service, but the terms are still legally binding. * Question 14 – specific UDRP case cited, where inaccurate data was disclosed – is there a flow between WIPO and ICANN – if so, do standards apply, or is it a case-by-case basis? * Recommend every scoping team member read the WIPO decision in D2021-1050 – it’s relevant to the team’s work * Question 16 – expecting ICANN to say that operational validation is required, syntactic validation is required for the country code, and no validation of any kind is imposed on any other data elements. * Question 17 – focus of these contracts is what are the requirements, but there is an implicit question whether registrars can do more work – are higher levels of validation permitted? * Question 18 – do registrars have to provide the level of validation with the data element – for example, tagging? * The answers to these three questions can be found in the RAA. Q17 – this is answered by registries who voluntarily commit to levels of accuracy beyond what is in the RAA. Q18 – the answer is no. In the application and audits, CPs are only required to answer what answers match the requirements of the RAA, so that level of verification is not required – Rrs just have to outline how they match the requirements. Q16 – there is a difference b/w accuracy that is required of the registrant, and the accuracy that is required – requirements from registry agreement is lower. Higher levels may be triggered from an inaccuracy complaint. * Accuracy and validation requirements – would recommend replacing accuracy with validation requirements. * The answers to these questions are documented in the background material; accordingly, what is the purpose for asking these questions? Uncomfortable asking questions that show that the team hasn’t done its homework * Question 19 notes for consistency check for some fields – in many cases, registrars do not do this. Has there been an outcome to this question? * Most registrars operate on a global scale, and it is not feasible to do cross-field validation worldwide * Question still stands – for many large countries, postal service offers cross-field validation for addresses. If a decision was made that this is not feasible, it needs to be documented. The fact that the only thing that can be found is an old document that says discussions that are ongoing, needs an update. * For Q20 – would like confirmation that ARS was terminated because it couldn’t be done exactly as before. * There was a public comment in 2015 regarding the Whois Accuracy Program Specification – no changes have happened – this is part of the community’s business even though it’s part of a contract * Q21 – did not know there was a process to manually verify the information – what process is acceptable to ICANN to verify an email address manually * This option was negotiated into the agreement by registrars – ICANN wanted the name to be deleted if no affirmative response – the manual verification was requested by registrars. * What does “look for trends of abuse” mean? * Does ICANN look at the bigger picture? It could be helpful if so. * Action: Support Staff to organize the questions and group questions that focus on a similar topic and produce updated version. * Question to the group: do all of these questions still need to be asked? * Action: Scoping Team to review questions to confirm they are still relevant by COB Friday, 10 Dec. * Will Staff Support be removing questions that are duplicative? * If questions can be grouped by concept, that would be helpful. * Scoping team input * Confirm final questions for submission to ICANN org 1. Gap Analysis (50 minutes) * Review input received from scoping team: https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit[d…<https://urldefense.com/v3/__https:/docs.google.com/document/d/11msexuoqWSUs…> * Scoping team input * Confirm next steps * So far, we have received input from RySG, RrSG, IPC, and ALAC. * Are the missing groups still planning to add feedback? * GAC will have an answer by next week’s call. 1. Confirm action items & next meeting (Thursday 16 December at 13.00 UTC)

1 0

Post call | Registration Data Accuracy Scoping Team | Thursday, 09 December 2021
by Terri Agnew Dec. 9, 2021

Dec. 9, 2021

Dear all, All recordings for the Registration Data Accuracy Scoping Team held on Thursday, 09 December 2021 can be found on the agenda wiki page <https://community.icann.org/x/5gC7Cg> (attendance included) and the GNSO Master Calendar [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…>. These include: * Attendance (please let me know if your name has been left off the attendance list) * Audio recording * Zoom chat archive * Zoom recording (including audio, visual, rough transcript) * Transcript For additional information, you may consult the mailing list archives <https://mm.icann.org/pipermail/gnso-accuracy-st/> and the main wiki page<https://community.icann.org/x/hQIuCg>. Thank you! Kind Regards, Terri

1 0