March 2024 - CPWG - lists.icann.org

Re: [CPWG] Are Blockchain Domains within the Mission of ICANN - WAS RE: Questions to the board about distributed DNS
by Chokri Ben Romdhane Oct. 18, 2024

Oct. 18, 2024

Dear Friends, Please find the record of the Emerging Identifier Technologies <https://icann.zoom.us/rec/play/4ZhSDuzFnVqw66kYgnTuHdDzi_RH0IFCKqKuAzmmcFy7…> session , held during the ICANN75 meeting, it provides some use cases of the emerging identifiers technologie. Thank you @MOULOUD KHELIF <kelif(a)hotmail.com> for the reminder. Friendly regards Chokri Le sam. 27 août 2022 à 19:17, Evan Leibovitch <evan(a)telly.org> a écrit : > On Thu, Aug 25, 2022 at 5:39 AM Chokri Ben Romdhane <chokribr(a)gmail.com> > wrote: > > >> But be aware if you confirm that the collision issues is/will never >> happened , as you have mentioned in your previous mail, and cross your >> finger that the regular DNS market will continue to attract more customers, >> compared to those NFT, Blockchain TLDs considering the ease of DNS >> management and security they are conferred to end users. >> > > Hi again, > > You made one fatal error in your assessment above: Internet end-users are > not registrants. > > End users don't care about DNS management, and the security THEY seek is > access to registrant details in the case of domains used for abuse. > The "security" you mention protects registrants and works against the > interests of end-users. > > It's totally possible that the hubris of DNS alternatives may lead to > collisions, but end-users will never see the effect of that, Browsers > continue to use the ICANN root and to date have never seen the benefit of > pointing to alternames. Plus, two of the biggest browser makers, Google and > Microsoft, have a deep vested interest in obstructing any alternative DNS. > Any alternate DNS hoping to be successful would need to create its own > browser, which is what the TOR project did. > > So even if alternative DNSs create TLDs that duplicate ICANN's they will > never present any collision or confusion to end-users. The only losers will > be registrants in the alternate systems. I have zero pity for them and they > are certainly not ALAC's concern or even ICANN's. > > Cheers, > - Evan > >

11 33

Update on ICM Registry
by mike palage.com March 31, 2024

March 31, 2024

Hello All, Listed below is a complaint that I submitted to ICANN Compliance this weekend consistent with the concerns I raised on the CPWG call this past Wednesday. I will keep the community informed of any developments. <Complaint Submitted to ICANN Compliance> ICM Registry during its application to become the registry operator of the .XXX TLD made several material representations to ICANN (Org/Board/Community) as well as the broader Internet community in connection with how it would operate the .XXX TLD. Two such representations involved registry safeguards (services) designed to minimize abuse and child sexual abusive material. The first involved enhanced registrant verification to ensure that ICM knew every registrant and that they had met the registration criteria. The second involved the use of a Membership Contact ROID that was associated with each domain name registration. This feature allowed ICM Registry to quickly remove from the zone file all domain names associated with a problematic registrant upon becoming aware of a problem. As ICANN compliance is keenly aware Registry Operators are required to file a Registry Services Evaluation Process (RSEP) in connection with any new, modified, or deprecated registry service. ICANN Org has taken a very expansive definition of when a Registry Operator is required to submit an RSEP. Case in point, ICANN required fTLD to file an RSEP in connection with minor changes in how .Bank and .Insurance registrants are verified, see https://www.icann.org/en/system/files/files/rsep-2017039-bank-et-al-request… Upon information and belief ICM Registry has changed the process by which registrants are verified and they have removed the Membership Contact ROID without submitting an RSEP which is a violation of their Registry Agreement. Additionally, any attempt by ICM Registry to deprecate these services would constitute a material deviation from the representations made by ICM Registry when securing their right to operate the .XXX TLD.

1 0

Apology - Need to step down from co-chairing the CPWG
by Hadia El Miniawi March 29, 2024

March 29, 2024

Dear All, After much consideration and thinking I have realised the necessity of devoting more time to my responsibilities as AFRALO chair and the planing of the upcoming meeting in Africa. Additionally, I am eager to initiate more engagement activities that will require more focus and time. Olivier it was a pleasure co-chairing the group with you. However, stepping down from this role means I will have more time to contribute to the At-large policy statements and work as I remain an active member of the CPWG. See you all on the next CPWG call P.S. Olivier you will need to look for another co-chair or run the call solo! I will now be more on the policy contributors side, I had no time for both. Thanks again. Kind regardsHadia Elminiawi

12 15

Input Requested - Draft Public Comment Statement - Review of the Draft Applicant Support Program (ASP) Handbook – New gTLD Program
by Andrew Chen March 29, 2024

March 29, 2024

Dear CPWG Members, In preparation for the Public Comment Statement submission for the Review of the Draft Applicant Support Program (ASP) Handbook – New gTLD Program<https://www.icann.org/en/public-comment/proceeding/review-of-the-draft-appl…>, please see linked below the Draft Public Comment Statement for the Review of the Draft Applicant Support Program (ASP) Handbook – New gTLD Program Public Comment Proceeding. Please have all comments submitted by tomorrow, no later than 20:00UTC. The ALAC will begin its vote to endorse this statement shortly after the closure of the comment period. Voting will take place between 28 March and 01 April 2024. Draft Public Comment Statement: https://docs.google.com/document/d/14xXyM_mDl7nv5ImqlnEXFsD3womZbLwdhmMUi53… 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

2 1

Proposed response to the Change of Registrant Data (CORD) policy
by Steinar Grøtterød March 29, 2024

March 29, 2024

Dear all, Attached is my proposed response to the CORD policy (PDF copy). Please review the draft preliminary recommendations in detail. Using the tables provided (starting on p.9 of the worksheet), please identify any recommendations you believe should be changed. The tables contemplate levels of support (or lack of support): * Cannot live with the recommendation as written - this means that, unless significantly altered, your group cannot live with the text being included in the Initial Report * Could live with, but would prefer a change * Grammatical/typographical edits * Support recommendation as written All with the link to the Google doc (https://docs.google.com/document/d/1kQzyDWRydL6r9lroP8LwMRIhwEqmvBEIHXxDcFX…) can add comments. If you need access to write, please let me know. GNSO-TPR working group members are instructed to get feedback from the group (At-Large), hence your input to the proposed CORD policy is of importance. A key question is At-Large is in favor of enabling an opt out for mandatory notifications when there is a change of Registrant Data. Enabling the opt out for notification can be seen as a security risk. In my view, it should NOT be possible for Registrars to enable an opt out for notifications. I will ask for 15-20 minutes to discuss this at the CPWG meeting on April 3, 2024. Regards, Steinar Grøtterød

1 0

At-Large Consolidated Policy Working Group (CPWG)
by ICANN Policy Calendar March 28, 2024

March 28, 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, 03 April 2024 at 14:00 UTC for 90 mins, For other times: https://tinyurl.com/nwmsv58d<http://tinyurl.com/bdcm479f> The agenda (to be updated) and call details can be found at: https://community.icann.org/x/UwAsEw 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

Re: [CPWG] Apology - Need to step down from co-chairing the CPWG
by Hadia El Miniawi March 28, 2024

March 28, 2024

Thank you a lot Cheryl. Much appreciated. Hadia On Wednesday, March 27, 2024 at 11:25:45 PM GMT+2, Cheryl Langdon-Orr <langdonorr(a)gmail.com> wrote: Sensible move... You of course have my support... On Thu, 28 Mar 2024, 08:23 Hadia El Miniawi via CPWG, <cpwg(a)icann.org> wrote: Dear All, After much consideration and thinking I have realised the necessity of devoting more time to my responsibilities as AFRALO chair and the planing of the upcoming meeting in Africa. Additionally, I am eager to initiate more engagement activities that will require more focus and time. Olivier it was a pleasure co-chairing the group with you. However, stepping down from this role means I will have more time to contribute to the At-large policy statements and work as I remain an active member of the CPWG. See you all on the next CPWG call P.S. Olivier you will need to look for another co-chair or run the call solo! I will now be more on the policy contributors side, I had no time for both. Thanks again. Kind regardsHadia Elminiawi _______________________________________________ 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, 27 March 2024 at 19:00 UTC
by ICANN At-Large Staff March 27, 2024

March 27, 2024

**f 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, 27 March 2024 at 19:00 UTC for 90 mins, For other times: https://tinyurl.com/mt6enak2 The agenda and call details can be found at: https://community.icann.org/x/DwAZEw Zoom Room: https://icann.zoom.us/j/765717566?pwd=UTJCdWRSZVdJNEhOYW02OVBqQVQ1Zz09 / Passcode: #CPWG2345* Real time transcription (RTT) available at: 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, 27 March 2024 at 19:00 UTC
by ICANN At-Large Staff March 27, 2024

March 27, 2024

**f 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, 27 March 2024 at 19:00 UTC for 90 mins, For other times: https://tinyurl.com/mt6enak2<http://tinyurl.com/bdcm479f> The agenda (to be updated) and call details can be found at: https://community.icann.org/x/DwAZEw 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

REMINDER / Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 27 March 2024 at 19:00 UTC
by ICANN At-Large Staff March 26, 2024

March 26, 2024

**f 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, 27 March 2024 at 19:00 UTC for 90 mins, For other times: https://tinyurl.com/mt6enak2 The agenda (to be updated) and call details can be found at: https://community.icann.org/x/DwAZEw 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> [signature_607142721]

1 0