CPH letter to ICANN org on DNS Abuse now
Dear GNSO Councillors, As you may recall, a recommendation in the DNS Abuse small team report was to consult with contracted parties re: potential issues with the existing accreditation agreements with ICANN. It seems Contracted Parties may be ahead of the curve and have sent a CPH letter to ICANN org re: DNS Abuse provisions in their contracts (see https://www.icann.org/en/system/files/correspondence/heineman-demetriou-to-m...) . I am flagging it here for everyone's reference. Thanks, Greg
Thank you, Greg. That letter reached the BC this morning and I had a read. It is very much in alignment with everything we have discussed and what is being recommended by the Small Team. I will incentivize the members to move ahead in drafting our letter so that we continue to add legitimacy and transparency to the process, leaving behind a solid trail of documents that validates this to the broader Internet community and something all stakeholders are getting behind. Best, On 8 Nov 2022 19:53, DiBiase, Gregory via council wrote:
Dear GNSO Councillors,
As you may recall, a recommendation in the DNS Abuse small team report was to consult with contracted parties re: potential issues with the existing accreditation agreements with ICANN. It seems Contracted Parties may be ahead of the curve and have sent a CPH letter to ICANN org re: DNS Abuse provisions in their contracts (see https://www.icann.org/en/system/files/correspondence/heineman-demetriou-to-m...) . I am flagging it here for everyone’s reference.
Thanks,
Greg
_______________________________________________ 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.
-- Mark W. Datysgeld [markwd.website <https://markwd.website>] Director at Governance Primer [governanceprimer.com <https://governanceprimer.com>] ICANN GNSO Councilor
Hi Mark, I am not sure if I understand what you are proposing? For the first time in ICANN history the CPH's are volunteering to make some key critical adjustments to the contract we have with ICANN. CPH's are determined to advance the language where the community always felt it was lacking in certain areas. So I am not sure how this process needs more legitimacy and transparancy? Our goal is very clear I think and I am a big supporter of the letter as it will be a game changer in the end. But maybe I am missing some key details here? Thanks, Theo On Wed, Nov 9, 2022, at 3:07 AM, Mark Datysgeld via council wrote:
Thank you, Greg.
That letter reached the BC this morning and I had a read. It is very much in alignment with everything we have discussed and what is being recommended by the Small Team.
I will incentivize the members to move ahead in drafting our letter so that we continue to add legitimacy and transparency to the process, leaving behind a solid trail of documents that validates this to the broader Internet community and something all stakeholders are getting behind.
Best,
On 8 Nov 2022 19:53, DiBiase, Gregory via council wrote:
Dear GNSO Councillors,
As you may recall, a recommendation in the DNS Abuse small team report was to consult with contracted parties re: potential issues with the existing accreditation agreements with ICANN. It seems Contracted Parties may be ahead of the curve and have sent a CPH letter to ICANN org re: DNS Abuse provisions in their contracts (see https://www.icann.org/en/system/files/correspondence/heineman-demetriou-to-m...) . I am flagging it here for everyone’s reference.
Thanks, Greg
_______________________________________________ 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. -- Mark W. Datysgeld [markwd.website] Director at Governance Primer [governanceprimer.com] ICANN GNSO Councilor
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.
Theo, hope you are doing well. No need to read too much into my words, I'm just saying the GNSO Council's letter is still useful, as it helps us show to people who were not a part of this process that the community is in full support of this negotiation. :) The idea is precisely to highlight the CPH's efforts by giving it the community support. Best, On 9 Nov 2022 15:31, Theo Geurts via council wrote:
Hi Mark,
I am not sure if I understand what you are proposing?
For the first time in ICANN history the CPH's are volunteering to make some key critical adjustments to the contract we have with ICANN. CPH's are determined to advance the language where the community always felt it was lacking in certain areas.
So I am not sure how this process needs more legitimacy and transparancy? Our goal is very clear I think and I am a big supporter of the letter as it will be a game changer in the end.
But maybe I am missing some key details here?
Thanks, Theo
On Wed, Nov 9, 2022, at 3:07 AM, Mark Datysgeld via council wrote:
Thank you, Greg.
That letter reached the BC this morning and I had a read. It is very much in alignment with everything we have discussed and what is being recommended by the Small Team.
I will incentivize the members to move ahead in drafting our letter so that we continue to add legitimacy and transparency to the process, leaving behind a solid trail of documents that validates this to the broader Internet community and something all stakeholders are getting behind.
Best,
On 8 Nov 2022 19:53, DiBiase, Gregory via council wrote:
Dear GNSO Councillors,
As you may recall, a recommendation in the DNS Abuse small team report was to consult with contracted parties re: potential issues with the existing accreditation agreements with ICANN. It seems Contracted Parties may be ahead of the curve and have sent a CPH letter to ICANN org re: DNS Abuse provisions in their contracts (see https://www.icann.org/en/system/files/correspondence/heineman-demetriou-to-m... <https://www.icann.org/en/system/files/correspondence/heineman-demetriou-to-m...>) . I am flagging it here for everyone’s reference.
Thanks,
Greg
_______________________________________________ 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.
-- Mark W. Datysgeld [markwd.website <https://markwd.website>] Director at Governance Primer [governanceprimer.com <https://governanceprimer.com>] ICANN GNSO Councilor _______________________________________________ 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.
_______________________________________________ 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. -- Mark W. Datysgeld [markwd.website <https://markwd.website>] Director at Governance Primer [governanceprimer.com <https://governanceprimer.com>] ICANN GNSO Councilor
Hi Mark, My apologies, I guess my day job which involves making sure bad people are having a bad day by taking down their domain names made me somewhat protective around the letter which in my mind is a major step in the right direction. Thanks for the clarification and all is well here, thanks for asking. Theo On Wed, Nov 9, 2022, at 7:55 PM, Mark Datysgeld wrote:
Theo, hope you are doing well.
No need to read too much into my words, I'm just saying the GNSO Council's letter is still useful, as it helps us show to people who were not a part of this process that the community is in full support of this negotiation. :)
The idea is precisely to highlight the CPH's efforts by giving it the community support.
Best,
On 9 Nov 2022 15:31, Theo Geurts via council wrote:
Hi Mark,
I am not sure if I understand what you are proposing?
For the first time in ICANN history the CPH's are volunteering to make some key critical adjustments to the contract we have with ICANN. CPH's are determined to advance the language where the community always felt it was lacking in certain areas.
So I am not sure how this process needs more legitimacy and transparancy? Our goal is very clear I think and I am a big supporter of the letter as it will be a game changer in the end.
But maybe I am missing some key details here?
Thanks, Theo
On Wed, Nov 9, 2022, at 3:07 AM, Mark Datysgeld via council wrote:
Thank you, Greg.
That letter reached the BC this morning and I had a read. It is very much in alignment with everything we have discussed and what is being recommended by the Small Team.
I will incentivize the members to move ahead in drafting our letter so that we continue to add legitimacy and transparency to the process, leaving behind a solid trail of documents that validates this to the broader Internet community and something all stakeholders are getting behind.
Best,
On 8 Nov 2022 19:53, DiBiase, Gregory via council wrote:
Dear GNSO Councillors,
As you may recall, a recommendation in the DNS Abuse small team report was to consult with contracted parties re: potential issues with the existing accreditation agreements with ICANN. It seems Contracted Parties may be ahead of the curve and have sent a CPH letter to ICANN org re: DNS Abuse provisions in their contracts (see https://www.icann.org/en/system/files/correspondence/heineman-demetriou-to-m...) . I am flagging it here for everyone’s reference.
Thanks, Greg
_______________________________________________ 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.
-- Mark W. Datysgeld [markwd.website] Director at Governance Primer [governanceprimer.com] ICANN GNSO Councilor _______________________________________________ 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.
_______________________________________________ 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. -- Mark W. Datysgeld [markwd.website] Director at Governance Primer [governanceprimer.com] ICANN GNSO Councilor
Agree that the letter is a major step in the right direction! Best, Paul Taft / Paul D. McGrady, Jr. Partner PMcGrady@taftlaw.com<mailto:PMcGrady@taftlaw.com> Dir: 312.836.4094 | Cell: 312.882.5020 Tel: 312.527.4000 | Fax: 312.754.2354 111 E. Wacker Drive, Suite 2600 Chicago, Illinois 60601-4208 Download vCard<http://www.taftlaw.com/vcard/PMcGrady@taftlaw.com> taftlaw.com<http://www.taftlaw.com> [https://taftlawpr.blob.core.windows.net/taft/files/fileuploads/62f506bb609f40002f521357/Taft%20Jaffe%20Logo%20-%20Signature%20Block-02.png]<https://taftlawpr.blob.core.windows.net/taft/files/fileuploads/62f506bb609f40002f521357/Taft%20Jaffe%20Logo%20-%20Signature%20Block-02.png> Jaffe is joining Taft, effective Dec 31, 2022. Learn more here.<https://www.taftlaw.com/news-events/news/taft-expands-midwest-reach-and-capa...> 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 Theo Geurts via council Sent: Wednesday, November 9, 2022 1:27 PM To: Mark Datysgeld <mark@governanceprimer.com>; Steve Chan <council@gnso.icann.org> Subject: Re: [council] CPH letter to ICANN org on DNS Abuse now Hi Mark, My apologies, I guess my day job which involves making sure bad people are having a bad day by taking down their domain names made me somewhat protective around the letter which in my mind is a major step in the right direction. Thanks for the clarification and all is we [https://alert-dg01.redatatech.com/onprem_security_warning_fetch?r=1&dep=UdYADUxlB0%2BqO9q8AvgA4w%3D%3DoQCjaAB5YLtNOGi74FwIsk5u8wFzQDyCQp7KF%2BDC2Bqn%2F0DVBsxCNDiI48VqZJ4vZ5d8FQHaBygKVTnAEDE9FmitCCqN%2BtiXp%2F%2BA5hrDbSLE6QNPOCdWB2HKzrYhkny%2FLTermufdQx4CY%2BwbZCaCwhS%2Bg5fPu8%2BgrqLc8VB4dDSPJX6mVPTKqhKzaPudx8LnYxTMftPZ2GDnDwJAtCde37bi7wyfXIOs%2B1mvXMUTKV5Za1tXecDxmXqtzlWU9SsOJL2TiB4y5S2WtHlT5emmXhvuxmhipVOzydSREiPe66RENca963BLzXMvuc2mL5TXYq169vMHLnPXa4N24kKJ7FrNYTNeKjN0H3SJOYBnhoJeyYmgub7NZIf4t7IVypJ5NLZMLaOL%2FN6%2B%2Ba%2FuPUOGQH1lxjNHZe7ZrPaH0PeI9Gs7lSSNP4TF9pxFR%2BZwGTAL1pg9yZ5gHveTVuP%2Bz%2BNvB1jjKGs5%2FUY6ol5Y6lIi0kH2ZL%2Bo8200wI1KRsY9CR34plGPxylY9teui%2BBLCjWm6406y1vB61WA5306bhqwgYypg05bkKqPNBIPPkhCf4%2Fm%2BIjP7jZVg8Kkg5fWHE70Dy9yvR3hnlZt7MQXmb55Nm2wWeyGmW7yANzbx7X6%2BxykR98QQLJ1L2s6VlqxMsCunnqJlczDiEvX9wp42vKr8P2g69ajVgukL%2BnSetOg3X5a]<https://us.report.cybergraph.mimecast.com/alert-details/?dep=UdYADUxlB0%2BqO9q8AvgA4w%3D%3DoQCjaAB5YLtNOGi74FwIsk5u8wFzQDyCQp7KF%2BDC2Bqn%2F0DVBsxCNDiI48VqZJ4vZ5d8FQHaBygKVTnAEDE9FmitCCqN%2BtiXp%2F%2BA5hrDbSLE6QNPOCdWB2HKzrYhkny%2FLTermufdQx4CY%2BwbZCaCwhS%2Bg5fPu8%2BgrqLc8VB4dDSPJX6mVPTKqhKzaPudx8LnYxTMftPZ2GDnDwJAtCde37bi7wyfXIOs%2B1mvXMUTKV5Za1tXecDxmXqtzlWU9SsOJL2TiB4y5S2WtHlT5emmXhvuxmhipVOzydSREiPe66RENca963BLzXMvuc2mL5TXYq169vMHLnPXa4N24kKJ7FrNYTNeKjN0H3SJOYBnhoJeyYmgub7NZIf4t7IVypJ5NLZMLaOL%2FN6%2B%2Ba%2FuPUOGQH1lxjNHZe7ZrPaH0PeI9Gs7lSSNP4TF9pxFR%2BZwGTAL1pg9yZ5gHveTVuP%2Bz%2BNvB1jjKGs5%2FUY6ol5Y6lIi0kH2ZL%2Bo8200wI1KRsY9CR34plGPxylY9teui%2BBLCjWm6406y1vB61WA5306bhqwgYypg05bkKqPNBIPPkhCf4%2Fm%2BIjP7jZVg8Kkg5fWHE70Dy9yvR3hnlZt7MQXmb55Nm2wWeyGmW7yANzbx7X6%2BxykR98QQLJ1L2s6VlqxMsCunnqJlczDiEvX9wp42vKr8P2g69ajVgukL%2BnSetOg3X5a> Hi Mark, My apologies, I guess my day job which involves making sure bad people are having a bad day by taking down their domain names made me somewhat protective around the letter which in my mind is a major step in the right direction. Thanks for the clarification and all is well here, thanks for asking. Theo On Wed, Nov 9, 2022, at 7:55 PM, Mark Datysgeld wrote: Theo, hope you are doing well. No need to read too much into my words, I'm just saying the GNSO Council's letter is still useful, as it helps us show to people who were not a part of this process that the community is in full support of this negotiation. :) The idea is precisely to highlight the CPH's efforts by giving it the community support. Best, On 9 Nov 2022 15:31, Theo Geurts via council wrote: Hi Mark, I am not sure if I understand what you are proposing? For the first time in ICANN history the CPH's are volunteering to make some key critical adjustments to the contract we have with ICANN. CPH's are determined to advance the language where the community always felt it was lacking in certain areas. So I am not sure how this process needs more legitimacy and transparancy? Our goal is very clear I think and I am a big supporter of the letter as it will be a game changer in the end. But maybe I am missing some key details here? Thanks, Theo On Wed, Nov 9, 2022, at 3:07 AM, Mark Datysgeld via council wrote: Thank you, Greg. That letter reached the BC this morning and I had a read. It is very much in alignment with everything we have discussed and what is being recommended by the Small Team. I will incentivize the members to move ahead in drafting our letter so that we continue to add legitimacy and transparency to the process, leaving behind a solid trail of documents that validates this to the broader Internet community and something all stakeholders are getting behind. Best, On 8 Nov 2022 19:53, DiBiase, Gregory via council wrote: Dear GNSO Councillors, As you may recall, a recommendation in the DNS Abuse small team report was to consult with contracted parties re: potential issues with the existing accreditation agreements with ICANN. It seems Contracted Parties may be ahead of the curve and have sent a CPH letter to ICANN org re: DNS Abuse provisions in their contracts (see https://www.icann.org/en/system/files/correspondence/heineman-demetriou-to-m...) . I am flagging it here for everyone’s reference. Thanks, Greg _______________________________________________ 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. -- Mark W. Datysgeld [markwd.website<https://markwd.website>] Director at Governance Primer [governanceprimer.com<https://governanceprimer.com>] ICANN GNSO Councilor _______________________________________________ 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. _______________________________________________ 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. -- Mark W. Datysgeld [markwd.website<https://markwd.website>] Director at Governance Primer [governanceprimer.com<https://governanceprimer.com>] ICANN GNSO Councilor
participants (4)
-
DiBiase, Gregory -
Mark Datysgeld -
McGrady, Jr., Paul D. -
Theo Geurts