November 2023 - CPWG - lists.icann.org

Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 22 November 2023 at 14:00 UTC
by ICANN At-Large Staff Nov. 16, 2023

Nov. 16, 2023

**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, 22 November 2023 at 14:00 UTC for 90 mins, For other times: https://tinyurl.com/2fcwbncs<https://tinyurl.com/22ne3mpb> The agenda (to be updated) and call details can be found at: https://community.icann.org/x/TgDFE<https://community.icann.org/x/Y4FUDw> 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: 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

Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 15 November 2023 at 19:00 UTC
by ICANN At-Large Staff Nov. 15, 2023

Nov. 15, 2023

**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, 15 November 2023 at 19:00 UTC for 90 mins, For other times: https://tinyurl.com/4n922c83<https://tinyurl.com/22ne3mpb> The agenda (to be updated) and call details can be found at: https://community.icann.org/x/8QKfE<https://community.icann.org/x/Y4FUDw> 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: 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

REMINDER / Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 08 November 2023 at 13:00 UTC
by ICANN At-Large Staff Nov. 8, 2023

Nov. 8, 2023

**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, 08 November 2023 at 13:00 UTC fo 90 mins. For other times: https://tinyurl.com/55vxamad The agenda and call details can be found at: https://community.icann.org/x/4QJ6E 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: 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> [signature_1563901265]

2 1

Closed Generics Advice to the Board.
by Alan Greenberg Nov. 8, 2023

Nov. 8, 2023

The Facilitated Dialogue on Closed Generics issued a draft report that received very negative comments. As a result, the Facilitated Dialogue (FD) referred the matter to the Chairs of the GNSO, GAC and ALAC. Their reply to the FD (https://gac.icann.org/contentMigrated/gac-alac-gnso-chairs-letter-to-closed…) indicated that the Chairs suggested that the Board FD finalize its report saying that no compromise could be found and that they would advise the Board to not allow Closed Generics in the coming round of new gTLDs. A letter from the Chairs to the Board was drafted, but the GNSO Council could not accept their Chair making such a statement. The letter was revised, but still no agreement from the GNSO. Accordingly, the Chairs of the GAC and ALAC issued the letter saying that they could not come to agreement with the GNSO (https://www.icann.org/en/system/files/correspondence/caballero-zuck-to-sinh…) The GNSO Chair sent a letter saying that the Board should decide on how to address the issue (https://www.icann.org/en/system/files/correspondence/ducos-to-sinha-21oct23…) During ICANN78, the GAC issued advice to the Board in support of its Chair's letter. The advice was clear and concise. Do not allow Closed Generics in the coming round. You can find the GAC Communique at https://gac.icann.org/contentMigrated/icann78-hamburg-communique with its CG advice on page 11. The next step is for the ALAC to issue comparable advice in support of our Chair's letter. With Greg's support, I have drafted the following advice which we are recommending that the ALAC issue. It is short and in addition to supporting the GAC advice to not have Closed Generics in the coming round, it makes clear that the divisions within the FD were VERY wide and that the chances of future work closing them highly unlikely. ALAC Advice to the Board on Closed Generic TLDs The ALAC, along with the GAC and the GNSO, participated in good faith in the Facilitated Dialog on Closed Generics. This effort notwithstanding, the Facilitated Dialog failed to create a framework allowing Closed Generic TLDs which would serve a public interest goal. The GAC, in its communiqué from ICANN78 in Hamburg, Germany, gave unequivocal Advice to the Board on this matter. To quote: Prior to the next round of New gTLDs, to ensure that the forthcoming Applicant Guidebook clearly states that Closed Generic gTLD applications will not be considered. The ALAC fully supports this Advice and its accompanying rationale and echoes this Advice to the Board. Moreover, based on discussions within the Facilitated Dialogue after reviewing the comments received on its draft framework, and in the community since that time, the ALAC posits that the differences among the various parties on what would satisfy a public interest or the global public interest may well be irreconcilable, and that the benefit of such Closed Generic gTLDs are not worth expending more community time and ICANN resources on this issue.

3 2

Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 08 November 2023 at 13:00 UTC
by ICANN At-Large Staff Nov. 7, 2023

Nov. 7, 2023

*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, 08 November 2023 at 13:00 UTC for 90 mins, For other times: https://tinyurl.com/55vxamad<https://tinyurl.com/22ne3mpb> The agenda (to be updated) and call details can be found at: https://community.icann.org/x/4QJ6E<https://community.icann.org/x/Y4FUDw> 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: 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 2

Open Letter to ICANN from Jeff Neuman
by jeff＠jjnsolutions.com Nov. 6, 2023

Nov. 6, 2023

All, I wanted to bring this incredibly sensitive matter to the attention of the At Large. It is a letter I wrote to the Board and CEO of ICANN. I just wanted to forward this on and perhaps this is something that the At-Large wants to discuss. If ICANN truly wants to live up to its Expected Standards of Behavior, they need to take firm swift action. https://www.jjnsolutions.com/post/open-letter-to-icann#:~:text=Open%20Lette…. Open Letter to ICANN I am posting this letter I just sent to ICANN's Chair and Vice Chair as well as to the CEO regarding the statements made by the founder of an organization that hosts an instance of the L-Root Server. I am not posting this to be critical of ICANN at all. ICANN has always done the right thing here and I am sure they will do what is right this time as well. I have faith in ICANN Org and their leaders. So if anyone posts anything about this open letter, please make sure to include that I do NOT fault ICANN for any of this. Dear Tripti, Sally and Danko, I wanted to thank you for your unequivocal statement at the ICANN78 Public Forum that certain political commentary has no place at ICANN and at ICANN meetings. As a Jewish person that lost much of my extended family in the Holocaust in Germany (where the meeting was hosted), it was truly upsetting to see a well-intentioned color-board ruined with words which represent a movement that stands for the eradication of Israel and the extermination of all Jews in the world. While I certainly do not want to stifle any free speech, at the same time, people need to recognize that their words have meaning and can be hurtful to others. It is on this same matter that I want to draw your attention to the comments by Talal Abu Ghazaleh, the founder and chairman of the Jordan-based organization, Talal Abu-Ghazzaleh Organization. In these awful comments (https://www.memri.org/tv/jordanian-businessman-talal-abu-ghazaleh-gaza-loss…) Talal engages in explicit antisemitic speech where he states: ""The Jews do not have any ideology. All they care about is money and interests. I had a friend who was a German cabinet member. I once asked him: 'When Hitler, may God forgive him, carried out the Holocaust, why didn’t he finish the job and kill all the Jews?’ He said to me: 'It's the other way around, but don't tell anyone I said this. He left a group of them on purpose, so that people would know why we carried out the Holocaust. When you would be tormented by them, you would know the reason.'" I also recall that TAG-Org hosts an instance of ICANN's L Root in Jordan (https://www.agip.com/news.aspx?id=6292) I believe ICANN must take immediate action to remove this instance from TAG-Org and find a new home for this instance. In addition, ICANN should make an unequivocal statement ASAP that it does not condone such hate speech and that it will not have any partnerships whose founders or leaders espouse such views. I do not consider myself a political activist by any means, but I care about ICANN and its future. And that future cannot associate itself with organizations that support antisemitism. Other Organizations have already come out against TAG-Org and ICANN should as well. See https://www.managingip.com/article/2cdiik8ybhxoc337hchds/managing-ips-state… and https://www.iam-media.com/article/statement-removal-of-talal-abu-ghazaleh-t…. Please feel free to post this message to the Correspondence page. I am going to post this on my blog in the spirit of openness and transparency.

1 0

CENTR: Registration Data Policy — a sense of urgency
by Steinar Grøtterød Nov. 6, 2023

Nov. 6, 2023

Dear all, Maybe something we should spend some time discussing? https://www.centr.org/news/blog/icann78-urgency.html Regards, Steinar Grøtterød

1 0

DNS Abuse in link-shortening service using .US
by Greg Shatan [NARALO] Nov. 3, 2023

Nov. 3, 2023

All, Here's another form of DNS Abuse that is quite problematic, and described in detail in the Krebs on Security piece. Apparently, there is a link-shortening service called Prolific Puma that has become a favorite for use in malware and phishing scams. Prolific Puma creates second level .us domains that obfuscate the true URL. The Krebs piese is based on an Infoblox report that is mentioned in the article. .US Harbors Prolific Malicious Link Shortening Service – Krebs on Security <https://krebsonsecurity.com/2023/10/us-harbors-prolific-malicious-link-shor…> "The top-level domain for the United States — *.US* — is home to thousands of newly-registered domains tied to a malicious link shortening service that facilitates malware and phishing scams, new research suggests. The findings come close on the heels of a report that identified .US domains as among the most prevalent in phishing attacks over the past year." -- *Greg Shatan* *Chair, NARALO*

1 0

GNSO-TPP: Transfer Policy Review Working Group Recap
by Steinar Grøtterød Nov. 2, 2023

Nov. 2, 2023

Dear all, The GNSO-TPR working group has received a recap of all charter questions (attached). This is an overview of the recommendations the group has agreed on to date. The GNSO-TPR working group will “re-open” the charter questions connected to “Change of Registrant (CoR)”. The first meeting after ICANN78 is scheduled to Nov 7, 2023. If you have any feedback and/or proposals to the recommendations, please let the At-Large representatives know by posting to this group or directly to me. Regards, Steinar Grøtterød

1 0

SSAC and Steve Crocker interventions - and the Global Public Interest
by Olivier MJ Crépin-Leblond Nov. 1, 2023

Nov. 1, 2023

Dear Colleagues, during the ICANN meeting, the ALAC met with the SSAC and touched on several topics. A recording is linked below - but a particularly interesting intervention was that of Dr. Steve Crocker. *Joint Session: ALAC & SSAC* *Session Details: https://sched.co/1T4Kr Zoom Recording: https://icann.zoom.us/rec/share/wglfBxy1wiD1QWzk0yxQbBf5Wa-1ocJWLCcfc7SUCrr… * Steve Crocker starts on: 00:08:56 - and touches on some interesting topics. At 21:48 - Dr. Crocker provides his opinion about the WHOIS situation, which in his view has been broken for many years. The "System", meaning the ICANN policy and implementation of the Registration Data Request System (RDRS) reflects concerns of the domain owner side, its Registrar, Registries, but very little on the Requester side. And then the comments on: 26:24 tagged a personal opinion about the ICANN consensus process being flawed relating to this topic. These are significant words coming from an ex-Chair of ICANN who had access to all of the ICANN inside track. The SSAC also had a meeting with the ICANN Board. Again, several members of the SSAC raised some significant points - whereas the "consumer" which includes end users are faced with ridiculous process put in place by incorrect implementation of ICANN policy. *Joint Session: ICANN Board and SSAC* *Session Details: https://sched.co/1T4Ht Zoom Recording: https://icann.zoom.us/rec/share/EgEGgiDRs1DIr7arQu_UBULIw1k-zhsk9bouuxnufPY… * Several SSAC members noted a pattern of not involving the consumer in the design of these systems. A particular concern relates to "urgent requests" which the PDP has responded to as a response in a matter of days - not hours or minutes. Steve Crocker speaks at: 22:42 John Levine speaks at: 32:49 Both Avri Doria and Edmon Chung provide very valuable input into the discussion - and explain that ultimately the Board is tasked with upholding the Global Public Interest. But the point is made that CISA DS ( https://www.cisa.gov/news-events/directives ) which was included initially as consensus policy does not appear to be in the contracts signed with ICANN - and the SSAC member asking the question (Benedict Addis - a technical officer in the Cyber and Forensics department of the Serious Organised Crime Agency (SOCA), a UK law enforcement body) regarding access to Registrant data in emergency situations - those of hostage taking or where there is a matter of life or death, does not seem particularly impressed. The ICANN Board - as Becky Burr said, agree that the system is not fit for purpose. "The Board will be bringing the urgent request issue back to the GNSO council". At 50:00 Rod Rasmussen spoke of "things that don't quite work right" - but is careful in mentioning SSAC are not picking on Contracted Parties. Sadly, two of the Board members that focussed in particular on the topic were Avri and Matthew and they have now left the Board. I hope other Board members will pick up the helm of the Public Interest because it becomes clear that there is a problem here. Could it be useful to take these problems as examples to support the need for an ICANN pilot Holistic Review? Kindest regards, Olivier

3 3