- ALAC - lists.icann.org

ccNSO Achievements Report
by Laura Margolis Feb. 15, 2024

Feb. 15, 2024

Dear All: Just to let you know that the ccNSO just launched its Achievements Report for 2023. Just some highlights on the report: 1. Two Internationalized Domain Name (IDN) country code top-level domain (ccTLD) members were welcomed by the ccNSO. 2. The creation of the Universal Acceptance Committee (UAC) indicates a concerted effort to address issues related to the acceptance of all domain names and email addresses by internet applications and systems. 3. The DNS Abuse Standing Committee (DASC) has kicked off, signaling a focused approach to combating abuse and misuse within the ccTLDs domain name system. 4. The acceptance and submission of the review mechanism policy for ccTLDs to the ICANN board. 5. Lastly, the celebration of the ccNSO's 20th anniversary marks a significant milestone in the organization's history and underscores its enduring commitment to supporting the interests of country code top-level domain operators. For more detailed insights, please read the attached document with the full achievements report. Thank you! -- *Laura Margolis* ALAC Liason to ccNSO margolisl(a)gmail.com +59899690992 skype: lauri.margolis ccNSO Liason Workspace <https://community.icann.org/display/atlarge/ALAC+Liaison+to+the+ccNSO+Repor…>

2 2

ICANN79 Prep Week: GNSO New gTLD SubPro PDP: Supplemental Recommendations Community Update, 22 Feb at 20:30 UTC
by Justine Chew Feb. 6, 2024

Feb. 6, 2024

Dear all, The ICANN79 Prep Week Schedule <https://icann79.sched.com/> is now out. In the event I am time-limited to discuss with the ALAC and/or CPWG, the SubPro supplemental recommendations out of the GNSO SubPro Small Team Plus, please be informed that these are expected to be previewed at the last ICANN79 Prep Week session (details set out below). I would encourage those with an interest in this area of community work to attend this Prep Week session. *GNSO New gTLD Subsequent Procedures Policy Development Process: Supplemental Recommendations Community Update https://sched.co/1ZUnf <https://sched.co/1ZUnf>* 16:30 San Juan (UTC -4), 22 February 2024 20:30 UTC, 22 February 2024 Prep 1 ID# 15052 *Session Details* With all pending SubPro recommendations having been addressed in some manner, the GNSO Council's Small Team Plus has now been tasked with developing Supplemental Recommendations in respect of any SubPro recommendations that were not adopted by the ICANN Board. This purpose of this prep week session is to brief the community on proposed amendments to the SubPro recommendations that were not adopted by the ICANN Board, in preparation for a community consultation session during ICANN79. Kind regards, Justine Chew ALAC Liaison to the GNSO GNSO Liaison Report Workspace <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…> ------

1 0

GNSO Council 18 Jan 2024 meeting agenda is out
by Justine Chew Jan. 22, 2024

Jan. 22, 2024

Dear all, Just a note to inform you that they agenda for the GNSO Council meeting of 18 Jan 2024 is out. For a curated version of the highlighted agenda item, please visit this link <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…> . *GNSO Council Meeting #1 of 2024 held on 18 Jan 2024 * *Full Agenda <https://community.icann.org/x/OgG1E> | Documents <https://community.icann.org/x/7oAvEQ> | Motions <https://community.icann.org/x/_IAvEQ>* - *Item 1: Administrative Matters* - Item 2: Opening Remarks / Review of Projects List <https://gnso.icann.org/en/council/project> and Action Item List. <https://community.icann.org/x/RgZlAg> - *Item 3: Consent Agenda* - *Item 4: COUNCIL DISCUSSION - SubPro Small Team Update on Non-Adopted Recommendations* - Item 5: COUNCIL DISCUSSION - Communications Small Team Follow-up Conversation - Item 6: COUNCIL DISCUSSION - Council Engagement with PDP Working Group Chairs - *Item 7: COUNCIL DISCUSSION - Registration Data Accuracy* - *Item 8: ANY OTHER BUSINESS * - 8.1 Update on ICANN79 planning and GNSO Draft schedule <https://gnso.icann.org/sites/default/files/policy/2024/draft/draft-gnso-ica…> - 8.2 Update from SO/AC Roundtable - *8.3 Update on Diacritic Study Request* - 8.4 Update on PPSAI Implementation (GDS will provide update) - 8.5 Expected Standards of Behavior As usual, Council meetings are open to observers in listen-only mode. If you would like to observe the meeting, please check this link <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…> for details. Thanks for reading / considering. Justine Chew ALAC Liaison to the GNSO GNSO Liaison Report Workspace <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…> ------

2 2

ccNSO updates
by Laura Margolis Dec. 28, 2023

Dec. 28, 2023

Dear All: The ccNSO meeting #201 was held on December 21st. at 21:00 UTC. You can find the AGENDA here <https://community.icann.org/display/atlarge/ALAC+Liaison+to+the+ccNSO+Repor…>, but I would like to highlight some topics: *Update on ccPDP4-IDN* The fourth Country Code Names Supporting Organization (ccNSO) Policy Development Process Working Group (ccPDP4-IDN) sought *community input* <https://r20.rs6.net/tn.jsp?f=001hcExTmrHTB4PonYkxjo7sn9OmNxSscKeDNJsWqwhCr2…> on its initial policy proposals and is now analyzing the comments. The group hopes to complete its evaluation by January 2024. Once the ccNSO Council recommends adoption of the proposed policy, it will be put to a vote of the ccNSO membership. The fourth ccPDP defines the criteria, process, and procedures for the (de)selection of Internationalized Domain Name (IDN) ccTLDs associated with the country codes assigned to countries, territories, or other areas of geopolitical interest listed in the ISO 3166-1 standard. This ccPDP also responds to the ICANN Board's request to address issues related to variants of IDN ccTLD strings in coordination with the Generic Names Supporting Organization (GNSO) and the ICANN Board's question as to whether IDN tables should be reviewed upon submission. Once adopted by the ICANN Board and implemented by the ICANN organization, the proposed IDN ccTLD string selection policy will eventually replace the IDN ccTLD Fast Track process. *IGLC – Internet Governance Liason Committee* The IGLC prepared an FAQ <https://community.icann.org/display/ccnsowkspc/Repository> prior to ICANN78, in preparation for its session on WSIS+20. The WSIS+20 FAQ for ccTLDs is a comprehensive guide to understanding the significance of the 2025 review of the World Summit on the Information Society (WSIS+20) for ccTLDs. During ICANN78, the IGLC held a working session where ccTLD community members and ICANN’s Government and Intergovernmental Organization Engagement (GE) team explored what the hot issues in Internet governance are on a regional basis. The IGLC compared the input with previous trends exercises. *WSIS+20: Frequently Asked Questions* Are you curious about the future of the internet and how it affects country code top-level domains? Look no further! Welcome to the WSIS+20 FAQ for ccTLDs, your comprehensive guide to understanding the significance of the 2025 review of the World Summit on the Information Society (WSIS+20) for ccTLDs. In this FAQ developed by the ccNSO Internet Governance Liaison Committee, we delve into the key questions surrounding the evolving landscape of Internet Governance and the critical role that ccTLDs play in shaping the digital world, ensuring that you are well-equipped to participate in the global dialogue. - What is WSIS+20 and when will it take place? <https://docs.google.com/document/d/1QXAkkp6xUZAtW1azElsbXpTlbvzWaw_2ro6Vkso…> - Why is WSIS+20 important to ccTLDs and what role do they play in the discussions? <https://docs.google.com/document/d/1QXAkkp6xUZAtW1azElsbXpTlbvzWaw_2ro6Vkso…> - How can ccTLDs participate or engage in the WSIS+20 discussions, follow-up and implementation processes? <https://docs.google.com/document/d/1QXAkkp6xUZAtW1azElsbXpTlbvzWaw_2ro6Vkso…> - Does WSIS+20 introduce any new opportunities or challenges for ccTLD managers? <https://docs.google.com/document/d/1QXAkkp6xUZAtW1azElsbXpTlbvzWaw_2ro6Vkso…> - What is the Tunis Agenda for the Information Society? <https://docs.google.com/document/d/1QXAkkp6xUZAtW1azElsbXpTlbvzWaw_2ro6Vkso…> - What is the Global Digital Compact (GDC) and will it affect the WSIS+20 consultations? <https://docs.google.com/document/d/1QXAkkp6xUZAtW1azElsbXpTlbvzWaw_2ro6Vkso…> - How will WSIS+20 affect IGF? <https://docs.google.com/document/d/1QXAkkp6xUZAtW1azElsbXpTlbvzWaw_2ro6Vkso…> - Will WSIS+20 affect the Multistakeholder Model of Internet Governance? <https://docs.google.com/document/d/1QXAkkp6xUZAtW1azElsbXpTlbvzWaw_2ro6Vkso…> - Are there any resources or guidance available to ccTLDs to better understand WSIS+20 and its implications? <https://docs.google.com/document/d/1QXAkkp6xUZAtW1azElsbXpTlbvzWaw_2ro6Vkso…> *Update on ccNSO working groups and committees* https://docs.google.com/document/d/1mGY0DAnqi2MXl7mJp4kGjVhZMdpsQmZtL2aGOfI… *December Newsletter* https://community.icann.org/display/atlarge/ALAC+Liaison+to+the+ccNSO+Repor… At the ccNSO Liason Wiki Space <https://community.icann.org/display/atlarge/ALAC+Liaison+to+the+ccNSO+Repor…> you can find linked documents to the Agenda, Notes, Working Groups and last newsletters too. Please, let me know any questions or comments. Thank you and Happy Holidays to everyone. *Laura Margolis* ALAC Liason to ccNSO *Email:* margolisl(a)gmail.com *Office*: ++598 27066044 *Mobile / Whatsapp*: ++598 99690992 *skype:* lauri.margolis ccNSO Liason Workspace <https://community.icann.org/display/atlarge/ALAC+Liaison+to+the+ccNSO+Repor…>

1 0

GNSO Council 21 Dec 2023 meeting agenda is out
by Justine Chew Dec. 26, 2023

Dec. 26, 2023

Dear all, Just a note to inform you that the agenda for the GNSO Council meeting of 21 Dec 2023 at 13:00 UTC is out as follows. For a curated version of the highlighted agenda item, please visit this link <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…> . *GNSO Council Meeting #12 of 2023 held on 21 Dec 2023 * *Full Agenda <https://community.icann.org/x/iIJME> | Documents <https://community.icann.org/x/g4JME> | Motions <https://community.icann.org/x/hYJME>* - *Item 1: Administrative Matters* - Item 2: Opening Remarks / Review of Projects List <https://gnso.icann.org/en/council/project> and Action Item List <https://community.icann.org/x/RgZlAg>. - Item 3: Consent Agenda - *Item 4: COUNCIL VOTE - EPDP on Internationalized Domain Names Phase 1 Final Report* - *Item 5: COUNCIL VOTE - GNSO Guidance Process (“GGP”) for Applicant Support Guidance Recommendation Final Report* - *Item 6: COUNCIL DISCUSSION - SubPro Small Team Update on Non-Adopted Recommendations * - *Item 7: COUNCIL DISCUSSION - EPDP on Temporary Specification Phase 1 Urgent Requests* - *Item 8: COUNCIL DISCUSSION - Request for Reconsideration from Intellectual Property Constituency * - *Item 9: COUNCIL DISCUSSION - Update on Key Outcomes and Action Items Coming out of GNSO Council Strategic Planning Session* - *Item 10: ANY OTHER BUSINESS* - 10.1 ccNSO & GAC Liaison updates - *10.2 Update on Diacritic Study Request* As usual, Council meetings are open to observers in listen-only mode. If you would like to observe the meeting, please check this link <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…> for details. Thanks for reading / considering. Justine Chew ALAC Liaison to the GNSO GNSO Liaison Report Workspace <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…> ------

1 2

The SSAC has published SAC123 and SAC122
by Matthias M. Hudobnik Dec. 21, 2023

Dec. 21, 2023

Hi colleagues, the SSAC has published SAC123 and SAC122. ### SSAC Report on the Evolution of Internet Name Resolution (SAC123): · Internet name resolution is evolving beyond just the global DNS to include alternative naming systems that are experimenting with different approaches for reasons like speed, privacy, censorship resistance, and governance. · Many alternative systems adopt DNS name syntax to leverage existing software. · Two concerning trends are increased ambiguity where the same name can resolve differently in different systems, and less visibility of names to end users even as names remain vital for security and trust. · Maintaining integrity and coordination in the shared domain namespace is important. · The report explores different perspectives on these trends from end users and developers. · It identifies proposals to facilitate namespace coordination and recommends ICANN continue tracking these issues and provide regular updates to the community. I highly recommend having a look at chapter: 7.1 End Users (some key aspects as follows): · Domain names used to play an important role for end users in discovering web resources, but search engines have now replaced them as the primary method of discovery. · End users today rarely directly interact with domain names due to the dominance of search engines and mobile devices. Features like browser "omnibars" also allow more free-form input. · Other identifiers like QR codes and social media handles now also compete for users' attention rather than domain names. · Domain names are becoming less visible in users' environments, yet they still provide an underlying ubiquitous resolution context relied upon by other technologies. · Surveys found search engines are by far the predominant method for accessing websites, with domain name usage declining. QR code usage is increasing but still limited except in Asia. · Decreased domain name visibility makes it easier for fraudsters to deceive users with lookalike names. Users are also generally unaware that some TLDs signal a different resolution context. In summary, domain names are no longer the primary method end users employ to find and access Internet resources, decreasing their visibility and understandability while introducing security issues. Link to the report: https://itp.cdn.icann.org/en/files/security-and-stability-advisory-committe… ### SSAC Report on Urgent Requests in gTLD Registration Data Policy (SAC122) · Focus is on handling of Urgent Requests in proposed gTLD registration data policy · Urgent Requests refer to imminent threats to life, injury, infrastructure or child exploitation · Proposed policy requires response to Urgent Requests in 24 hours generally · SSAC contends proposed policy for Urgent Requests is not fit for purpose · Definition and required response times are incompatible · Questions if need and rationale for separate Urgent Request process is fully justified · Existing ICANN policy and industry practices offer useful precedents · Proposed extensions allow responses up to 7 days, not reflecting urgency · Lack of concrete data on frequency and handling of such requests currently · Risks reputation of ICANN multistakeholder model effectiveness - Provides 3 recommendations § Add structure to ensure Urgent Requests handled expediently § Tighten response time requirements to be fit for purpose § Gather data on Urgent Requests for future policy making Link to the report: https://itp.cdn.icann.org/en/files/security-and-stability-advisory-committe… Have a nice evening! Best, M. ______________________________ Ing. Mag. Matthias M. Hudobnik FIP • CIPP/E • CIPT • DPO • CIS LA matthias(a)hudobnik.at http://www.hudobnik.at @mhudobnik

2 1

Re: [ALAC] [ALAC-Announce] Announcement of 2024 ALAC-Selected NextGen Mentor
by Judith Hellerstein Nov. 22, 2023

Nov. 22, 2023

4 3

GNSO Council 16 Nov 2023 meeting agenda is out
by Justine Chew Nov. 18, 2023

Nov. 18, 2023

Dear all, Just a note to inform you that the agenda for the GNSO Council meeting of 16 Nov 2023 at 21:00 UTC is out as follows. For a curated version of the highlighted agenda item, please visit this link <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…> . *GNSO Council Meeting #11 of 2023 held on 16 Nov 2023 * *Full Agenda <https://community.icann.org/x/gYJME> | Documents <https://community.icann.org/x/fIJME> | Motions <https://community.icann.org/x/f4JME>* - *Item 1: Administrative Matters* - Item 2: Opening Remarks / Review of Projects List <https://gnso.icann.org/en/council/project> and Action Item List <https://community.icann.org/x/RgZlAg>. - Item 3: Consent Agenda - *Item 4: COUNCIL VOTE - Approval Action Community Forum at ICANN78 - Fundamental Bylaws Amendments to Articles 18 and 19 of the ICANN Bylaws* - *Item 5: COUNCIL UPDATE - EPDP on Internationalized Domain Names Phase 1 Final Report * - *Item 6: COUNCIL DISCUSSION - Updates on Status of Data Processing Agreement (DPA) negotiations and Registration Data Accuracy* - *(i) DPA Negotiations* - *(ii) Registration Data Accuracy* - *Item 7: COUNCIL DISCUSSION - ICANN Board Action on the Final Report of the Cross-Community Working Group on New gTLD Auction Proceeds (CCWG-AP)* - *Item 8: COUNCIL DISCUSSION - Consider whether further work is needed after ICANN org outreach to European Network Information Security Agency (ENISA) * - *Item 9: ANY OTHER BUSINESS * - 9.1 SPS Planning - 9.2 Confirmation of RDRS Chair - 9.3 Update on Public Comment on Pilot Holistic Review - Terms of Reference - 9.4 Update on GAC Communique Update As usual, Council meetings are open to observers in listen-only mode. If you would like to observe the meeting, please check this link <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…> for details. Thanks for reading / considering. Justine Chew ALAC Liaison to the GNSO GNSO Liaison Report Workspace <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…> ------

2 2

Notes from the ALAC-GNSO Council Bilateral at ICANN78, Sat 21 Oct
by Justine Chew Nov. 6, 2023

Nov. 6, 2023

Dear all, Here are some notes on the ALAC's Bilateral Meeting at ICANN78 with GNSO Council. Link to the Zoom recording of the meeting is available on the ICANN78 schedule website or at the relevant ALAC Liaison to GNSO workspace tab here <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…> . *Notes on the 21 Oct 2023 ALAC-GNSO Council Bilateral Meeting <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…>* Jonathan Zuck, ALAC Chair, provided an update on incoming and outgoing ALAC leadership and Sebastien Ducos, GNSO Chair, provided an update on incoming and outgoing GNSO councilors and the change in GNSO Council leadership. ALAC and At-Large community members and Council leadership and councilors discussed 3 issues per the agenda <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…> : *1. Diacritics in New gTLDs (eg .Quebec and .Québec)* - The GNSO Council recognised that the ALAC, among others, have brought to Council's attention, the potential unsettling impact of certain existing gTLDs (in ASCII or not) running into string similarity issues if the existing registry operators of those certain gTLDs or other applicants were to apply for delegation of what are perceived as confusingly similar strings to those gTLDs but with diacritics. This situation could also impact applications for strings with or without diacritics in the next round. - Sebastien Ducos, GNSO Chair, reported that Council has not yet determined how they would like to proceed with the issue (whether eventually running a PDP, ie. a policy path, *if required* or an implementation for edge cases), and will be discussing this further at the Council meeting on Wed, 25 Oct. - Justine Chew, ALAC Liaison to the GNSO, would be able to provide an update in due course. *2. Next Round of New gTLD Program - Progress on pending or not adopted Subsequent Procedures recommendations* - There are a number of recommendations from the Subsequent Procedures PDP WG that have been marked (as still) pending and some which have been not adopted (rejected) by the ICANN Board on account of the Board holding that they are not in the best interest of ICANN. - GNSO Council had established a Council Small Team to address these pending/rejected recommendations to see if they can be clarified (for those pending) or revised in some way (for those rejected) that would address the Board's concern and rationale, respectively. - Paul McGrady, GNSO Councilor and the Council's Small Team Lead, reported that the GNSO Council is expanding the existing Council Small Team to a "Small Team Plus" to address such recommendations, which includes Recommendation 17.2 on Applicant Support, which he acknowledged as something the At-Large community have a major interest in. Paul encouraged the ALAC to send their very best representatives (a subject matter expert (SME) and an alternate) to join this Small Team Plus to work on those recommendations. - A workplan is being finalised and the invitation for an SME and alternate from every SOAC, C, and SG, will follow soon. - Tijani Ben Jemaa, AFRALO, expressed a hope that the major increased of interest in this topic is one that supports the success of an improved Applicant Support Program as compared to the 2012 Round. *3. Registration Data Request Service (RDRS) * - Greg DiBiase, GNSO Council Vice Chair, explained a bit of the background of the RDRS, from the GNSO recommendations to the Board on the System for Standardized Access/Disclosure (for registration data) (SSAD) and how those recommendations were viewed as prohibitively expensive to implement as-is, and that the Board wanted more data before considering committing a large fund to implement the same. This led to the idea to create a more lightweight system, i.e. a pilot, now called the RDRS, which is to serve as a central place for requestors of registration data that have been redacted to request such data. These requests would be routed to the appropriate registrar for evaluation (and disclosure where appropriate). - Greg DiBiase, GNSO Council Vice Chair, also reported that work has been done to define what the RDRS would look like and the sort of metrics that would be gathered and shared with the community. Also, that Registrar pre-onboarding has begun (around 10% of domains under management, with up to 35% pledged for on-boarding by launch) and that the RDRS should launch by the end of the calendar year. Onboarding by registrars to the RDRS is voluntary and will inform the paths forward for pending System for Standardized Access/Disclosure (SSAD) policy recommendations. The RDRS will run for 2 years and pending policy recommendations will then be revisited. - Greg DiBiase, GNSO Council Vice Chair, also reported that the GNSO Council Small Team that had worked on the RDRS design input will be transitioning to a Standing Committee which is tasked to look into issues with the RDRS as they arise, including metrics and reporting. - Jonathan Zuck, ALAC Chair, expressed a hope that the data being captured/stored will offer the community the ability to do some real analysis as opposed to just relying on reports generated by ICANN org. Sebastien Ducos, GNSO Chair and GNSO Council EPDP Small Team Lead, replied that the data is being stored for as long as the pilot runs but the data that will be shared will only be aggregate data. - Thomas Rickert, GNSO Councilor and GNSO Council EPDP Small Team member, reminded that the RDRS is in effect just of a basic design which excludes many better features per the SSAD recommendations. However, he reminded participants that it is important for us all to advocate for the use of the RDRS to help ensure that the system will work well to meet the needs both requestors and disclosers, in terms of better quality of requests and better quality disclosures. - Greg Shatan, NARALO Chair, inquired whether there has been discussions to handle privacy/proxy service providers who "hide" real registrant data and even registrar data. Sebastien Ducos, GNSO Chair and GNSO Council EPDP Small Team Lead, replied that there have been discussions but since the RDRS is not based on policy but is voluntary for registrars and related service providers, we can only encourage privacy/proxy service providers to also participate in the RDRS. Greg DiBiase, GNSO Council Vice Chair confirmed that there is only existing policy to handle redacted data but no policy to handle data under privacy/proxy services, and there could be future work on that. - Marie Patullo, GNSO Councilor, asked about what happens to requests are "ignored" by "unresponsive registrars". Sebastien Ducos, GNSO Chair and GNSO Council EPDP Small Team Lead, clarified that data related to requests that are unattended to will be stored and followed up in some way that would not disincentivize "responsive registrars". *Action by ALAC Liaison*: To look into periodic intersessional updates from GNSO and discussions with At-Large on the above topics. Kind regards, Justine Chew ALAC Liaison to the GNSO GNSO Liaison Report Workspace <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…> On Mon, 16 Oct 2023 at 17:27, Justine Chew <justine.chew.icann(a)gmail.com> wrote: > Dear all, > > The agenda for the ALAC - GNSO Council joint meeting at ICANN78 is posted > both at the ICANN78 At-Large wiki > <https://community.icann.org/display/atlarge/At-Large+Meetings+-+Saturday%2C…> > and the ALAC Liaison to GNSO workspace > <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…> > . > > Essentially, we will be discussing 3 items: > > 1. GNSO Council's plan to deal with the diacritics issue in Latin > Script (encompassing the .quebec situation) > 2. GNSO Council's plan in addressing the community-developed SubPro > Outputs which either remain marked as "pending" or have not been adopted by > the Board? > 3. What GNSO wishes to share with us in moving the Registration Data > Request Service (RDRS) forward in terms of registrar on-boarding and > post-RDRS launch focus. > > > Kind regards, > > Justine Chew > ALAC Liaison to the GNSO > GNSO Liaison Report Workspace > <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…> > ------ > >

2 1

GNSO Council 25 and 26 Oct 2023 (at ICANN78) meeting agenda is out
by Justine Chew Nov. 4, 2023

Nov. 4, 2023

Dear all, Just a note to inform you that the agenda for the GNSO Council meeting on 25 Oct 2023 at 11:00 UTC and on 26 Oct 2023 at 11:15 UTC is out as follows. For a curated version of the highlighted agenda items, please visit this link <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…> . *GNSO Council Meeting #10 of 2023 held on 25 Oct 2023 during ICANN 78, over 2 parts, and including a Council Wrap-up Session on 26 Oct 2023:* *Under Part 1 Agenda* *Full Agenda <https://community.icann.org/x/vYXxDg> | Documents <https://community.icann.org/x/toXxDg> | Motions <https://community.icann.org/x/uIXxDg>* - *Item 1: Administrative Matters* - Item 2: Opening Remarks / Review of Projects List <https://gnso.icann.org/en/council/project> and Action Item List <https://community.icann.org/x/RgZlAg>. - Item 3: Consent Agenda - *Item 4: COUNCIL VOTE - GNSO Council Committee for Overseeing and Implementing Continuous Improvement (CCOICI) Recommendations Report on Review of the Statement of Interest (SOI) Requirements * - *Item 5: COUNCIL DISCUSSION - Optional Topics for Potential Council Response* - *(i) Pilot Holistic Review Revised Draft Terms of Reference * - *(ii) Proposed Process for the Retirement of Non-Policy Recommendations * - *(iii) Continuous Improvement Program Community Coordination Group (CIP-CCG)* - Item 6: COUNCIL DISCUSSION - GNSO Liaison to the Governmental Advisory Committee (GAC) Annual Report - *Item 7: COUNCIL DISCUSSION - Diacritics Issue in Latin Script* - *Item 8: ANY OTHER BUSINESS* - 8.1 – Farewell to outgoing Councilors - *8.2 – Update - Open Contracted Party House DNS Abuse Calls* - 8.3 – GNSO Framework for Continuous Improvement Pilot Review - 8.4 – Open microphone (Continuation of anniversary session discussion / input *Under Part 2 Agenda* *Full Agenda <https://community.icann.org/x/tIXxDg>* - *Item 1: Seating of the 2022-2023 Council *INCOMING COUNCILORS: - - *Jennifer Chung*: SOI <https://community.icann.org/x/6AOuAg> Registries Stakeholder Group (RySG) - *Lawrence Olawale-Roberts*: SOI <https://community.icann.org/x/PAF1Aw> Commercial Stakeholder Group (CSG - BC) - *Damon Ashcroft*: SOI <https://community.icann.org/x/WEqAAw> Commercial Stakeholder Group (CSG - IPC) - *Peter Akinremi*: SOI <https://community.icann.org/x/squjBg> Non-commercial Stakeholder Group (NCSG) - *Item 2. Election of the Chair* - One nomination was received for this position from *Gregory DiBiase* of the Contracted Party House. Gregory circulated his candidate statement <https://gnso.icann.org/sites/default/files/file/field-file-attach/dibiase-s…>to the GNSO Council on 5 October 2023. - *Item 3. Election of GNSO Council Vice Chair 2022-2023* - Non-Contracted Party House - TBD - Contracted Party House - TBD - Item 4. ANY OTHER BUSINESS - TBD As usual Council meetings are open to observers; please check the ICANN78 schedule for meeting details and Zoom login links. Thank you for reading / considering. Justine Chew ALAC Liaison to the GNSO GNSO Liaison Report Workspace <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…> ------

1 1