As previously noted, the U.S. Senate Committee on Commerce, Science, and Transportation today held a full committee hearing on ICANN's expansion of top level domains (TLDs). The hearing was held to examine the merits and implications of the program and ICANN's efforts to address concerns raised. ICANN will begin accepting applications for new TLDs on January 12, 2012. more
The primary focus of this article is to illustrate that the Applicant Guidebook is not supplying sufficient protection mechanisms, and creates too high financial barrier for those who are interested in applying for multiple Top-Level Domains (TLDs) that are translations/transliterations of each other and/or of an existing generic Top-Level Domains (tt-gTLDs). more
New top-level domain applicants are getting plenty of advice nowadays about how to launch their new Registry. In addition to thinking about their branding and distribution, they should also be thinking about their business practices with Registrars. What many of them do not realize is that their cash flow practices, with respect to Registrars, may be a factor of whether ICANN Registrars even support their Registry. more
The Internet Corporation for Assigned Names and Numbers (ICANN) has officially reserved the top-level domain ".INTERNAL" for private-use applications. This decision follows years of technical evaluations, public consultations, and inter-organizational discussions. more
Tech pundit John Gruber threw in the towel on his domain ?df.ws. He writes: "What I didn't foresee was the tremendous amount of software out there that does not properly parse non-ASCII characters in URLs, particularly IDN domain names." more
I recently caught up with a former colleague Antony Van Couvering. Many here on CircleID probably know him, he's been active in the domain name business since the late 1990's. With the new Top-Level Domain (TLD) issue so white hot and with Antony's firm right in the mix, I thought it was time to get his take via an interview. If anyone has questions (or challenges perhaps?) to anything below, I'm happy to forward to Antony for a response. more
When Steve delBianco from NetChoice testified (April 2, 2014) in the Subcommittee on Communications and Technology of the US House of Representatives on "Ensuring the Security, Stability, Resilience, and Freedom of the Global Internet", he proposed a stresstest for new mechanisms which could substitute the role of the NTIA in overseeing the IANA contract with ICANN. Stresstests are good. It is good for cars, it is good for banks and it is good for new mechanisms... more
Back on February 4, 2013, I wrote a CircleID post entitled 'How the registrar Cash Flow Model Could Collapse with New ICANN gTLDs.' My key point back then was this: new gTLD applicants need to be mindful of how the cash flow policies of their registry (and of their back-end service provider) could impact whether their TLD is actively promoted by ICANN registrars... registries have historically assumed near-zero risk. This is going to change. more
Recently a proof of concept attack was announced on the Internet that demonstrated how a web address could be constructed that looked in some web browsers identical to that of a well known website. This technique could be used to trick a user into going to a website that they did not plan on visiting, and possibly provide sensitive information to a third party. As a result of this demonstration, there has been a number of voices calling for web browsers to disable or remove support for IDNs by default. ...CENTR, a group of many of the world's domain registries - representing over 98% of domain registrations worldwide - believes such strong reactions are heavily detrimental... more
On May 26, 2021, I submitted a complaint to ICANN's Complaints Officer, Krista Papac. In a nutshell, my complaint centers on ICANN's blatant violation of its Bylaws, specifically Section 2.2, named Restrictions, which expressly prohibits ICANN from acting as a registrar. However, despite the absence of any exceptions to this unambiguous prohibition, ICANN is acting improperly as a registrar for the purposes of warehousing and cybersquatting on certain domain names in the .com and .net registries. more
This is the fifth part of a multi-part series reported by ICANNfocus. This part focuses on Securing the Quality of WHOIS Data. "Information for which ICANN has responsibility includes the WHOIS databases. ICANN has been given specific responsibilities for these databases under: 1) their contract with the U.S. government's Department of Commerce to perform the technical management of the Internet; and 2) their Memorandum of Understanding with the Department of Commerce." more
Section 3.18 of the ICANN 2013 Registrar Accreditation Agreement (RAA) contains language requiring registrars to investigate and respond to abuse complaints. Nearly one year into the new RAA's effective period, what do we know about Section 3.18? If a person or entity wants to submit a complaint, what should they keep in mind? This article reviews the meaning of Section 3.18, how to leverage it, offers a list of do's and don'ts for complainants, and offers a few recommendations for registrars. more
ICANN Board of Directors today approved a new Domain Name Registrar Accreditation Agreement (RAA) following over a year of negotiations between ICANN and its Registrar Stakeholders Group - last RAA was approved in 2009. more
The voluntary Public Interest Commitments (PIC) have a long and sad history at ICANN. They were a process never created or evaluated by the Multistakeholder process, thrown together for one purpose and allowed to morph into a mechanism for an almost unlimited number of un-reviewed other purposes. Disputes are delegated to a resolution process which itself was never evaluated for... more
On December 1, 2014 the Cross Community Working Group (CWG) on Naming Related Functions published a Draft Transition Proposal. The comment period on the Proposal extended for twenty-one days; due to a requirement imposed by the separate IANA Coordination Group (ICG) that a final proposal be received by mid-January, there was no provision for a follow-up reply comment period as is standard ICANN Practice for issues of far less consequence. more