What is the current state of DNSSEC deployment around the world and also in Africa? How can you deploy DNSSEC at a massive scale? What is the state of using elliptic curve crypto algorithms in DNSSEC? What more can be done to accelerate DNSSEC deployment? Discussion of all those questions and much more can be found in the DNSSEC Workshop streaming live out of the ICANN 55 meeting in Marrakech, Morocco, on Wednesday, March 9, from 9:00 to 15:15 WET. more
If the timeline for turn-around of clarifying questions (CQs) remains two-weeks, the long pole in your CQ tent is likely to be revising your Q50 letter of credit or escrow agreement to meet the ICANN requirements. Based upon ICANN comments, it appears that many applicants are having trouble meeting the specific letter of credit (LOC) or escrow agreement language. To remedy this ICANN should consider publishing what it considers acceptable language for an LOC or escrow agreement. more
ICANN is barking up a number of wrong trees with the latest version of its Evaluation and Questions Criteria for generic top-level domains (gTLDs). The document asks for financial projections, the applicant's goals for its TLD, and the benefits the applicant expects to derive. All that information is meaningless. more
Since ICANN's CEO announced (on Twitter) that he would be leaving in July 2012, the Internet has been abuzz with details on what happened and why. Rod Beckstrom's tenure so far has earned praise and criticism, much of the latter dwelling on his management style, and on the rate of turnover in ICANN's staff since his appointment. As for the praise, it was implicit in the official announcement put out by ICANN on 16 September, with a link to a list of the outgoing CEO's achievements. Many in our community have a vivid recollection of the criticism leveled at Beckstrom, during a plenary session in an ICANN international meeting, by Maria Farrell, a former staff member. more
One of the largest domain name registrars, NameCheap, on Monday filed a Request for Reconsideration with regards to ICANN's recent decision to remove historical price caps for the .org top-level domain (TLD) from the Public Interest Registry (PIR) contract. more
Now just more than a quarter of the way into the pilot program, ICANN's Registration Data Request Service (RDRS) again will be the subject of intensive discussions during the ICANN80 meeting in Kigali in early June. This includes further consultations hosted by the Commercial Stakeholder Group (CSG) and including registrars, data requestors and ICANN Org. more
Let me begin by saying that I am big supporter of ICANN. But good grief ICANN, why must the ENTIRE new gTLD process be so painful? I could run through a long list of all the delays, missteps and glitches, but why bother? It's almost comical at this point -- although not for 1,930 new gTLD applicants who have been waiting for ICANN to get their act together. First we were led to believe that the batching of applications was necessary due to resourcing constraints, which I personally never understood as the evaluation of applications is being done be third-party consultants. more
Yesterday, I sent ICANN my comments about the draft recommendations from ICANN’s Implementation Recommendation Team (IRT), which has been tasked with coming up with a trademark protection scheme for new top-level domains. For the most part, I think they did an excellent job... more
ICANN is currently seeking public comment on the subject of "closed generic" Top Level Domain (TLD) applications. A "Closed Generic" is a TLD that is a generic term, but domains within that TLD will not be sold to the public. There are those who object to generic terms such as .book being operated as closed registries, which means that domain names within the .book Top Level Domain as proposed by Amazon would not be sold to the public, but instead, Amazon.com would own and operate all domain names within the .Book Top Level Domain. more
I am skeptical about how ICANN has arrived at a technical limit of a thousand new TLDs per year. The ICANN study driving this number must be made public so that our industry's risk management experts can size up the finding. Why am I skeptical? more
ICANN is the only institution with responsibility for the functioning of DNS. And so it is natural that when there is a DNS problem for people to expect ICANN to come up with the solution. But having the responsibility to act is not the same as having the ability. Like the IETF, ICANN appears to have been designed with the objective of achieving institutional paralysis. And this is not surprising since the first law of the Internet is 'You are so not in charge (for all values of you). more
Wales, a small Celtic country that has proudly withstood the depredations of Anglo-Saxons, Normans, and tourists, which has given the world everything from an enduring mythology to the world's longest single-world domain name, has been informed that they will not be allowed to proceed with .CYM (short for the Welsh name for Wales, Cymru) because that three-letter code is already claimed by the Cayman Islands. more
Yesterday ICANN announced that its new CEO Fadi Chehade accepted ICANN Chief Strategy Officer Kurt Pritz's resignation over conflict of Interests -- will a transparent investigation follow? Otherwise, what else and what next? In a statement on its ICANN website, Fadi Chehade states: "Kurt has submitted his resignation because of a recently identified conflict of interest". more
In an announcement at a registrars meeting in Tokyo on October 19th 2010, JPRS announced that they would be offering generic Top-Level Domains (.com, .net, .org, etc.) to their .jp accredited registrars in the near future. JPRS is already famous for their double-dipping practices, acting as both registry and registrar for .jp domains, for their dubious "campaigns" which are aimed at being dis-advantageous to smaller registrars and for their famous registrar back-end "system" which is circa 1995 technology and even prone to accidental DOS attacks by registrars trying to simply drop-catch domains. more
About two years ago I wrote with concern about Bit.ly's use of Libya's country code. I noted that It's always important to keep in mind that a company can't "own" a domain the way it owns real estate. Now it appears that companies that have built brand names on Libya's country code are facing difficult times. more