Re: [GNSO-Accuracy-ST] Proposed Alternative Text & Next Steps
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@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.
Thanks, Alan, done. Please note that with accepting the insertion your comment got removed, but we have re-added it. To all, please review the proposed alternative text and provide your feedback in the form of comments in the google doc (or on the mailing list). If you have specific edits you would like to Scoping Team to consider, please add these to the comment to facilitate review and discussion during Thursday’s meeting. Best regards, Chantelle, Berry and Marika From: GNSO-Accuracy-ST <gnso-accuracy-st-bounces@icann.org> on behalf of Alan Greenberg <alan.greenberg@mcgill.ca> Date: Tuesday, 23 August 2022 at 04:52 To: "michael palage.com" <michael@palage.com>, "gnso-accuracy-st@icann.org" <gnso-accuracy-st@icann.org> Subject: Re: [GNSO-Accuracy-ST] Proposed Alternative Text & Next Steps 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@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.
As a reminder, please do NOT edit the text directly but instead put any suggestions / proposed edits you have in the form of comments. Thanks. From: GNSO-Accuracy-ST <gnso-accuracy-st-bounces@icann.org> on behalf of Marika Konings <marika.konings@icann.org> Date: Tuesday, 23 August 2022 at 07:28 To: Alan Greenberg <alan.greenberg@mcgill.ca>, "michael palage.com" <michael@palage.com>, "gnso-accuracy-st@icann.org" <gnso-accuracy-st@icann.org> Subject: Re: [GNSO-Accuracy-ST] Proposed Alternative Text & Next Steps Thanks, Alan, done. Please note that with accepting the insertion your comment got removed, but we have re-added it. To all, please review the proposed alternative text and provide your feedback in the form of comments in the google doc (or on the mailing list). If you have specific edits you would like to Scoping Team to consider, please add these to the comment to facilitate review and discussion during Thursday’s meeting. Best regards, Chantelle, Berry and Marika From: GNSO-Accuracy-ST <gnso-accuracy-st-bounces@icann.org> on behalf of Alan Greenberg <alan.greenberg@mcgill.ca> Date: Tuesday, 23 August 2022 at 04:52 To: "michael palage.com" <michael@palage.com>, "gnso-accuracy-st@icann.org" <gnso-accuracy-st@icann.org> Subject: Re: [GNSO-Accuracy-ST] Proposed Alternative Text & Next Steps 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@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.
Hi Marika and All, Thank you. As a point of information, I changed the color of the text from yellow to blue so it is easy to pick out. Several of our colleagues pointed out that it was hard to distinguish the new text from the old text. IPC has responded to the RYSG input. Also, the representatives from IPC, SSAC and GAC are requesting a 30 day extension for statements. The reason that we are asking for this extension is that many of our colleagues are on summer vacation and our constituencies will need to vet the statements for approval. There are mandatory periods for review ranging from at least 7-10 days from the completion of the drafts. It is not realistic to expect the statements to be ready within 7 days from tomorrow since we do not have the final text until the close of tomorrow's meeting. Most of our colleagues who are on summer holiday will not be in their offices until early September. We understand that this runs up against the AGM but it cannot be helped as the AGM is much earlier this year. We hope that you will consider our request as we endeavor to provide meaningful statements to help move the process forward to the next stage. With kind regards, Lori S. Schulman Senior Director, Internet Policy International Trademark Association (INTA) +1-202-704-0408, Skype: LSSchulman lschulman@inta.org<mailto:lschulman@inta.org>, www.inta.org<blocked::http://www.inta.org> From: GNSO-Accuracy-ST <gnso-accuracy-st-bounces@icann.org> On Behalf Of Marika Konings Sent: Tuesday, August 23, 2022 11:05 AM To: Alan Greenberg <alan.greenberg@mcgill.ca>; michael palage.com <michael@palage.com>; gnso-accuracy-st@icann.org Subject: Re: [GNSO-Accuracy-ST] Proposed Alternative Text & Next Steps As a reminder, please do NOT edit the text directly but instead put any suggestions / proposed edits you have in the form of comments. Thanks. From: GNSO-Accuracy-ST <gnso-accuracy-st-bounces@icann.org<mailto:gnso-accuracy-st-bounces@icann.org>> on behalf of Marika Konings <marika.konings@icann.org<mailto:marika.konings@icann.org>> Date: Tuesday, 23 August 2022 at 07:28 To: Alan Greenberg <alan.greenberg@mcgill.ca<mailto:alan.greenberg@mcgill.ca>>, "michael palage.com" <michael@palage.com<mailto:michael@palage.com>>, "gnso-accuracy-st@icann.org<mailto:gnso-accuracy-st@icann.org>" <gnso-accuracy-st@icann.org<mailto:gnso-accuracy-st@icann.org>> Subject: Re: [GNSO-Accuracy-ST] Proposed Alternative Text & Next Steps Thanks, Alan, done. Please note that with accepting the insertion your comment got removed, but we have re-added it. To all, please review the proposed alternative text and provide your feedback in the form of comments in the google doc (or on the mailing list). If you have specific edits you would like to Scoping Team to consider, please add these to the comment to facilitate review and discussion during Thursday's meeting. Best regards, Chantelle, Berry and Marika From: GNSO-Accuracy-ST <gnso-accuracy-st-bounces@icann.org<mailto:gnso-accuracy-st-bounces@icann.org>> on behalf of Alan Greenberg <alan.greenberg@mcgill.ca<mailto:alan.greenberg@mcgill.ca>> Date: Tuesday, 23 August 2022 at 04:52 To: "michael palage.com" <michael@palage.com<mailto:michael@palage.com>>, "gnso-accuracy-st@icann.org<mailto:gnso-accuracy-st@icann.org>" <gnso-accuracy-st@icann.org<mailto:gnso-accuracy-st@icann.org>> Subject: Re: [GNSO-Accuracy-ST] Proposed Alternative Text & Next Steps 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@icann.org<mailto:GNSO-Accuracy-ST@icann.org> https://mm.icann.org/mailman/listinfo/gnso-accuracy-st<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmm.icann.org%2Fmailman%2Flistinfo%2Fgnso-accuracy-st&data=05%7C01%7Clschulman%40inta.org%7Cf876cb802c994e80f40608da8518cd11%7C1b6dad14b17645319562fdf3080f9d47%7C0%7C0%7C637968639863483290%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VlkaIGpFhZ5QDM4AdH1b%2B4Tx2fxUDCjDklpRFuivtrs%3D&reserved=0> _______________________________________________ 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<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.icann.org%2Fprivacy%2Fpolicy&data=05%7C01%7Clschulman%40inta.org%7Cf876cb802c994e80f40608da8518cd11%7C1b6dad14b17645319562fdf3080f9d47%7C0%7C0%7C637968639863483290%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=8CaMqjOmQp%2BUcVE3N%2FnFmjULwA%2Fro1v%2Br8QmI%2Bh3OPg%3D&reserved=0>) and the website Terms of Service ( https://www.icann.org/privacy/tos<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.icann.org%2Fprivacy%2Ftos&data=05%7C01%7Clschulman%40inta.org%7Cf876cb802c994e80f40608da8518cd11%7C1b6dad14b17645319562fdf3080f9d47%7C0%7C0%7C637968639863483290%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=hUnBxMSfiKImQaukRAbgwWv%2FP8d2zjZ8XO63oQDvJes%3D&reserved=0>). 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.
The BC also supports this request for an extension of the timeline, for the reasons stated by Lori. Mason Cole | Perkins Coie LLP INTERNET GOVERNANCE ADVISOR 1120 N.W. Couch Street Tenth Floor D. +1.503.727.2074 E. MCole@perkinscoie.com<mailto:%20MCole@perkinscoie.com> From: GNSO-Accuracy-ST <gnso-accuracy-st-bounces@icann.org> On Behalf Of Lori Schulman Sent: Wednesday, August 24, 2022 9:10 AM To: Marika Konings <marika.konings@icann.org>; Alan Greenberg <alan.greenberg@mcgill.ca>; michael palage.com <michael@palage.com>; gnso-accuracy-st@icann.org Subject: Re: [GNSO-Accuracy-ST] Proposed Alternative Text & Next Steps Hi Marika and All, Thank you. As a point of information, I changed the color of the text from yellow to blue so it is easy to pick out. Several of our colleagues pointed out that it was hard to distinguish the new text from the old text. IPC has responded to the RYSG input. Also, the representatives from IPC, SSAC and GAC are requesting a 30 day extension for statements. The reason that we are asking for this extension is that many of our colleagues are on summer vacation and our constituencies will need to vet the statements for approval. There are mandatory periods for review ranging from at least 7-10 days from the completion of the drafts. It is not realistic to expect the statements to be ready within 7 days from tomorrow since we do not have the final text until the close of tomorrow's meeting. Most of our colleagues who are on summer holiday will not be in their offices until early September. We understand that this runs up against the AGM but it cannot be helped as the AGM is much earlier this year. We hope that you will consider our request as we endeavor to provide meaningful statements to help move the process forward to the next stage. With kind regards, Lori S. Schulman Senior Director, Internet Policy International Trademark Association (INTA) +1-202-704-0408, Skype: LSSchulman lschulman@inta.org<mailto:lschulman@inta.org>, www.inta.org<blocked::http://www.inta.org> From: GNSO-Accuracy-ST <gnso-accuracy-st-bounces@icann.org<mailto:gnso-accuracy-st-bounces@icann.org>> On Behalf Of Marika Konings Sent: Tuesday, August 23, 2022 11:05 AM To: Alan Greenberg <alan.greenberg@mcgill.ca<mailto:alan.greenberg@mcgill.ca>>; michael palage.com <michael@palage.com<mailto:michael@palage.com>>; gnso-accuracy-st@icann.org<mailto:gnso-accuracy-st@icann.org> Subject: Re: [GNSO-Accuracy-ST] Proposed Alternative Text & Next Steps As a reminder, please do NOT edit the text directly but instead put any suggestions / proposed edits you have in the form of comments. Thanks. From: GNSO-Accuracy-ST <gnso-accuracy-st-bounces@icann.org<mailto:gnso-accuracy-st-bounces@icann.org>> on behalf of Marika Konings <marika.konings@icann.org<mailto:marika.konings@icann.org>> Date: Tuesday, 23 August 2022 at 07:28 To: Alan Greenberg <alan.greenberg@mcgill.ca<mailto:alan.greenberg@mcgill.ca>>, "michael palage.com" <michael@palage.com<mailto:michael@palage.com>>, "gnso-accuracy-st@icann.org<mailto:gnso-accuracy-st@icann.org>" <gnso-accuracy-st@icann.org<mailto:gnso-accuracy-st@icann.org>> Subject: Re: [GNSO-Accuracy-ST] Proposed Alternative Text & Next Steps Thanks, Alan, done. Please note that with accepting the insertion your comment got removed, but we have re-added it. To all, please review the proposed alternative text and provide your feedback in the form of comments in the google doc (or on the mailing list). If you have specific edits you would like to Scoping Team to consider, please add these to the comment to facilitate review and discussion during Thursday's meeting. Best regards, Chantelle, Berry and Marika From: GNSO-Accuracy-ST <gnso-accuracy-st-bounces@icann.org<mailto:gnso-accuracy-st-bounces@icann.org>> on behalf of Alan Greenberg <alan.greenberg@mcgill.ca<mailto:alan.greenberg@mcgill.ca>> Date: Tuesday, 23 August 2022 at 04:52 To: "michael palage.com" <michael@palage.com<mailto:michael@palage.com>>, "gnso-accuracy-st@icann.org<mailto:gnso-accuracy-st@icann.org>" <gnso-accuracy-st@icann.org<mailto:gnso-accuracy-st@icann.org>> Subject: Re: [GNSO-Accuracy-ST] Proposed Alternative Text & Next Steps 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@icann.org<mailto:GNSO-Accuracy-ST@icann.org> https://mm.icann.org/mailman/listinfo/gnso-accuracy-st<https://urldefense.com/v3/__https:/nam04.safelinks.protection.outlook.com/?url=https*3A*2F*2Fmm.icann.org*2Fmailman*2Flistinfo*2Fgnso-accuracy-st&data=05*7C01*7Clschulman*40inta.org*7Cf876cb802c994e80f40608da8518cd11*7C1b6dad14b17645319562fdf3080f9d47*7C0*7C0*7C637968639863483290*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C3000*7C*7C*7C&sdata=VlkaIGpFhZ5QDM4AdH1b*2B4Tx2fxUDCjDklpRFuivtrs*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSU!!K_R5ZAeIjLw!H1RvLnCrG-HEJ4cVfvvhe3KN6S8QtbfGIbHroUJTZmdYo09LUJZHi2wyzvCPAAPe4fti0QTtYzkKru4eIQ$> _______________________________________________ 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<https://urldefense.com/v3/__https:/nam04.safelinks.protection.outlook.com/?url=https*3A*2F*2Fwww.icann.org*2Fprivacy*2Fpolicy&data=05*7C01*7Clschulman*40inta.org*7Cf876cb802c994e80f40608da8518cd11*7C1b6dad14b17645319562fdf3080f9d47*7C0*7C0*7C637968639863483290*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C3000*7C*7C*7C&sdata=8CaMqjOmQp*2BUcVE3N*2FnFmjULwA*2Fro1v*2Br8QmI*2Bh3OPg*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSU!!K_R5ZAeIjLw!H1RvLnCrG-HEJ4cVfvvhe3KN6S8QtbfGIbHroUJTZmdYo09LUJZHi2wyzvCPAAPe4fti0QTtYzkRJfDe8Q$>) and the website Terms of Service ( https://www.icann.org/privacy/tos<https://urldefense.com/v3/__https:/nam04.safelinks.protection.outlook.com/?url=https*3A*2F*2Fwww.icann.org*2Fprivacy*2Ftos&data=05*7C01*7Clschulman*40inta.org*7Cf876cb802c994e80f40608da8518cd11*7C1b6dad14b17645319562fdf3080f9d47*7C0*7C0*7C637968639863483290*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C3000*7C*7C*7C&sdata=hUnBxMSfiKImQaukRAbgwWv*2FP8d2zjZ8XO63oQDvJes*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUlJQ!!K_R5ZAeIjLw!H1RvLnCrG-HEJ4cVfvvhe3KN6S8QtbfGIbHroUJTZmdYo09LUJZHi2wyzvCPAAPe4fti0QTtYzkvsfne-Q$>). 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. ________________________________ NOTICE: This communication may contain privileged or other confidential information. If you have received it in error, please advise the sender by reply email and immediately delete the message and any attachments without copying or disclosing the contents. Thank you.
participants (4)
-
Alan Greenberg -
Cole, Mason (POR) -
Lori Schulman -
Marika Konings