- CPWG - lists.icann.org

Re: [CPWG] REMINDER / Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 24 April 2024 at 17:30 UTC
by Tijani April 25, 2024

April 25, 2024

Good morning I missed this call as well as the othr call that conflited with this one because of a health issue Not sure I will participate in the upcoming calls I apologize tijani De : CPWG <cpwg-bounces(a)icann.org> au nom de ICANN At-Large Staff via CPWG <cpwg(a)icann.org> Répondre à : ICANN At-Large Staff <staff(a)atlarge.icann.org> Date : mercredi 24 avril 2024 à 11:02 À : CPWG <cpwg(a)icann.org>, na-discuss <na-discuss(a)atlarge-lists.icann.org>, "euro-discuss(a)atlarge-lists.icann.org" <euro-discuss(a)atlarge-lists.icann.org>, APAC-Discuss <apac-discuss(a)atlarge-lists.icann.org>, AFRI-Discuss <afri-discuss(a)atlarge-lists.icann.org>, lac-discuss-en <lac-discuss-en(a)atlarge-lists.icann.org> Objet : [CPWG] REMINDER / Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 24 April 2024 at 17:30 UTC **If you require a dial out or need to state an apology, please contact At-Large staff at staff(a)atlarge.icann.org with your preferred number*** Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 24 April 2024 at 17:30 UTC for 90 mins, For other times: https://tinyurl.com/ebuk8a57 The agenda and call details can be found at: https://community.icann.org/x/dQJyEw Zoom Room: https://icann.zoom.us/j/765717566?pwd=UTJCdWRSZVdJNEhOYW02OVBqQVQ1Zz09 / Passcode: #CPWG2345* Real time transcription (RTT) available at (subject to availability): https://www.streamtext.net/player?event=ICANN ADIGO Conference Bridge: (subject to availability) EN, ES & FR: 3535 Toll-free access number (US and Canada): 800 550 6865 Other toll-free numbers: https://www.adigo.com/icann At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org Thank you. Kind Regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org Facebook: facebook.com/icannatlarge Twitter: @ICANNAtLarge _______________________________________________ CPWG mailing list CPWG(a)icann.org https://mm.icann.org/mailman/listinfo/cpwg _______________________________________________ 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 0

REMINDER / Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 24 April 2024 at 17:30 UTC
by ICANN At-Large Staff April 24, 2024

April 24, 2024

**If you require a dial out or need to state an apology, please contact At-Large staff at staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> with your preferred number*** Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 24 April 2024 at 17:30 UTC for 90 mins, For other times: https://tinyurl.com/ebuk8a57 The agenda and call details can be found at: https://community.icann.org/x/dQJyEw Zoom Room: https://icann.zoom.us/j/765717566?pwd=UTJCdWRSZVdJNEhOYW02OVBqQVQ1Zz09 / Passcode: #CPWG2345* Real time transcription (RTT) available at (subject to availability): https://www.streamtext.net/player?event=ICANN ADIGO Conference Bridge: (subject to availability) EN, ES & FR: 3535 Toll-free access number (US and Canada): 800 550 6865 Other toll-free numbers: https://www.adigo.com/icann At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Kind Regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

2 1

Additional Alternative Statement on .XXX Registry Renewal
by Andrew Chen April 24, 2024

April 24, 2024

Dear CPWG members, Please see linked below a proposed draft on the Proposed Renewal of the Registry Agreement for the .XXX top-level domain (TLD) public comment statement recently submitted by Jonathan Zuck. This draft, along with additional draft statements, will be discussed during the upcoming CPWG meeting. Draft Proposed Compromise: https://docs.google.com/document/d/1NBrt_yXez2ExkQmfKisJs5flFe_it6-JTm-WOoq… Sincerely, Andrew -- Andrew Chen Policy Development Support Sr. Specialist, Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org/ Skype: atchen122

1 0

Alternative Statement on .XXX Registry Renewal
by Evan Leibovitch April 23, 2024

April 23, 2024

As we get closer to the submission deadline, Carlton and I have reviewed the draft of the proposed ALAC response to the .XXX agreement renewal. In response to the .XXX registry wishing to simplify its contract obligations and bring them inline with those of other gTLDs, ALAC's comment counter-proposes five *new* requirements, including a third-party auditor for provisions not demanded of others. It is outrageous and unabashedly punitive in nature. I consider both the results and rationale of the draft ALAC comment to be as far from a true end-user perspective as could possibly be. So irreconcilable are our own views with it that we have crafted our own response for submission rather than try to word-tune the existing one. As a courtesy and to inform the next GPWG meeting, a draft of our response is available here <https://docs.google.com/document/d/1oDRSATHcjC-hDW9KrOheBLo497Y63DuZtHM4n0O…>. We welcome comments and co-signatories. -- Evan Leibovitch, Toronto Canada @evanleibovitch / @el56

1 0

On adult websites, inertia, and basic fairness
by Evan Leibovitch April 22, 2024

April 22, 2024

Hi all, On Wednesday, among other topics was a presentation suggesting the position that ALAC should take regarding renewal of the contract for the .XXX TLD. The presentation offered was a dissection of the substance of changes proposed by the ICM registry for its new contract. Responses to the assertion that the CPWG was engaging in mission-creep were, IMO, confused and disturbing. Some of the counter-arguments made were that the registry was reneging on previous commitments and that it was somehow breaking the rules. Now, if during the run of its contract to date the registry did not keep true to its commitments, that is a serious issue and, as Carlton said in the call, as much a matter for ICANN compliance as for the registry. But that's not what was presented. What I saw was the registry taking the opportunity of the contract renewal to request a change in its terms and it is totally legitimate of them to do so. This renegotiation, on its face, is not an abuse of process, but exactly how the process is supposed to work. If the concern is that ICM has proposed contract changes, especially to remove safeguards, then let's examine those requests on their merits, and *strictly* through the lens of end-user impact. Specifically, I find the notion that provisions in the previous contract that are the subject of change request should be rejected primarily because they existed in the previous contract is ... ill-considered. "Because we've always done things that way" is broadly considered to be a dangerous <https://www.forbes.com/sites/forbeslacouncil/2019/01/28/the-most-dangerous-…> and regressive basis for decision-making. If there is a change request that specifically impacts end-users, absolutely bring it forward. I found little of that, mainly because there was such a broad scattering of out-of-scope complaints that legitimate ones were surely buried. Complaining that the registry wants to enable the use of the TLD by registrants that are not part of the adult industry, for instance, does not serve the interest of end-users. That is a choice for would-be registrants to make. The approach taken demonstrates quite well the mission-creep pervasive within ALAC and this committee. Such overreach reflects poorly on us and diminishes the likelihood that our advice will be heeded. Legitimate concerns risk being rejected alongside the extraneous ones. Recall that this is a particular case of a TLD application made under very charged and political circumstances. I was at the 2011 San Francisco meeting where it was up for delegation and saw the street protests up-close. And while ICANN likes to say that it doesn't regulate^H^H^H^H^H^H^H^Hcontract based on content, any controversy about .XXX at the time concerned nothing EXCEPT content. As a result I'm not surprised if the registry had to make extraordinary promises that have proven to be unsustainable in the dozen years that have passed. And now we have the benefit of hindsight. As it turns out, .XXX did not become the porn ghetto whose mass-blockage could keep the Internet clean by decree. A survey of the industry today reveals that NONE, not one, of the top 20 adult Internet destinations worldwide use .XXX. As a consequence, the singling out of .XXX for attention regarding sexual or child exploitation (etc), and insisting that it meet requirements not demanded of TLDs where the actual adult industry can be found, is the height of hypocrisy and political posturing. Either let's advocate to raise the mandatory standards of other TLDs to those demanded of .XXX, or allow it to relax its standards to the levels of other TLDs. What was ultimately most noteworthy to me about the debate was the use of "trust" to justify both the hypocrisy and the resistance to change. Indeed, this weaponization of "trust" on display was more obscene than anything found in the websites under .XXX. But that's a separate topic, best kept for another day. Cheers, Evan

6 10

Input Requested - Draft Public Comment Statement - Proposed Renewal of the Registry Agreement for the .XXX top-level domain (TLD)
by Andrew Chen April 22, 2024

April 22, 2024

Dear CPWG Members, In preparation for the Public Comment Statement submission for the Proposed Renewal of the Registry Agreement for the .XXX top-level domain (TLD)<https://www.icann.org/en/public-comment/proceeding/proposed-renewal-of-the-…>, please see linked below the Draft Public Comment Statement for the Proposed Renewal of the Registry Agreement for the .XXX top-level domain (TLD) Public Comment Proceeding. Please have all comments submitted by Wednesday, 24 April no later than 15:00 UTC. The Public Comment Statement may be further discussed during the 24 April CPWG call. Voting is scheduled to take place between 25 April and 28 April 2024. Draft Public Comment Statement: https://docs.google.com/document/d/1C04oyYcUDLlKRC4fGoQNUc2f45cAcEC5jYDTCcg… Please let us know if you have any questions. Sincerely, Andrew -- Andrew Chen Policy Development Support Sr. Specialist, Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org/ Skype: atchen122

1 0

Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 24 April 2024 at 17:30 UTC
by ICANN At-Large Staff April 19, 2024

April 19, 2024

**If you require a dial out or need to state an apology, please contact At-Large staff at staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> with your preferred number*** Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 24 April 2024 at 17:30 UTC for 90 mins, For other times: https://tinyurl.com/ebuk8a57<http://tinyurl.com/bdcm479f> The agenda (to be updated) and call details can be found at: https://community.icann.org/x/dQJyEw<https://community.icann.org/x/cABkEw> Zoom Room: https://icann.zoom.us/j/765717566?pwd=UTJCdWRSZVdJNEhOYW02OVBqQVQ1Zz09 / Passcode: #CPWG2345* Real time transcription (RTT) available at (subject to availability): https://www.streamtext.net/player?event=ICANN ADIGO Conference Bridge: (subject to availability) EN, ES & FR: 3535 Toll-free access number (US and Canada): 800 550 6865 Other toll-free numbers: https://www.adigo.com/icann At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Kind Regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0

At-Large Consolidated Policy Working Group (CPWG)
by ICANN Policy Calendar April 19, 2024

April 19, 2024

**If you require a dial out or need to state an apology, please contact At-Large staff at staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> with your preferred number*** Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 24 April 2024 at 17:30 UTC for 90 mins, For other times: https://tinyurl.com/ebuk8a57<http://tinyurl.com/bdcm479f> The agenda (to be updated) and call details can be found at: https://community.icann.org/x/dQJyEw<https://community.icann.org/x/cABkEw> Zoom Room: https://icann.zoom.us/j/765717566?pwd=UTJCdWRSZVdJNEhOYW02OVBqQVQ1Zz09 / Passcode: #CPWG2345* Real time transcription (RTT) available at (subject to availability): https://www.streamtext.net/player?event=ICANN ADIGO Conference Bridge: (subject to availability) EN, ES & FR: 3535 Toll-free access number (US and Canada): 800 550 6865 Other toll-free numbers: https://www.adigo.com/icann At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Kind Regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0

Is ICM Registry's Registry Agreement within ALAC' Remit
by mike palage.com April 18, 2024

April 18, 2024

Hello All, During yesterday's ALAC CPWG call, Evan articulated his viewpoint on why responding ALAC submitting a response in connection with the ICM Registry Agreement was potentially outside the scope of ALAC's remit. Justine and I respectfully disagreed with this position. Listed below are my Top 3 reasons why this is not only within ALAC's remit but an affirmative obligation. 1. ICM Registry's application and original registry agreement made many direct and indirect references to how their operation of the TLD would benefit Internet end users. In fact the opening paragraph of ICM Registry application to ICANN specifically cited Internet users: ICM Registry, Inc (ICM) and the International Foundation for Online Responsibility (IFFOR) conducted extensive outreach and discussion to develop a strategy for identifying a TLD string for the responsible online adult-entertainment community that would transcend geographic regions and languages while having high recognition and lasting value for both registrants and Internet users. (emphasis added) See https://archive.icann.org/en/tlds/stld-apps-19mar04/xxx.htm The sTLD Charter includes a Policy Goal statement makes the following reference: The sTLD will (i) foster communication between the Sponsored Community and other Internet stakeholders, (ii) protect free expression rights as defined in the United Nations Declaration of Human Rights, and (iii) promote the development and adoption of responsible business practices designed to combat child pornography, facilitate user choice and parental control regarding access to Online Adult Entertainment, and protect the privacy, security, and consumer rights of consenting adult consumers of Online Adult Entertainment goods and services (the "Policy Goals"). See https://www.icann.org/en/registry-agreements/xxx/xxx-agreement-appendix-s-3… My strong personal belief, and one that I hope is shared by other stakeholders within ALAC, is that when a commercial entity wraps itself in a cloth proposing to benefit Internet end users to secure a defacto contract in perpetuity worth tens of millions of dollars and then attempts to walk away from those commitments to Internet end users, ALAC has an affirmative obligation to bring that to the attention of ICANN. Full Stop. 1. The European Union's recent passage NIS 2.0 Cybersecurity directive reinforces a lot of the important work that ALAC has been engaged in regarding enhancing the overall security of the Internet to benefit Internet end users. TLD Name Registries are now specifically enumerated as an essential entity. Additionally, Article 28 specifically calls out the accuracy and accessibility of domain name registration data as part of this overall security framework. In Appendix S to their current Registry Agreement, ICM Registry represented to authenticate and verify registrants. Potential registrants are authenticated as members of the community by a variety of means including, but not limited to, third party Authentication Providers See https://www.icann.org/en/registry-agreements/xxx/xxx-agreement-appendix-s-3… Attached are the authentication and verification procedures that ICM Registry publicly shared with the ICANN community. Another cutting-edge feature of this process was the distinguishing between natural and legal registrants. Coupled with the use of the Membership Contact ROID, ICM Registry minimized the collection of personal identifying information. When ICM Registry rolled out this registrant verification program in 2011, it was years ahead of its time. This process appears to comply with the letter and spirit of NIS 2.0 Article 28. Therefore, when ICM Registry proposes to replace its contractual obligations to drive a Bentley with a Ford Pinto, I have a problem. Moreover, when this proposed contractual change related to Internet cybersecurity, I think ALAC should see this as a problem as well. 1. The ability of ICANN Compliance to properly enforce its contracts with Registrars and Registries is critically important to the sustainability of the ICANN multistakeholder model, especially concerning Consensus Policies developed by the ICANN community. One of the issues that has concerned Justine and me in preparing this document, is the apparent non-compliance of ICM Registry in depreciating the heightened authentication and verification of .XXX registrant in violation of what was represented in Appendix S and their failure to submit a RSEP in connection with this change. I again hope there is universal agreement within the ALAC community on the need for a robust ICANN Compliance framework to support the ICANN multistakeholder model. In conclusion, I agree with Evan that we should always be asking ourselves the question - is this within ALAC's remit? Because as a community we have limited bandwidth and resources. However, as I hopefully have demonstrated by the reasons set forth above, submitting a public comment in connection with ICM Registry's proposed Registry Agreement is clearly within ALAC's remit. Best regards, Michael

1 0

**UPDATED Meeting invitation: with NEW TIME** - At-Large Consolidated Policy Working Group (CPWG) CalL on Wednesday, 17 April 2024 at 15:00 UTC
by ICANN At-Large Staff April 17, 2024

April 17, 2024

**If you require a dial out or need to state an apology, please contact At-Large staff at staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> with your preferred number*** Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 17 April 2024 at 15:00 UTC for 90 mins, Please update your calendars as the meeting time has been changed. For other times: https://tinyurl.com/4avbxt5v<http://tinyurl.com/bdcm479f> The agenda (to be updated) and call details can be found at: https://community.icann.org/x/cABkEw Zoom Room: https://icann.zoom.us/j/765717566?pwd=UTJCdWRSZVdJNEhOYW02OVBqQVQ1Zz09 / Passcode: #CPWG2345* Real time transcription (RTT) available at (subject to availability): https://www.streamtext.net/player?event=ICANN ADIGO Conference Bridge: (subject to availability) EN, ES & FR: 3535 Toll-free access number (US and Canada): 800 550 6865 Other toll-free numbers: https://www.adigo.com/icann At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Kind Regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 1