FW: [CORRESPONDENCE] Tripti Sinha to Alejandra Reynoso - Reminder RE: PICs/RVCs Consultation
Dear all, Please find included a letter from Tripti Sinha regarding the Community Consultation on PICs/RVCs in response to the Council letter dated 30 January 2024. The Council is requested to reconsider by 12 April 2024 its initial response and “provide input to the questions, particularly regarding the consultation topic 2 concerning the ICANN Bylaws. The purpose of this consultation is twofold: 1. To solicit community feedback on a proposed framework for the implementation of these recommended commitments in the New gTLD Program: Next Round. 2. To ensure the Board understands whether the broader ICANN community supports ICANN’s enforcement of contractual terms that could be argued to regulate content in gTLDs and, if so, whether the community also supports an amendment to the ICANN Bylaws to clarify ICANN’s ability to do so.” The Council letter was sent 30 January 2024 and can be found here: https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-... . This letter was a response to the letter from Tripti Sinha dated 7 December 2023 (https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-.... On behalf of Alejandra, Kind regards, Bart
Dear Councillors This is a topic I'm not familiar with and I'd really appreciate the opinion of those who have been following this process more closely. After watching the recording of the plenary session at ICANN79 <https://icann79.sched.com/event/1a1AR/plenary-session-community-consultation...> it seems to me that there is a concern on whether ICANN might be getting involved with content regulation, directly or indirectly, by enforcing contractual terms relating to future gTLD Registry Voluntary Commitments (RVCs) dealing with content; and if this is out of the scope of ICANN's mission <https://www.icann.org/resources/pages/governance/bylaws-en/#article1> according to the Bylaws. My understanding is that these RVCs are proposed by the Registry and not by ICANN, nevertheless, they end up as part of the contract and ICANN's Contractual Compliance <https://www.icann.org/resources/pages/compliance-2012-02-25-en> needs to ensure that ICANN's contracted parties fulfill the requirements set forth in their agreements with ICANN. As stated in the previous letter from Tripti [page #2] <https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-...>: " *The proposed implementation framework would limit ICANN’s direct involvement in restricting content within gTLDs. However, implementation of the content-related commitments recommended by the policy development process working group 4 could still place ICANN in a position of enforcing contract requirements that have the effect of restricting content in gTLDs. This creates a risk of successful challenges asserting that content-related commitments in future Registry Agreements are beyond the scope of ICANN’s Mission. Further, there are political, practical, and reputational risks associated with ICANN negotiating and entering into contract provisions that have the effect of restricting content in gTLDs.*" My first impression regarding what we are being asked to provide feedback is the following: 1. *It seems strange that we [ccNSO] give feedback on a framework that we have not participated in. Isn't it out of our scope?* From previous letter from Tripti [page #9] <https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-...>: "*Please note one key difference between this proposed framework and the approach taken in the 2012 round of the New gTLD Program: This framework would require all applicants who propose to enter into RVCs and/or community gTLD commitments to include a detailed process for enforcement of such commitments in their Registry Agreements. This framework would require the applicant to engage, at the registry operator’s own expense, an independent third party to periodically audit their compliance with any content-related commitments and certify such compliance to ICANN. This third party must be identified when the commitment is proposed for evaluation, and is subject to approval by ICANN during the evaluation process*" 2. Supporting ICANN’s enforcement of contractual terms that could be argued to regulate content in gTLDs. *I'm not sure if we can support or not such a thing (scope), but we certainly express our opinion on ICANN's mission.* 3. Supporting an amendment to the ICANN Bylaws to clarify ICANN’s ability to do what was stated above in 2. *Without the potential text to be used, it's very hard to say if we will support a Fundamental Bylaw change in advance.* Please let me know your thoughts as soon as possible, since we are requested to reconsider by 12 April 2024. Best regards, Alejandra ******************************************* Work like you don't need the money. Love like you've never been hurt. Dance like nobody's watching. Sing like nobody's listening. And live like it's Heaven on Earth. ******************************************* On Fri, Mar 29, 2024 at 1:26 PM Bart Boswinkel via Ccnso-council < ccnso-council@icann.org> wrote:
Dear all,
Please find included a letter from Tripti Sinha regarding the Community Consultation on PICs/RVCs in response to the Council letter dated 30 January 2024. The Council is requested to reconsider by 12 April 2024 its initial response and *“**provide input to the questions, particularly regarding the consultation topic 2 concerning the ICANN Bylaws. *
*The purpose of this consultation is twofold: *
1. *To solicit community feedback on a proposed framework for the implementation of these recommended commitments in the New gTLD Program: Next Round. * 2. *To ensure the Board understands whether the broader ICANN community supports ICANN’s enforcement of contractual terms that could be argued to regulate content in gTLDs and, if so, whether the community also supports an amendment to the ICANN Bylaws to clarify ICANN’s ability to do so.**”*
The Council letter was sent 30 January 2024 and can be found here: https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-... . This letter was a response to the letter from Tripti Sinha dated 7 December 2023 ( https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-... .
On behalf of Alejandra,
Kind regards,
Bart
_______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org https://mm.icann.org/mailman/listinfo/ccnso-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 think that’s exactly right Ale, people think it could be beneficial to have these RVCs, but that this could conflict with the (anti) content regulation requirements in the bye-laws if you take a particularly narrow reading of those sections, which I’m guessing ICANN’s legal dept does. This is obviously gTLD specific, and so arguably we don’t have a horse in this race, but I guess if it comes down to the question of us supporting (or at least not objecting to) a proposed bye-law amendment. Personally it seems like a reasonable and positive initiative which has led to the RVCs policy recommendation, and therefore we’d be amenable? I.e. it’s not the role of the ccNSO to block or veto things which other parts of the community need our support to make happen. Conversely if we had strong ideological objections to content regulation then it’s best we signal that to the board before they put any more work into implementing the policy recommendation, as a bye-law amendment would be hard to get through if the community rose up against it. From: Ccnso-council <ccnso-council-bounces@icann.org> On Behalf Of Alejandra Reynoso Barral via Ccnso-council Sent: Tuesday, April 2, 2024 3:24 PM To: Bart Boswinkel <bart.boswinkel@icann.org> Cc: ccnso-council@icann.org Subject: Re: [ccnso-council] FW: [CORRESPONDENCE] Tripti Sinha to Alejandra Reynoso - Reminder RE: PICs/RVCs Consultation Caution: This is an external email and may be malicious. Please take extra care when clicking links or opening attachments. Dear Councillors This is a topic I'm not familiar with and I'd really appreciate the opinion of those who have been following this process more closely. After watching the recording of the plenary session at ICANN79<https://secure-web.cisco.com/1TBPHRfcP9LWS1Tjjh1gtpDXbdcSZ8NMPHAUP3G9nmhr8Q4...> it seems to me that there is a concern on whether ICANN might be getting involved with content regulation, directly or indirectly, by enforcing contractual terms relating to future gTLD Registry Voluntary Commitments (RVCs) dealing with content; and if this is out of the scope of ICANN's mission<https://www.icann.org/resources/pages/governance/bylaws-en/#article1> according to the Bylaws. My understanding is that these RVCs are proposed by the Registry and not by ICANN, nevertheless, they end up as part of the contract and ICANN's Contractual Compliance<https://www.icann.org/resources/pages/compliance-2012-02-25-en> needs to ensure that ICANN's contracted parties fulfill the requirements set forth in their agreements with ICANN. As stated in the previous letter from Tripti [page #2]<https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-...>: " The proposed implementation framework would limit ICANN’s direct involvement in restricting content within gTLDs. However, implementation of the content-related commitments recommended by the policy development process working group 4 could still place ICANN in a position of enforcing contract requirements that have the effect of restricting content in gTLDs. This creates a risk of successful challenges asserting that content-related commitments in future Registry Agreements are beyond the scope of ICANN’s Mission. Further, there are political, practical, and reputational risks associated with ICANN negotiating and entering into contract provisions that have the effect of restricting content in gTLDs." My first impression regarding what we are being asked to provide feedback is the following: 1. It seems strange that we [ccNSO] give feedback on a framework that we have not participated in. Isn't it out of our scope? From previous letter from Tripti [page #9]<https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-...>: "Please note one key difference between this proposed framework and the approach taken in the 2012 round of the New gTLD Program: This framework would require all applicants who propose to enter into RVCs and/or community gTLD commitments to include a detailed process for enforcement of such commitments in their Registry Agreements. This framework would require the applicant to engage, at the registry operator’s own expense, an independent third party to periodically audit their compliance with any content-related commitments and certify such compliance to ICANN. This third party must be identified when the commitment is proposed for evaluation, and is subject to approval by ICANN during the evaluation process" 2. Supporting ICANN’s enforcement of contractual terms that could be argued to regulate content in gTLDs. I'm not sure if we can support or not such a thing (scope), but we certainly express our opinion on ICANN's mission. 3. Supporting an amendment to the ICANN Bylaws to clarify ICANN’s ability to do what was stated above in 2. Without the potential text to be used, it's very hard to say if we will support a Fundamental Bylaw change in advance. Please let me know your thoughts as soon as possible, since we are requested to reconsider by 12 April 2024. Best regards, Alejandra ******************************************* Work like you don't need the money. Love like you've never been hurt. Dance like nobody's watching. Sing like nobody's listening. And live like it's Heaven on Earth. ******************************************* On Fri, Mar 29, 2024 at 1:26 PM Bart Boswinkel via Ccnso-council <ccnso-council@icann.org<mailto:ccnso-council@icann.org>> wrote: Dear all, Please find included a letter from Tripti Sinha regarding the Community Consultation on PICs/RVCs in response to the Council letter dated 30 January 2024. The Council is requested to reconsider by 12 April 2024 its initial response and “provide input to the questions, particularly regarding the consultation topic 2 concerning the ICANN Bylaws. The purpose of this consultation is twofold: 1. To solicit community feedback on a proposed framework for the implementation of these recommended commitments in the New gTLD Program: Next Round. 2. To ensure the Board understands whether the broader ICANN community supports ICANN’s enforcement of contractual terms that could be argued to regulate content in gTLDs and, if so, whether the community also supports an amendment to the ICANN Bylaws to clarify ICANN’s ability to do so.” The Council letter was sent 30 January 2024 and can be found here: https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-... . This letter was a response to the letter from Tripti Sinha dated 7 December 2023 (https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-.... On behalf of Alejandra, Kind regards, Bart _______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org<mailto:Ccnso-council@icann.org> https://mm.icann.org/mailman/listinfo/ccnso-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.
Hello All, I am very familiar with this (sigh!). We could spend many happy hours thinking about and discussing this. However, it is my view that it would be entirely inappropriate for us to opine on matters related to ICANN’s relationship with gTLDs. We should reply that we still have no comment to make. Happy to discuss further. Cheers, CD Chris Disspain +44 7880 642456 Donuts and Afilias have rebranded to Identity Digital. identity.digital On 2 Apr 2024 at 18:24 +0100, Sean Copeland via Ccnso-council <ccnso-council@icann.org>, wrote:
I agree with the earlier comments.
I’m not familiar with this but I must wonder whose community standard would reign supreme when and if voluntary became compulsory? Could a sovereign latch on to it effectively making it compulsory? For sure.
At the same time I’m all to aware of sites on the Internet that do real harm. I don’t want to discount that at all especially having a front row seat to it.
From anecdotal evidence the problem here, at least in so far as Canadian law enforcement, is they (say they) lack the resources to effectively deal with the matter in a timely matter. Offloading that willingly by ICANN could be a poison pill that is not recoverable. One that would impact us.
We, more than a corporation using an algorithm to drive people to content have the best case to be made as a common carrier.
Domain name resellers while their motivation may be for the right reasons are not the police, and we are not the funding mechanism for such a thing. They can put their safety goals into their mission statements, not into an icann contract.
Me
Sent from my iPhone
On Apr 2, 2024, at 07:24, Alejandra Reynoso Barral via Ccnso-council <ccnso-council@icann.org> wrote:
Dear Councillors
This is a topic I'm not familiar with and I'd really appreciate the opinion of those who have been following this process more closely.
After watching the recording of the plenary session at ICANN79 it seems to me that there is a concern on whether ICANN might be getting involved with content regulation, directly or indirectly, by enforcing contractual terms relating to future gTLD Registry Voluntary Commitments (RVCs) dealing with content; and if this is out of the scope of ICANN's mission according to the Bylaws.
My understanding is that these RVCs are proposed by the Registry and not by ICANN, nevertheless, they end up as part of the contract and ICANN's Contractual Compliance needs to ensure that ICANN's contracted parties fulfill the requirements set forth in their agreements with ICANN.
As stated in the previous letter from Tripti [page #2]: " The proposed implementation framework would limit ICANN’s direct involvement in restricting content within gTLDs. However, implementation of the content-related commitments recommended by the policy development process working group 4 could still place ICANN in a position of enforcing contract requirements that have the effect of restricting content in gTLDs. This creates a risk of successful challenges asserting that content-related commitments in future Registry Agreements are beyond the scope of ICANN’s Mission. Further, there are political, practical, and reputational risks associated with ICANN negotiating and entering into contract provisions that have the effect of restricting content in gTLDs."
My first impression regarding what we are being asked to provide feedback is the following:
1. It seems strange that we [ccNSO] give feedback on a framework that we have not participated in. Isn't it out of our scope? From previous letter from Tripti [page #9]: "Please note one key difference between this proposed framework and the approach taken in the 2012 round of the New gTLD Program: This framework would require all applicants who propose to enter into RVCs and/or community gTLD commitments to include a detailed process for enforcement of such commitments in their Registry Agreements. This framework would require the applicant to engage, at the registry operator’s own expense, an independent third party to periodically audit their compliance with any content-related commitments and certify such compliance to ICANN. This third party must be identified when the commitment is proposed for evaluation, and is subject to approval by ICANN during the evaluation process" 2. Supporting ICANN’s enforcement of contractual terms that could be argued to regulate content in gTLDs. I'm not sure if we can support or not such a thing (scope), but we certainly express our opinion on ICANN's mission. 3. Supporting an amendment to the ICANN Bylaws to clarify ICANN’s ability to do what was stated above in 2. Without the potential text to be used, it's very hard to say if we will support a Fundamental Bylaw change in advance.
Please let me know your thoughts as soon as possible, since we are requested to reconsider by 12 April 2024.
Best regards, Alejandra
******************************************* Work like you don't need the money. Love like you've never been hurt. Dance like nobody's watching. Sing like nobody's listening. And live like it's Heaven on Earth. *******************************************
On Fri, Mar 29, 2024 at 1:26 PM Bart Boswinkel via Ccnso-council <ccnso-council@icann.org> wrote:
Dear all, Please find included a letter from Tripti Sinha regarding the Community Consultation on PICs/RVCs in response to the Council letter dated 30 January 2024. The Council is requested to reconsider by 12 April 2024 its initial response and “provide input to the questions, particularly regarding the consultation topic 2 concerning the ICANN Bylaws. The purpose of this consultation is twofold:
1. To solicit community feedback on a proposed framework for the implementation of these recommended commitments in the New gTLD Program: Next Round. 2. To ensure the Board understands whether the broader ICANN community supports ICANN’s enforcement of contractual terms that could be argued to regulate content in gTLDs and, if so, whether the community also supports an amendment to the ICANN Bylaws to clarify ICANN’s ability to do so.”
The Council letter was sent 30 January 2024 and can be found here: https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-... . This letter was a response to the letter from Tripti Sinha dated 7 December 2023 (https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-.... On behalf of Alejandra, Kind regards, Bart
_______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org https://mm.icann.org/mailman/listinfo/ccnso-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.
Ccnso-council mailing list Ccnso-council@icann.org https://mm.icann.org/mailman/listinfo/ccnso-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.
Ccnso-council mailing list Ccnso-council@icann.org https://mm.icann.org/mailman/listinfo/ccnso-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.
+1 Chris. //Stephen From: Ccnso-council <ccnso-council-bounces@icann.org> on behalf of Chris Disspain via Ccnso-council <ccNSO-council@icann.org> Reply-To: Chris Disspain <chris.disspain@identity.digital> Date: Wednesday, April 3, 2024 at 08:08 To: Alejandra Reynoso Barral <alejandra.reynoso@gmail.com> Cc: "ccNSO-council@icann.org" <ccNSO-council@icann.org> Subject: Re: [ccnso-council] FW: [CORRESPONDENCE] Tripti Sinha to Alejandra Reynoso - Reminder RE: PICs/RVCs Consultation Hello All, I am very familiar with this (sigh!). We could spend many happy hours thinking about and discussing this. However, it is my view that it would be entirely inappropriate for us to opine on matters related to ICANN’s relationship with gTLDs. We should reply that we still have no comment to make. Happy to discuss further. Cheers, CD Chris Disspain +44 7880 642456 [cid:86731993AE474E189DB54EBC4FBAB26D] Donuts and Afilias have rebranded to Identity Digital. identity.digital<http://www.identity.digital> On 2 Apr 2024 at 18:24 +0100, Sean Copeland via Ccnso-council <ccnso-council@icann.org>, wrote: I agree with the earlier comments. I’m not familiar with this but I must wonder whose community standard would reign supreme when and if voluntary became compulsory? Could a sovereign latch on to it effectively making it compulsory? For sure. At the same time I’m all to aware of sites on the Internet that do real harm. I don’t want to discount that at all especially having a front row seat to it. From anecdotal evidence the problem here, at least in so far as Canadian law enforcement, is they (say they) lack the resources to effectively deal with the matter in a timely matter. Offloading that willingly by ICANN could be a poison pill that is not recoverable. One that would impact us. We, more than a corporation using an algorithm to drive people to content have the best case to be made as a common carrier. Domain name resellers while their motivation may be for the right reasons are not the police, and we are not the funding mechanism for such a thing. They can put their safety goals into their mission statements, not into an icann contract. Me Sent from my iPhone On Apr 2, 2024, at 07:24, Alejandra Reynoso Barral via Ccnso-council <ccnso-council@icann.org> wrote: Dear Councillors This is a topic I'm not familiar with and I'd really appreciate the opinion of those who have been following this process more closely. After watching the recording of the plenary session at ICANN79<https://icann79.sched.com/event/1a1AR/plenary-session-community-consultation...> it seems to me that there is a concern on whether ICANN might be getting involved with content regulation, directly or indirectly, by enforcing contractual terms relating to future gTLD Registry Voluntary Commitments (RVCs) dealing with content; and if this is out of the scope of ICANN's mission<https://www.icann.org/resources/pages/governance/bylaws-en/#article1> according to the Bylaws. My understanding is that these RVCs are proposed by the Registry and not by ICANN, nevertheless, they end up as part of the contract and ICANN's Contractual Compliance<https://www.icann.org/resources/pages/compliance-2012-02-25-en> needs to ensure that ICANN's contracted parties fulfill the requirements set forth in their agreements with ICANN. As stated in the previous letter from Tripti [page #2]<https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-...>: " The proposed implementation framework would limit ICANN’s direct involvement in restricting content within gTLDs. However, implementation of the content-related commitments recommended by the policy development process working group 4 could still place ICANN in a position of enforcing contract requirements that have the effect of restricting content in gTLDs. This creates a risk of successful challenges asserting that content-related commitments in future Registry Agreements are beyond the scope of ICANN’s Mission. Further, there are political, practical, and reputational risks associated with ICANN negotiating and entering into contract provisions that have the effect of restricting content in gTLDs." My first impression regarding what we are being asked to provide feedback is the following: 1. It seems strange that we [ccNSO] give feedback on a framework that we have not participated in. Isn't it out of our scope? From previous letter from Tripti [page #9]<https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-...>: "Please note one key difference between this proposed framework and the approach taken in the 2012 round of the New gTLD Program: This framework would require all applicants who propose to enter into RVCs and/or community gTLD commitments to include a detailed process for enforcement of such commitments in their Registry Agreements. This framework would require the applicant to engage, at the registry operator’s own expense, an independent third party to periodically audit their compliance with any content-related commitments and certify such compliance to ICANN. This third party must be identified when the commitment is proposed for evaluation, and is subject to approval by ICANN during the evaluation process" 2. Supporting ICANN’s enforcement of contractual terms that could be argued to regulate content in gTLDs. I'm not sure if we can support or not such a thing (scope), but we certainly express our opinion on ICANN's mission. 3. Supporting an amendment to the ICANN Bylaws to clarify ICANN’s ability to do what was stated above in 2. Without the potential text to be used, it's very hard to say if we will support a Fundamental Bylaw change in advance. Please let me know your thoughts as soon as possible, since we are requested to reconsider by 12 April 2024. Best regards, Alejandra ******************************************* Work like you don't need the money. Love like you've never been hurt. Dance like nobody's watching. Sing like nobody's listening. And live like it's Heaven on Earth. ******************************************* On Fri, Mar 29, 2024 at 1:26 PM Bart Boswinkel via Ccnso-council <ccnso-council@icann.org<mailto:ccnso-council@icann.org>> wrote: Dear all, Please find included a letter from Tripti Sinha regarding the Community Consultation on PICs/RVCs in response to the Council letter dated 30 January 2024. The Council is requested to reconsider by 12 April 2024 its initial response and “provide input to the questions, particularly regarding the consultation topic 2 concerning the ICANN Bylaws. The purpose of this consultation is twofold: 1. To solicit community feedback on a proposed framework for the implementation of these recommended commitments in the New gTLD Program: Next Round. 2. To ensure the Board understands whether the broader ICANN community supports ICANN’s enforcement of contractual terms that could be argued to regulate content in gTLDs and, if so, whether the community also supports an amendment to the ICANN Bylaws to clarify ICANN’s ability to do so.” The Council letter was sent 30 January 2024 and can be found here: https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-... . This letter was a response to the letter from Tripti Sinha dated 7 December 2023 (https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-.... On behalf of Alejandra, Kind regards, Bart _______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org<mailto:Ccnso-council@icann.org> https://mm.icann.org/mailman/listinfo/ccnso-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. _______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org https://mm.icann.org/mailman/listinfo/ccnso-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. _______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org https://mm.icann.org/mailman/listinfo/ccnso-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.
Hi all I tend to agree with Chris "that we still have no comment to make" (and Alejandra original concerns below...) best demi On 03/04/2024 09:07, Chris Disspain via Ccnso-council wrote:
Hello All,
I am very familiar with this (sigh!).
We could spend many happy hours thinking about and discussing this. However, it is my view that it would be entirely inappropriate for us to opine on matters related to ICANN’s relationship with gTLDs. We should reply that we still have no comment to make.
Happy to discuss further.
Cheers,
CD
Chris Disspain
+44 7880 642456
Donuts and Afilias have rebranded to Identity Digital. identity.digital <http://www.identity.digital> On 2 Apr 2024 at 18:24 +0100, Sean Copeland via Ccnso-council <ccnso-council@icann.org>, wrote:
I agree with the earlier comments.
I’m not familiar with this but I must wonder whose community standard would reign supreme when and if voluntary became compulsory? Could a sovereign latch on to it effectively making it compulsory? For sure.
At the same time I’m all to aware of sites on the Internet that do real harm. I don’t want to discount that at all especially having a front row seat to it.
From anecdotal evidence the problem here, at least in so far as Canadian law enforcement, is they (say they) lack the resources to effectively deal with the matter in a timely matter. Offloading that willingly by ICANN could be a poison pill that is not recoverable. One that would impact us.
We, more than a corporation using an algorithm to drive people to content have the best case to be made as a common carrier.
Domain name resellers while their motivation may be for the right reasons are not the police, and we are not the funding mechanism for such a thing. They can put their safety goals into their mission statements, not into an icann contract.
Me
Sent from my iPhone
On Apr 2, 2024, at 07:24, Alejandra Reynoso Barral via Ccnso-council <ccnso-council@icann.org> wrote:
Dear Councillors
This is a topic I'm not familiar with and I'd really appreciate the opinion of those who have been following this process more closely.
After watching the recording of the plenary session at ICANN79 <https://icann79.sched.com/event/1a1AR/plenary-session-community-consultation...> it seems to me that there is a concern on whether ICANN might be getting involved with content regulation, directly or indirectly, by enforcing contractual terms relating to future gTLD Registry Voluntary Commitments (RVCs) dealing with content; and if this is out of the scope of ICANN's mission <https://www.icann.org/resources/pages/governance/bylaws-en/#article1> according to the Bylaws.
My understanding is that these RVCs are proposed by the Registry and not by ICANN, nevertheless, they end up as part of the contract and ICANN's Contractual Compliance <https://www.icann.org/resources/pages/compliance-2012-02-25-en> needs to ensure that ICANN's contracted parties fulfill the requirements set forth in their agreements with ICANN.
As stated in the previous letter from Tripti [page #2] <https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-...>: " /The proposed implementation framework would limit ICANN’s direct involvement in restricting content within gTLDs. However, implementation of the content-related commitments recommended by the policy development process working group 4 could still place ICANN in a position of enforcing contract requirements that have the effect of restricting content in gTLDs. This creates a risk of successful challenges asserting that content-related commitments in future Registry Agreements are beyond the scope of ICANN’s Mission. Further, there are political, practical, and reputational risks associated with ICANN negotiating and entering into contract provisions that have the effect of restricting content in gTLDs./"
My first impression regarding what we are being asked to provide feedback is the following:
1. *It seems strange that we [ccNSO] give feedback on a framework that we have not participated in. Isn't it out of our scope?* From previous letter from Tripti [page #9] <https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-...>: "/Please note one key difference between this proposed framework and the approach taken in the 2012 round of the New gTLD Program: This framework would require all applicants who propose to enter into RVCs and/or community gTLD commitments to include a detailed process for enforcement of such commitments in their Registry Agreements. This framework would require the applicant to engage, at the registry operator’s own expense, an independent third party to periodically audit their compliance with any content-related commitments and certify such compliance to ICANN. This third party must be identified when the commitment is proposed for evaluation, and is subject to approval by ICANN during the evaluation process/" 2. Supporting ICANN’s enforcement of contractual terms that could be argued to regulate content in gTLDs. *I'm not sure if we can support or not such a thing (scope), but we certainly express our opinion on ICANN's mission.* 3. Supporting an amendment to the ICANN Bylaws to clarify ICANN’s ability to do what was stated above in 2. *Without the potential text to be used, it's very hard to say if we will support a Fundamental Bylaw change in advance.*
Please let me know your thoughts as soon as possible, since we are requested to reconsider by 12 April 2024.
Best regards, Alejandra
******************************************* Work like you don't need the money. Love like you've never been hurt. Dance like nobody's watching. Sing like nobody's listening. And live like it's Heaven on Earth. *******************************************
On Fri, Mar 29, 2024 at 1:26 PM Bart Boswinkel via Ccnso-council <ccnso-council@icann.org> wrote:
Dear all,
Please find included a letter from Tripti Sinha regarding the Community Consultation on PICs/RVCs in response to the Council letter dated 30 January 2024. The Council is requested to reconsider by 12 April 2024 its initial response and /“//provide input to the questions, particularly regarding the consultation topic 2 concerning the ICANN Bylaws./
/The purpose of this consultation is twofold:/
1. /To solicit community feedback on a proposed framework for the implementation of these recommended commitments in the New gTLD Program: Next Round./ 2. /To ensure the Board understands whether the broader ICANN community supports ICANN’s enforcement of contractual terms that could be argued to regulate content in gTLDs and, if so, whether the community also supports an amendment to the ICANN Bylaws to clarify ICANN’s ability to do so.//”/////
The Council letter was sent 30 January 2024 and can be found here: https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-... . This letter was a response to the letter from Tripti Sinha dated 7 December 2023 (https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-....
On behalf of Alejandra,
Kind regards,
Bart
_______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org https://mm.icann.org/mailman/listinfo/ccnso-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.
_______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org https://mm.icann.org/mailman/listinfo/ccnso-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.
Ccnso-council mailing list Ccnso-council@icann.org https://mm.icann.org/mailman/listinfo/ccnso-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.
_______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org https://mm.icann.org/mailman/listinfo/ccnso-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.
+1 Chris On Wed, Apr 3, 2024 at 8:08 AM Chris Disspain via Ccnso-council < ccnso-council@icann.org> wrote:
Hello All,
I am very familiar with this (sigh!).
We could spend many happy hours thinking about and discussing this. However, it is my view that it would be entirely inappropriate for us to opine on matters related to ICANN’s relationship with gTLDs. We should reply that we still have no comment to make.
Happy to discuss further.
Cheers,
CD
Chris Disspain
+44 7880 642456
Donuts and Afilias have rebranded to Identity Digital. identity.digital <http://www.identity.digital> On 2 Apr 2024 at 18:24 +0100, Sean Copeland via Ccnso-council < ccnso-council@icann.org>, wrote:
I agree with the earlier comments.
I’m not familiar with this but I must wonder whose community standard would reign supreme when and if voluntary became compulsory? Could a sovereign latch on to it effectively making it compulsory? For sure.
At the same time I’m all to aware of sites on the Internet that do real harm. I don’t want to discount that at all especially having a front row seat to it.
From anecdotal evidence the problem here, at least in so far as Canadian law enforcement, is they (say they) lack the resources to effectively deal with the matter in a timely matter. Offloading that willingly by ICANN could be a poison pill that is not recoverable. One that would impact us.
We, more than a corporation using an algorithm to drive people to content have the best case to be made as a common carrier.
Domain name resellers while their motivation may be for the right reasons are not the police, and we are not the funding mechanism for such a thing. They can put their safety goals into their mission statements, not into an icann contract.
Me
Sent from my iPhone
On Apr 2, 2024, at 07:24, Alejandra Reynoso Barral via Ccnso-council < ccnso-council@icann.org> wrote:
Dear Councillors
This is a topic I'm not familiar with and I'd really appreciate the opinion of those who have been following this process more closely.
After watching the recording of the plenary session at ICANN79 <https://icann79.sched.com/event/1a1AR/plenary-session-community-consultation...> it seems to me that there is a concern on whether ICANN might be getting involved with content regulation, directly or indirectly, by enforcing contractual terms relating to future gTLD Registry Voluntary Commitments (RVCs) dealing with content; and if this is out of the scope of ICANN's mission <https://www.icann.org/resources/pages/governance/bylaws-en/#article1> according to the Bylaws.
My understanding is that these RVCs are proposed by the Registry and not by ICANN, nevertheless, they end up as part of the contract and ICANN's Contractual Compliance <https://www.icann.org/resources/pages/compliance-2012-02-25-en> needs to ensure that ICANN's contracted parties fulfill the requirements set forth in their agreements with ICANN.
As stated in the previous letter from Tripti [page #2] <https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-...>: " *The proposed implementation framework would limit ICANN’s direct involvement in restricting content within gTLDs. However, implementation of the content-related commitments recommended by the policy development process working group 4 could still place ICANN in a position of enforcing contract requirements that have the effect of restricting content in gTLDs. This creates a risk of successful challenges asserting that content-related commitments in future Registry Agreements are beyond the scope of ICANN’s Mission. Further, there are political, practical, and reputational risks associated with ICANN negotiating and entering into contract provisions that have the effect of restricting content in gTLDs.*"
My first impression regarding what we are being asked to provide feedback is the following:
1. *It seems strange that we [ccNSO] give feedback on a framework that we have not participated in. Isn't it out of our scope?* From previous letter from Tripti [page #9] <https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-...>: "*Please note one key difference between this proposed framework and the approach taken in the 2012 round of the New gTLD Program: This framework would require all applicants who propose to enter into RVCs and/or community gTLD commitments to include a detailed process for enforcement of such commitments in their Registry Agreements. This framework would require the applicant to engage, at the registry operator’s own expense, an independent third party to periodically audit their compliance with any content-related commitments and certify such compliance to ICANN. This third party must be identified when the commitment is proposed for evaluation, and is subject to approval by ICANN during the evaluation process*" 2. Supporting ICANN’s enforcement of contractual terms that could be argued to regulate content in gTLDs. *I'm not sure if we can support or not such a thing (scope), but we certainly express our opinion on ICANN's mission.* 3. Supporting an amendment to the ICANN Bylaws to clarify ICANN’s ability to do what was stated above in 2. *Without the potential text to be used, it's very hard to say if we will support a Fundamental Bylaw change in advance.*
Please let me know your thoughts as soon as possible, since we are requested to reconsider by 12 April 2024.
Best regards, Alejandra
******************************************* Work like you don't need the money. Love like you've never been hurt. Dance like nobody's watching. Sing like nobody's listening. And live like it's Heaven on Earth. *******************************************
On Fri, Mar 29, 2024 at 1:26 PM Bart Boswinkel via Ccnso-council < ccnso-council@icann.org> wrote:
Dear all,
Please find included a letter from Tripti Sinha regarding the Community Consultation on PICs/RVCs in response to the Council letter dated 30 January 2024. The Council is requested to reconsider by 12 April 2024 its initial response and *“**provide input to the questions, particularly regarding the consultation topic 2 concerning the ICANN Bylaws. *
*The purpose of this consultation is twofold: *
1. *To solicit community feedback on a proposed framework for the implementation of these recommended commitments in the New gTLD Program: Next Round. * 2. *To ensure the Board understands whether the broader ICANN community supports ICANN’s enforcement of contractual terms that could be argued to regulate content in gTLDs and, if so, whether the community also supports an amendment to the ICANN Bylaws to clarify ICANN’s ability to do so.**”*
The Council letter was sent 30 January 2024 and can be found here: https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-... . This letter was a response to the letter from Tripti Sinha dated 7 December 2023 ( https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-... .
On behalf of Alejandra,
Kind regards,
Bart
_______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org https://mm.icann.org/mailman/listinfo/ccnso-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.
_______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org https://mm.icann.org/mailman/listinfo/ccnso-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.
_______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org https://mm.icann.org/mailman/listinfo/ccnso-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.
_______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org https://mm.icann.org/mailman/listinfo/ccnso-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.
Indeed Still no comments to make Best Wafa Le mer. 3 avr. 2024, 16:20, Pablo Rodriguez via Ccnso-council < ccnso-council@icann.org> a écrit :
+1 Chris
On Wed, Apr 3, 2024 at 8:08 AM Chris Disspain via Ccnso-council < ccnso-council@icann.org> wrote:
Hello All,
I am very familiar with this (sigh!).
We could spend many happy hours thinking about and discussing this. However, it is my view that it would be entirely inappropriate for us to opine on matters related to ICANN’s relationship with gTLDs. We should reply that we still have no comment to make.
Happy to discuss further.
Cheers,
CD
Chris Disspain
+44 7880 642456
Donuts and Afilias have rebranded to Identity Digital. identity.digital <http://www.identity.digital> On 2 Apr 2024 at 18:24 +0100, Sean Copeland via Ccnso-council < ccnso-council@icann.org>, wrote:
I agree with the earlier comments.
I’m not familiar with this but I must wonder whose community standard would reign supreme when and if voluntary became compulsory? Could a sovereign latch on to it effectively making it compulsory? For sure.
At the same time I’m all to aware of sites on the Internet that do real harm. I don’t want to discount that at all especially having a front row seat to it.
From anecdotal evidence the problem here, at least in so far as Canadian law enforcement, is they (say they) lack the resources to effectively deal with the matter in a timely matter. Offloading that willingly by ICANN could be a poison pill that is not recoverable. One that would impact us.
We, more than a corporation using an algorithm to drive people to content have the best case to be made as a common carrier.
Domain name resellers while their motivation may be for the right reasons are not the police, and we are not the funding mechanism for such a thing. They can put their safety goals into their mission statements, not into an icann contract.
Me
Sent from my iPhone
On Apr 2, 2024, at 07:24, Alejandra Reynoso Barral via Ccnso-council < ccnso-council@icann.org> wrote:
Dear Councillors
This is a topic I'm not familiar with and I'd really appreciate the opinion of those who have been following this process more closely.
After watching the recording of the plenary session at ICANN79 <https://icann79.sched.com/event/1a1AR/plenary-session-community-consultation...> it seems to me that there is a concern on whether ICANN might be getting involved with content regulation, directly or indirectly, by enforcing contractual terms relating to future gTLD Registry Voluntary Commitments (RVCs) dealing with content; and if this is out of the scope of ICANN's mission <https://www.icann.org/resources/pages/governance/bylaws-en/#article1> according to the Bylaws.
My understanding is that these RVCs are proposed by the Registry and not by ICANN, nevertheless, they end up as part of the contract and ICANN's Contractual Compliance <https://www.icann.org/resources/pages/compliance-2012-02-25-en> needs to ensure that ICANN's contracted parties fulfill the requirements set forth in their agreements with ICANN.
As stated in the previous letter from Tripti [page #2] <https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-...>: " *The proposed implementation framework would limit ICANN’s direct involvement in restricting content within gTLDs. However, implementation of the content-related commitments recommended by the policy development process working group 4 could still place ICANN in a position of enforcing contract requirements that have the effect of restricting content in gTLDs. This creates a risk of successful challenges asserting that content-related commitments in future Registry Agreements are beyond the scope of ICANN’s Mission. Further, there are political, practical, and reputational risks associated with ICANN negotiating and entering into contract provisions that have the effect of restricting content in gTLDs.*"
My first impression regarding what we are being asked to provide feedback is the following:
1. *It seems strange that we [ccNSO] give feedback on a framework that we have not participated in. Isn't it out of our scope?* From previous letter from Tripti [page #9] <https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-...>: "*Please note one key difference between this proposed framework and the approach taken in the 2012 round of the New gTLD Program: This framework would require all applicants who propose to enter into RVCs and/or community gTLD commitments to include a detailed process for enforcement of such commitments in their Registry Agreements. This framework would require the applicant to engage, at the registry operator’s own expense, an independent third party to periodically audit their compliance with any content-related commitments and certify such compliance to ICANN. This third party must be identified when the commitment is proposed for evaluation, and is subject to approval by ICANN during the evaluation process*" 2. Supporting ICANN’s enforcement of contractual terms that could be argued to regulate content in gTLDs. *I'm not sure if we can support or not such a thing (scope), but we certainly express our opinion on ICANN's mission.* 3. Supporting an amendment to the ICANN Bylaws to clarify ICANN’s ability to do what was stated above in 2. *Without the potential text to be used, it's very hard to say if we will support a Fundamental Bylaw change in advance.*
Please let me know your thoughts as soon as possible, since we are requested to reconsider by 12 April 2024.
Best regards, Alejandra
******************************************* Work like you don't need the money. Love like you've never been hurt. Dance like nobody's watching. Sing like nobody's listening. And live like it's Heaven on Earth. *******************************************
On Fri, Mar 29, 2024 at 1:26 PM Bart Boswinkel via Ccnso-council < ccnso-council@icann.org> wrote:
Dear all,
Please find included a letter from Tripti Sinha regarding the Community Consultation on PICs/RVCs in response to the Council letter dated 30 January 2024. The Council is requested to reconsider by 12 April 2024 its initial response and *“**provide input to the questions, particularly regarding the consultation topic 2 concerning the ICANN Bylaws. *
*The purpose of this consultation is twofold: *
1. *To solicit community feedback on a proposed framework for the implementation of these recommended commitments in the New gTLD Program: Next Round. * 2. *To ensure the Board understands whether the broader ICANN community supports ICANN’s enforcement of contractual terms that could be argued to regulate content in gTLDs and, if so, whether the community also supports an amendment to the ICANN Bylaws to clarify ICANN’s ability to do so.**”*
The Council letter was sent 30 January 2024 and can be found here: https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-... . This letter was a response to the letter from Tripti Sinha dated 7 December 2023 ( https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-... .
On behalf of Alejandra,
Kind regards,
Bart
_______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org https://mm.icann.org/mailman/listinfo/ccnso-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.
_______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org https://mm.icann.org/mailman/listinfo/ccnso-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.
_______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org https://mm.icann.org/mailman/listinfo/ccnso-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.
_______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org https://mm.icann.org/mailman/listinfo/ccnso-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.
_______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org https://mm.icann.org/mailman/listinfo/ccnso-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.
Hello all, As Chris has said before, I think this time we should stay out and respond that we have no comment to make, because this only reflects issues related to ICANN's relationship with gTLDs and not something involving ccTLDs. Best, Lcda. Jenifer López de Gómez | Administradora | NIC-Panamá | DITIC | Universidad Tecnológica de Panamá jenifer.lopez@utp.ac.pa | Tel. +(507) 560-3400 [cid:9179ba58-cf1c-46d3-9284-c90a1e4fddfd] [cid:19286749-1b1c-4aa8-8bf2-69ad67d32d26] [cid:24e0ed0b-6102-4a67-a5d2-c1e27ba5e24e] ________________________________ De: Ccnso-council <ccnso-council-bounces@icann.org> en nombre de wafa Dahmani via Ccnso-council <ccnso-council@icann.org> Enviado: miércoles, 3 de abril de 2024 4:26 p. m. Para: Pablo Rodriguez <pablo@nic.pr> Cc: ccNSO-Council@icann.org <ccNSO-council@icann.org> Asunto: Re: [ccnso-council] FW: [CORRESPONDENCE] Tripti Sinha to Alejandra Reynoso - Reminder RE: PICs/RVCs Consultation Indeed Still no comments to make Best Wafa Le mer. 3 avr. 2024, 16:20, Pablo Rodriguez via Ccnso-council <ccnso-council@icann.org<mailto:ccnso-council@icann.org>> a écrit : +1 Chris [https://ci3.googleusercontent.com/mail-sig/AIorK4zDLhyxAs-0iV9eN8tKtSDUnST8K...] On Wed, Apr 3, 2024 at 8:08 AM Chris Disspain via Ccnso-council <ccnso-council@icann.org<mailto:ccnso-council@icann.org>> wrote: Hello All, I am very familiar with this (sigh!). We could spend many happy hours thinking about and discussing this. However, it is my view that it would be entirely inappropriate for us to opine on matters related to ICANN’s relationship with gTLDs. We should reply that we still have no comment to make. Happy to discuss further. Cheers, CD Chris Disspain +44 7880 642456 [cid:ii_18ea48bcff950b10f9a1] Donuts and Afilias have rebranded to Identity Digital. identity.digital<http://www.identity.digital> On 2 Apr 2024 at 18:24 +0100, Sean Copeland via Ccnso-council <ccnso-council@icann.org<mailto:ccnso-council@icann.org>>, wrote: I agree with the earlier comments. I’m not familiar with this but I must wonder whose community standard would reign supreme when and if voluntary became compulsory? Could a sovereign latch on to it effectively making it compulsory? For sure. At the same time I’m all to aware of sites on the Internet that do real harm. I don’t want to discount that at all especially having a front row seat to it. From anecdotal evidence the problem here, at least in so far as Canadian law enforcement, is they (say they) lack the resources to effectively deal with the matter in a timely matter. Offloading that willingly by ICANN could be a poison pill that is not recoverable. One that would impact us. We, more than a corporation using an algorithm to drive people to content have the best case to be made as a common carrier. Domain name resellers while their motivation may be for the right reasons are not the police, and we are not the funding mechanism for such a thing. They can put their safety goals into their mission statements, not into an icann contract. Me Sent from my iPhone On Apr 2, 2024, at 07:24, Alejandra Reynoso Barral via Ccnso-council <ccnso-council@icann.org<mailto:ccnso-council@icann.org>> wrote: Dear Councillors This is a topic I'm not familiar with and I'd really appreciate the opinion of those who have been following this process more closely. After watching the recording of the plenary session at ICANN79<https://icann79.sched.com/event/1a1AR/plenary-session-community-consultation...> it seems to me that there is a concern on whether ICANN might be getting involved with content regulation, directly or indirectly, by enforcing contractual terms relating to future gTLD Registry Voluntary Commitments (RVCs) dealing with content; and if this is out of the scope of ICANN's mission<https://www.icann.org/resources/pages/governance/bylaws-en/#article1> according to the Bylaws. My understanding is that these RVCs are proposed by the Registry and not by ICANN, nevertheless, they end up as part of the contract and ICANN's Contractual Compliance<https://www.icann.org/resources/pages/compliance-2012-02-25-en> needs to ensure that ICANN's contracted parties fulfill the requirements set forth in their agreements with ICANN. As stated in the previous letter from Tripti [page #2]<https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-...>: " The proposed implementation framework would limit ICANN’s direct involvement in restricting content within gTLDs. However, implementation of the content-related commitments recommended by the policy development process working group 4 could still place ICANN in a position of enforcing contract requirements that have the effect of restricting content in gTLDs. This creates a risk of successful challenges asserting that content-related commitments in future Registry Agreements are beyond the scope of ICANN’s Mission. Further, there are political, practical, and reputational risks associated with ICANN negotiating and entering into contract provisions that have the effect of restricting content in gTLDs." My first impression regarding what we are being asked to provide feedback is the following: 1. It seems strange that we [ccNSO] give feedback on a framework that we have not participated in. Isn't it out of our scope? From previous letter from Tripti [page #9]<https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-...>: "Please note one key difference between this proposed framework and the approach taken in the 2012 round of the New gTLD Program: This framework would require all applicants who propose to enter into RVCs and/or community gTLD commitments to include a detailed process for enforcement of such commitments in their Registry Agreements. This framework would require the applicant to engage, at the registry operator’s own expense, an independent third party to periodically audit their compliance with any content-related commitments and certify such compliance to ICANN. This third party must be identified when the commitment is proposed for evaluation, and is subject to approval by ICANN during the evaluation process" 2. Supporting ICANN’s enforcement of contractual terms that could be argued to regulate content in gTLDs. I'm not sure if we can support or not such a thing (scope), but we certainly express our opinion on ICANN's mission. 3. Supporting an amendment to the ICANN Bylaws to clarify ICANN’s ability to do what was stated above in 2. Without the potential text to be used, it's very hard to say if we will support a Fundamental Bylaw change in advance. Please let me know your thoughts as soon as possible, since we are requested to reconsider by 12 April 2024. Best regards, Alejandra ******************************************* Work like you don't need the money. Love like you've never been hurt. Dance like nobody's watching. Sing like nobody's listening. And live like it's Heaven on Earth. ******************************************* On Fri, Mar 29, 2024 at 1:26 PM Bart Boswinkel via Ccnso-council <ccnso-council@icann.org<mailto:ccnso-council@icann.org>> wrote: Dear all, Please find included a letter from Tripti Sinha regarding the Community Consultation on PICs/RVCs in response to the Council letter dated 30 January 2024. The Council is requested to reconsider by 12 April 2024 its initial response and “provide input to the questions, particularly regarding the consultation topic 2 concerning the ICANN Bylaws. The purpose of this consultation is twofold: 1. To solicit community feedback on a proposed framework for the implementation of these recommended commitments in the New gTLD Program: Next Round. 2. To ensure the Board understands whether the broader ICANN community supports ICANN’s enforcement of contractual terms that could be argued to regulate content in gTLDs and, if so, whether the community also supports an amendment to the ICANN Bylaws to clarify ICANN’s ability to do so.” The Council letter was sent 30 January 2024 and can be found here: https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-... . This letter was a response to the letter from Tripti Sinha dated 7 December 2023 (https://ccnso.icann.org/sites/default/files/field-attached/sinha-to-reynoso-.... On behalf of Alejandra, Kind regards, Bart _______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org<mailto:Ccnso-council@icann.org> https://mm.icann.org/mailman/listinfo/ccnso-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. _______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org<mailto:Ccnso-council@icann.org> https://mm.icann.org/mailman/listinfo/ccnso-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. _______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org<mailto:Ccnso-council@icann.org> https://mm.icann.org/mailman/listinfo/ccnso-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. _______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org<mailto:Ccnso-council@icann.org> https://mm.icann.org/mailman/listinfo/ccnso-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. _______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org<mailto:Ccnso-council@icann.org> https://mm.icann.org/mailman/listinfo/ccnso-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. ***************Este mensaje (y sus adjuntos), en adelante "mensaje", ha sido enviado exclusivamente a su(s) destinatario(s) y es confidencial. Si usted recibe este mensaje por error, por favor bórrelo y comunique inmediatamente al remitente. Toda utilización o publicación, total o parcial, queda prohibida salvo autorización expresa. La UTP no podrá ser considerada responsable si el mensaje ha sido modificado y/o utilizado sin autorización. This message (and any attachments), are confidential intended solely for the people whose addresses appear. If you have received this message by error, please delete it and immediately notify the sender. Any use, dissemination or disclosure, either whole or partial, without formal approval is prohibited. The UTP will not therefore be liable for the message if modified and/or used without approval.************** ***************Este mensaje (y sus adjuntos), en adelante "mensaje", ha sido enviado exclusivamente a su(s) destinatario(s) y es confidencial. Si usted recibe este mensaje por error, por favor bórrelo y comunique inmediatamente al remitente. Toda utilización o publicación, total o parcial, queda prohibida salvo autorización expresa. La UTP no podrá ser considerada responsable si el mensaje ha sido modificado y/o utilizado sin autorización. This message (and any attachments), are confidential intended solely for the people whose addresses appear. If you have received this message by error, please delete it and immediately notify the sender. Any use, dissemination or disclosure, either whole or partial, without formal approval is prohibited. The UTP will not therefore be liable for the message if modified and/or used without approval.**************
Dear Councillors
1. *It seems strange that we [ccNSO] give feedback on a framework that we have not participated in. Isn't it out of our scope?* From previous letter from Tripti [page #9]
accepting (and agreeing with) the principle of non-interference, not responding to this part makes sense to me.
2. Supporting ICANN's enforcement of contractual terms that could be argued to regulate content in gTLDs. *I'm not sure if we can support or not such a thing (scope), but we certainly express our opinion on ICANN's mission.* 3. Supporting an amendment to the ICANN Bylaws to clarify ICANN's ability to do what was stated above in 2. *Without the potential text to be used, it's very hard to say if we will support a Fundamental Bylaw change in advance.*
The aforementioned principle does not apply here and given the risk of a spillover effect, why would we not want to send a message for (I'd prefer 'dogmatic' over 'ideological') reasons? Essence of that message being that we would expect significant confusion among ccTLDs regarding such a move, so beyond the caveats raised by Alejandra, we would not be able to predict a positive result. Best regards Peter
Dear All Here you'll find the draft letter to send to Tripti on this matter https://docs.google.com/document/d/1Yhf3ro61Y0vgd1rSkG66kzF-Ig4WSC_dJTFajSSQ... Please add your comments and suggestions no later than Thursday 11.April, so it can be sent on the 12 April. Best regards, Alejandra ******************************************* Work like you don't need the money. Love like you've never been hurt. Dance like nobody's watching. Sing like nobody's listening. And live like it's Heaven on Earth. ******************************************* On Thu, Apr 4, 2024 at 5:19 PM Peter Koch <pk@denic.de> wrote:
Dear Councillors
1. *It seems strange that we [ccNSO] give feedback on a framework that we have not participated in. Isn't it out of our scope?* From previous letter from Tripti [page #9]
accepting (and agreeing with) the principle of non-interference, not responding to this part makes sense to me.
2. Supporting ICANN's enforcement of contractual terms that could be argued to regulate content in gTLDs. *I'm not sure if we can support or not such a thing (scope), but we certainly express our opinion on ICANN's mission.* 3. Supporting an amendment to the ICANN Bylaws to clarify ICANN's ability to do what was stated above in 2. *Without the potential text to be used, it's very hard to say if we will support a Fundamental Bylaw change in advance.*
The aforementioned principle does not apply here and given the risk of a spillover effect, why would we not want to send a message for (I'd prefer 'dogmatic' over 'ideological') reasons? Essence of that message being that we would expect significant confusion among ccTLDs regarding such a move, so beyond the caveats raised by Alejandra, we would not be able to predict a positive result.
Best regards Peter
Greetings Alejandra, I fiddled with the text a bit. Given my historic “hate-hate” relationship with Google Docs, I cannot guarantee they “took” 😉 Best regards, //Stephen From: Ccnso-council <ccnso-council-bounces@icann.org> on behalf of Alejandra Reynoso Barral via Ccnso-council <ccnso-council@icann.org> Reply-To: Alejandra Reynoso Barral <alejandra.reynoso@gmail.com> Date: Monday, April 8, 2024 at 07:12 To: Peter Koch <pk@denic.de> Cc: "ccnso-council@icann.org" <ccnso-council@icann.org> Subject: Re: [ccnso-council] FW: [CORRESPONDENCE] Tripti Sinha to Alejandra Reynoso - Reminder RE: PICs/RVCs Consultation Dear All Here you'll find the draft letter to send to Tripti on this matter https://docs.google.com/document/d/1Yhf3ro61Y0vgd1rSkG66kzF-Ig4WSC_dJTFajSSQ... Please add your comments and suggestions no later than Thursday 11.April, so it can be sent on the 12 April. Best regards, Alejandra ******************************************* Work like you don't need the money. Love like you've never been hurt. Dance like nobody's watching. Sing like nobody's listening. And live like it's Heaven on Earth. ******************************************* On Thu, Apr 4, 2024 at 5:19 PM Peter Koch <pk@denic.de<mailto:pk@denic.de>> wrote: Dear Councillors
1. *It seems strange that we [ccNSO] give feedback on a framework that we have not participated in. Isn't it out of our scope?* From previous letter from Tripti [page #9]
accepting (and agreeing with) the principle of non-interference, not responding to this part makes sense to me.
2. Supporting ICANN's enforcement of contractual terms that could be argued to regulate content in gTLDs. *I'm not sure if we can support or not such a thing (scope), but we certainly express our opinion on ICANN's mission.* 3. Supporting an amendment to the ICANN Bylaws to clarify ICANN's ability to do what was stated above in 2. *Without the potential text to be used, it's very hard to say if we will support a Fundamental Bylaw change in advance.*
The aforementioned principle does not apply here and given the risk of a spillover effect, why would we not want to send a message for (I'd prefer 'dogmatic' over 'ideological') reasons? Essence of that message being that we would expect significant confusion among ccTLDs regarding such a move, so beyond the caveats raised by Alejandra, we would not be able to predict a positive result. Best regards Peter
participants (11)
-
Alejandra Reynoso Barral -
Bart Boswinkel -
Chris Disspain -
Demi Getschko -
Jenifer Lopez -
Nick Wenban-Smith -
Pablo Rodriguez -
Peter Koch -
Sean Copeland -
Stephen Deerhake ＠ ASNIC -
wafa Dahmani