Featured Blogs

Putting Some Circuit Breakers Into DNS to Protect The Net

There are a lot of bad, but smart, people out there on the net. They are quick to find and capitalize on vulnerabilities, particularly those vulnerabilities in mass market software. These bad folks are quite creative when it comes to making it hard to locate and shutdown the computers involved. For example, a virus that takes over a victim's computer might communicate with its control point, or send its captured/stolen information, by looking up a domain name. Normally domain names are somewhat static - the addresses they map to don't change very frequently - typically changes occur over periods measured in months or longer. more

Put Security Alongside .XXX

Isn't security as important to discuss as .XSS? The DNS has become an abuse infrastructure, it is no longer just a functional infrastructure. It is not being used by malware, phishing and other Bad Things [TM], it facilitates them. Operational needs require the policy and governance folks to start taking notice. It's high time security got where it needs to be on the agenda, not just because it is important to consider security, but rather because lack of security controls made it a necessity. more

.COM and .NET: Thick Or Thin?

The fallout from the failure of RegisterFly has been largely addressed as an issue of regulation and enforcement. ...ICANN has not historically enforced the escrow obligation, and in any case, if a company has failed, who exactly is going to take responsibility for updating the escrowed data? It seems to me that the problems that have arisen as a result of RegisterFly's collapse have more to do with the design of the "shared registry system" for the .COM and .NET TLDs than they do with ICANN's failure to enforce the RAA. more

Ongoing Internet Emergency and Domain Names

There is a current ongoing Internet emergency: a critical 0day vulnerability currently exploited in the wild threatens numerous desktop systems which are being compromised and turned into bots, and the domain names hosting it are a significant part of the reason why this attack has not yet been mitigated. This incident is currently being handled by several operational groups. This past February, I sent an email to the Reg-Ops (Registrar Operations) mailing list. The email, which is quoted below, states how DNS abuse (not the DNS infrastructure) is the biggest unmitigated current vulnerability in day-to-day Internet security operations, not to mention abuse. more

When Domain Names Aren’t Enough

A recent trend in the Japanese web advertising market may presage changes that could come to the Western world. ...some advertising in Japan now includes a picture of a filled-in browser search box instead of a domain name. The idea is that an advertiser can buy top-of-page advertising at the main search engines for various terms and then suggest to people reading their print ads to use those terms to search. more

Why I Voted for .XXX

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

Registerfly Victims Are Really Stuck Now

Last week I noted here that cutting off collapsed domain Registerfly will leave a huge problem for registrants. ICANN is supposed to have escrowed copies of each registrar's registrant data, but has never got around to setting that up. This means that unless Registerfly can supply the data, there may be no record of the actual owner of their domains. more

Please, Keep the Core Neutral

Many in the technical community attribute the rapid growth and spread of the Internet to innovation that took place at the "edge" of the network, while its "core" was left largely application neutral to provide a universal and predictable building block for innovation. It is this core neutrality that provides a basis for the security and stability of the Internet as a whole. And it is this same core neutrality that is critical to the continued spread of the Internet across the Digital Divide. Unfortunately, when the politics of censorship rather than solely technical concerns drive the coordination of these "core" Internet resources, it threatens the future security and stability of the Internet. This paper proposes a paradigm upon which all the governments of the world have equal access to these core Internet resources to empower them and their citizens with the rights acknowledged in the WSIS Declaration of Principles. more

Recent COPA Ruling Shedding Light on Usefulness of XXX as Voluntary Self Regulatory Vehicle?

ICM Registry applauds the decision yesterday of Judge Lowell Reed of the United States District Court for the Eastern District of Pennsylvania in ACLU v. Gonzales to permanently enjoin enforcement of the Child Online Protection Act ("COPA"). Praising Judge Reed's meticulously documented opinion, ICM Registry President Stuart Lawley said, "This continues the unbroken chain of court decisions in the U.S. upholding free expression on the Internet, and it underscores the superiority of voluntary measures that empower users to select content compared with government regulations." Lawley concluded, "Now, more than ever, it underscores the need for ICANN to approve the proposal for a voluntary .xxx domain as another alternative to government regulation." more

Whois Policy Reform Advances

The Associated Press reports this week on ICANN developments involving the Whois reform. The Whois database, which displays domain name registrant information including names, addresses, phone numbers, postal and email addresses, has been the subject of years of debate within ICANN as many in the Internet community have expressed concerns about the mandatory disclosure of such personal information. The Generic Names Supporting Organization (GNSO) has successfully pushed for reform, though it is uncertain how the ICANN board will respond. more

An Alternative to .XXX: IANA Adult Port Assignments

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

If ICANN’t Keep a Contract, Let the Public Enforce It

Earlier in the Registerfly controversy, ICANN Vice President Paul Levins posted to the ICANN Blog: "ICANN is not a regulator. We rely mainly on contract law. We do not condone in any way whatsoever RegisterFly's business practice and behaviour." This is disingenuous. ICANN is the central link in a web of contracts that regulate the business of domain name allocation. ICANN has committed, as a public benefit corporation, to enforcing those contracts in the public interest. Domain name registrants, among others, rely on those contracts to establish a secure, stable environment for domain name registration and through that for online content location. more

The Real Problem with dot-XXX

Shakespeare has Marcellus say in Act 1 of Hamlet, "Something's rotten in the state of Denmark." ...Milton Mueller, in his recent post to this site, would have us believe that since ICANN's Board long ago agreed that ICM's application for dot-xxx registry satisfied its own criteria for a sponsored TLD, then the only explanation for all the delay is, "I'm beginning to think that ICANN's approach to TLD approval was cooked up by a demented sergeant from Abu Ghraib." Milton goes on to assert that ICM's claim on dot-xxx is protected by the 1st Amendment. If this is so, then why after more than six years of discussion, is dot-xxx still raising such a fuss? more

Are We Slowly Losing Control of the Internet?

I have long been intrigued by the question of how do we turn the internet into a lifeline grade infrastructure... My hope that this will occur soon or even within decades is diminishing. Most of us observe, almost daily, how even well established infrastructures tend to crumble when stressed, even slightly... I was at the O'Reilly Etel conference last week. The content was impressive and the people there were frequently the primary actors in the creation and deployment of VOIP. However, not once during the three days did I hear a serious discussion by a speaker or in the hallways about how this evolving system would be managed, monitored, diagnosed, or repaired. more

XXX Comes to a Head

Just when you thought the .xxx affair couldn't get any worse, it does. I'm beginning to think that ICANN's approach to TLD approval was cooked up by a demented sergeant from Abu Ghraib... Now, after the triple x people negotiated with ICANN's staff a contract that met all prior objections, and heads into what should be its final approval, word is that a few ICANN Board members are leaning in a negative direction. What is the reason? A group of pornographers has organized a campaign against .xxx, flooding ICANN's comment box with overwhelmingly negative remarks. more