#ICANN84: the churn of GAC reps continues - 32 new GAC reps joined GAC since #ICANN83 in June.
Note: constant turnover of GAC reps means there's always a need for capacity-building. It also means many newbie questions get asked in GAC sessions that otherwise would be deep dives on policy issues.
🎧 #ICANN83 insights from The Com Laude Podcast
✅ Draft Applicant Guidebook breakdown
✅ DNS abuse updates
✅ Registration Data Policy changes
Essential for anyone tracking #newgTLDs or #ICANN policy developments
Listen: comlaude.com/recap-of-ica...
#DNSabuse #domainnames
🎙️ New podcast episode! #ICANN83 recap with key updates:
✅ Draft #ApplicantGuidebook breakdown
✅ #DNSabuse developments
✅ Registration Data Policy changes
Essential listening for TLD applicants & ICANN policy watchers.
🎧 Listen: comlaude.com/recap-of-ica...
#ICANN #newgTLDs
🚨 New Podcast Episode Alert!
We cover key #ICANN83 updates:
✔️ New gTLD Guidebook
✔️Next Round of TLds
✔️ DNS abuse & API controls
✔️ Registration data accuracy, proxy services & more
🎧 Tune in: comlaude.com/recap-of-ica...
#DNSabuse #newgTLDs #ICANN #dotbrand #domainnames #RDRS
📣 Don’t miss out on tomorrow’s recap of the #ICANN83 Policy Forum, hosted by ICANN and CODI founding member eco-Association of the Internet Industry and featuring CODI Chairman Ram Mohan!
Learn more: international.eco.de/event/icann8...
Wrapping up our final day at #ICANN83 in beautiful #Prague! 🏰✨
Thanks to ICANN and to everyone who connected with us, our team has thoroughly enjoyed every moment - from insightful policy sessions to meaningful conversations with industry leaders.
#gTLDs #domainnames
Enjoyed presenting the new RIR Governance Document in Prague and answering questions from the governments of China, India, Russia, Switzerland, and the United States #ICANN83
V. GAC Consensus Advice to ICANN Board The following items of advice from the GAC to the Board have been reached on the basis of consensus as defined in the ICANN Bylaws: 1. Policy Development Related to DNS Abuse a. The GAC advises the Board: To urge the GNSO Council to undertake all necessary preparations prior to ICANN84 towards starting targeted and narrowly scoped Policy Development Processes (PDPs) on DNS Abuse issues, prioritizing bulk registration of malicious domain names and the responsibility of registrars to investigate domains associated with registrant accounts that are the subject of actionable reports of DNS Abuse.
RATIONALE Before new strings are added to the DNS as a result of the next round, further work on DNS Abuse is needed to stem the increasing cost to the public of phishing, malware, botnets, and other forms of DNS abuse. Furthermore, the GAC encourages PDPs that are targeted and clearly scoped to achieve results according to shorter timelines. The GAC appreciates the wealth of proposals for further policy work recently expressed by different parts of the community and maintains they all deserve attention. The GAC supports multistakeholder action to achieve Consensus Policy outcomes and encourages, for the time being, prioritization of specific issues such as malicious use of bulk registrations. Given this timeline, the GAC encourages progress on commencing narrowly-scoped PDPs between ICANN83 and ICANN84.
The #ICANN83 GAC Communique has been put to bed! There is only one piece of consensus advice, regarding DNS abuse. There will now be a 72-hour review period before the Communique is published officially.
Governments erect bulk-reg barrier to new gTLD next round domainincite.com/31131-govern... #icann83 #icann #domains #newgtlds
Proposed #ICANN83 GAC Communique draft consensus advice text on DNS Abuse Policy Development parked for now, so GAC members have more time to review it. GAC moves to draft text (and there is a lot text there!) in the "Issues of importance to the GAC" section.
[Topic Leads: EC, JP, US] 1. Policy Development a. The GAC advises the Board: To direct the GNSO Council to develop and publish an issues report, prior to ICANN84, addressing the following: the bulk registration of malicious domain names; and the ability of registrars to investigate domains associated with registrant accounts that are the subject of actionable reports of DNS Abuse. RATIONALE Before new strings are added to the DNS as a result of the next round, further work on DNS Abuse is needed to stem the increasing cost to the public of phishing, malware, botnets, and other forms of DNS abuse. Further, the GAC strongly supports a significant shift and "step-change" in how PDPs are conducted at ICANN and encourages policy work that is targeted and clearly scoped to achieve results according to shorter timelines. The GAC appreciates the wealth of proposals for further policy work recently expressed by different parts of the community and maintains they all deserve attention. The GAC supports multistakeholder action to achieve Consensus Policy outcomes and encourages, for the time being, prioritization of specific issues such as malicious use of bulk registrations. Given this timeline, the GAC encourages progress on commencing narrowly-scoped PDPs between ICANN83 and ICANN84.
Draft of proposed #ICANN83 GAC Consensus Advice on Policy Development on DNS Abuse currently being looked at by the GAC. This is the first time most GAC members have seen this text (deadline for text submission was only 29 minutes ago), so GAC members still trying to get their heads around the text.
Issues of Importance to the GAC 1. Registration Data a. Registration Data Request System (RDRS) b. b. Urgent Requests for Disclosure of Registration Data c. c. Accuracy of Registration Data 2. DNS Abuse 3. Next Round of New gTLDs a. Implementation Review Team (IRT) b. Applicant Support Program c. GAC Readiness 4. Governance of the Regional Internet Registries 5. Community Statements of Interest (Sol) 6. Deferral of the Fourth ICANN Accountability and Transparency Review (ATRT4) GAC Consensus Advice to ICANN Board 1. Policy Development (related to DNS abuse) Follow up on Previous Advice (None)
Deadline for proposed topics for #ICANN83 GAC communique closed at 9 am Prague time today. This is the list of topics now included for the communique drafting today:
Little interest in cheapo gTLD program domainincite.com/31129-little... #newgtlds #icann #domains #icann83
🗓️ On 6/18, #CODI founding member eco - Association of the Internet Industry joins ICANN to host a virtual discussion with highlights from the #ICANN83 Policy Forum, featuring CODI Co-Founder Ram Mohan.
🔗 to register: international.eco.de/event/icann8...
The #CODI team is in Prague this week for the #ICANN83 Policy Forum, participating in critical discussions around Internet policy with ICANN and global stakeholders.
#OneWorldOneInternet
#ICANN83 GAC/ICANN Board session is beginning in Prague. Topics up for discussion:
1. ICANN Policy Development
2. Registration Data - Accuracy
3. Privacy and Proxy Accreditation
4. Community Statements of Interest
5. Deferral of ATRT4 Review
🔐Na reunión de #ICANN xa estamos entrando en materia: falamos de mellorar a seguridade para todas, complicando as cousas para quen suplantan identidades de empresas ou persoas na rede. #ICANN83 🔐
The team from ICANN staff, has worked very hard with good faith to produce an application program that is available and understandable to any qualified applicant. They have been very true to the policy in the implementation design and kept the notion of equitability in mind and were very receptive to community comments. And yet, I am concerned. Not about the implementation's intent, nor necessarily its design. But rather, I am concerned about the implementation itself. It is not easy, even for some of us who are experienced with ICANN, its lingo, and its way with forms. Those handling the process, are not well trained in the variety of ways things are named and done in the global non profit and service worlds. They do not seem to be flexible in understanding the varieties and features of a deserving applicant. Those who should meet the intent of the policy, but do not have identities, names, or processes that are not Western, i,.e California look alikes, face difficulty. Those processing also do not seem willing or capable of doing the research necessary to understand responses. They reject with statements that the applicants knows are patently false. Perhaps researching answers to understand them is not their inclination nor their job, but they respond with answers, sometimes containing false statements, that need an ICANN translator to understand. ASP applicants need as much assistance with the application for ASP as they will need for the TLD application itself. This does not seem to be available to them. Additionally I am concerned about outreach - there are too few even trying to apply for ASP.
#ICANN83 GAC is meeting with ALAC (At-large Advisory Committee). @avri.bsky.social says she's been helping someone fill out the new gTLD Applicant Support Program form, & even as a longtime ICANN insider, found it confusing; very concerned about targeted groups of applicants giving up completely.
#ICANN83 GAC Chair, following up on community concerns re USA's statement yesterday: "The GAC is not intending to stop the next round of gTLDs [...] I heard many weird questions in that regard, so again, to my knowledge, I have not heard a single GAC member stating anything related to that concept."
Welcome to Day 2 of ICANN in Prague! The .eu team is busy with meeting industry peers and attending sessions, we are pleased to welcome the heart of the Internet to one of the .eu homes! #ICANN83 See you around, colleagues!
#ICANN83 GAC is meeting with the GNSO (Generic Names Supporting Organization) for the next 45 minutes.
Topics for discussion:
- Accuracy of Registration Data
- DNS Abuse
- Registration Data Request Service
- Urgent Requests/Law Enforcement Authentication
#ICANN83 GAC is discussing DNS abuse mitigation first thing this morning. Session info:
@puntogal.bsky.social empeza en Praga unha nova xornada na reunión anual de #icann, o organismo que regula a rede a nivel global. Falamos de seguridade, diversidade linguüística na rede e mantemos reunións para poñer en marcha novas iniciativas e proxectos. #icann83
#ICANN83 Day 2 begins shortly in Prague.
meetings.icann.org/en/meetings/...
I'm participating online from Brisbane, meaning I can enjoy being up close & personal with the local wildlife before the meeting day starts, e.g. this hungry baby cockatoo begging anyone (bird or human) nearby to feed it!
If you're at the #ICANN83, visit our booth. We will be happy to introduce you our main projects #FRED, #KnotDNS or #KnotResolver and you can also take a photo with us. See you at the CZ.NIC booth! #ICANN
US government opposes most new gTLDs domainincite.com/31117-us-gov... #icann #icann83 #newgtlds #domains
I happen to find myself at #ICANN83 this week. Happy to talk to you if you are there too.
#ICANN83 session on #WSIS20 is just beginning. ICANN community perspectives on WSIS can be a little niche (focused mostly on ICANN and IGF), so it'll be interesting to see if this session manages to address the wider context of WSIS.
Excited 🤩 Strategic agreement made Shreedeep Rayamajhi!! Stay tuned for the #DNForum updates!! Helmuts
#ICANN83 #domainindustry #dnformwiki
ISC is out and about this week! Several of our staff members are attending/presenting at #ICANN83 in Prague - if you're there, please say hello to them!