September 2021 - council - lists.icann.org

FW: ICANN Launches Improved Public Comment Feature
by philippe.fouquart＠orange.com Sept. 1, 2021

Sept. 1, 2021

Dear SG/C leaders, Councilors, You may be aware of the following already, apologies for duplicates Regards, Philippe From: soac-chairs [mailto:soac-chairs-bounces@icann.org] On Behalf Of David Olive via soac-chairs Sent: Tuesday, August 31, 2021 10:03 PM To: soac-chairs(a)icann.org Cc: Carlos Reyes <carlos.reyes(a)icann.org>; Jana Juginovic <jana.juginovic(a)icann.org> Subject: [soac-chairs] ICANN Launches Improved Public Comment Feature https://www.icann.org/en/blogs/details/icann-launches-improved-public-comme… ICANN Launches Improved Public Comment Feature 31 August 2021 David Olive<https://www.icann.org/en/blogs/details/icann-launches-improved-public-comme…>, SVP, Policy Development Support & Managing Director – Washington, D.C. Today, I am pleased to announce that the Information Transparency Initiative (ITI) has reached another important milestone with the release of an improved Public Comment feature<https://www.icann.org/en/public-comment>. This enhanced feature is part of the ICANN organization's ongoing commitment to increase the findability and transparency of our information. Feature Improvements The ITI team has made several improvements including: * Submissions available in search results * Number of submissions published to individual proceedings available in real time * Filtered search by category or date range * Improved keyword(s) search for proceedings, submissions, and files * Email subscription alerts for individual proceedings and their submissions * New guided form submission feature * Submission management feature allowing individual users or ICANN groups to track their submissions * New consolidated Other Public Consultations pages to provide the community with a central location for other ICANN community surveys or public consultations that fall outside the Public Comment process * Improved layout and user experience Accessing Submissions and Subscriptions To publish a submission or subscribe to Public Comment updates, you will need to create an ICANN Account<https://account.icann.org/> using a unique username and password. You will be asked to add basic profile information. If you already have an ICANN Account, you can log into your account to publish a submission to a proceeding or sign up for Public Comment alerts. For more information on publishing a Public Comment submission or how to subscribe to the latest Public Comment content, please read our Public Comment Step-by-Step Submission Guidelines<https://www.icann.org/en/system/files/files/public-comment-submission-guide…>. You can also watch a recorded training webinar<https://icann.zoom.us/rec/share/yOsz6gE0lkRkXpB3M_n5HApBAkD6W8q3F2nuELx-onc…> about the improved Public Comment submission process. About Public Comment Public Comment is a critical part of our multistakeholder model. It provides a mechanism by which stakeholders can have their opinions and recommendations documented in a formal, public manner. It presents the ICANN community with the chance to provide inputs for consideration within ICANN's decision-making processes. As I have written about previously<https://www.icann.org/en/blogs/details/improving-the-public-comment-feature…>, we received a lot of feedback from our stakeholders and the ICANN community about the Public Comment information available on https://icann.org<https://www.icann.org/>. You told us that it was challenging to find information and that it was as equally challenging to stay up to date on the latest Public Comment news. This feedback informed our requirements and recommendations for improving search, the submission process, and content subscriptions. Thank You to the Community On behalf of the ITI and Policy Development teams, we'd like to extend a huge thank you to all the ICANN community members who took the time to participate in and provide feedback on how to improve Public Comment. Your input was invaluable, and we hope that you can see the steady progress we are making at improving the findability of content on https://icann.org<https://www.icann.org/>. If you want to learn more about ITI, visit https://www.icann.org/iti. As always, if you have any questions or comments, please email the ITI team at: informationtransparency(a)icann.org<mailto:informationtransparency@icann.org>. Sent from my iPhone David A. Olive Senior Vice President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

1 0

FW: [gnso-chairs] Appointment of ICANN org liaison to GNSO Registration Data Accuracy Scoping Team
by philippe.fouquart＠orange.com Sept. 1, 2021

Sept. 1, 2021

Hi everyone, Please note Göran’s response attached and appointment of Brian Gutterman as ICANN org’s liaison to the accuracy scoping team. Regards, Philippe From: Gnso-chairs <gnso-chairs-bounces(a)icann.org<mailto:gnso-chairs-bounces@icann.org>> on behalf of Goran Marby via Gnso-chairs <gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>> Reply-To: Goran Marby <goran.marby(a)icann.org<mailto:goran.marby@icann.org>> Date: Friday, August 27, 2021 at 3:35 PM To: "philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com>" <philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com>> Cc: "gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>" <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>>, "gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>" <gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>>, Cassia Oliveira <cassia.oliveira(a)icann.org<mailto:cassia.oliveira@icann.org>> Subject: Re: [gnso-chairs] Appointment of ICANN org liaison to GNSO Registration Data Accuracy Scoping Team Cassia Oliveira on behalf of Mr. Marby Dear Mr. Fouquart, Attached please find letter from Mr. Marby in response to your letter dated 3 August 2021. Thank you. Regards, Göran Marby President & CEO ICANN +1(310) 578 8690 Cássia Oliveira Sr. Manager, Office of the President & CEO cassia.oliveira(a)icann.org<mailto:cassia.oliveira@icann.org> +1(310) 578 8656 ________________________________ From: philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com> <philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com>> Sent: Tuesday, August 3, 2021 4:04 AM To: Goran Marby Cc: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>; gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org> Subject: [Ext] Appointment of ICANN org liaison to GNSO Registration Data Accuracy Scoping Team Dear Goran, I trust this email finds you well. I am following up on our discussion during the Board – GNSO Council meeting on 24 June 2021 in relation to the Registration Data Accuracy Scoping Team. As discussed, the GNSO Council would welcome the participation of a liaison from ICANN Org in this effort. The attached letter provides the background on this Registration Data Accuracy Scoping Team - it covers both Org and Board liaisons, I’m sending a similar follow-up to Maarten. Best Regards, Philippe _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

1 0

Document and Motion deadline Monday, 13 September 2021 at 23:59 UTC for GNSO Council Meeting 23 September 2021 at 19:00 UTC
by Nathalie Peregrine Sept. 1, 2021

Sept. 1, 2021

Dear all, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday, 13 September 2021 at 23:59 UTC) of the GNSO Council Meeting on Thursday,23 August 2021 at 19:00 UTC. Motions should be sent to the Council mailing list by a councilor and will then be posted on the Wiki at: https://community.icann.org/x/DYJLCg Thank you. Nathalie

1 0