DNS |
Sponsored by |
The U.S. "Scorecard" for Brussels Proposes Draconian Trademark Rules - And May Mean the End of Unlimited New gTLDs and/or the ICANN Experiment in Private Sector-Led Internet Governance... On Friday, January 28th the U.S. Department of Commerce (DOC) circulated its submission to ICANN's Governmental Advisory Committee (GAC) containing suggestions for what positions the GAC should push for at its February 28 - March 1 meeting with ICANN's Board to air disagreements over provisions of the Proposed Final Applicant Guidebook (AG) for new gTLDs. more
I consult on communication issues for Neustar, an Internet infrastructure company. As most CircleIDers know, Neustar works behind the scenes to ensure the smooth operation of many critical systems like DNS, .us and .biz, local number portability and digital rights management. One of the cool things about working for them is the chance to attend the events they sponsor. Last week Neustar held a security briefing for senior federal IT personnel focused on Cybersecurity and Domain Name System Security Extensions (DNSSEC)... more
One of the most disastrous things that could happen to the DNS would be for the root to "split", as it would mean that identifiers would no longer be universal. Instead, "Example.com" would have totally different meanings for different users, substantially reducing the benefits of domain names. Can this happen? Important lessons for ICANN can be learned by studying the history of Rod Beckstrom, Twiki and Foswiki. more
The ICANN Board and GAC will be having a meeting in Geneva next month to resolve outstanding issues in connection with the new gTLD implementation process. Unfortunately to date details of whether this meeting will be open or closed to observers has not yet been publicly addressed. As a strong advocate toward openness and transparency I have drafted the following text which calls for the meeting to be open to observers. more
Internationalized domain names (IDNs) have been available to Internet users for many years, but this year the first fully non-Latin IDN domains have become enabled by ICANN and country-code top-level domain registries. The recent success of the launch of Russia's .?? (.rf) ccTLD shows that there is an enormous demand for domain names in Internet users' native languages. more
We have just returned from the Brussels, Belgium ICANN meeting where we released our Registrar audit, the Internet "Doomsday Book." There are many topics covered in the report, but we wanted to follow up specifically on the issue of WHOIS access and add data to our previous column Who Is Blocking WHOIS? which covered Registrar denial of their contracted obligation to support Port 43 WHOIS access. more
The proposed final Guidebook for the New generic Top-Level Domains (gTLDs) and Internationalized Domain Name (IDN) gTLDs contains elements that raise grave risks to the ICANN single root of the Internet caused by none other than ICANN itself. Below is my intervention at the ICANN Cartagena Public Forum today. ICANN President and CEO Mr. Rod Beckstrom was prompt to reply and acknowledge the validity of my statement adding that ICANN is fully aware of the problem. more
Yesterday CommunityDNS noticed a sudden, heavy spike in traffic through its Anycast node in Hong Kong. While comfortably processing queries at 863,000 queries per second for close to 2 hours the occurrence was undeniable. While we can't say the increase in traffic was specifically due to DDoS, its sudden increase is suspicious and reminds us that DDoS is still a popular tool used by the malicious community. more
As many of us in the Internet community gear up for the ICANN meeting in Colombia next week, it's important to remember that not everybody embraces the multi-stakeholder approach that we've gradually learned to love. Just a month ago, a group with a very different vision of how to run things wrapped up their own Internet governance meeting in Latin America. Their meeting was three times as long and accomplished about a third as much, but they'd still like to see their model replace the ICANN model. more
History is a great teacher, we are told. So, on the cusp of an explosion in new top-level domains, what can we learn from the two previous expansions of the Internet's naming space? And what are the pitfalls to avoid? Let's just assume the fundamental and obvious lessons of realistic expectations, a solid business plan and prudent resource management, and instead focus on the little talked about but still critical lessons that will separate the winners and the losers in this race. But first - a caveat! more
This visual depicts about half of the currently approved internationalized domain names (IDNs), positioned over their respective regions. Notice the wide range of scripts over India and the wide range of Arabic domains. I left off the Latin country code equivalents (in, cn, th, sa, etc.) to illustrate what the Internet is going to look like (at a very high level) in the years ahead. more
May 6th 2007: ARIN board of trustees passes a resolution advising the Internet community that migration to a new version of the internet protocol, IPv6, will be necessary to allow continued growth of the internet. June 29th 2007, Puerto Rico: ICANN Board resolution states that: The Board further resolves to work with the Regional Internet Registries and other stakeholders to promote education and outreach, with the goal of supporting the future growth of the Internet by encouraging the timely deployment of IPv6. Oct 26th 2007 at the RIPE 55 meeting in Amsterdam... Nov 15th 2007: IGF meeting, Rio de Janeiro... This is but a small sample of the fast growing visibility IPv6 acquired this year, 2007. more
The new guidebook represents an enormous step forward for the new Top-Level Domain program for a number of key reasons. As we have commented previously, the naming convention as the 'Final' guidebook is of significant importance and reinforces the ICANN Board's intention to get to the finish line with the program. Of equal importance however, is that the number of changes from the previous version of the guidebook is relatively small and focus on a few key issues which shows that the end is indeed near. more
Following up from my post yesterday, I thought I would take a look at how spammy each particular TLD is. At the moment, I only track 8 TLD's - .cn, .ru, .com, .net, .org, .info, .biz and .name. To check to see which one is the spammiest, I took all of our post-IP blocked mail and determined how many times those messages occurred in email, and how many times that email was marked as spam... more
A couple of weeks ago, NetworkWorld published an article indicating that the .com TLD was the riskiest TLD in terms of containing code that can steal passwords or take advantage of browser vulnerabilities to distribute malware... It is unclear to me what they mean by TLD's being risky. The number of domains, 31.3% of .com's being considered risky, what does this actually mean? Is it that 31% of .com's are actually serving up malware or something similar? If so, that seems like a lot because for many of us, nearly 1 in every 3 pages that most people visit would be insecure... more