ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana: During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN's current Legislative/Regulatory tracking effort. As we discussed, ICANN's work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa's group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development. Please work together and with Staff to help kick off this important and timely work. Thanks, Keith
Thanks, Keith. To kick off this discussion, broadly there are three areas where I would like to see improvements to this document. Firstly, I'd like to see a new planning stage altogether. This should see a proper regulatory impact assessment carried out, so we can understand the intended rationale for a law/regulation/directive, specific extracts of the proposed text that could have implications on activities within ICANN's remit, and perhaps most importantly, the document should outline concretely what implications are anticipated for ICANN. A roadmap or timeline should be included so we understand how imminent the law/regulation/directive is and when we need to take action. The current, crowdsourced approach where the community is expected to identify errors and omissions in the document is inappropriate. If ICANN is a professional organization then its professional staff should be monitoring the regulatory landscape within which we operate. Then, I'd like to see a new stage or chapter to the report outlining the response being taken. So, once a law/regulation/directive is here and we've identified we need to take action and we know when enforcement begins, the report should offer a detailed analysis that outlines more specifically what options the GNSO Council or other parties could consider taking to ensure legal compliance. Third, once a law/regulation/directive is in place and we have taken actions to comply with it, ICANN should monitor 1) the impact the law/regulation/directive has had as it relates to ICANN's remit, 2) evaluate how successful/unsuccessful our response was, and 3) if necessary and only with extensive community consultation first feed back to lawmakers if there has been a mismatch between their intended rationale for a law/regulation/directive and reality. There are two other characteristics that I consider to be very important for this tracker. It should use clear, succinct, and plain language, regardless of the issue's complexity. It must be accurate and kept up to date, always based upon the latest information. In order for this resource to be useful it should not be circulated until ICANN has verified that it transports the correct and necessary messages. Best wishes, Ayden Férdeline ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Thursday, April 4, 2019 8:35 PM, Drazek, Keith via council <council@gnso.icann.org> wrote:
Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana:
During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort.
As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development.
Please work together and with Staff to help kick off this important and timely work.
Thanks,
Keith
I now in the LAC region we have intensive community activity with a LAC Strategy group and all. I can alway give my input, but it will always be better to not duplicate efforts, If the LAC staff is already doing update on this issue , I am fine following that work and not leading a new one from scratch. If they are not specially doing an update on this, then I am happily helping them to put something together. In all cases, I think ICANN regional staff could send a few emails and get legal updates from every LAC country, specially if it uses the partnerships and links it has with NGOs and Chambers. What do you guys think? Should we talk this as an GNSO thing or level thing region by region? Best, Martin Silva Valent mpsilvavalent@gmail.com Partner | Silva.legal martin@silva.legal Director | Dat.as martin.silva@dat.as Skype ID: mpsilvavalent Tel: +5491164993943 Libertador 5990, Off. 406 Buenos Aires, Argentina. Este email, incluyendo adjuntos, podría contener información confidencial protegida por ley y es para uso exclusivo de su destinatario. Si Ud. no es el destinatario, se le advierte que cualquier uso, difusión, copia o retención de este email o su contenido está estrictamente prohibido. Si Ud. recibió este email por error, por favor avise inmediatamente al remitente por teléfono o email y borre el mismo de su computadora. / This e-mail, including any attachments, may contain information that is protected by law as privileged and confidential, and is transmitted for the sole use of the intended recipient. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying or retention of this e-mail or the information contained herein is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by telephone or reply e-mail, and permanently delete this e-mail from your computer system.
On Apr 6, 2019, at 4:52 PM, Ayden Férdeline <icann@ferdeline.com> wrote:
Thanks, Keith.
To kick off this discussion, broadly there are three areas where I would like to see improvements to this document.
Firstly, I'd like to see a new planning stage altogether. This should see a proper regulatory impact assessment carried out, so we can understand the intended rationale for a law/regulation/directive, specific extracts of the proposed text that could have implications on activities within ICANN's remit, and perhaps most importantly, the document should outline concretely what implications are anticipated for ICANN. A roadmap or timeline should be included so we understand how imminent the law/regulation/directive is and when we need to take action.
The current, crowdsourced approach where the community is expected to identify errors and omissions in the document is inappropriate. If ICANN is a professional organization then its professional staff should be monitoring the regulatory landscape within which we operate.
Then, I'd like to see a new stage or chapter to the report outlining the response being taken. So, once a law/regulation/directive is here and we've identified we need to take action and we know when enforcement begins, the report should offer a detailed analysis that outlines more specifically what options the GNSO Council or other parties could consider taking to ensure legal compliance.
Third, once a law/regulation/directive is in place and we have taken actions to comply with it, ICANN should monitor 1) the impact the law/regulation/directive has had as it relates to ICANN's remit, 2) evaluate how successful/unsuccessful our response was, and 3) if necessary and only with extensive community consultation first feed back to lawmakers if there has been a mismatch between their intended rationale for a law/regulation/directive and reality.
There are two other characteristics that I consider to be very important for this tracker.
It should use clear, succinct, and plain language, regardless of the issue's complexity.
It must be accurate and kept up to date, always based upon the latest information. In order for this resource to be useful it should not be circulated until ICANN has verified that it transports the correct and necessary messages.
Best wishes,
Ayden Férdeline
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Thursday, April 4, 2019 8:35 PM, Drazek, Keith via council <council@gnso.icann.org> wrote:
Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana:
During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort.
As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development.
Please work together and with Staff to help kick off this important and timely work.
Thanks,
Keith
_______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council
Hi All, As I tried to express from the Council table in Kobe, I guess I am less concerned with the format, etc. of the document and, instead, believe that we need ICANN’s government relations folks to visit us at Council and highlight the main issues it sees heading our way. Otherwise, this is just one more of a thousand documents we all need to read to get ready for the next meeting and we may or may not have the appropriate sense of urgency. We can’t let whether or not contracted parties may face a fine be the only method by which we decide compliance with a forthcoming law is, or is not, important and urgent. This process needs to be a dialogue with Org staff, not a pen pal. Best, Paul From: council <council-bounces@gnso.icann.org> On Behalf Of Martin Pablo Silva Valent Sent: Saturday, April 6, 2019 8:39 PM To: Ayden Férdeline <icann@ferdeline.com> Cc: gnso-secs@icann.org; council@gnso.icann.org Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements I now in the LAC region we have intensive community activity with a LAC Strategy group and all. I can alway give my input, but it will always be better to not duplicate efforts, If the LAC staff is already doing update on this issue , I am fine following that work and not leading a new one from scratch. If they are not specially doing an update on this, then I am happily helping them to put something together. In all cases, I think ICANN regional staff could send a few emails and get legal updates from every LAC country, specially if it uses the partnerships and links it has with NGOs and Chambers. What do you guys think? Should we talk this as an GNSO thing or level thing region by region? Best, Martin Silva Valent mpsilvavalent@gmail.com<mailto:mpsilvavalent@gmail.com> Partner | Silva.legal martin@silva.legal<mailto:martin@silva.legal> Director | Dat.as martin.silva@dat.as<mailto:martin.silva@dat.as> Skype ID: mpsilvavalent Tel: +5491164993943 Libertador 5990, Off. 406 Buenos Aires, Argentina. Este email, incluyendo adjuntos, podría contener información confidencial protegida por ley y es para uso exclusivo de su destinatario. Si Ud. no es el destinatario, se le advierte que cualquier uso, difusión, copia o retención de este email o su contenido está estrictamente prohibido. Si Ud. recibió este email por error, por favor avise inmediatamente al remitente por teléfono o email y borre el mismo de su computadora. / This e-mail, including any attachments, may contain information that is protected by law as privileged and confidential, and is transmitted for the sole use of the intended recipient. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying or retention of this e-mail or the information contained herein is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by telephone or reply e-mail, and permanently delete this e-mail from your computer system. On Apr 6, 2019, at 4:52 PM, Ayden Férdeline <icann@ferdeline.com<mailto:icann@ferdeline.com>> wrote: Thanks, Keith. To kick off this discussion, broadly there are three areas where I would like to see improvements to this document. Firstly, I'd like to see a new planning stage altogether. This should see a proper regulatory impact assessment carried out, so we can understand the intended rationale for a law/regulation/directive, specific extracts of the proposed text that could have implications on activities within ICANN's remit, and perhaps most importantly, the document should outline concretely what implications are anticipated for ICANN. A roadmap or timeline should be included so we understand how imminent the law/regulation/directive is and when we need to take action. The current, crowdsourced approach where the community is expected to identify errors and omissions in the document is inappropriate. If ICANN is a professional organization then its professional staff should be monitoring the regulatory landscape within which we operate. Then, I'd like to see a new stage or chapter to the report outlining the response being taken. So, once a law/regulation/directive is here and we've identified we need to take action and we know when enforcement begins, the report should offer a detailed analysis that outlines more specifically what options the GNSO Council or other parties could consider taking to ensure legal compliance. Third, once a law/regulation/directive is in place and we have taken actions to comply with it, ICANN should monitor 1) the impact the law/regulation/directive has had as it relates to ICANN's remit, 2) evaluate how successful/unsuccessful our response was, and 3) if necessary and only with extensive community consultation first feed back to lawmakers if there has been a mismatch between their intended rationale for a law/regulation/directive and reality. There are two other characteristics that I consider to be very important for this tracker. It should use clear, succinct, and plain language, regardless of the issue's complexity. It must be accurate and kept up to date, always based upon the latest information. In order for this resource to be useful it should not be circulated until ICANN has verified that it transports the correct and necessary messages. Best wishes, Ayden Férdeline ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Thursday, April 4, 2019 8:35 PM, Drazek, Keith via council <council@gnso.icann.org<mailto:council@gnso.icann.org>> wrote: Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana: During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort. As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development. Please work together and with Staff to help kick off this important and timely work. Thanks, Keith _______________________________________________ council mailing list council@gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council ________________________________ The contents of this message may be privileged and confidential. If this message has been received in error, please delete it without reading it. Your receipt of this message is not intended to waive any applicable privilege. Please do not disseminate this message without the permission of the author. Any tax advice contained in this email was not intended to be used, and cannot be used, by you (or any other taxpayer) to avoid penalties under applicable tax laws and regulations.
Dear All: 1. I think valid points are being made. Dialogue is key, but I also believe the report – if quality is assured – can be a useful tool to streamline discussions and set priorities. The regulatory impact report should supplement, not replace, dialogue with ICANN’s government relations staff. If we indeed want the report to help structure the dialogue and assist with our policy planning, it is key that the report contains correct and up-to-date information. I agree that the current approach, where the community is expected to identify errors and omissions, is inappropriate. We may expect from ICANN that it is on top of things and consults with regional experts to correctly assess the impact of new/impending legislation. 2. It is my understanding that the Report currently focuses on Privacy/Data Protection and Cybersecurity only. Should we/ICANN org not expand the scope? For instance, it might be useful to add the proposed EU Directive on Copyright in the Digital Single Market (already approved by the European Parliament) to our watchlist, as well as regulations regarding net neutrality or geoblocking. I would expect us/ICANN to take a proactive approach on the legislative/regulatory field. I am interested to hear your thoughts. Best, Flip Flip Petillion fpetillion@petillion.law +32484652653 www.petillion.law [signature_787659922]<http://www.petillion.law/> Attorneys – Advocaten - Avocats From: council <council-bounces@gnso.icann.org> on behalf of "McGrady, Paul D." <PMcGrady@winston.com> Date: Sunday, 7 April 2019 at 13:16 To: Martin Pablo Silva Valent <mpsilvavalent@gmail.com>, Ayden Férdeline <icann@ferdeline.com> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org>, "council@gnso.icann.org" <council@gnso.icann.org> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Hi All, As I tried to express from the Council table in Kobe, I guess I am less concerned with the format, etc. of the document and, instead, believe that we need ICANN’s government relations folks to visit us at Council and highlight the main issues it sees heading our way. Otherwise, this is just one more of a thousand documents we all need to read to get ready for the next meeting and we may or may not have the appropriate sense of urgency. We can’t let whether or not contracted parties may face a fine be the only method by which we decide compliance with a forthcoming law is, or is not, important and urgent. This process needs to be a dialogue with Org staff, not a pen pal. Best, Paul From: council <council-bounces@gnso.icann.org> On Behalf Of Martin Pablo Silva Valent Sent: Saturday, April 6, 2019 8:39 PM To: Ayden Férdeline <icann@ferdeline.com> Cc: gnso-secs@icann.org; council@gnso.icann.org Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements I now in the LAC region we have intensive community activity with a LAC Strategy group and all. I can alway give my input, but it will always be better to not duplicate efforts, If the LAC staff is already doing update on this issue , I am fine following that work and not leading a new one from scratch. If they are not specially doing an update on this, then I am happily helping them to put something together. In all cases, I think ICANN regional staff could send a few emails and get legal updates from every LAC country, specially if it uses the partnerships and links it has with NGOs and Chambers. What do you guys think? Should we talk this as an GNSO thing or level thing region by region? Best, Martin Silva Valent mpsilvavalent@gmail.com<mailto:mpsilvavalent@gmail.com> Partner | Silva.legal martin@silva.legal<mailto:martin@silva.legal> Director | Dat.as martin.silva@dat.as<mailto:martin.silva@dat.as> Skype ID: mpsilvavalent Tel: +5491164993943 Libertador 5990, Off. 406 Buenos Aires, Argentina. Este email, incluyendo adjuntos, podría contener información confidencial protegida por ley y es para uso exclusivo de su destinatario. Si Ud. no es el destinatario, se le advierte que cualquier uso, difusión, copia o retención de este email o su contenido está estrictamente prohibido. Si Ud. recibió este email por error, por favor avise inmediatamente al remitente por teléfono o email y borre el mismo de su computadora. / This e-mail, including any attachments, may contain information that is protected by law as privileged and confidential, and is transmitted for the sole use of the intended recipient. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying or retention of this e-mail or the information contained herein is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by telephone or reply e-mail, and permanently delete this e-mail from your computer system. On Apr 6, 2019, at 4:52 PM, Ayden Férdeline <icann@ferdeline.com<mailto:icann@ferdeline.com>> wrote: Thanks, Keith. To kick off this discussion, broadly there are three areas where I would like to see improvements to this document. Firstly, I'd like to see a new planning stage altogether. This should see a proper regulatory impact assessment carried out, so we can understand the intended rationale for a law/regulation/directive, specific extracts of the proposed text that could have implications on activities within ICANN's remit, and perhaps most importantly, the document should outline concretely what implications are anticipated for ICANN. A roadmap or timeline should be included so we understand how imminent the law/regulation/directive is and when we need to take action. The current, crowdsourced approach where the community is expected to identify errors and omissions in the document is inappropriate. If ICANN is a professional organization then its professional staff should be monitoring the regulatory landscape within which we operate. Then, I'd like to see a new stage or chapter to the report outlining the response being taken. So, once a law/regulation/directive is here and we've identified we need to take action and we know when enforcement begins, the report should offer a detailed analysis that outlines more specifically what options the GNSO Council or other parties could consider taking to ensure legal compliance. Third, once a law/regulation/directive is in place and we have taken actions to comply with it, ICANN should monitor 1) the impact the law/regulation/directive has had as it relates to ICANN's remit, 2) evaluate how successful/unsuccessful our response was, and 3) if necessary and only with extensive community consultation first feed back to lawmakers if there has been a mismatch between their intended rationale for a law/regulation/directive and reality. There are two other characteristics that I consider to be very important for this tracker. It should use clear, succinct, and plain language, regardless of the issue's complexity. It must be accurate and kept up to date, always based upon the latest information. In order for this resource to be useful it should not be circulated until ICANN has verified that it transports the correct and necessary messages. Best wishes, Ayden Férdeline ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Thursday, April 4, 2019 8:35 PM, Drazek, Keith via council <council@gnso.icann.org<mailto:council@gnso.icann.org>> wrote: Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana: During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort. As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development. Please work together and with Staff to help kick off this important and timely work. Thanks, Keith _______________________________________________ council mailing list council@gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council ________________________________ The contents of this message may be privileged and confidential. If this message has been received in error, please delete it without reading it. Your receipt of this message is not intended to waive any applicable privilege. Please do not disseminate this message without the permission of the author. Any tax advice contained in this email was not intended to be used, and cannot be used, by you (or any other taxpayer) to avoid penalties under applicable tax laws and regulations.
Keith, All - I believe the current format and information gathering practice ( https://www.icann.org/en/system/files/files/legislative-regulatory-30jan19-e...) is not sufficient and would therefore recommend few things: - ICANN ORG should work with a professional firm in receiving regular updates (monitoring report) about regulatory issues that cause concern - To make such a Monitoring Report (MR) not too expensive - ICANN should focus on few regions, regions that cause the majority of concerns - Monitoring reports should be received 4 times/year - Early warning notes should be received as quickly as possible - The current Crowed Sourced Tracking Report should remain as an additional information source https://www.icann.org/en/system/files/files/legislative-regulatory-30jan19-e... - I agree with Paul that it is key "CANN’s government relations folks to visit us at Council and highlight the main issues it sees heading our way" - I agree with Flip, the list of topics that should be monitored need to be broadened - I agree with Ayden to some degree but recommend to focus on few aspect "ICANN should monitor 1) the impact the law/regulation/directive has had as it relates to ICANN's remit" and, once a legislation is introduced, ICANN must do a compliance assessment. I don't believe that lobbying strategies should be broadly discussed in the community. - I agree with Martin, the Crowed Sourced Tracking Report should cooperate with existing Regional Intelligence Tracking Reports. Kind regards, Erika On Thu, Apr 4, 2019 at 8:35 PM Drazek, Keith via council < council@gnso.icann.org> wrote:
Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana:
During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort.
As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development.
Please work together and with Staff to help kick off this important and timely work.
Thanks,
Keith
_______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council
Are there any firms that offer this kind of tracking service globally? I know of ones that track EU *or* US issues, but I’m not aware of any that are global in coverage and expertise Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ https://blacknight.blog/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 Personal blog: https://michele.blog/ Some thoughts: https://ceo.hosting/ ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845 From: council <council-bounces@gnso.icann.org> on behalf of Erika Mann <erika@erikamann.com> Date: Wednesday 10 April 2019 at 11:01 To: Keith Drazek <kdrazek@verisign.com> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org>, "council@gnso.icann.org" <council@gnso.icann.org> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Keith, All - I believe the current format and information gathering practice (https://www.icann.org/en/system/files/files/legislative-regulatory-30jan19-e...) is not sufficient and would therefore recommend few things: * ICANN ORG should work with a professional firm in receiving regular updates (monitoring report) about regulatory issues that cause concern * To make such a Monitoring Report (MR) not too expensive * ICANN should focus on few regions, regions that cause the majority of concerns * Monitoring reports should be received 4 times/year * Early warning notes should be received as quickly as possible * The current Crowed Sourced Tracking Report should remain as an additional information source https://www.icann.org/en/system/files/files/legislative-regulatory-30jan19-e... * I agree with Paul that it is key "CANN’s government relations folks to visit us at Council and highlight the main issues it sees heading our way" * I agree with Flip, the list of topics that should be monitored need to be broadened * I agree with Ayden to some degree but recommend to focus on few aspect "ICANN should monitor 1) the impact the law/regulation/directive has had as it relates to ICANN's remit" and, once a legislation is introduced, ICANN must do a compliance assessment. I don't believe that lobbying strategies should be broadly discussed in the community. * I agree with Martin, the Crowed Sourced Tracking Report should cooperate with existing Regional Intelligence Tracking Reports. Kind regards, Erika On Thu, Apr 4, 2019 at 8:35 PM Drazek, Keith via council <council@gnso.icann.org<mailto:council@gnso.icann.org>> wrote: Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana: During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort. As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development. Please work together and with Staff to help kick off this important and timely work. Thanks, Keith _______________________________________________ council mailing list council@gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council
Yes, few are even good. But I don’t believe ICANN needs global monitoring. It’s sufficient to focus on regions/countries that take the lead in regulatory efforts. Sent from my iPhone
On Apr 10, 2019, at 1:55 PM, Michele Neylon - Blacknight <michele@blacknight.com> wrote:
Are there any firms that offer this kind of tracking service globally?
I know of ones that track EU *or* US issues, but I’m not aware of any that are global in coverage and expertise
Regards
Michele
-- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ https://blacknight.blog/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 Personal blog: https://michele.blog/ Some thoughts: https://ceo.hosting/ ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845
From: council <council-bounces@gnso.icann.org> on behalf of Erika Mann <erika@erikamann.com> Date: Wednesday 10 April 2019 at 11:01 To: Keith Drazek <kdrazek@verisign.com> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org>, "council@gnso.icann.org" <council@gnso.icann.org> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
Keith, All -
I believe the current format and information gathering practice (https://www.icann.org/en/system/files/files/legislative-regulatory-30jan19-e...) is not sufficient and would therefore recommend few things: ICANN ORG should work with a professional firm in receiving regular updates (monitoring report) about regulatory issues that cause concern To make such a Monitoring Report (MR) not too expensive ICANN should focus on few regions, regions that cause the majority of concerns Monitoring reports should be received 4 times/year Early warning notes should be received as quickly as possible The current Crowed Sourced Tracking Report should remain as an additional information source https://www.icann.org/en/system/files/files/legislative-regulatory-30jan19-e... I agree with Paul that it is key "CANN’s government relations folks to visit us at Council and highlight the main issues it sees heading our way" I agree with Flip, the list of topics that should be monitored need to be broadened I agree with Ayden to some degree but recommend to focus on few aspect "ICANN should monitor 1) the impact the law/regulation/directive has had as it relates to ICANN's remit" and, once a legislation is introduced, ICANN must do a compliance assessment. I don't believe that lobbying strategies should be broadly discussed in the community. I agree with Martin, the Crowed Sourced Tracking Report should cooperate with existing Regional Intelligence Tracking Reports. Kind regards, Erika
On Thu, Apr 4, 2019 at 8:35 PM Drazek, Keith via council <council@gnso.icann.org> wrote: Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana:
During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort.
As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development.
Please work together and with Staff to help kick off this important and timely work.
Thanks, Keith
_______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council
Carlos A very logical suggestion in my view! Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ https://blacknight.blog/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 Personal blog: https://michele.blog/ Some thoughts: https://ceo.hosting/ ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845 From: council <council-bounces@gnso.icann.org> on behalf of Carlos Raul Gutierrez <carlosraul@gutierrez.se> Date: Wednesday 10 April 2019 at 13:27 To: Erika Mann <erika@erikamann.com> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org>, "council@gnso.icann.org" <council@gnso.icann.org> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements A lot of good ideas but I don't see the GAC in any of those. The most probable source or shapping force of any initiative that may be closely related and affect the DNS is sitting in the next room at every meeting. What about asking them? Thanks! Carlos Raúl Gutiérrez El 10 abr. 2019 4:01, Erika Mann <erika@erikamann.com> escribió: Keith, All - I believe the current format and information gathering practice (https://www.icann.org/en/system/files/files/legislative-regulatory-30jan19-e...) is not sufficient and would therefore recommend few things: * ICANN ORG should work with a professional firm in receiving regular updates (monitoring report) about regulatory issues that cause concern · * To make such a Monitoring Report (MR) not too expensive o * ICANN should focus on few regions, regions that cause the majority of concerns * Monitoring reports should be received 4 times/year * Early warning notes should be received as quickly as possible * The current Crowed Sourced Tracking Report should remain as an additional information source https://www.icann.org/en/system/files/files/legislative-regulatory-30jan19-e... * I agree with Paul that it is key "CANN’s government relations folks to visit us at Council and highlight the main issues it sees heading our way" * I agree with Flip, the list of topics that should be monitored need to be broadened * I agree with Ayden to some degree but recommend to focus on few aspect "ICANN should monitor 1) the impact the law/regulation/directive has had as it relates to ICANN's remit" and, once a legislation is introduced, ICANN must do a compliance assessment. I don't believe that lobbying strategies should be broadly discussed in the community. * I agree with Martin, the Crowed Sourced Tracking Report should cooperate with existing Regional Intelligence Tracking Reports. Kind regards, Erika On Thu, Apr 4, 2019 at 8:35 PM Drazek, Keith via council <council@gnso.icann.org<mailto:council@gnso.icann.org>> wrote: Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana: During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort. As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development. Please work together and with Staff to help kick off this important and timely work. Thanks, Keith _______________________________________________ council mailing list council@gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council
Carlos - we can add the GAC to the list as an important partner but I doubt many will be able in alerting ICANN about potentially problematic legislations they're or their parliaments are drafting. In many cases they will not even know. For example, I'm doubtful that the European Parliament, the European Commission or European Member States are aware about potentially - for the domain sector - problematic aspects of the copyright law they recently all supported. Erika On Wed, Apr 10, 2019 at 2:26 PM Carlos Raul Gutierrez < carlosraul@gutierrez.se> wrote:
A lot of good ideas but I don't see the GAC in any of those. The most probable source or shapping force of any initiative that may be closely related and affect the DNS is sitting in the next room at every meeting. What about asking them?
Thanks! Carlos Raúl Gutiérrez
El 10 abr. 2019 4:01, Erika Mann <erika@erikamann.com> escribió:
Keith, All -
I believe the current format and information gathering practice ( https://www.icann.org/en/system/files/files/legislative-regulatory-30jan19-e...) is not sufficient and would therefore recommend few things:
- ICANN ORG should work with a professional firm in receiving regular updates (monitoring report) about regulatory issues that cause concern - - To make such a Monitoring Report (MR) not too expensive - - ICANN should focus on few regions, regions that cause the majority of concerns - Monitoring reports should be received 4 times/year - Early warning notes should be received as quickly as possible - The current Crowed Sourced Tracking Report should remain as an additional information source https://www.icann.org/en/system/files/files/legislative-regulatory-30jan19-e... - I agree with Paul that it is key "CANN’s government relations folks to visit us at Council and highlight the main issues it sees heading our way" - I agree with Flip, the list of topics that should be monitored need to be broadened - I agree with Ayden to some degree but recommend to focus on few aspect "ICANN should monitor 1) the impact the law/regulation/directive has had as it relates to ICANN's remit" and, once a legislation is introduced, ICANN must do a compliance assessment. I don't believe that lobbying strategies should be broadly discussed in the community. - I agree with Martin, the Crowed Sourced Tracking Report should cooperate with existing Regional Intelligence Tracking Reports.
Kind regards, Erika
On Thu, Apr 4, 2019 at 8:35 PM Drazek, Keith via council < council@gnso.icann.org> wrote:
Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana:
During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort.
As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development.
Please work together and with Staff to help kick off this important and timely work.
Thanks,
Keith
_______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council
I don't mind Carlos, but keep in mind, DNA related legislative challenges are often embedded in legislation that don't appear to carry such risks. Erika On Wed, Apr 10, 2019 at 8:59 PM Carlos Raul Gutierrez < carlosraul@gutierrez.se> wrote:
Let's start with a short survey to all GAC participants during ICANN65, to test their level of involvement with their local legislation relating to the DNS. We may get some leads.....
Thanks! Carlos Raúl Gutiérrez
El 10 abr. 2019 7:27, Erika Mann <erika@erikamann.com> escribió:
Carlos - we can add the GAC to the list as an important partner but I doubt many will be able in alerting ICANN about potentially problematic legislations they're or their parliaments are drafting. In many cases they will not even know. For example, I'm doubtful that the European Parliament, the European Commission or European Member States are aware about potentially - for the domain sector - problematic aspects of the copyright law they recently all supported. Erika
On Wed, Apr 10, 2019 at 2:26 PM Carlos Raul Gutierrez < carlosraul@gutierrez.se> wrote:
A lot of good ideas but I don't see the GAC in any of those. The most probable source or shapping force of any initiative that may be closely related and affect the DNS is sitting in the next room at every meeting. What about asking them?
Thanks! Carlos Raúl Gutiérrez
El 10 abr. 2019 4:01, Erika Mann <erika@erikamann.com> escribió:
Keith, All -
I believe the current format and information gathering practice ( https://www.icann.org/en/system/files/files/legislative-regulatory-30jan19-e...) is not sufficient and would therefore recommend few things:
- ICANN ORG should work with a professional firm in receiving regular updates (monitoring report) about regulatory issues that cause concern - - To make such a Monitoring Report (MR) not too expensive - - ICANN should focus on few regions, regions that cause the majority of concerns - Monitoring reports should be received 4 times/year - Early warning notes should be received as quickly as possible - The current Crowed Sourced Tracking Report should remain as an additional information source https://www.icann.org/en/system/files/files/legislative-regulatory-30jan19-e... - I agree with Paul that it is key "CANN’s government relations folks to visit us at Council and highlight the main issues it sees heading our way" - I agree with Flip, the list of topics that should be monitored need to be broadened - I agree with Ayden to some degree but recommend to focus on few aspect "ICANN should monitor 1) the impact the law/regulation/directive has had as it relates to ICANN's remit" and, once a legislation is introduced, ICANN must do a compliance assessment. I don't believe that lobbying strategies should be broadly discussed in the community. - I agree with Martin, the Crowed Sourced Tracking Report should cooperate with existing Regional Intelligence Tracking Reports.
Kind regards, Erika
On Thu, Apr 4, 2019 at 8:35 PM Drazek, Keith via council < council@gnso.icann.org> wrote:
Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana:
During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort.
As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development.
Please work together and with Staff to help kick off this important and timely work.
Thanks,
Keith
_______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council
Erika Sure, but I think the point Carlos was trying to make is that we and ICANN should be leveraging the resources we already have. The GAC should be one. Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ https://blacknight.blog/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 Personal blog: https://michele.blog/ Some thoughts: https://ceo.hosting/ ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845 From: council <council-bounces@gnso.icann.org> on behalf of Erika Mann <erika@erikamann.com> Date: Thursday 11 April 2019 at 10:30 To: Carlos Raul Gutierrez <carlosraul@gutierrez.se> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org>, "GNSO Council List (council@gnso.icann.org)" <council@gnso.icann.org> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements I don't mind Carlos, but keep in mind, DNA related legislative challenges are often embedded in legislation that don't appear to carry such risks. Erika On Wed, Apr 10, 2019 at 8:59 PM Carlos Raul Gutierrez <carlosraul@gutierrez.se<mailto:carlosraul@gutierrez.se>> wrote: Let's start with a short survey to all GAC participants during ICANN65, to test their level of involvement with their local legislation relating to the DNS. We may get some leads..... Thanks! Carlos Raúl Gutiérrez El 10 abr. 2019 7:27, Erika Mann <erika@erikamann.com<mailto:erika@erikamann.com>> escribió: Carlos - we can add the GAC to the list as an important partner but I doubt many will be able in alerting ICANN about potentially problematic legislations they're or their parliaments are drafting. In many cases they will not even know. For example, I'm doubtful that the European Parliament, the European Commission or European Member States are aware about potentially - for the domain sector - problematic aspects of the copyright law they recently all supported. Erika On Wed, Apr 10, 2019 at 2:26 PM Carlos Raul Gutierrez <carlosraul@gutierrez.se<mailto:carlosraul@gutierrez.se>> wrote: A lot of good ideas but I don't see the GAC in any of those. The most probable source or shapping force of any initiative that may be closely related and affect the DNS is sitting in the next room at every meeting. What about asking them? Thanks! Carlos Raúl Gutiérrez El 10 abr. 2019 4:01, Erika Mann <erika@erikamann.com<mailto:erika@erikamann.com>> escribió: Keith, All - I believe the current format and information gathering practice (https://www.icann.org/en/system/files/files/legislative-regulatory-30jan19-e...) is not sufficient and would therefore recommend few things: * ICANN ORG should work with a professional firm in receiving regular updates (monitoring report) about regulatory issues that cause concern · * To make such a Monitoring Report (MR) not too expensive o * ICANN should focus on few regions, regions that cause the majority of concerns * Monitoring reports should be received 4 times/year * Early warning notes should be received as quickly as possible * The current Crowed Sourced Tracking Report should remain as an additional information source https://www.icann.org/en/system/files/files/legislative-regulatory-30jan19-e... * I agree with Paul that it is key "CANN’s government relations folks to visit us at Council and highlight the main issues it sees heading our way" * I agree with Flip, the list of topics that should be monitored need to be broadened * I agree with Ayden to some degree but recommend to focus on few aspect "ICANN should monitor 1) the impact the law/regulation/directive has had as it relates to ICANN's remit" and, once a legislation is introduced, ICANN must do a compliance assessment. I don't believe that lobbying strategies should be broadly discussed in the community. * I agree with Martin, the Crowed Sourced Tracking Report should cooperate with existing Regional Intelligence Tracking Reports. Kind regards, Erika On Thu, Apr 4, 2019 at 8:35 PM Drazek, Keith via council <council@gnso.icann.org<mailto:council@gnso.icann.org>> wrote: Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana: During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort. As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development. Please work together and with Staff to help kick off this important and timely work. Thanks, Keith _______________________________________________ council mailing list council@gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council
Michele - Absolutely, and I supported his approach but I don't expect a successful outcome. Best, Erika On Thu, Apr 11, 2019 at 11:44 AM Michele Neylon - Blacknight < michele@blacknight.com> wrote:
Erika
Sure, but I think the point Carlos was trying to make is that we and ICANN should be leveraging the resources we already have. The GAC should be one.
Regards
Michele
--
Mr Michele Neylon
Blacknight Solutions
Hosting, Colocation & Domains
Intl. +353 (0) 59 9183072
Direct Dial: +353 (0)59 9183090
Personal blog: https://michele.blog/
Some thoughts: https://ceo.hosting/
-------------------------------
Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty
Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845
*From: *council <council-bounces@gnso.icann.org> on behalf of Erika Mann < erika@erikamann.com> *Date: *Thursday 11 April 2019 at 10:30 *To: *Carlos Raul Gutierrez <carlosraul@gutierrez.se> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org>, "GNSO Council List ( council@gnso.icann.org)" <council@gnso.icann.org> *Subject: *Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
I don't mind Carlos, but keep in mind, DNA related legislative challenges are often embedded in legislation that don't appear to carry such risks.
Erika
On Wed, Apr 10, 2019 at 8:59 PM Carlos Raul Gutierrez < carlosraul@gutierrez.se> wrote:
Let's start with a short survey to all GAC participants during ICANN65, to test their level of involvement with their local legislation relating to the DNS. We may get some leads.....
Thanks! Carlos Raúl Gutiérrez
El 10 abr. 2019 7:27, Erika Mann <erika@erikamann.com> escribió:
Carlos - we can add the GAC to the list as an important partner but I doubt many will be able in alerting ICANN about potentially problematic legislations they're or their parliaments are drafting. In many cases they will not even know. For example, I'm doubtful that the European Parliament, the European Commission or European Member States are aware about potentially - for the domain sector - problematic aspects of the copyright law they recently all supported.
Erika
On Wed, Apr 10, 2019 at 2:26 PM Carlos Raul Gutierrez < carlosraul@gutierrez.se> wrote:
A lot of good ideas but I don't see the GAC in any of those. The most probable source or shapping force of any initiative that may be closely related and affect the DNS is sitting in the next room at every meeting. What about asking them?
Thanks! Carlos Raúl Gutiérrez
El 10 abr. 2019 4:01, Erika Mann <erika@erikamann.com> escribió:
Keith, All -
I believe the current format and information gathering practice ( https://www.icann.org/en/system/files/files/legislative-regulatory-30jan19-e...) is not sufficient and would therefore recommend few things:
- ICANN ORG should work with a professional firm in receiving regular updates (monitoring report) about regulatory issues that cause concern
·
- To make such a Monitoring Report (MR) not too expensive
o
- ICANN should focus on few regions, regions that cause the majority of concerns - Monitoring reports should be received 4 times/year - Early warning notes should be received as quickly as possible
- The current Crowed Sourced Tracking Report should remain as an additional information source https://www.icann.org/en/system/files/files/legislative-regulatory-30jan19-e... - I agree with Paul that it is key "CANN’s government relations folks to visit us at Council and highlight the main issues it sees heading our way" - I agree with Flip, the list of topics that should be monitored need to be broadened - I agree with Ayden to some degree but recommend to focus on few aspect "ICANN should monitor 1) the impact the law/regulation/directive has had as it relates to ICANN's remit" and, once a legislation is introduced, ICANN must do a compliance assessment. I don't believe that lobbying strategies should be broadly discussed in the community. - I agree with Martin, the Crowed Sourced Tracking Report should cooperate with existing Regional Intelligence Tracking Reports.
Kind regards,
Erika
On Thu, Apr 4, 2019 at 8:35 PM Drazek, Keith via council < council@gnso.icann.org> wrote:
Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana:
During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort.
As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development.
Please work together and with Staff to help kick off this important and timely work.
Thanks,
Keith
_______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council
I also agree with this approach. Probably not hold our breath, nor recommend to use them as the sole source of information, for the reasons Erika gave. But anyway this is not a GNSO-specific effort, I would think GAC can be expected to provide some input on a “cross community” initiative tagged with words like “regulatory” or “governmental”. Question is indeed, is it reliable, authoritative, consistent etc. Regards, Philippe From: council [mailto:council-bounces@gnso.icann.org] On Behalf Of Erika Mann Sent: Thursday, April 11, 2019 11:56 AM To: Michele Neylon - Blacknight Cc: gnso-SECS; GNSO Council List (council@gnso.icann.org) Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Michele - Absolutely, and I supported his approach but I don't expect a successful outcome. Best, Erika On Thu, Apr 11, 2019 at 11:44 AM Michele Neylon - Blacknight <michele@blacknight.com<mailto:michele@blacknight.com>> wrote: Erika Sure, but I think the point Carlos was trying to make is that we and ICANN should be leveraging the resources we already have. The GAC should be one. Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ https://blacknight.blog/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 Personal blog: https://michele.blog/ Some thoughts: https://ceo.hosting/ ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845 From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of Erika Mann <erika@erikamann.com<mailto:erika@erikamann.com>> Date: Thursday 11 April 2019 at 10:30 To: Carlos Raul Gutierrez <carlosraul@gutierrez.se<mailto:carlosraul@gutierrez.se>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>>, "GNSO Council List (council@gnso.icann.org<mailto:council@gnso.icann.org>)" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements I don't mind Carlos, but keep in mind, DNA related legislative challenges are often embedded in legislation that don't appear to carry such risks. Erika On Wed, Apr 10, 2019 at 8:59 PM Carlos Raul Gutierrez <carlosraul@gutierrez.se<mailto:carlosraul@gutierrez.se>> wrote: Let's start with a short survey to all GAC participants during ICANN65, to test their level of involvement with their local legislation relating to the DNS. We may get some leads..... Thanks! Carlos Raúl Gutiérrez El 10 abr. 2019 7:27, Erika Mann <erika@erikamann.com<mailto:erika@erikamann.com>> escribió: Carlos - we can add the GAC to the list as an important partner but I doubt many will be able in alerting ICANN about potentially problematic legislations they're or their parliaments are drafting. In many cases they will not even know. For example, I'm doubtful that the European Parliament, the European Commission or European Member States are aware about potentially - for the domain sector - problematic aspects of the copyright law they recently all supported. Erika On Wed, Apr 10, 2019 at 2:26 PM Carlos Raul Gutierrez <carlosraul@gutierrez.se<mailto:carlosraul@gutierrez.se>> wrote: A lot of good ideas but I don't see the GAC in any of those. The most probable source or shapping force of any initiative that may be closely related and affect the DNS is sitting in the next room at every meeting. What about asking them? Thanks! Carlos Raúl Gutiérrez El 10 abr. 2019 4:01, Erika Mann <erika@erikamann.com<mailto:erika@erikamann.com>> escribió: Keith, All - I believe the current format and information gathering practice (https://www.icann.org/en/system/files/files/legislative-regulatory-30jan19-e...) is not sufficient and would therefore recommend few things: * ICANN ORG should work with a professional firm in receiving regular updates (monitoring report) about regulatory issues that cause concern • * To make such a Monitoring Report (MR) not too expensive o * ICANN should focus on few regions, regions that cause the majority of concerns * Monitoring reports should be received 4 times/year * Early warning notes should be received as quickly as possible * The current Crowed Sourced Tracking Report should remain as an additional information source https://www.icann.org/en/system/files/files/legislative-regulatory-30jan19-e... * I agree with Paul that it is key "CANN’s government relations folks to visit us at Council and highlight the main issues it sees heading our way" * I agree with Flip, the list of topics that should be monitored need to be broadened * I agree with Ayden to some degree but recommend to focus on few aspect "ICANN should monitor 1) the impact the law/regulation/directive has had as it relates to ICANN's remit" and, once a legislation is introduced, ICANN must do a compliance assessment. I don't believe that lobbying strategies should be broadly discussed in the community. * I agree with Martin, the Crowed Sourced Tracking Report should cooperate with existing Regional Intelligence Tracking Reports. Kind regards, Erika On Thu, Apr 4, 2019 at 8:35 PM Drazek, Keith via council <council@gnso.icann.org<mailto:council@gnso.icann.org>> wrote: Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana: During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort. As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development. Please work together and with Staff to help kick off this important and timely work. Thanks, Keith _______________________________________________ council mailing list council@gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
Dear Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana, In reviewing the Council’s action items, we recognized that the item below is still outstanding: Small group of Councilors to develop draft message to ICANN Org to provide input on legislative tracker. Based on feedback, Council leadership to consider scheduling follow up discussion at ICANN65. We wanted to bring this to your attention, as you all volunteered to work on this item. While the latter part of the action item (e.g., engaging at ICANN65) is likely impractical at this point, you may still want to draft a message to send to ICANN org. As Keith noted, please work together and let staff know if you need any assistance. Best, Steve From: council <council-bounces@gnso.icann.org> on behalf of "Drazek, Keith via council" <council@gnso.icann.org> Reply-To: "Drazek, Keith" <kdrazek@verisign.com> Date: Thursday, April 4, 2019 at 7:35 PM To: "council@gnso.icann.org" <council@gnso.icann.org> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org> Subject: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana: During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort. As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development. Please work together and with Staff to help kick off this important and timely work. Thanks, Keith
Dear Steve - I believe I forwarded such information about regulatory initiates, that I believe ICANN should look into, already - in case I forgot, apologies. I will review my old list and will update it with new and relevant information. The most important initiatives for ICANN are the following in the European Union: - Transposition of the European Union Copyright Directive into national laws. The European Union legislation will not be transposed into national laws identically. This may cause difficulties for some of ICANNs stakeholders. - NEW - review of the eCommerce Directive. Danger is that the existing liability exemptions for Internet providers, operators, will fall. - New obligations to monitor and censor harmful content. Various initiatives currently under legal considerations, in particular in the UK, France and, to some degree, in the EU. Kind regards, Erika On Sun, Jun 23, 2019 at 6:02 PM Steve Chan <steve.chan@icann.org> wrote:
Dear Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana,
In reviewing the Council’s action items, we recognized that the item below is still outstanding:
*Small group of Councilors* to develop draft message to ICANN Org to provide input on legislative tracker. Based on feedback, Council leadership to consider scheduling follow up discussion at ICANN65.
We wanted to bring this to your attention, as you all volunteered to work on this item. While the latter part of the action item (e.g., engaging at ICANN65) is likely impractical at this point, you may still want to draft a message to send to ICANN org. As Keith noted, please work together and let staff know if you need any assistance.
Best,
Steve
*From: *council <council-bounces@gnso.icann.org> on behalf of "Drazek, Keith via council" <council@gnso.icann.org> *Reply-To: *"Drazek, Keith" <kdrazek@verisign.com> *Date: *Thursday, April 4, 2019 at 7:35 PM *To: *"council@gnso.icann.org" <council@gnso.icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org> *Subject: *[council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana:
During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort.
As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development.
Please work together and with Staff to help kick off this important and timely work.
Thanks,
Keith
_______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council
_______________________________________________ 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.
In LAC I would need to reach out to a lot of folks, so I can have a country by country update. If I had ICANN power to follow that is absolutely doable. To have an excel with each country initiatives, receiving three reports from each country, one from a big law firm and another one from a civil society NGO with legal activism and a last one from a government representative: In the region there is relevant activity in the following areas that could impact DNS operations (there are others, I am sure, but this I know for a fact exist in several jurisdictions): - New Data Privacy laws, some of them as ripples of the GDPR in Europe - Intermediary Liability laws and Supreme Court precedents, to either filter, control o provide protections to third parties right, image, IP, fake news, etc. - Trademark or Domain Name laws, INCLUDING Treaties. (Some Free trade agreements in LatAm have DNS provision to address trademark protection, as they might also have Data Protection or Intermediary Liability provisions) - Ciber-crime laws, might also put special strains in the infrastructure law requirements in legal investigations, from scams to child protection. Best, Martin Silva Valent mpsilvavalent@gmail.com Partner | Silva.legal martin@silva.legal Director | Dat.as martin.silva@dat.as Skype ID: mpsilvavalent Tel: +5491164993943 Libertador 5990, Off. 406 Buenos Aires, Argentina. Este email, incluyendo adjuntos, podría contener información confidencial protegida por ley y es para uso exclusivo de su destinatario. Si Ud. no es el destinatario, se le advierte que cualquier uso, difusión, copia o retención de este email o su contenido está estrictamente prohibido. Si Ud. recibió este email por error, por favor avise inmediatamente al remitente por teléfono o email y borre el mismo de su computadora. / This e-mail, including any attachments, may contain information that is protected by law as privileged and confidential, and is transmitted for the sole use of the intended recipient. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying or retention of this e-mail or the information contained herein is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by telephone or reply e-mail, and permanently delete this e-mail from your computer system.
On Jun 23, 2019, at 6:37 PM, Erika Mann <erika@erikamann.com> wrote:
Dear Steve -
I believe I forwarded such information about regulatory initiates, that I believe ICANN should look into, already - in case I forgot, apologies. I will review my old list and will update it with new and relevant information.
The most important initiatives for ICANN are the following in the European Union: - Transposition of the European Union Copyright Directive into national laws. The European Union legislation will not be transposed into national laws identically. This may cause difficulties for some of ICANNs stakeholders. - NEW - review of the eCommerce Directive. Danger is that the existing liability exemptions for Internet providers, operators, will fall. - New obligations to monitor and censor harmful content. Various initiatives currently under legal considerations, in particular in the UK, France and, to some degree, in the EU.
Kind regards, Erika
On Sun, Jun 23, 2019 at 6:02 PM Steve Chan <steve.chan@icann.org <mailto:steve.chan@icann.org>> wrote: Dear Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana,
In reviewing the Council’s action items, we recognized that the item below is still outstanding:
Small group of Councilors to develop draft message to ICANN Org to provide input on legislative tracker. Based on feedback, Council leadership to consider scheduling follow up discussion at ICANN65.
We wanted to bring this to your attention, as you all volunteered to work on this item. While the latter part of the action item (e.g., engaging at ICANN65) is likely impractical at this point, you may still want to draft a message to send to ICANN org. As Keith noted, please work together and let staff know if you need any assistance.
Best,
Steve
From: council <council-bounces@gnso.icann.org <mailto:council-bounces@gnso.icann.org>> on behalf of "Drazek, Keith via council" <council@gnso.icann.org <mailto:council@gnso.icann.org>> Reply-To: "Drazek, Keith" <kdrazek@verisign.com <mailto:kdrazek@verisign.com>> Date: Thursday, April 4, 2019 at 7:35 PM To: "council@gnso.icann.org <mailto:council@gnso.icann.org>" <council@gnso.icann.org <mailto:council@gnso.icann.org>> Cc: "gnso-secs@icann.org <mailto:gnso-secs@icann.org>" <gnso-secs@icann.org <mailto:gnso-secs@icann.org>> Subject: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana:
During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort.
As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development.
Please work together and with Staff to help kick off this important and timely work.
Thanks,
Keith
_______________________________________________ council mailing list council@gnso.icann.org <mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council <https://mm.icann.org/mailman/listinfo/council>
_______________________________________________ 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://www.icann.org/privacy/policy>) and the website Terms of Service (https://www.icann.org/privacy/tos <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. _______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council
_______________________________________________ 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.
Just to follow up on Tatiana’s intervention today, I also think this is 100% ICANN org work, daily for operational reasons. As Council we can help to find the proper channels of information, but I think ICANN Org is in a far better position to say how to set up regular update system of relevant legislative and judiciary (legal?) norms to the DNS ecosystem of each country. Community can help to fund the best legal firms, NGOs or Government official, so staff can interact with and have an automated or quick way to monitor the legal risks that could impact our work. Not leaving this to ICANN org has the risk of becoming irrational, inefficient and yet another power struggle with GAC, when it should be a very data driven oriented work, where in the best scenario we can all review, analyze and even provide further input, but the base is there and general big thing won’t sneak up on us. Best, Martin Silva Valent mpsilvavalent@gmail.com Partner | Silva.legal martin@silva.legal Director | Dat.as martin.silva@dat.as Skype ID: mpsilvavalent Tel: +5491164993943 Libertador 5990, Off. 406 Buenos Aires, Argentina. Este email, incluyendo adjuntos, podría contener información confidencial protegida por ley y es para uso exclusivo de su destinatario. Si Ud. no es el destinatario, se le advierte que cualquier uso, difusión, copia o retención de este email o su contenido está estrictamente prohibido. Si Ud. recibió este email por error, por favor avise inmediatamente al remitente por teléfono o email y borre el mismo de su computadora. / This e-mail, including any attachments, may contain information that is protected by law as privileged and confidential, and is transmitted for the sole use of the intended recipient. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying or retention of this e-mail or the information contained herein is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by telephone or reply e-mail, and permanently delete this e-mail from your computer system.
On Jun 24, 2019, at 10:22 AM, Martin Pablo Silva Valent <mpsilvavalent@gmail.com> wrote:
In LAC I would need to reach out to a lot of folks, so I can have a country by country update. If I had ICANN power to follow that is absolutely doable. To have an excel with each country initiatives, receiving three reports from each country, one from a big law firm and another one from a civil society NGO with legal activism and a last one from a government representative:
In the region there is relevant activity in the following areas that could impact DNS operations (there are others, I am sure, but this I know for a fact exist in several jurisdictions):
- New Data Privacy laws, some of them as ripples of the GDPR in Europe - Intermediary Liability laws and Supreme Court precedents, to either filter, control o provide protections to third parties right, image, IP, fake news, etc. - Trademark or Domain Name laws, INCLUDING Treaties. (Some Free trade agreements in LatAm have DNS provision to address trademark protection, as they might also have Data Protection or Intermediary Liability provisions) - Ciber-crime laws, might also put special strains in the infrastructure law requirements in legal investigations, from scams to child protection.
Best,
Martin Silva Valent
mpsilvavalent@gmail.com <mailto:mpsilvavalent@gmail.com>
Partner | Silva.legal martin@silva.legal <mailto:martin@silva.legal>
Director | Dat.as martin.silva@dat.as <mailto:martin.silva@dat.as>
Skype ID: mpsilvavalent Tel: +5491164993943 Libertador 5990, Off. 406 Buenos Aires, Argentina.
Este email, incluyendo adjuntos, podría contener información confidencial protegida por ley y es para uso exclusivo de su destinatario. Si Ud. no es el destinatario, se le advierte que cualquier uso, difusión, copia o retención de este email o su contenido está estrictamente prohibido. Si Ud. recibió este email por error, por favor avise inmediatamente al remitente por teléfono o email y borre el mismo de su computadora. / This e-mail, including any attachments, may contain information that is protected by law as privileged and confidential, and is transmitted for the sole use of the intended recipient. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying or retention of this e-mail or the information contained herein is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by telephone or reply e-mail, and permanently delete this e-mail from your computer system.
On Jun 23, 2019, at 6:37 PM, Erika Mann <erika@erikamann.com <mailto:erika@erikamann.com>> wrote:
Dear Steve -
I believe I forwarded such information about regulatory initiates, that I believe ICANN should look into, already - in case I forgot, apologies. I will review my old list and will update it with new and relevant information.
The most important initiatives for ICANN are the following in the European Union: - Transposition of the European Union Copyright Directive into national laws. The European Union legislation will not be transposed into national laws identically. This may cause difficulties for some of ICANNs stakeholders. - NEW - review of the eCommerce Directive. Danger is that the existing liability exemptions for Internet providers, operators, will fall. - New obligations to monitor and censor harmful content. Various initiatives currently under legal considerations, in particular in the UK, France and, to some degree, in the EU.
Kind regards, Erika
On Sun, Jun 23, 2019 at 6:02 PM Steve Chan <steve.chan@icann.org <mailto:steve.chan@icann.org>> wrote: Dear Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana,
In reviewing the Council’s action items, we recognized that the item below is still outstanding:
Small group of Councilors to develop draft message to ICANN Org to provide input on legislative tracker. Based on feedback, Council leadership to consider scheduling follow up discussion at ICANN65.
We wanted to bring this to your attention, as you all volunteered to work on this item. While the latter part of the action item (e.g., engaging at ICANN65) is likely impractical at this point, you may still want to draft a message to send to ICANN org. As Keith noted, please work together and let staff know if you need any assistance.
Best,
Steve
From: council <council-bounces@gnso.icann.org <mailto:council-bounces@gnso.icann.org>> on behalf of "Drazek, Keith via council" <council@gnso.icann.org <mailto:council@gnso.icann.org>> Reply-To: "Drazek, Keith" <kdrazek@verisign.com <mailto:kdrazek@verisign.com>> Date: Thursday, April 4, 2019 at 7:35 PM To: "council@gnso.icann.org <mailto:council@gnso.icann.org>" <council@gnso.icann.org <mailto:council@gnso.icann.org>> Cc: "gnso-secs@icann.org <mailto:gnso-secs@icann.org>" <gnso-secs@icann.org <mailto:gnso-secs@icann.org>> Subject: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana:
During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort.
As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development.
Please work together and with Staff to help kick off this important and timely work.
Thanks,
Keith
_______________________________________________ council mailing list council@gnso.icann.org <mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council <https://mm.icann.org/mailman/listinfo/council>
_______________________________________________ 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://www.icann.org/privacy/policy>) and the website Terms of Service (https://www.icann.org/privacy/tos <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. _______________________________________________ council mailing list council@gnso.icann.org <mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council
_______________________________________________ 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.
I have drafted a message on behalf of the Council for Council's consideration on this topic. This is based upon our previous conversations. Please find attached and pasted below my signature. Thanks. Ayden Férdeline -- Recommended Improvements from the GNSO Council on ICANN Org Legislative Statement The GNSO Council supports ICANN org in its initiative to identify legislative and regulatory efforts across the globe that may have impacts on ICANN activities. However, we have some recommended improvements to the approach that ICANN org takes. - First, the GNSO Council believes that the current, crowdsourced approach where the community is expected to identify errors and omissions in the Global Legislative and Regulatory Developments Report is inappropriate. If ICANN is a professional organization then its professional staff should be comprehensively monitoring the regulatory landscape within which we operate. - Second, we encourage ICANN org to conduct proper regulatory impact assessments so that the community can understand the intended rationale for a law/regulation/directive, specific extracts of the proposed text that could have implications on activities within ICANN’s remit, and outline concretely what implications are anticipated for ICANN. A timeline should be included so we understand how imminent the law/regulation/directive is and when we need to take action. - Third, we encourage ICANN org to partner with a professional firm to receive regular updates (at least every three months) focused on those key regions which cause the majority of concerns. These reports must be made available to ICANN community members in a timely manner. - Fourth, while the GNSO Council would be pleased to accept ongoing monitoring reports, we would also welcome the opportunity to be briefed at our face-to-face meetings by ICANN’s government relations team and to enter into a dialogue about issues that have the potential to cause us concern. - Fifth, once a law or regulation has been adopted, ICANN org must undertake a compliance assessment in order to fully understand what implications there may or may not be on ICANN activities. - Sixth, the GNSO Council considers the GAC to be an important partner in these discussions and we would be delighted if they are able to alert us to potentially problematic legislation. However, we understand that often the GAC is not in a position to be able to do so, so we believe the onus must ultimately fall on ICANN org to structure the dialogue and to monitor regulatory and legislative developments. Thank you for welcoming our input. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, 23 June 2019 18:01, Steve Chan <steve.chan@icann.org> wrote:
Dear Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana,
In reviewing the Council’s action items, we recognized that the item below is still outstanding:
Small group of Councilors to develop draft message to ICANN Org to provide input on legislative tracker. Based on feedback, Council leadership to consider scheduling follow up discussion at ICANN65.
We wanted to bring this to your attention, as you all volunteered to work on this item. While the latter part of the action item (e.g., engaging at ICANN65) is likely impractical at this point, you may still want to draft a message to send to ICANN org. As Keith noted, please work together and let staff know if you need any assistance.
Best,
Steve
From: council <council-bounces@gnso.icann.org> on behalf of "Drazek, Keith via council" <council@gnso.icann.org> Reply-To: "Drazek, Keith" <kdrazek@verisign.com> Date: Thursday, April 4, 2019 at 7:35 PM To: "council@gnso.icann.org" <council@gnso.icann.org> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org> Subject: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana:
During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort.
As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development.
Please work together and with Staff to help kick off this important and timely work.
Thanks,
Keith
Thanks Ayden. All, attached is a revision version with a few edits, mostly around tone. Best, Paul This message may contain information that is attorney-client privileged, attorney work product or otherwise confidential. If you are not an intended recipient, use and disclosure of this message are prohibited. If you received this transmission in error, please notify the sender by reply e-mail and delete the message and any attachments. From: council <council-bounces@gnso.icann.org> On Behalf Of Ayden Férdeline Sent: Sunday, June 30, 2019 6:25 AM To: Steve Chan <steve.chan@icann.org> Cc: gnso-secs@icann.org; council@gnso.icann.org Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements I have drafted a message on behalf of the Council for Council's consideration on this topic. This is based upon our previous conversations. Please find attached and pasted below my signature. Thanks. Ayden Férdeline -- Recommended Improvements from the GNSO Council on ICANN Org Legislative Statement The GNSO Council supports ICANN org in its initiative to identify legislative and regulatory efforts across the globe that may have impacts on ICANN activities. However, we have some recommended improvements to the approach that ICANN org takes. * First, the GNSO Council believes that the current, crowdsourced approach where the community is expected to identify errors and omissions in the Global Legislative and Regulatory Developments Report is inappropriate. If ICANN is a professional organization then its professional staff should be comprehensively monitoring the regulatory landscape within which we operate. * Second, we encourage ICANN org to conduct proper regulatory impact assessments so that the community can understand the intended rationale for a law/regulation/directive, specific extracts of the proposed text that could have implications on activities within ICANN’s remit, and outline concretely what implications are anticipated for ICANN. A timeline should be included so we understand how imminent the law/regulation/directive is and when we need to take action. * Third, we encourage ICANN org to partner with a professional firm to receive regular updates (at least every three months) focused on those key regions which cause the majority of concerns. These reports must be made available to ICANN community members in a timely manner. * Fourth, while the GNSO Council would be pleased to accept ongoing monitoring reports, we would also welcome the opportunity to be briefed at our face-to-face meetings by ICANN’s government relations team and to enter into a dialogue about issues that have the potential to cause us concern. * Fifth, once a law or regulation has been adopted, ICANN org must undertake a compliance assessment in order to fully understand what implications there may or may not be on ICANN activities. * Sixth, the GNSO Council considers the GAC to be an important partner in these discussions and we would be delighted if they are able to alert us to potentially problematic legislation. However, we understand that often the GAC is not in a position to be able to do so, so we believe the onus must ultimately fall on ICANN org to structure the dialogue and to monitor regulatory and legislative developments. Thank you for welcoming our input. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, 23 June 2019 18:01, Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>> wrote: Dear Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana, In reviewing the Council’s action items, we recognized that the item below is still outstanding: Small group of Councilors to develop draft message to ICANN Org to provide input on legislative tracker. Based on feedback, Council leadership to consider scheduling follow up discussion at ICANN65. We wanted to bring this to your attention, as you all volunteered to work on this item. While the latter part of the action item (e.g., engaging at ICANN65) is likely impractical at this point, you may still want to draft a message to send to ICANN org. As Keith noted, please work together and let staff know if you need any assistance. Best, Steve From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of "Drazek, Keith via council" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Reply-To: "Drazek, Keith" <kdrazek@verisign.com<mailto:kdrazek@verisign.com>> Date: Thursday, April 4, 2019 at 7:35 PM To: "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana: During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort. As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development. Please work together and with Staff to help kick off this important and timely work. Thanks, Keith
Thanks for taking the lead, Ayden, and for your edits, Paul. I support Paul’s edits. I have proposed some additional edits in addition to Paul’s in the attached. I think it may be better received if we qualify what we’re seeking from ICANN Org, rather than referencing ICANN activities, which could be perceived as so sweepingly broad that it’s not doable. Thanks, Darcy From: council <council-bounces@gnso.icann.org> on behalf of "McGrady, Paul D." <PMcGrady@taftlaw.com> Date: Sunday, June 30, 2019 at 8:28 AM To: Ayden Férdeline <icann@ferdeline.com>, Steve Chan <steve.chan@icann.org> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org>, "council@gnso.icann.org" <council@gnso.icann.org> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thanks Ayden. All, attached is a revision version with a few edits, mostly around tone. Best, Paul This message may contain information that is attorney-client privileged, attorney work product or otherwise confidential. If you are not an intended recipient, use and disclosure of this message are prohibited. If you received this transmission in error, please notify the sender by reply e-mail and delete the message and any attachments. From: council <council-bounces@gnso.icann.org> On Behalf Of Ayden Férdeline Sent: Sunday, June 30, 2019 6:25 AM To: Steve Chan <steve.chan@icann.org> Cc: gnso-secs@icann.org; council@gnso.icann.org Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements I have drafted a message on behalf of the Council for Council's consideration on this topic. This is based upon our previous conversations. Please find attached and pasted below my signature. Thanks. Ayden Férdeline -- Recommended Improvements from the GNSO Council on ICANN Org Legislative Statement The GNSO Council supports ICANN org in its initiative to identify legislative and regulatory efforts across the globe that may have impacts on ICANN activities. However, we have some recommended improvements to the approach that ICANN org takes. First, the GNSO Council believes that the current, crowdsourced approach where the community is expected to identify errors and omissions in the Global Legislative and Regulatory Developments Report is inappropriate. If ICANN is a professional organization then its professional staff should be comprehensively monitoring the regulatory landscape within which we operate. Second, we encourage ICANN org to conduct proper regulatory impact assessments so that the community can understand the intended rationale for a law/regulation/directive, specific extracts of the proposed text that could have implications on activities within ICANN’s remit, and outline concretely what implications are anticipated for ICANN. A timeline should be included so we understand how imminent the law/regulation/directive is and when we need to take action. Third, we encourage ICANN org to partner with a professional firm to receive regular updates (at least every three months) focused on those key regions which cause the majority of concerns. These reports must be made available to ICANN community members in a timely manner. Fourth, while the GNSO Council would be pleased to accept ongoing monitoring reports, we would also welcome the opportunity to be briefed at our face-to-face meetings by ICANN’s government relations team and to enter into a dialogue about issues that have the potential to cause us concern. Fifth, once a law or regulation has been adopted, ICANN org must undertake a compliance assessment in order to fully understand what implications there may or may not be on ICANN activities. Sixth, the GNSO Council considers the GAC to be an important partner in these discussions and we would be delighted if they are able to alert us to potentially problematic legislation. However, we understand that often the GAC is not in a position to be able to do so, so we believe the onus must ultimately fall on ICANN org to structure the dialogue and to monitor regulatory and legislative developments. Thank you for welcoming our input. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, 23 June 2019 18:01, Steve Chan <steve.chan@icann.org> wrote: Dear Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana, In reviewing the Council’s action items, we recognized that the item below is still outstanding: Small group of Councilors to develop draft message to ICANN Org to provide input on legislative tracker. Based on feedback, Council leadership to consider scheduling follow up discussion at ICANN65. We wanted to bring this to your attention, as you all volunteered to work on this item. While the latter part of the action item (e.g., engaging at ICANN65) is likely impractical at this point, you may still want to draft a message to send to ICANN org. As Keith noted, please work together and let staff know if you need any assistance. Best, Steve From: council <council-bounces@gnso.icann.org> on behalf of "Drazek, Keith via council" <council@gnso.icann.org> Reply-To: "Drazek, Keith" <kdrazek@verisign.com> Date: Thursday, April 4, 2019 at 7:35 PM To: "council@gnso.icann.org" <council@gnso.icann.org> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org> Subject: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana: During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort. As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development. Please work together and with Staff to help kick off this important and timely work. Thanks, Keith _______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council _______________________________________________ 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 Paul, and thanks Darcy, for these edits. These all strike me as very sensible. Best wishes, Ayden ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Tuesday, 2 July 2019 00:57, Darcy Southwell <darcy.southwell@endurance.com> wrote:
Thanks for taking the lead, Ayden, and for your edits, Paul. I support Paul’s edits. I have proposed some additional edits in addition to Paul’s in the attached.
I think it may be better received if we qualify what we’re seeking from ICANN Org, rather than referencing ICANN activities, which could be perceived as so sweepingly broad that it’s not doable.
Thanks,
Darcy
From: council <council-bounces@gnso.icann.org> on behalf of "McGrady, Paul D." <PMcGrady@taftlaw.com> Date: Sunday, June 30, 2019 at 8:28 AM To: Ayden Férdeline <icann@ferdeline.com>, Steve Chan <steve.chan@icann.org> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org>, "council@gnso.icann.org" <council@gnso.icann.org> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
Thanks Ayden.
All, attached is a revision version with a few edits, mostly around tone.
Best,
Paul
This message may contain information that is attorney-client privileged, attorney work product or otherwise confidential. If you are not an intended recipient, use and disclosure of this message are prohibited. If you received this transmission in error, please notify the sender by reply e-mail and delete the message and any attachments.
From: council <council-bounces@gnso.icann.org> On Behalf Of Ayden Férdeline Sent: Sunday, June 30, 2019 6:25 AM To: Steve Chan <steve.chan@icann.org> Cc: gnso-secs@icann.org; council@gnso.icann.org Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
I have drafted a message on behalf of the Council for Council's consideration on this topic. This is based upon our previous conversations. Please find attached and pasted below my signature. Thanks.
Ayden Férdeline
--
Recommended Improvements from the GNSO Council on ICANN Org Legislative Statement
The GNSO Council supports ICANN org in its initiative to identify legislative and regulatory efforts across the globe that may have impacts on ICANN activities. However, we have some recommended improvements to the approach that ICANN org takes.
- First, the GNSO Council believes that the current, crowdsourced approach where the community is expected to identify errors and omissions in the Global Legislative and Regulatory Developments Report is inappropriate. If ICANN is a professional organization then its professional staff should be comprehensively monitoring the regulatory landscape within which we operate. - Second, we encourage ICANN org to conduct proper regulatory impact assessments so that the community can understand the intended rationale for a law/regulation/directive, specific extracts of the proposed text that could have implications on activities within ICANN’s remit, and outline concretely what implications are anticipated for ICANN. A timeline should be included so we understand how imminent the law/regulation/directive is and when we need to take action. - Third, we encourage ICANN org to partner with a professional firm to receive regular updates (at least every three months) focused on those key regions which cause the majority of concerns. These reports must be made available to ICANN community members in a timely manner. - Fourth, while the GNSO Council would be pleased to accept ongoing monitoring reports, we would also welcome the opportunity to be briefed at our face-to-face meetings by ICANN’s government relations team and to enter into a dialogue about issues that have the potential to cause us concern. - Fifth, once a law or regulation has been adopted, ICANN org must undertake a compliance assessment in order to fully understand what implications there may or may not be on ICANN activities. - Sixth, the GNSO Council considers the GAC to be an important partner in these discussions and we would be delighted if they are able to alert us to potentially problematic legislation. However, we understand that often the GAC is not in a position to be able to do so, so we believe the onus must ultimately fall on ICANN org to structure the dialogue and to monitor regulatory and legislative developments.
Thank you for welcoming our input.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, 23 June 2019 18:01, Steve Chan <steve.chan@icann.org> wrote:
Dear Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana,
In reviewing the Council’s action items, we recognized that the item below is still outstanding:
Small group of Councilors to develop draft message to ICANN Org to provide input on legislative tracker. Based on feedback, Council leadership to consider scheduling follow up discussion at ICANN65.
We wanted to bring this to your attention, as you all volunteered to work on this item. While the latter part of the action item (e.g., engaging at ICANN65) is likely impractical at this point, you may still want to draft a message to send to ICANN org. As Keith noted, please work together and let staff know if you need any assistance.
Best,
Steve
From: council <council-bounces@gnso.icann.org> on behalf of "Drazek, Keith via council" <council@gnso.icann.org> Reply-To: "Drazek, Keith" <kdrazek@verisign.com> Date: Thursday, April 4, 2019 at 7:35 PM To: "council@gnso.icann.org" <council@gnso.icann.org> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org> Subject: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana:
During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort.
As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development.
Please work together and with Staff to help kick off this important and timely work.
Thanks,
Keith
_______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council _______________________________________________ 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 Darcy. These edits look great. Sorry so slow in responding. I was overtaken by the holiday! Best, Paul From: Darcy Southwell <darcy.southwell@endurance.com> Sent: Monday, July 1, 2019 6:58 PM To: McGrady, Paul D. <PMcGrady@taftlaw.com>; Ayden Férdeline <icann@ferdeline.com>; Steve Chan <steve.chan@icann.org> Cc: gnso-secs@icann.org; council@gnso.icann.org Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thanks for taking the lead, Ayden, and for your edits, Paul. I support Paul’s edits. I have proposed some additional edits in addition to Paul’s in the attached. I think it may be better received if we qualify what we’re seeking from ICANN Org, rather than referencing ICANN activities, which could be perceived as so sweepingly broad that it’s not doable. Thanks, Darcy From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of "McGrady, Paul D." <PMcGrady@taftlaw.com<mailto:PMcGrady@taftlaw.com>> Date: Sunday, June 30, 2019 at 8:28 AM To: Ayden Férdeline <icann@ferdeline.com<mailto:icann@ferdeline.com>>, Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>>, "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thanks Ayden. All, attached is a revision version with a few edits, mostly around tone. Best, Paul This message may contain information that is attorney-client privileged, attorney work product or otherwise confidential. If you are not an intended recipient, use and disclosure of this message are prohibited. If you received this transmission in error, please notify the sender by reply e-mail and delete the message and any attachments. From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of Ayden Férdeline Sent: Sunday, June 30, 2019 6:25 AM To: Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>> Cc: gnso-secs@icann.org<mailto:gnso-secs@icann.org>; council@gnso.icann.org<mailto:council@gnso.icann.org> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements I have drafted a message on behalf of the Council for Council's consideration on this topic. This is based upon our previous conversations. Please find attached and pasted below my signature. Thanks. Ayden Férdeline -- Recommended Improvements from the GNSO Council on ICANN Org Legislative Statement The GNSO Council supports ICANN org in its initiative to identify legislative and regulatory efforts across the globe that may have impacts on ICANN activities. However, we have some recommended improvements to the approach that ICANN org takes. * First, the GNSO Council believes that the current, crowdsourced approach where the community is expected to identify errors and omissions in the Global Legislative and Regulatory Developments Report is inappropriate. If ICANN is a professional organization then its professional staff should be comprehensively monitoring the regulatory landscape within which we operate. * Second, we encourage ICANN org to conduct proper regulatory impact assessments so that the community can understand the intended rationale for a law/regulation/directive, specific extracts of the proposed text that could have implications on activities within ICANN’s remit, and outline concretely what implications are anticipated for ICANN. A timeline should be included so we understand how imminent the law/regulation/directive is and when we need to take action. * Third, we encourage ICANN org to partner with a professional firm to receive regular updates (at least every three months) focused on those key regions which cause the majority of concerns. These reports must be made available to ICANN community members in a timely manner. * Fourth, while the GNSO Council would be pleased to accept ongoing monitoring reports, we would also welcome the opportunity to be briefed at our face-to-face meetings by ICANN’s government relations team and to enter into a dialogue about issues that have the potential to cause us concern. * Fifth, once a law or regulation has been adopted, ICANN org must undertake a compliance assessment in order to fully understand what implications there may or may not be on ICANN activities. * Sixth, the GNSO Council considers the GAC to be an important partner in these discussions and we would be delighted if they are able to alert us to potentially problematic legislation. However, we understand that often the GAC is not in a position to be able to do so, so we believe the onus must ultimately fall on ICANN org to structure the dialogue and to monitor regulatory and legislative developments. Thank you for welcoming our input. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, 23 June 2019 18:01, Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>> wrote: Dear Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana, In reviewing the Council’s action items, we recognized that the item below is still outstanding: Small group of Councilors to develop draft message to ICANN Org to provide input on legislative tracker. Based on feedback, Council leadership to consider scheduling follow up discussion at ICANN65. We wanted to bring this to your attention, as you all volunteered to work on this item. While the latter part of the action item (e.g., engaging at ICANN65) is likely impractical at this point, you may still want to draft a message to send to ICANN org. As Keith noted, please work together and let staff know if you need any assistance. Best, Steve From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of "Drazek, Keith via council" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Reply-To: "Drazek, Keith" <kdrazek@verisign.com<mailto:kdrazek@verisign.com>> Date: Thursday, April 4, 2019 at 7:35 PM To: "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana: During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort. As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development. Please work together and with Staff to help kick off this important and timely work. Thanks, Keith _______________________________________________ council mailing list council@gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council _______________________________________________ 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.
Steve, Do we have a target send date on this letter? Darcy On Mon, Jul 8, 2019 at 4:30 AM McGrady, Paul D. <PMcGrady@taftlaw.com> wrote:
Thanks Darcy. These edits look great. Sorry so slow in responding. I was overtaken by the holiday!
Best,
Paul
*From:* Darcy Southwell <darcy.southwell@endurance.com> *Sent:* Monday, July 1, 2019 6:58 PM *To:* McGrady, Paul D. <PMcGrady@taftlaw.com>; Ayden Férdeline < icann@ferdeline.com>; Steve Chan <steve.chan@icann.org> *Cc:* gnso-secs@icann.org; council@gnso.icann.org *Subject:* Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
Thanks for taking the lead, Ayden, and for your edits, Paul. I support Paul’s edits. I have proposed some additional edits in addition to Paul’s in the attached.
I think it may be better received if we qualify what we’re seeking from ICANN Org, rather than referencing ICANN activities, which could be perceived as so sweepingly broad that it’s not doable.
Thanks,
Darcy
*From: *council <council-bounces@gnso.icann.org> on behalf of "McGrady, Paul D." <PMcGrady@taftlaw.com> *Date: *Sunday, June 30, 2019 at 8:28 AM *To: *Ayden Férdeline <icann@ferdeline.com>, Steve Chan < steve.chan@icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org>, "council@gnso.icann.org" <council@gnso.icann.org> *Subject: *Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
Thanks Ayden.
All, attached is a revision version with a few edits, mostly around tone.
Best,
Paul
This message may contain information that is attorney-client privileged, attorney work product or otherwise confidential. If you are not an intended recipient, use and disclosure of this message are prohibited. If you received this transmission in error, please notify the sender by reply e-mail and delete the message and any attachments.
*From:* council <council-bounces@gnso.icann.org> *On Behalf Of *Ayden Férdeline *Sent:* Sunday, June 30, 2019 6:25 AM *To:* Steve Chan <steve.chan@icann.org> *Cc:* gnso-secs@icann.org; council@gnso.icann.org *Subject:* Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
I have drafted a message on behalf of the Council for Council's consideration on this topic. This is based upon our previous conversations. Please find attached and pasted below my signature. Thanks.
Ayden Férdeline
--
*Recommended Improvements from the GNSO Council on ICANN Org Legislative Statement*
The GNSO Council supports ICANN org in its initiative to identify legislative and regulatory efforts across the globe that may have impacts on ICANN activities. However, we have some recommended improvements to the approach that ICANN org takes.
- First, the GNSO Council believes that the current, crowdsourced approach where the community is expected to identify errors and omissions in the Global Legislative and Regulatory Developments Report is inappropriate. If ICANN is a professional organization then its professional staff should be comprehensively monitoring the regulatory landscape within which we operate. - Second, we encourage ICANN org to conduct proper regulatory impact assessments so that the community can understand the intended rationale for a law/regulation/directive, specific extracts of the proposed text that could have implications on activities within ICANN’s remit, and outline concretely what implications are anticipated for ICANN. A timeline should be included so we understand how imminent the law/regulation/directive is and when we need to take action. - Third, we encourage ICANN org to partner with a professional firm to receive regular updates (at least every three months) focused on those key regions which cause the majority of concerns. These reports must be made available to ICANN community members in a timely manner. - Fourth, while the GNSO Council would be pleased to accept ongoing monitoring reports, we would also welcome the opportunity to be briefed at our face-to-face meetings by ICANN’s government relations team and to enter into a dialogue about issues that have the potential to cause us concern. - Fifth, once a law or regulation has been adopted, ICANN org must undertake a compliance assessment in order to fully understand what implications there may or may not be on ICANN activities. - Sixth, the GNSO Council considers the GAC to be an important partner in these discussions and we would be delighted if they are able to alert us to potentially problematic legislation. However, we understand that often the GAC is not in a position to be able to do so, so we believe the onus must ultimately fall on ICANN org to structure the dialogue and to monitor regulatory and legislative developments.
Thank you for welcoming our input.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, 23 June 2019 18:01, Steve Chan <steve.chan@icann.org> wrote:
Dear Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana,
In reviewing the Council’s action items, we recognized that the item below is still outstanding:
*Small group of Councilors* to develop draft message to ICANN Org to provide input on legislative tracker. Based on feedback, Council leadership to consider scheduling follow up discussion at ICANN65.
We wanted to bring this to your attention, as you all volunteered to work on this item. While the latter part of the action item (e.g., engaging at ICANN65) is likely impractical at this point, you may still want to draft a message to send to ICANN org. As Keith noted, please work together and let staff know if you need any assistance.
Best,
Steve
*From: *council <council-bounces@gnso.icann.org> on behalf of "Drazek, Keith via council" <council@gnso.icann.org> *Reply-To: *"Drazek, Keith" <kdrazek@verisign.com> *Date: *Thursday, April 4, 2019 at 7:35 PM *To: *"council@gnso.icann.org" <council@gnso.icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org> *Subject: *[council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana:
During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort.
As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development.
Please work together and with Staff to help kick off this important and timely work.
Thanks,
Keith
_______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council _______________________________________________ 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 (and I don’t even have the holidays to blame :s ). Both Ayden’s points, and the rephrasing suggested by Darcy are excellent. The first item relative to community’s input has been raised a number of times; I remember asking a question during a CSG meeting with the Board in Kobe. Not that the answer was unsatisfactory but it was hardly practical. Ultimately, I think we need to keep in mind the primary goal of all this, ie (I think) should there be a “new GDPR in the making” (in terms of having an impact on policies), the community should be able to detect it with this tool. I’m not sure it would in its current state, so the points are well made. Regards, Philippe From: council [mailto:council-bounces@gnso.icann.org] On Behalf Of McGrady, Paul D. Sent: Monday, July 08, 2019 1:30 PM To: Darcy Southwell; Ayden Férdeline; Steve Chan Cc: gnso-secs@icann.org; council@gnso.icann.org Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thanks Darcy. These edits look great. Sorry so slow in responding. I was overtaken by the holiday! Best, Paul From: Darcy Southwell <darcy.southwell@endurance.com> Sent: Monday, July 1, 2019 6:58 PM To: McGrady, Paul D. <PMcGrady@taftlaw.com>; Ayden Férdeline <icann@ferdeline.com>; Steve Chan <steve.chan@icann.org> Cc: gnso-secs@icann.org; council@gnso.icann.org Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thanks for taking the lead, Ayden, and for your edits, Paul. I support Paul’s edits. I have proposed some additional edits in addition to Paul’s in the attached. I think it may be better received if we qualify what we’re seeking from ICANN Org, rather than referencing ICANN activities, which could be perceived as so sweepingly broad that it’s not doable. Thanks, Darcy From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of "McGrady, Paul D." <PMcGrady@taftlaw.com<mailto:PMcGrady@taftlaw.com>> Date: Sunday, June 30, 2019 at 8:28 AM To: Ayden Férdeline <icann@ferdeline.com<mailto:icann@ferdeline.com>>, Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>>, "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thanks Ayden. All, attached is a revision version with a few edits, mostly around tone. Best, Paul This message may contain information that is attorney-client privileged, attorney work product or otherwise confidential. If you are not an intended recipient, use and disclosure of this message are prohibited. If you received this transmission in error, please notify the sender by reply e-mail and delete the message and any attachments. From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of Ayden Férdeline Sent: Sunday, June 30, 2019 6:25 AM To: Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>> Cc: gnso-secs@icann.org<mailto:gnso-secs@icann.org>; council@gnso.icann.org<mailto:council@gnso.icann.org> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements I have drafted a message on behalf of the Council for Council's consideration on this topic. This is based upon our previous conversations. Please find attached and pasted below my signature. Thanks. Ayden Férdeline -- Recommended Improvements from the GNSO Council on ICANN Org Legislative Statement The GNSO Council supports ICANN org in its initiative to identify legislative and regulatory efforts across the globe that may have impacts on ICANN activities. However, we have some recommended improvements to the approach that ICANN org takes. * First, the GNSO Council believes that the current, crowdsourced approach where the community is expected to identify errors and omissions in the Global Legislative and Regulatory Developments Report is inappropriate. If ICANN is a professional organization then its professional staff should be comprehensively monitoring the regulatory landscape within which we operate. * Second, we encourage ICANN org to conduct proper regulatory impact assessments so that the community can understand the intended rationale for a law/regulation/directive, specific extracts of the proposed text that could have implications on activities within ICANN’s remit, and outline concretely what implications are anticipated for ICANN. A timeline should be included so we understand how imminent the law/regulation/directive is and when we need to take action. * Third, we encourage ICANN org to partner with a professional firm to receive regular updates (at least every three months) focused on those key regions which cause the majority of concerns. These reports must be made available to ICANN community members in a timely manner. * Fourth, while the GNSO Council would be pleased to accept ongoing monitoring reports, we would also welcome the opportunity to be briefed at our face-to-face meetings by ICANN’s government relations team and to enter into a dialogue about issues that have the potential to cause us concern. * Fifth, once a law or regulation has been adopted, ICANN org must undertake a compliance assessment in order to fully understand what implications there may or may not be on ICANN activities. * Sixth, the GNSO Council considers the GAC to be an important partner in these discussions and we would be delighted if they are able to alert us to potentially problematic legislation. However, we understand that often the GAC is not in a position to be able to do so, so we believe the onus must ultimately fall on ICANN org to structure the dialogue and to monitor regulatory and legislative developments. Thank you for welcoming our input. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, 23 June 2019 18:01, Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>> wrote: Dear Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana, In reviewing the Council’s action items, we recognized that the item below is still outstanding: Small group of Councilors to develop draft message to ICANN Org to provide input on legislative tracker. Based on feedback, Council leadership to consider scheduling follow up discussion at ICANN65. We wanted to bring this to your attention, as you all volunteered to work on this item. While the latter part of the action item (e.g., engaging at ICANN65) is likely impractical at this point, you may still want to draft a message to send to ICANN org. As Keith noted, please work together and let staff know if you need any assistance. Best, Steve From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of "Drazek, Keith via council" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Reply-To: "Drazek, Keith" <kdrazek@verisign.com<mailto:kdrazek@verisign.com>> Date: Thursday, April 4, 2019 at 7:35 PM To: "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana: During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort. As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development. Please work together and with Staff to help kick off this important and timely work. Thanks, Keith _______________________________________________ council mailing list council@gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council _______________________________________________ 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. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
All, I made a minor clarification in the fifth issue. Thanks, Darcy On Tue, Jul 9, 2019 at 8:26 AM <philippe.fouquart@orange.com> wrote:
Thanks (and I don’t even have the holidays to blame :s ). Both Ayden’s points, and the rephrasing suggested by Darcy are excellent.
The first item relative to community’s input has been raised a number of times; I remember asking a question during a CSG meeting with the Board in Kobe. Not that the answer was unsatisfactory but it was hardly practical.
Ultimately, I think we need to keep in mind the primary goal of all this, ie (I think) should there be a “new GDPR in the making” (in terms of having an impact on policies), the community should be able to detect it with this tool. I’m not sure it would in its current state, so the points are well made.
Regards,
Philippe
*From:* council [mailto:council-bounces@gnso.icann.org] *On Behalf Of *McGrady, Paul D. *Sent:* Monday, July 08, 2019 1:30 PM *To:* Darcy Southwell; Ayden Férdeline; Steve Chan *Cc:* gnso-secs@icann.org; council@gnso.icann.org *Subject:* Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
Thanks Darcy. These edits look great. Sorry so slow in responding. I was overtaken by the holiday!
Best,
Paul
*From:* Darcy Southwell <darcy.southwell@endurance.com> *Sent:* Monday, July 1, 2019 6:58 PM *To:* McGrady, Paul D. <PMcGrady@taftlaw.com>; Ayden Férdeline < icann@ferdeline.com>; Steve Chan <steve.chan@icann.org> *Cc:* gnso-secs@icann.org; council@gnso.icann.org *Subject:* Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
Thanks for taking the lead, Ayden, and for your edits, Paul. I support Paul’s edits. I have proposed some additional edits in addition to Paul’s in the attached.
I think it may be better received if we qualify what we’re seeking from ICANN Org, rather than referencing ICANN activities, which could be perceived as so sweepingly broad that it’s not doable.
Thanks,
Darcy
*From: *council <council-bounces@gnso.icann.org> on behalf of "McGrady, Paul D." <PMcGrady@taftlaw.com> *Date: *Sunday, June 30, 2019 at 8:28 AM *To: *Ayden Férdeline <icann@ferdeline.com>, Steve Chan < steve.chan@icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org>, "council@gnso.icann.org" <council@gnso.icann.org> *Subject: *Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
Thanks Ayden.
All, attached is a revision version with a few edits, mostly around tone.
Best,
Paul
This message may contain information that is attorney-client privileged, attorney work product or otherwise confidential. If you are not an intended recipient, use and disclosure of this message are prohibited. If you received this transmission in error, please notify the sender by reply e-mail and delete the message and any attachments.
*From:* council <council-bounces@gnso.icann.org> *On Behalf Of *Ayden Férdeline *Sent:* Sunday, June 30, 2019 6:25 AM *To:* Steve Chan <steve.chan@icann.org> *Cc:* gnso-secs@icann.org; council@gnso.icann.org *Subject:* Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
I have drafted a message on behalf of the Council for Council's consideration on this topic. This is based upon our previous conversations. Please find attached and pasted below my signature. Thanks.
Ayden Férdeline
--
*Recommended Improvements from the GNSO Council on ICANN Org Legislative Statement*
The GNSO Council supports ICANN org in its initiative to identify legislative and regulatory efforts across the globe that may have impacts on ICANN activities. However, we have some recommended improvements to the approach that ICANN org takes.
- First, the GNSO Council believes that the current, crowdsourced approach where the community is expected to identify errors and omissions in the Global Legislative and Regulatory Developments Report is inappropriate. If ICANN is a professional organization then its professional staff should be comprehensively monitoring the regulatory landscape within which we operate. - Second, we encourage ICANN org to conduct proper regulatory impact assessments so that the community can understand the intended rationale for a law/regulation/directive, specific extracts of the proposed text that could have implications on activities within ICANN’s remit, and outline concretely what implications are anticipated for ICANN. A timeline should be included so we understand how imminent the law/regulation/directive is and when we need to take action. - Third, we encourage ICANN org to partner with a professional firm to receive regular updates (at least every three months) focused on those key regions which cause the majority of concerns. These reports must be made available to ICANN community members in a timely manner. - Fourth, while the GNSO Council would be pleased to accept ongoing monitoring reports, we would also welcome the opportunity to be briefed at our face-to-face meetings by ICANN’s government relations team and to enter into a dialogue about issues that have the potential to cause us concern. - Fifth, once a law or regulation has been adopted, ICANN org must undertake a compliance assessment in order to fully understand what implications there may or may not be on ICANN activities. - Sixth, the GNSO Council considers the GAC to be an important partner in these discussions and we would be delighted if they are able to alert us to potentially problematic legislation. However, we understand that often the GAC is not in a position to be able to do so, so we believe the onus must ultimately fall on ICANN org to structure the dialogue and to monitor regulatory and legislative developments.
Thank you for welcoming our input.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, 23 June 2019 18:01, Steve Chan <steve.chan@icann.org> wrote:
Dear Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana,
In reviewing the Council’s action items, we recognized that the item below is still outstanding:
*Small group of Councilors* to develop draft message to ICANN Org to provide input on legislative tracker. Based on feedback, Council leadership to consider scheduling follow up discussion at ICANN65.
We wanted to bring this to your attention, as you all volunteered to work on this item. While the latter part of the action item (e.g., engaging at ICANN65) is likely impractical at this point, you may still want to draft a message to send to ICANN org. As Keith noted, please work together and let staff know if you need any assistance.
Best,
Steve
*From: *council <council-bounces@gnso.icann.org> on behalf of "Drazek, Keith via council" <council@gnso.icann.org> *Reply-To: *"Drazek, Keith" <kdrazek@verisign.com> *Date: *Thursday, April 4, 2019 at 7:35 PM *To: *"council@gnso.icann.org" <council@gnso.icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org> *Subject: *[council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana:
During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort.
As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development.
Please work together and with Staff to help kick off this important and timely work.
Thanks,
Keith
_______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council _______________________________________________ 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.
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
All: I made a change in the third issue. Best Flip Flip Petillion fpetillion@petillion.law +32484652653 www.petillion.law [signature_2145422569]<http://www.petillion.law/> Attorneys – Advocaten - Avocats From: council <council-bounces@gnso.icann.org> on behalf of Darcy Southwell <darcy.southwell@endurance.com> Date: Friday, 12 July 2019 at 17:07 To: "philippe.fouquart@orange.com" <philippe.fouquart@orange.com> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org>, "council@gnso.icann.org" <council@gnso.icann.org> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements All, I made a minor clarification in the fifth issue. Thanks, Darcy On Tue, Jul 9, 2019 at 8:26 AM <philippe.fouquart@orange.com<mailto:philippe.fouquart@orange.com>> wrote: Thanks (and I don’t even have the holidays to blame :s ). Both Ayden’s points, and the rephrasing suggested by Darcy are excellent. The first item relative to community’s input has been raised a number of times; I remember asking a question during a CSG meeting with the Board in Kobe. Not that the answer was unsatisfactory but it was hardly practical. Ultimately, I think we need to keep in mind the primary goal of all this, ie (I think) should there be a “new GDPR in the making” (in terms of having an impact on policies), the community should be able to detect it with this tool. I’m not sure it would in its current state, so the points are well made. Regards, Philippe From: council [mailto:council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>] On Behalf Of McGrady, Paul D. Sent: Monday, July 08, 2019 1:30 PM To: Darcy Southwell; Ayden Férdeline; Steve Chan Cc: gnso-secs@icann.org<mailto:gnso-secs@icann.org>; council@gnso.icann.org<mailto:council@gnso.icann.org> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thanks Darcy. These edits look great. Sorry so slow in responding. I was overtaken by the holiday! Best, Paul From: Darcy Southwell <darcy.southwell@endurance.com<mailto:darcy.southwell@endurance.com>> Sent: Monday, July 1, 2019 6:58 PM To: McGrady, Paul D. <PMcGrady@taftlaw.com<mailto:PMcGrady@taftlaw.com>>; Ayden Férdeline <icann@ferdeline.com<mailto:icann@ferdeline.com>>; Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>> Cc: gnso-secs@icann.org<mailto:gnso-secs@icann.org>; council@gnso.icann.org<mailto:council@gnso.icann.org> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thanks for taking the lead, Ayden, and for your edits, Paul. I support Paul’s edits. I have proposed some additional edits in addition to Paul’s in the attached. I think it may be better received if we qualify what we’re seeking from ICANN Org, rather than referencing ICANN activities, which could be perceived as so sweepingly broad that it’s not doable. Thanks, Darcy From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of "McGrady, Paul D." <PMcGrady@taftlaw.com<mailto:PMcGrady@taftlaw.com>> Date: Sunday, June 30, 2019 at 8:28 AM To: Ayden Férdeline <icann@ferdeline.com<mailto:icann@ferdeline.com>>, Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>>, "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thanks Ayden. All, attached is a revision version with a few edits, mostly around tone. Best, Paul This message may contain information that is attorney-client privileged, attorney work product or otherwise confidential. If you are not an intended recipient, use and disclosure of this message are prohibited. If you received this transmission in error, please notify the sender by reply e-mail and delete the message and any attachments. From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of Ayden Férdeline Sent: Sunday, June 30, 2019 6:25 AM To: Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>> Cc: gnso-secs@icann.org<mailto:gnso-secs@icann.org>; council@gnso.icann.org<mailto:council@gnso.icann.org> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements I have drafted a message on behalf of the Council for Council's consideration on this topic. This is based upon our previous conversations. Please find attached and pasted below my signature. Thanks. Ayden Férdeline -- Recommended Improvements from the GNSO Council on ICANN Org Legislative Statement The GNSO Council supports ICANN org in its initiative to identify legislative and regulatory efforts across the globe that may have impacts on ICANN activities. However, we have some recommended improvements to the approach that ICANN org takes. * First, the GNSO Council believes that the current, crowdsourced approach where the community is expected to identify errors and omissions in the Global Legislative and Regulatory Developments Report is inappropriate. If ICANN is a professional organization then its professional staff should be comprehensively monitoring the regulatory landscape within which we operate. * Second, we encourage ICANN org to conduct proper regulatory impact assessments so that the community can understand the intended rationale for a law/regulation/directive, specific extracts of the proposed text that could have implications on activities within ICANN’s remit, and outline concretely what implications are anticipated for ICANN. A timeline should be included so we understand how imminent the law/regulation/directive is and when we need to take action. * Third, we encourage ICANN org to partner with a professional firm to receive regular updates (at least every three months) focused on those key regions which cause the majority of concerns. These reports must be made available to ICANN community members in a timely manner. * Fourth, while the GNSO Council would be pleased to accept ongoing monitoring reports, we would also welcome the opportunity to be briefed at our face-to-face meetings by ICANN’s government relations team and to enter into a dialogue about issues that have the potential to cause us concern. * Fifth, once a law or regulation has been adopted, ICANN org must undertake a compliance assessment in order to fully understand what implications there may or may not be on ICANN activities. * Sixth, the GNSO Council considers the GAC to be an important partner in these discussions and we would be delighted if they are able to alert us to potentially problematic legislation. However, we understand that often the GAC is not in a position to be able to do so, so we believe the onus must ultimately fall on ICANN org to structure the dialogue and to monitor regulatory and legislative developments. Thank you for welcoming our input. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, 23 June 2019 18:01, Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>> wrote: Dear Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana, In reviewing the Council’s action items, we recognized that the item below is still outstanding: Small group of Councilors to develop draft message to ICANN Org to provide input on legislative tracker. Based on feedback, Council leadership to consider scheduling follow up discussion at ICANN65. We wanted to bring this to your attention, as you all volunteered to work on this item. While the latter part of the action item (e.g., engaging at ICANN65) is likely impractical at this point, you may still want to draft a message to send to ICANN org. As Keith noted, please work together and let staff know if you need any assistance. Best, Steve From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of "Drazek, Keith via council" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Reply-To: "Drazek, Keith" <kdrazek@verisign.com<mailto:kdrazek@verisign.com>> Date: Thursday, April 4, 2019 at 7:35 PM To: "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana: During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort. As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development. Please work together and with Staff to help kick off this important and timely work. Thanks, Keith _______________________________________________ council mailing list council@gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council _______________________________________________ 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. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
Thank you very much to those who contributed to the draft. I have made a few more suggested edits, including the following for clarity and to avoid repetition: add a definition: ICANN’s contracts with registries and registrars, consensus policies, and policies in effect or in development (“ICANN’s Contracts and Policies”) merge the second and fifth points to read: · Second, we encourage ICANN org to conduct standard regulatory impact assessments so that the community can understand the intended rationale for a law/regulation/directive, specific extracts of the proposed text that could have implications on ICANN’s Contracts and Policies, and outline concretely what implications are anticipated. A timeline should be included so the community can understand how imminent the law/regulation/directive is and when it needs to take action. Once such law or regulation has been adopted, ICANN org should undertake a compliance assessment as soon as possible to ensure sufficient time to address any deficiencies or issues. I suggest we aim to send the finalized version by COB this Friday 19th July. So if you have further edits or any concerns or objections, please post to the Council mailing list. Kind regards, Pam ------------------------------------------------------------------ Sender:Flip Petillion <fpetillion@petillion.law> Sent At:2019 Jul. 16 (Tue.) 00:39 Recipient:Darcy Southwell <darcy.southwell@endurance.com>; philippe.fouquart@orange.com <philippe.fouquart@orange.com> Cc:gnso-secs@icann.org <gnso-secs@icann.org>; council@gnso.icann.org <council@gnso.icann.org> Subject:Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements All: I made a change in the third issue. Best Flip Flip Petillion fpetillion@petillion.law +32484652653 www.petillion.law [signature_2145422569] Attorneys – Advocaten - Avocats From: council <council-bounces@gnso.icann.org> on behalf of Darcy Southwell <darcy.southwell@endurance.com> Date: Friday, 12 July 2019 at 17:07 To: "philippe.fouquart@orange.com" <philippe.fouquart@orange.com> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org>, "council@gnso.icann.org" <council@gnso.icann.org> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements All, I made a minor clarification in the fifth issue. Thanks, Darcy On Tue, Jul 9, 2019 at 8:26 AM <philippe.fouquart@orange.com> wrote: Thanks (and I don’t even have the holidays to blame :s ). Both Ayden’s points, and the rephrasing suggested by Darcy are excellent. The first item relative to community’s input has been raised a number of times; I remember asking a question during a CSG meeting with the Board in Kobe. Not that the answer was unsatisfactory but it was hardly practical. Ultimately, I think we need to keep in mind the primary goal of all this, ie (I think) should there be a “new GDPR in the making” (in terms of having an impact on policies), the community should be able to detect it with this tool. I’m not sure it would in its current state, so the points are well made. Regards, Philippe From: council [mailto:council-bounces@gnso.icann.org] On Behalf Of McGrady, Paul D. Sent: Monday, July 08, 2019 1:30 PM To: Darcy Southwell; Ayden Férdeline; Steve Chan Cc: gnso-secs@icann.org; council@gnso.icann.org Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thanks Darcy. These edits look great. Sorry so slow in responding. I was overtaken by the holiday! Best, Paul From: Darcy Southwell <darcy.southwell@endurance.com> Sent: Monday, July 1, 2019 6:58 PM To: McGrady, Paul D. <PMcGrady@taftlaw.com>; Ayden Férdeline <icann@ferdeline.com>; Steve Chan <steve.chan@icann.org> Cc: gnso-secs@icann.org; council@gnso.icann.org Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thanks for taking the lead, Ayden, and for your edits, Paul. I support Paul’s edits. I have proposed some additional edits in addition to Paul’s in the attached. I think it may be better received if we qualify what we’re seeking from ICANN Org, rather than referencing ICANN activities, which could be perceived as so sweepingly broad that it’s not doable. Thanks, Darcy From: council <council-bounces@gnso.icann.org> on behalf of "McGrady, Paul D." <PMcGrady@taftlaw.com> Date: Sunday, June 30, 2019 at 8:28 AM To: Ayden Férdeline <icann@ferdeline.com>, Steve Chan <steve.chan@icann.org> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org>, "council@gnso.icann.org" <council@gnso.icann.org> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thanks Ayden. All, attached is a revision version with a few edits, mostly around tone. Best, Paul This message may contain information that is attorney-client privileged, attorney work product or otherwise confidential. If you are not an intended recipient, use and disclosure of this message are prohibited. If you received this transmission in error, please notify the sender by reply e-mail and delete the message and any attachments. From: council <council-bounces@gnso.icann.org> On Behalf Of Ayden Férdeline Sent: Sunday, June 30, 2019 6:25 AM To: Steve Chan <steve.chan@icann.org> Cc: gnso-secs@icann.org; council@gnso.icann.org Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements I have drafted a message on behalf of the Council for Council's consideration on this topic. This is based upon our previous conversations. Please find attached and pasted below my signature. Thanks. Ayden Férdeline -- Recommended Improvements from the GNSO Council on ICANN Org Legislative Statement The GNSO Council supports ICANN org in its initiative to identify legislative and regulatory efforts across the globe that may have impacts on ICANN activities. However, we have some recommended improvements to the approach that ICANN org takes. First, the GNSO Council believes that the current, crowdsourced approach where the community is expected to identify errors and omissions in the Global Legislative and Regulatory Developments Report is inappropriate. If ICANN is a professional organization then its professional staff should be comprehensively monitoring the regulatory landscape within which we operate. Second, we encourage ICANN org to conduct proper regulatory impact assessments so that the community can understand the intended rationale for a law/regulation/directive, specific extracts of the proposed text that could have implications on activities within ICANN’s remit, and outline concretely what implications are anticipated for ICANN. A timeline should be included so we understand how imminent the law/regulation/directive is and when we need to take action. Third, we encourage ICANN org to partner with a professional firm to receive regular updates (at least every three months) focused on those key regions which cause the majority of concerns. These reports must be made available to ICANN community members in a timely manner. Fourth, while the GNSO Council would be pleased to accept ongoing monitoring reports, we would also welcome the opportunity to be briefed at our face-to-face meetings by ICANN’s government relations team and to enter into a dialogue about issues that have the potential to cause us concern. Fifth, once a law or regulation has been adopted, ICANN org must undertake a compliance assessment in order to fully understand what implications there may or may not be on ICANN activities. Sixth, the GNSO Council considers the GAC to be an important partner in these discussions and we would be delighted if they are able to alert us to potentially problematic legislation. However, we understand that often the GAC is not in a position to be able to do so, so we believe the onus must ultimately fall on ICANN org to structure the dialogue and to monitor regulatory and legislative developments. Thank you for welcoming our input. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, 23 June 2019 18:01, Steve Chan <steve.chan@icann.org> wrote: Dear Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana, In reviewing the Council’s action items, we recognized that the item below is still outstanding: Small group of Councilors to develop draft message to ICANN Org to provide input on legislative tracker. Based on feedback, Council leadership to consider scheduling follow up discussion at ICANN65. We wanted to bring this to your attention, as you all volunteered to work on this item. While the latter part of the action item (e.g., engaging at ICANN65) is likely impractical at this point, you may still want to draft a message to send to ICANN org. As Keith noted, please work together and let staff know if you need any assistance. Best, Steve From: council <council-bounces@gnso.icann.org> on behalf of "Drazek, Keith via council" <council@gnso.icann.org> Reply-To: "Drazek, Keith" <kdrazek@verisign.com> Date: Thursday, April 4, 2019 at 7:35 PM To: "council@gnso.icann.org" <council@gnso.icann.org> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org> Subject: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana: During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort. As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development. Please work together and with Staff to help kick off this important and timely work. Thanks, Keith _______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council _______________________________________________ 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. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
Hi all, Apologies - I inadvertently omitted the version that Flip posted earlier, which contained further changes to the third issue. Please use the attached version instead. Kind regards, Pam ------------------------------------------------------------------ Sender:PAMELALITTLE <pam.little@alibaba-inc.com> Sent At:2019 Jul. 16 (Tue.) 09:01 Recipient:Darcy Southwell <darcy.southwell@endurance.com>; philippe.fouquart@orange.com <philippe.fouquart@orange.com>; council <council-bounces@gnso.icann.org> Cc:gnso-secs@icann.org <gnso-secs@icann.org>; council@gnso.icann.org <council@gnso.icann.org> Subject:Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thank you very much to those who contributed to the draft. I have made a few more suggested edits, including the following for clarity and to avoid repetition: add a definition: ICANN’s contracts with registries and registrars, consensus policies, and policies in effect or in development (“ICANN’s Contracts and Policies”) merge the second and fifth points to read: · Second, we encourage ICANN org to conduct standard regulatory impact assessments so that the community can understand the intended rationale for a law/regulation/directive, specific extracts of the proposed text that could have implications on ICANN’s Contracts and Policies, and outline concretely what implications are anticipated. A timeline should be included so the community can understand how imminent the law/regulation/directive is and when it needs to take action. Once such law or regulation has been adopted, ICANN org should undertake a compliance assessment as soon as possible to ensure sufficient time to address any deficiencies or issues. I suggest we aim to send the finalized version by COB this Friday 19th July. So if you have further edits or any concerns or objections, please post to the Council mailing list. Kind regards, Pam ------------------------------------------------------------------ Sender:Flip Petillion <fpetillion@petillion.law> Sent At:2019 Jul. 16 (Tue.) 00:39 Recipient:Darcy Southwell <darcy.southwell@endurance.com>; philippe.fouquart@orange.com <philippe.fouquart@orange.com> Cc:gnso-secs@icann.org <gnso-secs@icann.org>; council@gnso.icann.org <council@gnso.icann.org> Subject:Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements All: I made a change in the third issue. Best Flip Flip Petillion fpetillion@petillion.law +32484652653 www.petillion.law [signature_2145422569] Attorneys – Advocaten - Avocats From: council <council-bounces@gnso.icann.org> on behalf of Darcy Southwell <darcy.southwell@endurance.com> Date: Friday, 12 July 2019 at 17:07 To: "philippe.fouquart@orange.com" <philippe.fouquart@orange.com> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org>, "council@gnso.icann.org" <council@gnso.icann.org> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements All, I made a minor clarification in the fifth issue. Thanks, Darcy On Tue, Jul 9, 2019 at 8:26 AM <philippe.fouquart@orange.com> wrote: Thanks (and I don’t even have the holidays to blame :s ). Both Ayden’s points, and the rephrasing suggested by Darcy are excellent. The first item relative to community’s input has been raised a number of times; I remember asking a question during a CSG meeting with the Board in Kobe. Not that the answer was unsatisfactory but it was hardly practical. Ultimately, I think we need to keep in mind the primary goal of all this, ie (I think) should there be a “new GDPR in the making” (in terms of having an impact on policies), the community should be able to detect it with this tool. I’m not sure it would in its current state, so the points are well made. Regards, Philippe From: council [mailto:council-bounces@gnso.icann.org] On Behalf Of McGrady, Paul D. Sent: Monday, July 08, 2019 1:30 PM To: Darcy Southwell; Ayden Férdeline; Steve Chan Cc: gnso-secs@icann.org; council@gnso.icann.org Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thanks Darcy. These edits look great. Sorry so slow in responding. I was overtaken by the holiday! Best, Paul From: Darcy Southwell <darcy.southwell@endurance.com> Sent: Monday, July 1, 2019 6:58 PM To: McGrady, Paul D. <PMcGrady@taftlaw.com>; Ayden Férdeline <icann@ferdeline.com>; Steve Chan <steve.chan@icann.org> Cc: gnso-secs@icann.org; council@gnso.icann.org Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thanks for taking the lead, Ayden, and for your edits, Paul. I support Paul’s edits. I have proposed some additional edits in addition to Paul’s in the attached. I think it may be better received if we qualify what we’re seeking from ICANN Org, rather than referencing ICANN activities, which could be perceived as so sweepingly broad that it’s not doable. Thanks, Darcy From: council <council-bounces@gnso.icann.org> on behalf of "McGrady, Paul D." <PMcGrady@taftlaw.com> Date: Sunday, June 30, 2019 at 8:28 AM To: Ayden Férdeline <icann@ferdeline.com>, Steve Chan <steve.chan@icann.org> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org>, "council@gnso.icann.org" <council@gnso.icann.org> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thanks Ayden. All, attached is a revision version with a few edits, mostly around tone. Best, Paul This message may contain information that is attorney-client privileged, attorney work product or otherwise confidential. If you are not an intended recipient, use and disclosure of this message are prohibited. If you received this transmission in error, please notify the sender by reply e-mail and delete the message and any attachments. From: council <council-bounces@gnso.icann.org> On Behalf Of Ayden Férdeline Sent: Sunday, June 30, 2019 6:25 AM To: Steve Chan <steve.chan@icann.org> Cc: gnso-secs@icann.org; council@gnso.icann.org Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements I have drafted a message on behalf of the Council for Council's consideration on this topic. This is based upon our previous conversations. Please find attached and pasted below my signature. Thanks. Ayden Férdeline -- Recommended Improvements from the GNSO Council on ICANN Org Legislative Statement The GNSO Council supports ICANN org in its initiative to identify legislative and regulatory efforts across the globe that may have impacts on ICANN activities. However, we have some recommended improvements to the approach that ICANN org takes. First, the GNSO Council believes that the current, crowdsourced approach where the community is expected to identify errors and omissions in the Global Legislative and Regulatory Developments Report is inappropriate. If ICANN is a professional organization then its professional staff should be comprehensively monitoring the regulatory landscape within which we operate. Second, we encourage ICANN org to conduct proper regulatory impact assessments so that the community can understand the intended rationale for a law/regulation/directive, specific extracts of the proposed text that could have implications on activities within ICANN’s remit, and outline concretely what implications are anticipated for ICANN. A timeline should be included so we understand how imminent the law/regulation/directive is and when we need to take action. Third, we encourage ICANN org to partner with a professional firm to receive regular updates (at least every three months) focused on those key regions which cause the majority of concerns. These reports must be made available to ICANN community members in a timely manner. Fourth, while the GNSO Council would be pleased to accept ongoing monitoring reports, we would also welcome the opportunity to be briefed at our face-to-face meetings by ICANN’s government relations team and to enter into a dialogue about issues that have the potential to cause us concern. Fifth, once a law or regulation has been adopted, ICANN org must undertake a compliance assessment in order to fully understand what implications there may or may not be on ICANN activities. Sixth, the GNSO Council considers the GAC to be an important partner in these discussions and we would be delighted if they are able to alert us to potentially problematic legislation. However, we understand that often the GAC is not in a position to be able to do so, so we believe the onus must ultimately fall on ICANN org to structure the dialogue and to monitor regulatory and legislative developments. Thank you for welcoming our input. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, 23 June 2019 18:01, Steve Chan <steve.chan@icann.org> wrote: Dear Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana, In reviewing the Council’s action items, we recognized that the item below is still outstanding: Small group of Councilors to develop draft message to ICANN Org to provide input on legislative tracker. Based on feedback, Council leadership to consider scheduling follow up discussion at ICANN65. We wanted to bring this to your attention, as you all volunteered to work on this item. While the latter part of the action item (e.g., engaging at ICANN65) is likely impractical at this point, you may still want to draft a message to send to ICANN org. As Keith noted, please work together and let staff know if you need any assistance. Best, Steve From: council <council-bounces@gnso.icann.org> on behalf of "Drazek, Keith via council" <council@gnso.icann.org> Reply-To: "Drazek, Keith" <kdrazek@verisign.com> Date: Thursday, April 4, 2019 at 7:35 PM To: "council@gnso.icann.org" <council@gnso.icann.org> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org> Subject: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana: During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort. As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development. Please work together and with Staff to help kick off this important and timely work. Thanks, Keith _______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council _______________________________________________ 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. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
Hi all, Thanks for all the good work on this response. I have added one more bullet to the letter, which acknowledges and supports further consideration of the potential for the CCEG-IG to serve a formal or informal collaborating function between ICANN Board, ICANN Org, and the community (including GAC) on this important work. Best, Keith From: council <council-bounces@gnso.icann.org> On Behalf Of Pam Little Sent: Tuesday, July 16, 2019 10:08 AM To: Darcy Southwell <darcy.southwell@endurance.com>; philippe.fouquart@orange.com; council <council-bounces@gnso.icann.org> Cc: gnso-secs@icann.org; council@gnso.icann.org Subject: [EXTERNAL] Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Hi all, Apologies - I inadvertently omitted the version that Flip posted earlier, which contained further changes to the third issue. Please use the attached version instead. Kind regards, Pam ------------------------------------------------------------------ Sender:PAMELALITTLE <pam.little@alibaba-inc.com<mailto:pam.little@alibaba-inc.com>> Sent At:2019 Jul. 16 (Tue.) 09:01 Recipient:Darcy Southwell <darcy.southwell@endurance.com<mailto:darcy.southwell@endurance.com>>; philippe.fouquart@orange.com<mailto:philippe.fouquart@orange.com> <philippe.fouquart@orange.com<mailto:philippe.fouquart@orange.com>>; council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> Cc:gnso-secs@icann.org <gnso-secs@icann.org<mailto:gnso-secs@icann.org>>; council@gnso.icann.org<mailto:council@gnso.icann.org> <council@gnso.icann.org<mailto:council@gnso.icann.org>> Subject:Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thank you very much to those who contributed to the draft. I have made a few more suggested edits, including the following for clarity and to avoid repetition: * add a definition: ICANN’s contracts with registries and registrars, consensus policies, and policies in effect or in development (“ICANN’s Contracts and Policies”) * merge the second and fifth points to read: • Second, we encourage ICANN org to conduct standard regulatory impact assessments so that the community can understand the intended rationale for a law/regulation/directive, specific extracts of the proposed text that could have implications on ICANN’s Contracts and Policies, and outline concretely what implications are anticipated. A timeline should be included so the community can understand how imminent the law/regulation/directive is and when it needs to take action. Once such law or regulation has been adopted, ICANN org should undertake a compliance assessment as soon as possible to ensure sufficient time to address any deficiencies or issues. I suggest we aim to send the finalized version by COB this Friday 19th July. So if you have further edits or any concerns or objections, please post to the Council mailing list. Kind regards, Pam ------------------------------------------------------------------ Sender:Flip Petillion <fpetillion@petillion.law<mailto:fpetillion@petillion.law>> Sent At:2019 Jul. 16 (Tue.) 00:39 Recipient:Darcy Southwell <darcy.southwell@endurance.com<mailto:darcy.southwell@endurance.com>>; philippe.fouquart@orange.com<mailto:philippe.fouquart@orange.com> <philippe.fouquart@orange.com<mailto:philippe.fouquart@orange.com>> Cc:gnso-secs@icann.org <gnso-secs@icann.org<mailto:gnso-secs@icann.org>>; council@gnso.icann.org<mailto:council@gnso.icann.org> <council@gnso.icann.org<mailto:council@gnso.icann.org>> Subject:Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements All: I made a change in the third issue. Best Flip Flip Petillion fpetillion@petillion.law<mailto:fpetillion@petillion.law> +32484652653 www.petillion.law<http://www.petillion.law> <http://www.petillion.law/> Attorneys – Advocaten - Avocats From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of Darcy Southwell <darcy.southwell@endurance.com<mailto:darcy.southwell@endurance.com>> Date: Friday, 12 July 2019 at 17:07 To: "philippe.fouquart@orange.com<mailto:philippe.fouquart@orange.com>" <philippe.fouquart@orange.com<mailto:philippe.fouquart@orange.com>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>>, "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements All, I made a minor clarification in the fifth issue. Thanks, Darcy On Tue, Jul 9, 2019 at 8:26 AM <philippe.fouquart@orange.com<mailto:philippe.fouquart@orange.com>> wrote: Thanks (and I don’t even have the holidays to blame :s ). Both Ayden’s points, and the rephrasing suggested by Darcy are excellent. The first item relative to community’s input has been raised a number of times; I remember asking a question during a CSG meeting with the Board in Kobe. Not that the answer was unsatisfactory but it was hardly practical. Ultimately, I think we need to keep in mind the primary goal of all this, ie (I think) should there be a “new GDPR in the making” (in terms of having an impact on policies), the community should be able to detect it with this tool. I’m not sure it would in its current state, so the points are well made. Regards, Philippe From: council [mailto:council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>] On Behalf Of McGrady, Paul D. Sent: Monday, July 08, 2019 1:30 PM To: Darcy Southwell; Ayden Férdeline; Steve Chan Cc: gnso-secs@icann.org<mailto:gnso-secs@icann.org>; council@gnso.icann.org<mailto:council@gnso.icann.org> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thanks Darcy. These edits look great. Sorry so slow in responding. I was overtaken by the holiday! Best, Paul From: Darcy Southwell <darcy.southwell@endurance.com<mailto:darcy.southwell@endurance.com>> Sent: Monday, July 1, 2019 6:58 PM To: McGrady, Paul D. <PMcGrady@taftlaw.com<mailto:PMcGrady@taftlaw.com>>; Ayden Férdeline <icann@ferdeline.com<mailto:icann@ferdeline.com>>; Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>> Cc: gnso-secs@icann.org<mailto:gnso-secs@icann.org>; council@gnso.icann.org<mailto:council@gnso.icann.org> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thanks for taking the lead, Ayden, and for your edits, Paul. I support Paul’s edits. I have proposed some additional edits in addition to Paul’s in the attached. I think it may be better received if we qualify what we’re seeking from ICANN Org, rather than referencing ICANN activities, which could be perceived as so sweepingly broad that it’s not doable. Thanks, Darcy From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of "McGrady, Paul D." <PMcGrady@taftlaw.com<mailto:PMcGrady@taftlaw.com>> Date: Sunday, June 30, 2019 at 8:28 AM To: Ayden Férdeline <icann@ferdeline.com<mailto:icann@ferdeline.com>>, Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>>, "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thanks Ayden. All, attached is a revision version with a few edits, mostly around tone. Best, Paul This message may contain information that is attorney-client privileged, attorney work product or otherwise confidential. If you are not an intended recipient, use and disclosure of this message are prohibited. If you received this transmission in error, please notify the sender by reply e-mail and delete the message and any attachments. From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of Ayden Férdeline Sent: Sunday, June 30, 2019 6:25 AM To: Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>> Cc: gnso-secs@icann.org<mailto:gnso-secs@icann.org>; council@gnso.icann.org<mailto:council@gnso.icann.org> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements I have drafted a message on behalf of the Council for Council's consideration on this topic. This is based upon our previous conversations. Please find attached and pasted below my signature. Thanks. Ayden Férdeline -- Recommended Improvements from the GNSO Council on ICANN Org Legislative Statement The GNSO Council supports ICANN org in its initiative to identify legislative and regulatory efforts across the globe that may have impacts on ICANN activities. However, we have some recommended improvements to the approach that ICANN org takes. * First, the GNSO Council believes that the current, crowdsourced approach where the community is expected to identify errors and omissions in the Global Legislative and Regulatory Developments Report is inappropriate. If ICANN is a professional organization then its professional staff should be comprehensively monitoring the regulatory landscape within which we operate. * Second, we encourage ICANN org to conduct proper regulatory impact assessments so that the community can understand the intended rationale for a law/regulation/directive, specific extracts of the proposed text that could have implications on activities within ICANN’s remit, and outline concretely what implications are anticipated for ICANN. A timeline should be included so we understand how imminent the law/regulation/directive is and when we need to take action. * Third, we encourage ICANN org to partner with a professional firm to receive regular updates (at least every three months) focused on those key regions which cause the majority of concerns. These reports must be made available to ICANN community members in a timely manner. * Fourth, while the GNSO Council would be pleased to accept ongoing monitoring reports, we would also welcome the opportunity to be briefed at our face-to-face meetings by ICANN’s government relations team and to enter into a dialogue about issues that have the potential to cause us concern. * Fifth, once a law or regulation has been adopted, ICANN org must undertake a compliance assessment in order to fully understand what implications there may or may not be on ICANN activities. * Sixth, the GNSO Council considers the GAC to be an important partner in these discussions and we would be delighted if they are able to alert us to potentially problematic legislation. However, we understand that often the GAC is not in a position to be able to do so, so we believe the onus must ultimately fall on ICANN org to structure the dialogue and to monitor regulatory and legislative developments. Thank you for welcoming our input. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, 23 June 2019 18:01, Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>> wrote: Dear Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana, In reviewing the Council’s action items, we recognized that the item below is still outstanding: Small group of Councilors to develop draft message to ICANN Org to provide input on legislative tracker. Based on feedback, Council leadership to consider scheduling follow up discussion at ICANN65. We wanted to bring this to your attention, as you all volunteered to work on this item. While the latter part of the action item (e.g., engaging at ICANN65) is likely impractical at this point, you may still want to draft a message to send to ICANN org. As Keith noted, please work together and let staff know if you need any assistance. Best, Steve From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of "Drazek, Keith via council" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Reply-To: "Drazek, Keith" <kdrazek@verisign.com<mailto:kdrazek@verisign.com>> Date: Thursday, April 4, 2019 at 7:35 PM To: "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana: During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort. As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development. Please work together and with Staff to help kick off this important and timely work. Thanks, Keith _______________________________________________ council mailing list council@gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council _______________________________________________ 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. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
Hi all, After chatting with Pam and Rafik, I made some further edits to my proposed bullet 6, to ensure it does not detract from points 1-5. Please let me know if you have any concerns. Clean version attached. Thanks, Keith From: Drazek, Keith Sent: Tuesday, July 16, 2019 11:59 AM To: 'pam.little@alibaba-inc.com' <pam.little@alibaba-inc.com>; 'darcy.southwell@endurance.com' <darcy.southwell@endurance.com>; 'philippe.fouquart@orange.com' <philippe.fouquart@orange.com>; 'council-bounces@gnso.icann.org' <council-bounces@gnso.icann.org> Cc: 'gnso-secs@icann.org' <gnso-secs@icann.org>; 'council@gnso.icann.org' <council@gnso.icann.org> Subject: RE: [EXTERNAL] Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Hi all, Thanks for all the good work on this response. I have added one more bullet to the letter, which acknowledges and supports further consideration of the potential for the CCEG-IG to serve a formal or informal collaborating function between ICANN Board, ICANN Org, and the community (including GAC) on this important work. Best, Keith From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of Pam Little Sent: Tuesday, July 16, 2019 10:08 AM To: Darcy Southwell <darcy.southwell@endurance.com<mailto:darcy.southwell@endurance.com>>; philippe.fouquart@orange.com<mailto:philippe.fouquart@orange.com>; council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> Cc: gnso-secs@icann.org<mailto:gnso-secs@icann.org>; council@gnso.icann.org<mailto:council@gnso.icann.org> Subject: [EXTERNAL] Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Hi all, Apologies - I inadvertently omitted the version that Flip posted earlier, which contained further changes to the third issue. Please use the attached version instead. Kind regards, Pam ------------------------------------------------------------------ Sender:PAMELALITTLE <pam.little@alibaba-inc.com<mailto:pam.little@alibaba-inc.com>> Sent At:2019 Jul. 16 (Tue.) 09:01 Recipient:Darcy Southwell <darcy.southwell@endurance.com<mailto:darcy.southwell@endurance.com>>; philippe.fouquart@orange.com<mailto:philippe.fouquart@orange.com> <philippe.fouquart@orange.com<mailto:philippe.fouquart@orange.com>>; council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> Cc:gnso-secs@icann.org <gnso-secs@icann.org<mailto:gnso-secs@icann.org>>; council@gnso.icann.org<mailto:council@gnso.icann.org> <council@gnso.icann.org<mailto:council@gnso.icann.org>> Subject:Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thank you very much to those who contributed to the draft. I have made a few more suggested edits, including the following for clarity and to avoid repetition: * add a definition: ICANN’s contracts with registries and registrars, consensus policies, and policies in effect or in development (“ICANN’s Contracts and Policies”) * merge the second and fifth points to read: • Second, we encourage ICANN org to conduct standard regulatory impact assessments so that the community can understand the intended rationale for a law/regulation/directive, specific extracts of the proposed text that could have implications on ICANN’s Contracts and Policies, and outline concretely what implications are anticipated. A timeline should be included so the community can understand how imminent the law/regulation/directive is and when it needs to take action. Once such law or regulation has been adopted, ICANN org should undertake a compliance assessment as soon as possible to ensure sufficient time to address any deficiencies or issues. I suggest we aim to send the finalized version by COB this Friday 19th July. So if you have further edits or any concerns or objections, please post to the Council mailing list. Kind regards, Pam ------------------------------------------------------------------ Sender:Flip Petillion <fpetillion@petillion.law<mailto:fpetillion@petillion.law>> Sent At:2019 Jul. 16 (Tue.) 00:39 Recipient:Darcy Southwell <darcy.southwell@endurance.com<mailto:darcy.southwell@endurance.com>>; philippe.fouquart@orange.com<mailto:philippe.fouquart@orange.com> <philippe.fouquart@orange.com<mailto:philippe.fouquart@orange.com>> Cc:gnso-secs@icann.org <gnso-secs@icann.org<mailto:gnso-secs@icann.org>>; council@gnso.icann.org<mailto:council@gnso.icann.org> <council@gnso.icann.org<mailto:council@gnso.icann.org>> Subject:Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements All: I made a change in the third issue. Best Flip Flip Petillion fpetillion@petillion.law<mailto:fpetillion@petillion.law> +32484652653 www.petillion.law<http://www.petillion.law> <http://www.petillion.law/> Attorneys – Advocaten - Avocats From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of Darcy Southwell <darcy.southwell@endurance.com<mailto:darcy.southwell@endurance.com>> Date: Friday, 12 July 2019 at 17:07 To: "philippe.fouquart@orange.com<mailto:philippe.fouquart@orange.com>" <philippe.fouquart@orange.com<mailto:philippe.fouquart@orange.com>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>>, "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements All, I made a minor clarification in the fifth issue. Thanks, Darcy On Tue, Jul 9, 2019 at 8:26 AM <philippe.fouquart@orange.com<mailto:philippe.fouquart@orange.com>> wrote: Thanks (and I don’t even have the holidays to blame :s ). Both Ayden’s points, and the rephrasing suggested by Darcy are excellent. The first item relative to community’s input has been raised a number of times; I remember asking a question during a CSG meeting with the Board in Kobe. Not that the answer was unsatisfactory but it was hardly practical. Ultimately, I think we need to keep in mind the primary goal of all this, ie (I think) should there be a “new GDPR in the making” (in terms of having an impact on policies), the community should be able to detect it with this tool. I’m not sure it would in its current state, so the points are well made. Regards, Philippe From: council [mailto:council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>] On Behalf Of McGrady, Paul D. Sent: Monday, July 08, 2019 1:30 PM To: Darcy Southwell; Ayden Férdeline; Steve Chan Cc: gnso-secs@icann.org<mailto:gnso-secs@icann.org>; council@gnso.icann.org<mailto:council@gnso.icann.org> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thanks Darcy. These edits look great. Sorry so slow in responding. I was overtaken by the holiday! Best, Paul From: Darcy Southwell <darcy.southwell@endurance.com<mailto:darcy.southwell@endurance.com>> Sent: Monday, July 1, 2019 6:58 PM To: McGrady, Paul D. <PMcGrady@taftlaw.com<mailto:PMcGrady@taftlaw.com>>; Ayden Férdeline <icann@ferdeline.com<mailto:icann@ferdeline.com>>; Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>> Cc: gnso-secs@icann.org<mailto:gnso-secs@icann.org>; council@gnso.icann.org<mailto:council@gnso.icann.org> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thanks for taking the lead, Ayden, and for your edits, Paul. I support Paul’s edits. I have proposed some additional edits in addition to Paul’s in the attached. I think it may be better received if we qualify what we’re seeking from ICANN Org, rather than referencing ICANN activities, which could be perceived as so sweepingly broad that it’s not doable. Thanks, Darcy From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of "McGrady, Paul D." <PMcGrady@taftlaw.com<mailto:PMcGrady@taftlaw.com>> Date: Sunday, June 30, 2019 at 8:28 AM To: Ayden Férdeline <icann@ferdeline.com<mailto:icann@ferdeline.com>>, Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>>, "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thanks Ayden. All, attached is a revision version with a few edits, mostly around tone. Best, Paul This message may contain information that is attorney-client privileged, attorney work product or otherwise confidential. If you are not an intended recipient, use and disclosure of this message are prohibited. If you received this transmission in error, please notify the sender by reply e-mail and delete the message and any attachments. From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of Ayden Férdeline Sent: Sunday, June 30, 2019 6:25 AM To: Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>> Cc: gnso-secs@icann.org<mailto:gnso-secs@icann.org>; council@gnso.icann.org<mailto:council@gnso.icann.org> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements I have drafted a message on behalf of the Council for Council's consideration on this topic. This is based upon our previous conversations. Please find attached and pasted below my signature. Thanks. Ayden Férdeline -- Recommended Improvements from the GNSO Council on ICANN Org Legislative Statement The GNSO Council supports ICANN org in its initiative to identify legislative and regulatory efforts across the globe that may have impacts on ICANN activities. However, we have some recommended improvements to the approach that ICANN org takes. * First, the GNSO Council believes that the current, crowdsourced approach where the community is expected to identify errors and omissions in the Global Legislative and Regulatory Developments Report is inappropriate. If ICANN is a professional organization then its professional staff should be comprehensively monitoring the regulatory landscape within which we operate. * Second, we encourage ICANN org to conduct proper regulatory impact assessments so that the community can understand the intended rationale for a law/regulation/directive, specific extracts of the proposed text that could have implications on activities within ICANN’s remit, and outline concretely what implications are anticipated for ICANN. A timeline should be included so we understand how imminent the law/regulation/directive is and when we need to take action. * Third, we encourage ICANN org to partner with a professional firm to receive regular updates (at least every three months) focused on those key regions which cause the majority of concerns. These reports must be made available to ICANN community members in a timely manner. * Fourth, while the GNSO Council would be pleased to accept ongoing monitoring reports, we would also welcome the opportunity to be briefed at our face-to-face meetings by ICANN’s government relations team and to enter into a dialogue about issues that have the potential to cause us concern. * Fifth, once a law or regulation has been adopted, ICANN org must undertake a compliance assessment in order to fully understand what implications there may or may not be on ICANN activities. * Sixth, the GNSO Council considers the GAC to be an important partner in these discussions and we would be delighted if they are able to alert us to potentially problematic legislation. However, we understand that often the GAC is not in a position to be able to do so, so we believe the onus must ultimately fall on ICANN org to structure the dialogue and to monitor regulatory and legislative developments. Thank you for welcoming our input. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, 23 June 2019 18:01, Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>> wrote: Dear Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana, In reviewing the Council’s action items, we recognized that the item below is still outstanding: Small group of Councilors to develop draft message to ICANN Org to provide input on legislative tracker. Based on feedback, Council leadership to consider scheduling follow up discussion at ICANN65. We wanted to bring this to your attention, as you all volunteered to work on this item. While the latter part of the action item (e.g., engaging at ICANN65) is likely impractical at this point, you may still want to draft a message to send to ICANN org. As Keith noted, please work together and let staff know if you need any assistance. Best, Steve From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of "Drazek, Keith via council" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Reply-To: "Drazek, Keith" <kdrazek@verisign.com<mailto:kdrazek@verisign.com>> Date: Thursday, April 4, 2019 at 7:35 PM To: "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana: During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort. As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development. Please work together and with Staff to help kick off this important and timely work. Thanks, Keith _______________________________________________ council mailing list council@gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council _______________________________________________ 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. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
Apologies…here’s a new version incorporating Marie’s suggested edits from yesterday that I thought I’d captured. Keith From: Drazek, Keith Sent: Wednesday, July 17, 2019 3:33 PM To: 'pam.little@alibaba-inc.com' <pam.little@alibaba-inc.com>; 'darcy.southwell@endurance.com' <darcy.southwell@endurance.com>; 'philippe.fouquart@orange.com' <philippe.fouquart@orange.com> Cc: 'gnso-secs@icann.org' <gnso-secs@icann.org>; 'council@gnso.icann.org' <council@gnso.icann.org> Subject: RE: [EXTERNAL] Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Hi all, After chatting with Pam and Rafik, I made some further edits to my proposed bullet 6, to ensure it does not detract from points 1-5. Please let me know if you have any concerns. Clean version attached. Thanks, Keith From: Drazek, Keith Sent: Tuesday, July 16, 2019 11:59 AM To: 'pam.little@alibaba-inc.com' <pam.little@alibaba-inc.com<mailto:pam.little@alibaba-inc.com>>; 'darcy.southwell@endurance.com' <darcy.southwell@endurance.com<mailto:darcy.southwell@endurance.com>>; 'philippe.fouquart@orange.com' <philippe.fouquart@orange.com<mailto:philippe.fouquart@orange.com>>; 'council-bounces@gnso.icann.org' <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> Cc: 'gnso-secs@icann.org' <gnso-secs@icann.org<mailto:gnso-secs@icann.org>>; 'council@gnso.icann.org' <council@gnso.icann.org<mailto:council@gnso.icann.org>> Subject: RE: [EXTERNAL] Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Hi all, Thanks for all the good work on this response. I have added one more bullet to the letter, which acknowledges and supports further consideration of the potential for the CCEG-IG to serve a formal or informal collaborating function between ICANN Board, ICANN Org, and the community (including GAC) on this important work. Best, Keith From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of Pam Little Sent: Tuesday, July 16, 2019 10:08 AM To: Darcy Southwell <darcy.southwell@endurance.com<mailto:darcy.southwell@endurance.com>>; philippe.fouquart@orange.com<mailto:philippe.fouquart@orange.com>; council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> Cc: gnso-secs@icann.org<mailto:gnso-secs@icann.org>; council@gnso.icann.org<mailto:council@gnso.icann.org> Subject: [EXTERNAL] Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Hi all, Apologies - I inadvertently omitted the version that Flip posted earlier, which contained further changes to the third issue. Please use the attached version instead. Kind regards, Pam ------------------------------------------------------------------ Sender:PAMELALITTLE <pam.little@alibaba-inc.com<mailto:pam.little@alibaba-inc.com>> Sent At:2019 Jul. 16 (Tue.) 09:01 Recipient:Darcy Southwell <darcy.southwell@endurance.com<mailto:darcy.southwell@endurance.com>>; philippe.fouquart@orange.com<mailto:philippe.fouquart@orange.com> <philippe.fouquart@orange.com<mailto:philippe.fouquart@orange.com>>; council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> Cc:gnso-secs@icann.org <gnso-secs@icann.org<mailto:gnso-secs@icann.org>>; council@gnso.icann.org<mailto:council@gnso.icann.org> <council@gnso.icann.org<mailto:council@gnso.icann.org>> Subject:Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thank you very much to those who contributed to the draft. I have made a few more suggested edits, including the following for clarity and to avoid repetition: * add a definition: ICANN’s contracts with registries and registrars, consensus policies, and policies in effect or in development (“ICANN’s Contracts and Policies”) * merge the second and fifth points to read: • Second, we encourage ICANN org to conduct standard regulatory impact assessments so that the community can understand the intended rationale for a law/regulation/directive, specific extracts of the proposed text that could have implications on ICANN’s Contracts and Policies, and outline concretely what implications are anticipated. A timeline should be included so the community can understand how imminent the law/regulation/directive is and when it needs to take action. Once such law or regulation has been adopted, ICANN org should undertake a compliance assessment as soon as possible to ensure sufficient time to address any deficiencies or issues. I suggest we aim to send the finalized version by COB this Friday 19th July. So if you have further edits or any concerns or objections, please post to the Council mailing list. Kind regards, Pam ------------------------------------------------------------------ Sender:Flip Petillion <fpetillion@petillion.law<mailto:fpetillion@petillion.law>> Sent At:2019 Jul. 16 (Tue.) 00:39 Recipient:Darcy Southwell <darcy.southwell@endurance.com<mailto:darcy.southwell@endurance.com>>; philippe.fouquart@orange.com<mailto:philippe.fouquart@orange.com> <philippe.fouquart@orange.com<mailto:philippe.fouquart@orange.com>> Cc:gnso-secs@icann.org <gnso-secs@icann.org<mailto:gnso-secs@icann.org>>; council@gnso.icann.org<mailto:council@gnso.icann.org> <council@gnso.icann.org<mailto:council@gnso.icann.org>> Subject:Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements All: I made a change in the third issue. Best Flip Flip Petillion fpetillion@petillion.law<mailto:fpetillion@petillion.law> +32484652653 www.petillion.law<http://www.petillion.law> <http://www.petillion.law/> Attorneys – Advocaten - Avocats From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of Darcy Southwell <darcy.southwell@endurance.com<mailto:darcy.southwell@endurance.com>> Date: Friday, 12 July 2019 at 17:07 To: "philippe.fouquart@orange.com<mailto:philippe.fouquart@orange.com>" <philippe.fouquart@orange.com<mailto:philippe.fouquart@orange.com>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>>, "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements All, I made a minor clarification in the fifth issue. Thanks, Darcy On Tue, Jul 9, 2019 at 8:26 AM <philippe.fouquart@orange.com<mailto:philippe.fouquart@orange.com>> wrote: Thanks (and I don’t even have the holidays to blame :s ). Both Ayden’s points, and the rephrasing suggested by Darcy are excellent. The first item relative to community’s input has been raised a number of times; I remember asking a question during a CSG meeting with the Board in Kobe. Not that the answer was unsatisfactory but it was hardly practical. Ultimately, I think we need to keep in mind the primary goal of all this, ie (I think) should there be a “new GDPR in the making” (in terms of having an impact on policies), the community should be able to detect it with this tool. I’m not sure it would in its current state, so the points are well made. Regards, Philippe From: council [mailto:council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>] On Behalf Of McGrady, Paul D. Sent: Monday, July 08, 2019 1:30 PM To: Darcy Southwell; Ayden Férdeline; Steve Chan Cc: gnso-secs@icann.org<mailto:gnso-secs@icann.org>; council@gnso.icann.org<mailto:council@gnso.icann.org> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thanks Darcy. These edits look great. Sorry so slow in responding. I was overtaken by the holiday! Best, Paul From: Darcy Southwell <darcy.southwell@endurance.com<mailto:darcy.southwell@endurance.com>> Sent: Monday, July 1, 2019 6:58 PM To: McGrady, Paul D. <PMcGrady@taftlaw.com<mailto:PMcGrady@taftlaw.com>>; Ayden Férdeline <icann@ferdeline.com<mailto:icann@ferdeline.com>>; Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>> Cc: gnso-secs@icann.org<mailto:gnso-secs@icann.org>; council@gnso.icann.org<mailto:council@gnso.icann.org> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thanks for taking the lead, Ayden, and for your edits, Paul. I support Paul’s edits. I have proposed some additional edits in addition to Paul’s in the attached. I think it may be better received if we qualify what we’re seeking from ICANN Org, rather than referencing ICANN activities, which could be perceived as so sweepingly broad that it’s not doable. Thanks, Darcy From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of "McGrady, Paul D." <PMcGrady@taftlaw.com<mailto:PMcGrady@taftlaw.com>> Date: Sunday, June 30, 2019 at 8:28 AM To: Ayden Férdeline <icann@ferdeline.com<mailto:icann@ferdeline.com>>, Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>>, "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Thanks Ayden. All, attached is a revision version with a few edits, mostly around tone. Best, Paul This message may contain information that is attorney-client privileged, attorney work product or otherwise confidential. If you are not an intended recipient, use and disclosure of this message are prohibited. If you received this transmission in error, please notify the sender by reply e-mail and delete the message and any attachments. From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of Ayden Férdeline Sent: Sunday, June 30, 2019 6:25 AM To: Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>> Cc: gnso-secs@icann.org<mailto:gnso-secs@icann.org>; council@gnso.icann.org<mailto:council@gnso.icann.org> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements I have drafted a message on behalf of the Council for Council's consideration on this topic. This is based upon our previous conversations. Please find attached and pasted below my signature. Thanks. Ayden Férdeline -- Recommended Improvements from the GNSO Council on ICANN Org Legislative Statement The GNSO Council supports ICANN org in its initiative to identify legislative and regulatory efforts across the globe that may have impacts on ICANN activities. However, we have some recommended improvements to the approach that ICANN org takes. * First, the GNSO Council believes that the current, crowdsourced approach where the community is expected to identify errors and omissions in the Global Legislative and Regulatory Developments Report is inappropriate. If ICANN is a professional organization then its professional staff should be comprehensively monitoring the regulatory landscape within which we operate. * Second, we encourage ICANN org to conduct proper regulatory impact assessments so that the community can understand the intended rationale for a law/regulation/directive, specific extracts of the proposed text that could have implications on activities within ICANN’s remit, and outline concretely what implications are anticipated for ICANN. A timeline should be included so we understand how imminent the law/regulation/directive is and when we need to take action. * Third, we encourage ICANN org to partner with a professional firm to receive regular updates (at least every three months) focused on those key regions which cause the majority of concerns. These reports must be made available to ICANN community members in a timely manner. * Fourth, while the GNSO Council would be pleased to accept ongoing monitoring reports, we would also welcome the opportunity to be briefed at our face-to-face meetings by ICANN’s government relations team and to enter into a dialogue about issues that have the potential to cause us concern. * Fifth, once a law or regulation has been adopted, ICANN org must undertake a compliance assessment in order to fully understand what implications there may or may not be on ICANN activities. * Sixth, the GNSO Council considers the GAC to be an important partner in these discussions and we would be delighted if they are able to alert us to potentially problematic legislation. However, we understand that often the GAC is not in a position to be able to do so, so we believe the onus must ultimately fall on ICANN org to structure the dialogue and to monitor regulatory and legislative developments. Thank you for welcoming our input. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, 23 June 2019 18:01, Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>> wrote: Dear Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana, In reviewing the Council’s action items, we recognized that the item below is still outstanding: Small group of Councilors to develop draft message to ICANN Org to provide input on legislative tracker. Based on feedback, Council leadership to consider scheduling follow up discussion at ICANN65. We wanted to bring this to your attention, as you all volunteered to work on this item. While the latter part of the action item (e.g., engaging at ICANN65) is likely impractical at this point, you may still want to draft a message to send to ICANN org. As Keith noted, please work together and let staff know if you need any assistance. Best, Steve From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of "Drazek, Keith via council" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Reply-To: "Drazek, Keith" <kdrazek@verisign.com<mailto:kdrazek@verisign.com>> Date: Thursday, April 4, 2019 at 7:35 PM To: "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana: During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort. As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development. Please work together and with Staff to help kick off this important and timely work. Thanks, Keith _______________________________________________ council mailing list council@gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council _______________________________________________ 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. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
This version looks to me to be in good shape. Ayden ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Wednesday, 17 July 2019 14:52, Drazek, Keith via council <council@gnso.icann.org> wrote:
Apologies…here’s a new version incorporating Marie’s suggested edits from yesterday that I thought I’d captured.
Keith
From: Drazek, Keith Sent: Wednesday, July 17, 2019 3:33 PM To: 'pam.little@alibaba-inc.com' <pam.little@alibaba-inc.com>; 'darcy.southwell@endurance.com' <darcy.southwell@endurance.com>; 'philippe.fouquart@orange.com' <philippe.fouquart@orange.com> Cc: 'gnso-secs@icann.org' <gnso-secs@icann.org>; 'council@gnso.icann.org' <council@gnso.icann.org> Subject: RE: [EXTERNAL] Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
Hi all,
After chatting with Pam and Rafik, I made some further edits to my proposed bullet 6, to ensure it does not detract from points 1-5.
Please let me know if you have any concerns. Clean version attached.
Thanks,
Keith
From: Drazek, Keith Sent: Tuesday, July 16, 2019 11:59 AM To: 'pam.little@alibaba-inc.com' <pam.little@alibaba-inc.com>; 'darcy.southwell@endurance.com' <darcy.southwell@endurance.com>; 'philippe.fouquart@orange.com' <philippe.fouquart@orange.com>; 'council-bounces@gnso.icann.org' <council-bounces@gnso.icann.org> Cc: 'gnso-secs@icann.org' <gnso-secs@icann.org>; 'council@gnso.icann.org' <council@gnso.icann.org> Subject: RE: [EXTERNAL] Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
Hi all,
Thanks for all the good work on this response. I have added one more bullet to the letter, which acknowledges and supports further consideration of the potential for the CCEG-IG to serve a formal or informal collaborating function between ICANN Board, ICANN Org, and the community (including GAC) on this important work.
Best,
Keith
From: council <council-bounces@gnso.icann.org> On Behalf Of Pam Little Sent: Tuesday, July 16, 2019 10:08 AM To: Darcy Southwell <darcy.southwell@endurance.com>; philippe.fouquart@orange.com; council <council-bounces@gnso.icann.org> Cc: gnso-secs@icann.org; council@gnso.icann.org Subject: [EXTERNAL] Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
Hi all,
Apologies - I inadvertently omitted the version that Flip posted earlier, which contained further changes to the third issue. Please use the attached version instead.
Kind regards,
Pam
------------------------------------------------------------------
Sender:PAMELALITTLE <pam.little@alibaba-inc.com>
Sent At:2019 Jul. 16 (Tue.) 09:01
Recipient:Darcy Southwell <darcy.southwell@endurance.com>; philippe.fouquart@orange.com <philippe.fouquart@orange.com>; council <council-bounces@gnso.icann.org>
Cc:gnso-secs@icann.org <gnso-secs@icann.org>; council@gnso.icann.org <council@gnso.icann.org>
Subject:Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
Thank you very much to those who contributed to the draft.
I have made a few more suggested edits, including the following for clarity and to avoid repetition:
- add a definition: ICANN’s contracts with registries and registrars, consensus policies, and policies in effect or in development (“ICANN’s Contracts and Policies”)
- merge the second and fifth points to read:
· Second, we encourage ICANN org to conduct standard regulatory impact assessments so that the community can understand the intended rationale for a law/regulation/directive, specific extracts of the proposed text that could have implications on ICANN’s Contracts and Policies, and outline concretely what implications are anticipated. A timeline should be included so the community can understand how imminent the law/regulation/directive is and when it needs to take action. Once such law or regulation has been adopted, ICANN org should undertake a compliance assessment as soon as possible to ensure sufficient time to address any deficiencies or issues.
I suggest we aim to send the finalized version by COB this Friday 19th July. So if you have further edits or any concerns or objections, please post to the Council mailing list.
Kind regards,
Pam
------------------------------------------------------------------
Sender:Flip Petillion <fpetillion@petillion.law>
Sent At:2019 Jul. 16 (Tue.) 00:39
Recipient:Darcy Southwell <darcy.southwell@endurance.com>; philippe.fouquart@orange.com <philippe.fouquart@orange.com>
Cc:gnso-secs@icann.org <gnso-secs@icann.org>; council@gnso.icann.org <council@gnso.icann.org>
Subject:Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
All:
I made a change in the third issue.
Best
Flip
Flip Petillion
fpetillion@petillion.law
+32484652653
www.petillion.law
[signature_2145422569](http://www.petillion.law/)
Attorneys – Advocaten - Avocats
From: council <council-bounces@gnso.icann.org> on behalf of Darcy Southwell <darcy.southwell@endurance.com> Date: Friday, 12 July 2019 at 17:07 To: "philippe.fouquart@orange.com" <philippe.fouquart@orange.com> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org>, "council@gnso.icann.org" <council@gnso.icann.org> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
All, I made a minor clarification in the fifth issue.
Thanks,
Darcy
On Tue, Jul 9, 2019 at 8:26 AM <philippe.fouquart@orange.com> wrote:
Thanks (and I don’t even have the holidays to blame :s ). Both Ayden’s points, and the rephrasing suggested by Darcy are excellent.
The first item relative to community’s input has been raised a number of times; I remember asking a question during a CSG meeting with the Board in Kobe. Not that the answer was unsatisfactory but it was hardly practical.
Ultimately, I think we need to keep in mind the primary goal of all this, ie (I think) should there be a “new GDPR in the making” (in terms of having an impact on policies), the community should be able to detect it with this tool. I’m not sure it would in its current state, so the points are well made.
Regards,
Philippe
From: council [mailto:council-bounces@gnso.icann.org] On Behalf Of McGrady, Paul D. Sent: Monday, July 08, 2019 1:30 PM To: Darcy Southwell; Ayden Férdeline; Steve Chan Cc: gnso-secs@icann.org; council@gnso.icann.org Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
Thanks Darcy. These edits look great. Sorry so slow in responding. I was overtaken by the holiday!
Best,
Paul
From: Darcy Southwell <darcy.southwell@endurance.com> Sent: Monday, July 1, 2019 6:58 PM To: McGrady, Paul D. <PMcGrady@taftlaw.com>; Ayden Férdeline <icann@ferdeline.com>; Steve Chan <steve.chan@icann.org> Cc: gnso-secs@icann.org; council@gnso.icann.org Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
Thanks for taking the lead, Ayden, and for your edits, Paul. I support Paul’s edits. I have proposed some additional edits in addition to Paul’s in the attached.
I think it may be better received if we qualify what we’re seeking from ICANN Org, rather than referencing ICANN activities, which could be perceived as so sweepingly broad that it’s not doable.
Thanks,
Darcy
From: council <council-bounces@gnso.icann.org> on behalf of "McGrady, Paul D." <PMcGrady@taftlaw.com> Date: Sunday, June 30, 2019 at 8:28 AM To: Ayden Férdeline <icann@ferdeline.com>, Steve Chan <steve.chan@icann.org> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org>, "council@gnso.icann.org" <council@gnso.icann.org> Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
Thanks Ayden.
All, attached is a revision version with a few edits, mostly around tone.
Best,
Paul
This message may contain information that is attorney-client privileged, attorney work product or otherwise confidential. If you are not an intended recipient, use and disclosure of this message are prohibited. If you received this transmission in error, please notify the sender by reply e-mail and delete the message and any attachments.
From: council <council-bounces@gnso.icann.org> On Behalf Of Ayden Férdeline Sent: Sunday, June 30, 2019 6:25 AM To: Steve Chan <steve.chan@icann.org> Cc: gnso-secs@icann.org; council@gnso.icann.org Subject: Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
I have drafted a message on behalf of the Council for Council's consideration on this topic. This is based upon our previous conversations. Please find attached and pasted below my signature. Thanks.
Ayden Férdeline
--
Recommended Improvements from the GNSO Council on ICANN Org Legislative Statement
The GNSO Council supports ICANN org in its initiative to identify legislative and regulatory efforts across the globe that may have impacts on ICANN activities. However, we have some recommended improvements to the approach that ICANN org takes.
- First, the GNSO Council believes that the current, crowdsourced approach where the community is expected to identify errors and omissions in the Global Legislative and Regulatory Developments Report is inappropriate. If ICANN is a professional organization then its professional staff should be comprehensively monitoring the regulatory landscape within which we operate. - Second, we encourage ICANN org to conduct proper regulatory impact assessments so that the community can understand the intended rationale for a law/regulation/directive, specific extracts of the proposed text that could have implications on activities within ICANN’s remit, and outline concretely what implications are anticipated for ICANN. A timeline should be included so we understand how imminent the law/regulation/directive is and when we need to take action. - Third, we encourage ICANN org to partner with a professional firm to receive regular updates (at least every three months) focused on those key regions which cause the majority of concerns. These reports must be made available to ICANN community members in a timely manner. - Fourth, while the GNSO Council would be pleased to accept ongoing monitoring reports, we would also welcome the opportunity to be briefed at our face-to-face meetings by ICANN’s government relations team and to enter into a dialogue about issues that have the potential to cause us concern. - Fifth, once a law or regulation has been adopted, ICANN org must undertake a compliance assessment in order to fully understand what implications there may or may not be on ICANN activities. - Sixth, the GNSO Council considers the GAC to be an important partner in these discussions and we would be delighted if they are able to alert us to potentially problematic legislation. However, we understand that often the GAC is not in a position to be able to do so, so we believe the onus must ultimately fall on ICANN org to structure the dialogue and to monitor regulatory and legislative developments.
Thank you for welcoming our input.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, 23 June 2019 18:01, Steve Chan <steve.chan@icann.org> wrote:
Dear Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana,
In reviewing the Council’s action items, we recognized that the item below is still outstanding:
Small group of Councilors to develop draft message to ICANN Org to provide input on legislative tracker. Based on feedback, Council leadership to consider scheduling follow up discussion at ICANN65.
We wanted to bring this to your attention, as you all volunteered to work on this item. While the latter part of the action item (e.g., engaging at ICANN65) is likely impractical at this point, you may still want to draft a message to send to ICANN org. As Keith noted, please work together and let staff know if you need any assistance.
Best,
Steve
From: council <council-bounces@gnso.icann.org> on behalf of "Drazek, Keith via council" <council@gnso.icann.org> Reply-To: "Drazek, Keith" <kdrazek@verisign.com> Date: Thursday, April 4, 2019 at 7:35 PM To: "council@gnso.icann.org" <council@gnso.icann.org> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org> Subject: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana:
During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort.
As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development.
Please work together and with Staff to help kick off this important and timely work.
Thanks,
Keith
_______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council _______________________________________________ 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.
_________________________________________________________________________________________________________________________
Ce message et
ses
pieces
jointes
peuvent contenir des
informations
confidentielles ou privilegiees et ne doivent
donc
pas
etre
diffuses,
exploites
ou copies sans
autorisation
. Si
vous
avez
recu
ce message par
erreur
, veuillez le signaler
a l'expediteur et le detruire ainsi que
les
pieces
jointes
. Les messages electroniques etant susceptibles d'alteration,
Orange decline
toute
responsabilite si ce message a
ete
altere,
deforme
ou
falsifie
. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
Thanks to all who worked on this draft. I have a question about the fifth line: i don’t see the point of singling out the GAC given that we have already mentioned the importance of community input and the need for ICANN to take the lead on structuring dialogue and monitoring in the other points. For reference: Fifth, the GNSO Council considers the GAC to be an important partner in these discussions and we would be delighted if they are able to alert us to potentially problematic legislation. However, we understand that often the GAC is not in a position to be able to do so, so we believe the onus must ultimately fall on ICANN org to structure the dialogue and to monitor regulatory and legislative developments. Best, Elsa — On Tue, Jul 16, 2019 at 5:59 AM Drazek, Keith via council < council@gnso.icann.org> wrote: Hi all,
Thanks for all the good work on this response. I have added one more bullet to the letter, which acknowledges and supports further consideration of the potential for the CCEG-IG to serve a formal or informal collaborating function between ICANN Board, ICANN Org, and the community (including GAC) on this important work.
Best,
Keith
*From:* council <council-bounces@gnso.icann.org> *On Behalf Of *Pam Little *Sent:* Tuesday, July 16, 2019 10:08 AM *To:* Darcy Southwell <darcy.southwell@endurance.com>; philippe.fouquart@orange.com; council <council-bounces@gnso.icann.org> *Cc:* gnso-secs@icann.org; council@gnso.icann.org *Subject:* [EXTERNAL] Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
Hi all,
Apologies - I inadvertently omitted the version that Flip posted earlier, which contained further changes to the third issue. Please use the attached version instead.
Kind regards,
Pam
------------------------------------------------------------------
Sender:PAMELALITTLE <pam.little@alibaba-inc.com>
Sent At:2019 Jul. 16 (Tue.) 09:01
Recipient:Darcy Southwell <darcy.southwell@endurance.com>; philippe.fouquart@orange.com <philippe.fouquart@orange.com>; council < council-bounces@gnso.icann.org>
Cc:gnso-secs@icann.org <gnso-secs@icann.org>; council@gnso.icann.org < council@gnso.icann.org>
Subject:Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
Thank you very much to those who contributed to the draft.
I have made a few more suggested edits, including the following for clarity and to avoid repetition:
- add a definition: *ICANN’s contracts with registries and registrars, consensus policies, and policies in effect or in development (“ICANN’s Contracts and Policies”)*
- merge the second and fifth points to read:
· *Second, we encourage ICANN **org** to conduct standard regulatory impact assessments so that the community can understand the intended rationale for a law/regulation/directive, specific extracts of the proposed text that could have implications on ICANN’s Contracts and Policies, and outline concretely what implications are anticipated. A timeline should be included so the community can understand how imminent the law/regulation/directive is and when it needs to take action. Once such law or regulation has been adopted, ICANN **org** should undertake a compliance assessment as soon as possible to ensure sufficient time to address any deficiencies or issues.*
I suggest we aim to send the finalized version by COB this Friday 19th July. So if you have further edits or any concerns or objections, please post to the Council mailing list.
Kind regards,
Pam
------------------------------------------------------------------
Sender:Flip Petillion <fpetillion@petillion.law>
Sent At:2019 Jul. 16 (Tue.) 00:39
Recipient:Darcy Southwell <darcy.southwell@endurance.com>; philippe.fouquart@orange.com <philippe.fouquart@orange.com>
Cc:gnso-secs@icann.org <gnso-secs@icann.org>; council@gnso.icann.org < council@gnso.icann.org>
Subject:Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
All:
I made a change in the third issue.
Best
Flip
Flip Petillion
fpetillion@petillion.law
+32484652653
www.petillion.law
[image: signature_2145422569] <http://www.petillion.law/>
Attorneys – Advocaten - Avocats
*From: *council <council-bounces@gnso.icann.org> on behalf of Darcy Southwell <darcy.southwell@endurance.com> *Date: *Friday, 12 July 2019 at 17:07 *To: *"philippe.fouquart@orange.com" <philippe.fouquart@orange.com> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org>, "council@gnso.icann.org" <council@gnso.icann.org> *Subject: *Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
All, I made a minor clarification in the fifth issue.
Thanks,
Darcy
On Tue, Jul 9, 2019 at 8:26 AM <philippe.fouquart@orange.com> wrote:
Thanks (and I don’t even have the holidays to blame :s ). Both Ayden’s points, and the rephrasing suggested by Darcy are excellent.
The first item relative to community’s input has been raised a number of times; I remember asking a question during a CSG meeting with the Board in Kobe. Not that the answer was unsatisfactory but it was hardly practical.
Ultimately, I think we need to keep in mind the primary goal of all this, ie (I think) should there be a “new GDPR in the making” (in terms of having an impact on policies), the community should be able to detect it with this tool. I’m not sure it would in its current state, so the points are well made.
Regards,
Philippe
*From:* council [mailto:council-bounces@gnso.icann.org] *On Behalf Of *McGrady, Paul D. *Sent:* Monday, July 08, 2019 1:30 PM *To:* Darcy Southwell; Ayden Férdeline; Steve Chan *Cc:* gnso-secs@icann.org; council@gnso.icann.org *Subject:* Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
Thanks Darcy. These edits look great. Sorry so slow in responding. I was overtaken by the holiday!
Best,
Paul
*From:* Darcy Southwell <darcy.southwell@endurance.com> *Sent:* Monday, July 1, 2019 6:58 PM *To:* McGrady, Paul D. <PMcGrady@taftlaw.com>; Ayden Férdeline < icann@ferdeline.com>; Steve Chan <steve.chan@icann.org> *Cc:* gnso-secs@icann.org; council@gnso.icann.org *Subject:* Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
Thanks for taking the lead, Ayden, and for your edits, Paul. I support Paul’s edits. I have proposed some additional edits in addition to Paul’s in the attached.
I think it may be better received if we qualify what we’re seeking from ICANN Org, rather than referencing ICANN activities, which could be perceived as so sweepingly broad that it’s not doable.
Thanks,
Darcy
*From: *council <council-bounces@gnso.icann.org> on behalf of "McGrady, Paul D." <PMcGrady@taftlaw.com> *Date: *Sunday, June 30, 2019 at 8:28 AM *To: *Ayden Férdeline <icann@ferdeline.com>, Steve Chan < steve.chan@icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org>, "council@gnso.icann.org" <council@gnso.icann.org> *Subject: *Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
Thanks Ayden.
All, attached is a revision version with a few edits, mostly around tone.
Best,
Paul
This message may contain information that is attorney-client privileged, attorney work product or otherwise confidential. If you are not an intended recipient, use and disclosure of this message are prohibited. If you received this transmission in error, please notify the sender by reply e-mail and delete the message and any attachments.
*From:* council <council-bounces@gnso.icann.org> *On Behalf Of *Ayden Férdeline *Sent:* Sunday, June 30, 2019 6:25 AM *To:* Steve Chan <steve.chan@icann.org> *Cc:* gnso-secs@icann.org; council@gnso.icann.org *Subject:* Re: [council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
I have drafted a message on behalf of the Council for Council's consideration on this topic. This is based upon our previous conversations. Please find attached and pasted below my signature. Thanks.
Ayden Férdeline
--
*Recommended Improvements from the GNSO Council on ICANN Org Legislative Statement*
The GNSO Council supports ICANN org in its initiative to identify legislative and regulatory efforts across the globe that may have impacts on ICANN activities. However, we have some recommended improvements to the approach that ICANN org takes.
- First, the GNSO Council believes that the current, crowdsourced approach where the community is expected to identify errors and omissions in the Global Legislative and Regulatory Developments Report is inappropriate. If ICANN is a professional organization then its professional staff should be comprehensively monitoring the regulatory landscape within which we operate. - Second, we encourage ICANN org to conduct proper regulatory impact assessments so that the community can understand the intended rationale for a law/regulation/directive, specific extracts of the proposed text that could have implications on activities within ICANN’s remit, and outline concretely what implications are anticipated for ICANN. A timeline should be included so we understand how imminent the law/regulation/directive is and when we need to take action. - Third, we encourage ICANN org to partner with a professional firm to receive regular updates (at least every three months) focused on those key regions which cause the majority of concerns. These reports must be made available to ICANN community members in a timely manner. - Fourth, while the GNSO Council would be pleased to accept ongoing monitoring reports, we would also welcome the opportunity to be briefed at our face-to-face meetings by ICANN’s government relations team and to enter into a dialogue about issues that have the potential to cause us concern. - Fifth, once a law or regulation has been adopted, ICANN org must undertake a compliance assessment in order to fully understand what implications there may or may not be on ICANN activities. - Sixth, the GNSO Council considers the GAC to be an important partner in these discussions and we would be delighted if they are able to alert us to potentially problematic legislation. However, we understand that often the GAC is not in a position to be able to do so, so we believe the onus must ultimately fall on ICANN org to structure the dialogue and to monitor regulatory and legislative developments.
Thank you for welcoming our input.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, 23 June 2019 18:01, Steve Chan <steve.chan@icann.org> wrote:
Dear Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana,
In reviewing the Council’s action items, we recognized that the item below is still outstanding:
*Small group of Councilors* to develop draft message to ICANN Org to provide input on legislative tracker. Based on feedback, Council leadership to consider scheduling follow up discussion at ICANN65.
We wanted to bring this to your attention, as you all volunteered to work on this item. While the latter part of the action item (e.g., engaging at ICANN65) is likely impractical at this point, you may still want to draft a message to send to ICANN org. As Keith noted, please work together and let staff know if you need any assistance.
Best,
Steve
*From: *council <council-bounces@gnso.icann.org> on behalf of "Drazek, Keith via council" <council@gnso.icann.org> *Reply-To: *"Drazek, Keith" <kdrazek@verisign.com> *Date: *Thursday, April 4, 2019 at 7:35 PM *To: *"council@gnso.icann.org" <council@gnso.icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org> *Subject: *[council] ICANN's Legislative/Regulatory Tracker -- Recommended Improvements
Ayden, Darcy, Erika, Flip, Michele, Phillipe and Tatiana:
During our GNSO Working Session in Kobe, the seven of you volunteered to help develop GNSO Council recommendations for improvements to ICANN’s current Legislative/Regulatory tracking effort.
As we discussed, ICANN’s work in this area is relatively new and still evolving, and we have an opportunity to engage with Theresa’s group to help shape their approach to ensure it is applicable to our policy work and process management responsibilities. While their work product is currently a spreadsheet, I recall we agreed it needs to go much deeper in analysis and demonstrate a predictive capability for where future or existing regulations impact GNSO policies, in effect now or under future development.
Please work together and with Staff to help kick off this important and timely work.
Thanks,
Keith
_______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council _______________________________________________ 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.
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
_______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council
_______________________________________________ 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.
participants (14)
-
Ayden Férdeline -
Carlos Raul Gutierrez -
Darcy Southwell -
Drazek, Keith -
Elsa S -
Erika Mann -
Flip Petillion -
Martin Pablo Silva Valent -
McGrady, Paul D. -
McGrady, Paul D. -
Michele Neylon - Blacknight -
Pam Little -
philippe.fouquart＠orange.com -
Steve Chan