August 2022 - GNSO-Accuracy-ST

ICANN75 schedule is published / How to Get Organized
by Julie Bisland Aug. 30, 2022

Aug. 30, 2022

Dear all, With ICANN75 just around the corner, please take a moment to read the information below for a seamless and successful meeting. REGISTER TODAY * Sign into Your ICANN Account, or create an account here [account.icann.org]<https://urldefense.com/v3/__https:/account.icann.org/login__;!!PtGJab4!_Q3w…>. * Register by selecting Meeting Registration. * Click on the Registration link. Click here [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> for detailed instructions. Before creating your schedule, please read this page carefully: https://75.schedule.icann.org/participation-tools [75.schedule.icann.org]<https://urldefense.com/v3/__https:/75.schedule.icann.org/participation-tool…> CREATE YOUR MEETING SCHEDULE * If participating remotely, go here [75.schedule.icann.org]<https://urldefense.com/v3/__https:/75.schedule.icann.org/__;!!PtGJab4!_Q3wY…> and select the Schedule dropdown->Full Agenda->Scroll to the days and sessions you plan to attend and click the + to add the session to your agenda. * If participating on-site, please read the https://75.schedule.icann.org/health-safety [75.schedule.icann.org]<https://urldefense.com/v3/__https:/75.schedule.icann.org/health-safety__;!!…> page and then proceed to access to the schedule: https://75.schedule.icann.org/ [75.schedule.icann.org]<https://urldefense.com/v3/__https:/75.schedule.icann.org/__;!!PtGJab4!_Q3wY…>. Go to Schedule dropdown->Full Agenda->Scroll to the sessions you plan to attend and click the + to add the session to your agenda. * Please remember, for security purposes, participation links will be posted 24-hours prior to the session start times. There will be no calendar invitations sent, as the meeting schedule allows you to download all sessions of interest to you, to your individual calendars Review the Participation Tools and update Zoom * All sessions will use Zoom rooms. Access details are available 24hrs prior on the ICANN75 Meeting Schedule [75.schedule.icann.org]<https://urldefense.com/v3/__https:/75.schedule.icann.org/__;!!PtGJab4!_Q3wY…>. * Visit the Participation Tools page [75.schedule.icann.org]<https://urldefense.com/v3/__https:/75.schedule.icann.org/participation-tool…> for links to download the latest version of Zoom for access to the ICANN Meeting sessions. * Please see the *In-Person* or *Virtual* Participant How-To Guide for more information on how to get the most out of the virtual meeting tools. Links to Bookmark ICANN75 Meeting Schedule [75.schedule.icann.org]<https://urldefense.com/v3/__https:/75.schedule.icann.org/__;!!PtGJab4!_Q3wY…> GNSO ICANN75 Wiki Page<https://community.icann.org/x/cQcVD> GNSO Session agendas<https://community.icann.org/x/bwcVD> For all GNSO meeting-related queries (RP or others), please email us at: gnso-secs(a)icann.org and we will be more than happy to assist! Kind regards, GNSO SO/AC Support team -- Julie Bisland Policy Operations Sr. Coordinator (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Skype ID: 79613b691cb8a6c1 Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>

1 0

Final version - write up for assignments #1 & #2
by Marika Konings Aug. 29, 2022

Aug. 29, 2022

Dear All, As discussed during yesterday’s meeting, the staff support team has gone ahead and finalized the write up for assignments #1 and #2 (see https://docs.google.com/document/d/1cV5ExSZD6G-owksGmMEmig0OXVdGcAUU/edit?p… and attached). The one remaining section to be completed is Annex B – membership and attendance – this will be done before submission to the GNSO Council. As a reminder, the timeline for the next steps is as follows: * Staff support team to produce final clean version - Friday 26 August (completed) * Scoping Team members to indicate if they are planning to submit a statement for inclusion in the annex - Monday 29 August * Deadline for submitting statements – Thursday 1 September * Submission of write up for assignments #1 and #2 to the GNSO Council – Friday 2 September Of course, if you still spot any minor edits please feel free to flag these in the google doc. Thanks, Chantelle, Berry and Marika

3 2

Notes and action items - RDA Scoping Team Meeting #37 - 25 August 2022
by Chantelle Doerksen Aug. 26, 2022

Aug. 26, 2022

Dear RDA Scoping Team Members, Please find below the action items and notes from the recent call held on Thursday, 25 August 2022. Best, Marika, Berry, and Chantelle --------- Action Items Staff support team to produce final clean version. Scoping Team members to indicate if they are planning to submit a statement for inclusion in the annex. Deadline for submitting statements. Submission of write up for assignments #1 and #2 to the GNSO Council. Scoping Team to meet during ICANN75 sessions unless GNSO Council objects to proceeding until such time when Council has had an opportunity to review the write up and recommendations. Notes Welcome & Chair Updates Review proposed alternative text for recommendation #3 (see page 16 -https://docs.google.com/document/d/1cV5ExSZD6G-owksGmMEmig0OXVdGcAUU/edit?pli=1 Scoping Team input Gap Analysis to be left as-is, with certain comments still included as red-line suggestions from the constituencies. Intellectual Property Constituency (IPC) wanted their comments to remain, and stated it made a difference on how recommendation 3 is considered. Marika Konings: Alternative Recommendation 3 proposal was drafted by leadership and staff to highlight areas where the groups agree, and remove areas that caused confusion. In Recommendation 3, the first paragraph recognizes there are external dependencies that will impact the group’s work, such as proposals that require access to registration data. The reference to pause this work was specific to registration data, which should now be clearer with the most recent revisions. There is a sense of urgency that the GNSO Council could convey to ICANN org to ensure regular updates on the DPA and DPIA were provided. Specific scenarios, such as a subset of registration data obtained through monthly Domain Abuse Activity Reporting (DAAR) reports, need to be tested with the European Data Protection Board (EDPB). Michael Palage (Chair) sees a clear path on how to wrap-up Recommendation 3. Alan Greenberg (ALAC): Two important considerations are regular updates to the EDPB in conjunction with the European Community: This is a group which is scoping things that might lead to policy. Concerns of a dangerous situation if outreach is done purely by staff without any input from the multistakeholder community. Potentially asking a question and getting an answer that isn’t particularly relevant to this team’s work. Community needs to be involved to ensure the scenarios and questions needing to be asked are being addressed. Need to see results of consultation with the EDPB. If the answer is yes and it is fine to access data, then this would impact the analysis. Brian Gutterman (ICANN org): Appreciates ALAC’s comments about continuing the collaboration on the scenario work. ICANN org reiterates that it will work in good faith and collaborate. While ICANN org will hold the pen, they will continue to listen and allow the community to provide input before the DPIA is formally submitted to the DPA. The report should include language to articulate that ICANN org will interact with the community. RySG appreciates ICANN org’s explanation and acknowledges that this is ultimately an ICANN org task. Noted the work the RDA Scoping Team had previously done to draft the scenarios. Team supports removing the DAAR reference: “those identified by ICANN org through monthly DAAR reports as associated with security threat activity." Removal of this language will provide the team with more flexibility. IPC wants to keep language referencing DPA and DPIA language to ensure consistent messaging as to what has been discussed in the past year. Alan Greenberg (ALAC): Agree it is an ICANN org task, but it is really important that whatever they do meshes well with what we may propose to the GNSO Council. Agreement that while DPA and DPIA are out of scope for this team, the assessments will most likely influence the work this group proposes. Agreement to finish edits on recommendation 3. b. Confirm final text Support staff will work with ICANN org to produce a clean version of the report that will be available on Friday, 26 August. GNSO Council to communicate to ICANN org to proceed. 3. Confirm timeline for submission to GNSO Council: Staff support team to produce final clean version - Friday 26 August Scoping Team members to indicate if they are planning to submit a statement for inclusion in the annex - Monday 29 August Deadline for submitting statements – Thursday 1 September Submission of write up for assignments #1 and #2 to the GNSO Council – Friday 2 September Scoping Team approved timeline as follows: ICANN org to provide a clean report on Friday, 26 Aug Any community statements should be submitted on the list by no later than Thursday, 1 Sept. As Chair, Michael will submit the report on Friday, 2 Sept. After the report is submitted to Council, Michael Palage will step down from his role as chair. Olga Cavalli’s term within the GNSO Council is concluding at ICANN75, and she will transition to ccNSO. Additional leadership will be needed. 4. Confirm next steps As part of submission to GNSO Council, Chair to indicate that Scoping Team has a meeting scheduled at ICANN75 to informally continue work on registrar survey & registrar audit, with the understanding that this further work will need to be confirmed by the GNSO Council following its review of the write up for assignments #1 and #2. Scoping Team meeting at ICANN75 scheduled for Saturday 17 September from 9.00 – 10.00 local time (1.00 – 2.00 UTC) Subsequent meetings will be dependent on Council review of Write Up for Assignments #1 and #2 as well as search for a new Chair. Weekly calls are suspended until further notice. The mailing list will remain open during the interim. GNSO Council guidance is needed on next steps for the team. If the GNSO Council confirms the Scoping Team’s work after its review of the report, the ICANN75 meeting is scheduled to proceed to discuss registrar survey and registrar audit. Michael will indicate in his message to the GNSO Council that further statements may be forthcoming between now and Thursday, 1 Sept.

1 0

Post call | Registration Data Accuracy Scoping Team | Thursday, 25 August 2022
by Terri Agnew Aug. 25, 2022

Aug. 25, 2022

Dear all, All recordings for the Registration Data Accuracy Scoping Team held on Thursday, 25 August 2022 can be found on the agenda wiki page <https://community.icann.org/x/uYKLD> (attendance included) and the GNSO Master Calendar <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 and chat archive) * Audio recording * Zoom recording (including audio, visual, rough transcript and chat) * 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

**Starting in 15 minutes | Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 25 August 2022 at 15:15 UTC
by Terri Agnew Aug. 25, 2022

Aug. 25, 2022

**Starting in 15 minute Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 25 August 2022 at 15:15 UTC for 90 minutes. (adjusted start time due to conflict with the GNSO Council call) 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<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/uYKLD * Check your time zone: https://tinyurl.com/4pc6udhz [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/4pc6udhz__;!!PtGJab4!_NFIYX3…> ONLY for Members and Alternates * Please join via the above Webinar link and staff will promote you to panelist. * Please select Everyone, when posting to the chat in order for everyone to see and so it is captured in the recording. * 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 #37 on Thursday 25 August at 15.15 UTC
by Marika Konings Aug. 24, 2022

Aug. 24, 2022

Dear All, Please find below the proposed agenda for the next Registration Data Accuracy Scoping Team meeting which is scheduled for Thursday 25 August at 15.15 UTC (please take note of the updated start time). Best regards, Chantelle, Berry and Marika Registration Data Accuracy Scoping Team – Meeting #37 Thursday 25 August at 15.15 UTC 1. Welcome & Chair Updates 1. Review proposed alternative text for recommendation #3 (see page 16 - https://docs.google.com/document/d/1cV5ExSZD6G-owksGmMEmig0OXVdGcAUU/edit?p…) * Scoping Team input * Confirm final text 1. Confirm timeline for submission to GNSO Council: * Staff support team to produce final clean version - Friday 26 August * Scoping Team members to indicate if they are planning to submit a statement for inclusion in the annex - Monday 29 August * Deadline for submitting statements – Thursday 1 September * Submission of write up for assignments #1 and #2 to the GNSO Council – Friday 2 September 1. Confirm next steps * As part of submission to GNSO Council, Chair to indicate that Scoping Team has a meeting scheduled at ICANN75 to informally continue work on registrar survey & registrar audit, with the understanding that this further work will need to be confirmed by the GNSO Council following its review of the write up for assignments #1 and #2. * Scoping Team meeting at ICANN75 scheduled for Saturday 17 September from 9.00 – 10.00 local time (1.00 – 2.00 UTC) * Subsequent meetings will be dependent on Council review of Write Up for Assignments #1 and #2 as well as search for new Chair.

2 1

Re: [GNSO-Accuracy-ST] Proposed Alternative Text & Next Steps
by Alan Greenberg Aug. 24, 2022

Aug. 24, 2022

Marc Anderson inserted the new proposed text into the Google Doc, but as it is just a suggestion, it is not possible to target comments at particular parts of the new text. Can staff please edit in this new text (accepting Marc's insertion is fine) so that we can make specific comments. Alan At 2022-08-19 09:34 AM, michael palage.com wrote: >Dear All, > > > >As mentioned in my message earlier this week, my hope is to have one >more call to finish up our work on the write up for assignments #1 >and #2. In order to do this, I would like to draw your attention to >the following: > > > * All minor edits / placeholders have now been accepted in the > Google doc as no concerns were flagged. > * Following our discussion last week, the edits made during the > call as well as the footnote have been incorporated in > recommendation #2. Note that some additional language has been > added to the footnote to provide context for it. The alternative > proposal #2 has been removed as well as all comments that related > to these two recommendations as these are considered addressed. > * Below you will find an alternative proposal for recommendation > #3 that the leadership team has developed with the staff support > team as a proposed alternative recommendation that would replace > recommendation #3, alternative #3, and the new recommendation #4. > We hope that this captures the different sentiments that have been > expressed and aligns with the scoping team's discussions to date. > > > >As also indicated, I would like to encourage you to continue the >conversation via the Google doc and mailing list leading up to what >I expect to be our last call before the write up for assignments #1 >and #2 is submitted to the GNSO Council. If after this call there is >no agreement on the proposed alternative recommendation, groups will >have the ability to provide their statements for inclusion in the >report. Statements would need to be provided by Thursday, 1 >September at the latest, and kindly ask you to indicate by Monday, >29 August at the latest whether your group is planning to submit one. > > > >With the submission of the report, I will also request the GNSO >Council to commence its search for a replacement chair as soon as >possible but obviously finding and confirming a replacement may take >a bit of time. > > > >Proposed alternative recommendation (replacing recommendation #3, >alternative #3 and new #4) > > > >The Scoping Team recognizes that work in relation to proposals that >require access to registration data may be impacted by current >outreach being undertaken by the ICANN org at the request of the >ICANN Board. This outreach may provide further clarity on the >processing of personal registration data under the GDPR. > > > >As a result, the Scoping Team recommends that the GNSO Council >requests ICANN org to proceed with this outreach as a matter of >urgency and provides regular updates on the status of its outreach. >The Scoping Team would recommend that the GNSO Council specifically >calls out the importance of finalizing the Data Processing Agreement >between ICANN and the contracting parties as well as proceeding with >a Data Privacy Impact Assessment in connection with the scenario in >which the request and processing of Registrant data takes place in >relation to a sub-set of domain names, for example, those identified >by ICANN org through monthly DAAR reports as associated with >security threat activity. > > > > > >Best regards, > > > >Michael >_______________________________________________ >GNSO-Accuracy-ST mailing list >GNSO-Accuracy-ST(a)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.

4 4

**REMINDER** Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 25 August 2022 at 15:15 UTC
by Julie Bisland Aug. 24, 2022

Aug. 24, 2022

Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 25 August 2022 at 15:15 UTC for 90 minutes. (adjusted start time due to conflict with the GNSO Council call) 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<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/uYKLD * Check your time zone: https://tinyurl.com/4pc6udhz [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/4pc6udhz__;!!PtGJab4!_NFIYX3…> ONLY for Members and Alternates * Please join via the above Webinar link and staff will promote you to panelist. * Please select Everyone, when posting to the chat in order for everyone to see and so it is captured in the recording. * 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 Alternative Text & Next Steps
by michael palage.com Aug. 19, 2022

Aug. 19, 2022

Dear All, As mentioned in my message earlier this week, my hope is to have one more call to finish up our work on the write up for assignments #1 and #2. In order to do this, I would like to draw your attention to the following: * All minor edits / placeholders have now been accepted in the Google doc as no concerns were flagged. * Following our discussion last week, the edits made during the call as well as the footnote have been incorporated in recommendation #2. Note that some additional language has been added to the footnote to provide context for it. The alternative proposal #2 has been removed as well as all comments that related to these two recommendations as these are considered addressed. * Below you will find an alternative proposal for recommendation #3 that the leadership team has developed with the staff support team as a proposed alternative recommendation that would replace recommendation #3, alternative #3, and the new recommendation #4. We hope that this captures the different sentiments that have been expressed and aligns with the scoping team's discussions to date. As also indicated, I would like to encourage you to continue the conversation via the Google doc and mailing list leading up to what I expect to be our last call before the write up for assignments #1 and #2 is submitted to the GNSO Council. If after this call there is no agreement on the proposed alternative recommendation, groups will have the ability to provide their statements for inclusion in the report. Statements would need to be provided by Thursday, 1 September at the latest, and kindly ask you to indicate by Monday, 29 August at the latest whether your group is planning to submit one. With the submission of the report, I will also request the GNSO Council to commence its search for a replacement chair as soon as possible but obviously finding and confirming a replacement may take a bit of time. Proposed alternative recommendation (replacing recommendation #3, alternative #3 and new #4) The Scoping Team recognizes that work in relation to proposals that require access to registration data may be impacted by current outreach being undertaken by the ICANN org at the request of the ICANN Board. This outreach may provide further clarity on the processing of personal registration data under the GDPR. As a result, the Scoping Team recommends that the GNSO Council requests ICANN org to proceed with this outreach as a matter of urgency and provides regular updates on the status of its outreach. The Scoping Team would recommend that the GNSO Council specifically calls out the importance of finalizing the Data Processing Agreement between ICANN and the contracting parties as well as proceeding with a Data Privacy Impact Assessment in connection with the scenario in which the request and processing of Registrant data takes place in relation to a sub-set of domain names, for example, those identified by ICANN org through monthly DAAR reports as associated with security threat activity. Best regards, Michael

1 0

Update
by michael palage.com Aug. 19, 2022

Aug. 19, 2022

Hello Everyone, At today's leadership call the following was decided regarding how we wrap up the remainder of our work. - The leadership team will send proposed alternative recommendation text (Recs 3 & 4) based on last week's discussions and it will be circulated to the group within the next 24 hours. - There will be NO plenary call on Thursday. Instead, the group will be encouraged to use the mailing list and have internal discussions to determine if it is acceptable. If the proposed text is not acceptable, the leadership team expects to see exchanges within the draft document. - Next Thursday (Aug 25th) the group will have our LAST plenary call in connection with Assignments 1 & 2. - Our report will then be submitted to the GNSO Council on Friday Sept 2nd. Best regards, Michael

2 1