New TLDs |
Sponsored by |
|
ICANN has opened their new fast track process for "countries and territories that use languages based on scripts other than Latin" to get domain names that identify the country or territory in its own language. It's not clear to me what the policy is supposed to be for countries whose languages use extended Latin with accents and other marks that aren't in the ASCII set. more
Two sides can oppose each other strenuously and still be wrong in exactly the same way. For or against, too much of the debate about the new ICANN top-level domains (TLDs) ignores TLD signaling and uses inappropriate TLD success measures. Here I spotlight the key mistakes by concentrating on ".biz" registrations, and I put forward some possible remedies. more
There's been a lot of media attention on the new Top-Level Domain (TLD) process in the last few days, which is a good thing. Unfortunately most of it is badly written, misleading or simply misinformed. Let's look at the reality. To start with, there are currently 20 gTLDs i.e. "global" Top-Level Domains (extensions)... more
With the recent attacks against high-profile New Zealand domain names including Coca-Cola.co.nz and F-Secure.co.nz, fingers are naturally pointing to Domainz, the registrar of record for these domains, as the party responsible for this lapse in security. While domain name registrars certainly need to ensure the security and stability of their systems, domain name registries must also step up and take responsibility for mitigating risks posed by hackers... more
ICANN published the second version of its Application Guidebook for new generic top-level domains earlier today (late evening Los Angeles time). Alongside version two of the Guidebook – published by module and in a red-line version – are explanatory memoranda, the opening of a second public comment period (closing 13 April) and an extensive summary and analysis of the public comments made to the process so far. more
As we start the new year, it is worth noting some of the major events and news in 2008 that shaped the industry and fueled considerable discussions. Last year's occurrences made for a very historic year, bearing the seeds of future changes for the DNS and domain name industry. more
According to the draft of new Generic Top-level Domains (gTLD) contracts for Section 7.3, "Price controls have been removed for 2008 in favor of the transparent pricing model outlined above." Section 3.2.b) of the .com registry agreement states: "ICANN shall not apply standards, policies, procedures or practices arbitrarily, unjustifiably, or inequitably and shall not single out Registry Operator for disparate treatment unless justified by substantial and reasonable cause." In my opinion, VeriSign (and other existing gTLD operators) are almost being invited to ask for their contracts to be amended... more
This week ICANN held a public consultation in Washington, D.C., where ICANN's President's Strategy Committee (PSC) solicited remarks from a packed audience of intellectual property (IP) lawyers, domain name registrars and other Internet stakeholders on how the organization can improve institutional confidence. No surprise, ICANN's decision to add new generic top-level domains (gTLDs) to the Internet was on many participants' minds. more
It highly concerns me when domain registries controlling a certain Top-Level Domain (TLD) raise the wholesale prices they charge to registrars (domain retailers) without consultation to domain registrants (domain buyers). When this happens, all the registrars will need to pay more to the registry for every domain which they register or renew for a customer. They will in turn raise their prices to cover the additional cost to them. Transferring the domains to a different registrar will not help, as all the registrars for that TLD will be forced to raise prices as they all have to pay more to the registry. Don't think it hasn't happened before? more
ICANN staff has published a draft report on dispute resolution procedures for IGO (inter-governmental organization) domain names. This proposal has deep flaws and should be rejected by the community, as it does not have the balance and protection of registrant rights present in the existing UDRP. Initially, the proposed policy would apply to new Top-Level Domains (TLDs), but via a Policy Development Process (PDP) it could be extended to existing TLDs. more
ICANN has been wrangling about WHOIS privacy for years. Last week, yet another WHOIS working group ended without making any progress. What's the problem? Actually, there are two: one is that WHOIS privacy is not necessarily all it's cracked up to be, and the other is that so far, nothing in the debate has given any of the parties any incentive to come to agreement. The current ICANN rules for WHOIS say, approximately, that each time you register a domain in a gTLD (the domains that ICANN manages), you are supposed to provide contact information... WHOIS data is public, and despite unenforceable rules to the contrary, it is routinely scraped... more
ICANN has embarked on the IDN boat at the same time it wants to introduce DNSSEC and new gTLDs. This promises lots of fun. Or grey hair, depending how you look at it. First is the issue of country code IDNs. The ISO-3166 table, based on two letter codes, is a western convention. Some cultures do not use abbreviations or acronyms. Some do not use a character-based alphabet, but a syllabic one. Hence, the next logical step would be to represent the full country name in local script, rather than a transliteration of the ISO string... Imagine the case of India, where there are 1.652 languages, of which 24 are spoken by more than one million people... more
If you want to find out the WHOIS server for a particular TLD then in many cases you can do it with a simple DNS lookup. Just query for an SRV record for the domain _nicname._tcp.tld, like this... Many other TLDs follow this convention including .au .at .dk .fr .de .hu .ie .li .lu .nl .no .re .si .se and .ch. more
The ICANN Board voted today 9-5, with Paul Twomey abstaining, to reject a proposal to open .xxx. This is my statement in connection with that vote. I found the resolution adopted by the Board (rejecting xxx) both weak and unprincipled... I am troubled by the path the Board has followed on this issue since I joined the Board in December of 2005. I would like to make two points. First, ICANN only creates problems for itself when it acts in an ad hoc fashion in response to political pressures. Second, ICANN should take itself seriously as a private governance institution with a limited mandate and should resist efforts by governments to veto what it does. more
As an alternative to the creation of the .XXX TLD, ICANN/IANA can assign special port numbers that can be used to label adult content. IANA assigns port numbers as part of its duties. For example, port 80 is reserved for the HTTP protocol (i.e. the World Wide Web). Port 443 is reserved for the HTTPS protocol (SSL-secure version of HTTP). Port 23 is for Telnet, port 25 is for SMTP, and so on. One can see the full list at here... In a real sense, the IANA port assignments are just suggestions to the world as to what to expect on certain ports, whether it be a mail server, WHOIS, FTP, POP email or any other service/protocol. more
A World-Renowned Source for Internet Developments. Serving Since 2002.
