Nov 7, 2024 - by Lauren Tracey
Register for our upcoming ICANN webinar scheduled for November 21st, 2024, at 12 PM EST (9 AM PST, 5 PM GMT), where we break down all the announcements and insights we gathered.
ICANN81 is just around the corner, kicking off on November 9, 2024, in Istanbul, Republic of Türkiye. Though we cannot predict all the subjects, ICANN81 will be filled with critical discussions and updates on important issues facing the domain community. While developments on the next round of new gTLDs will be a primary focus, attendees can also look forward to insights on the Registry Data Request Service (RDRS) program, DNS abuse mitigation, and an exploration of what future new gTLD application rounds may look like. Here is what we expect the key takeaways to be so you can stay ahead of the curve:
A topic in pre-ICANN81 discussions has been the enforcement of new Domain Name System (DNS) abuse mitigation measures. These requirements compel contracted parties to address issues such as malware, botnets, phishing, pharming, and spam associated with these activities. A report presented during the pre-ICANN81 sessions showed that, in the first half of 2024, 192 DNS abuse investigations were launched, resulting in two formal breach notices and the suspension of over 2,700 domains involved in abusive behavior. ICANN81 will provide further updates on enforcement efforts and explore proactive monitoring initiatives to bolster compliance.
With the mandatory phase-out of WHOIS services by January 28, 2025, attention has shifted to the implementation of RDAP (Registration Data Access Protocol). ICANN81 will feature sessions and workshops addressing technical and content-related challenges that hinder RDAP lookups. Additionally, attendees will see demonstrations of the ICANN RDAP Conformance Tool, which aids registrars and registry operators in self-assessing and improving their RDAP services.
The next New gTLD application round remains on track, with the application window slated to open at the beginning of Q2 2026.
The ICANN Board has approved the Applicant Support Program (ASP) handbook, now available in all ICANN-supported languages. This is a crucial milestone in the timeline for the next round of new gTLDs, as it was decided for this round that the applicant support application had to run prior to the owning of the application for new gTLDs.
The ASP is for those individuals/businesses who want to own and operate a TLD but may not have the initial operation funds, it is also targeted at businesses from underrepresented regions. The ASP, funded with up to $5 million from the 2012 auction proceeds, is set to open for applications on November 19, 2024, and will run for 12 months.
Additionally, the Registry Service Provider (RSP) evaluation period, which must precede the opening of the new gTLD round, will commence on November 19, 2024, and conclude in May 2025. The Registry Service Provider (RSP) evaluation period is when back-end registry operators are evaluated for their readiness to manage and provide services for new gTLDs. One crucial milestone in the timeline for the next round of new gTLDs is the recent publication of the RSP handbook, detailing eligibility criteria, a code of conduct, and terms and conditions. The initial evaluated list of RSPs is expected to be released by December 2025.
In sessions leading up to ICANN81, the community has shown interest in considering a transition from the round-based application model, which was used for the last application period in 2012, and the upcoming application period, to a continuous application process, which would allow for a continuously open opportunity to apply for new gTLDs.
ICANN81 will explore the pros and cons of this shift, with a focus on applicant support, operational challenges, and alternative policy models and timelines.
As the Registry Data Request Service (RDRS) pilot program marks its first anniversary, ICANN81 will feature sessions evaluating its progress, user feedback, and plans for future development. As a reminder, this pilot sets to standardize handling requests to access nonpublic registration data related to gTLDs. These discussions will delve into key metrics such as request volume, approval rates, common denial reasons, and feedback from requesters and registrars. Pre-meeting insights highlighted the need for stronger authentication measures and suggested potential system enhancements, including request category revisions, improved help text, and the inclusion of WHOIS information. The Generic Names Supporting Organization (GNSO) Standing Committee, the group that helps to create and update policies for gTLDs, will present its recommendations for the future of standardized access and disclosure, leveraging lessons learned from the RDRS pilot.
Recent posts from Lauren Tracey