Whois

Why FOISA Should Never Become Law

In a recent issue of the Wall Street Journal, I noticed an underreported story about an embarrassing glitch that occurred involving the "washpost.com" domain name, which is used by the Washington Post Newspaper Company. Apparently, recently, the domain name stopped working -- no domain name services. This disrupted the flow and access of e-mail at the Washington Post as well as the operations of the washpost.com website.

ICANN and the Data Quality Act: Part II

This is the second part of a multi-part series reported by ICANNfocus. This part discusses the congressional concerns regarding ICANN's governance of the Internet. "Since 1999 Congress has repeatedly expressed serious concerns regarding ICANN's governance of the internet. Congress has substantial responsibility for overseeing the key aspects of internet governance. Among its specific responsibilities, Congress has the duty to oversee implementation of the Department of Commerce's Memorandum of Understanding (MOU) and contract with ICANN."

Using Whois to Enforce Law?

Before starting I'd like to remind you that there are two distinct Whois systems -- the one for IP address delegations and one for DNS registrations. I believe that the former is a useful system in which there are clear utility values that outweigh the privacy costs, and in which the person whose privacy is exposed has made a knowing choice. I do not believe that these arguments apply to the latter, the DNS, form of Whois.

Privacy Alert: Watch Out For FOISA

This morning, at 10 am in 2141 Rayburn, the Subcommittee on Courts, the Internet, and Intellectual Property is holding a hearing on "Internet Domain Name Fraud -- New Criminal and Civil Enforcement Tools." At that hearing, the Subcommittee will be considering a new Whois bill creating new penalties for people who provide false data when registering a domain name. We need to raise our collective eyebrows at this bill (which was suddenly dropped the evening before this hearing). The title of the bill is the "Fraudulent Online Identity Sanctions Act." (FOISA)

ICANN on Closing Off Port 43

ICANN has launched three task forces on WHOIS restructuring...It sounds innocuous enough -- nobody likes spam -- but the restrictions being discussed reach further than marketers. Pushed by registrars who feel that WHOIS amounts to forced disclosure of their customer lists, the task force is seriously discussing closing off port 43's straightforward access to WHOIS information, replacing it with GIF-based barriers or similar access restrictions.

ICANN, WSIS and the Making of a Global Civil Society - Part I

This is the first part of a two-part series interview by Geert Lovink with Milton Mueller discussing ICANN, World Summit on the Information Society, and the escalating debates over Internet Governance. Read the second part of this Interview here. Geert Lovink: "Would it make sense to analyse ICANN (and its predecessors) as a test model for some sort of secretive 'world government' that is run by self appointed experts? Could you explain why governments are seen as incapable of running the Internet? This all comes close to a conspiracy theory. I am not at all a fan of such reductionist easy-to-understand explanations. However, the discontent with 'global governance' discourse is widespread and it seems that the International Relations experts have little understanding how the Internet is actually run. Where do you think theorization of Internet governance should start?"

What is WSIS Getting At?

Attacks on ICANN are coming from several different directions, and the list of concerns includes "cybercrime and protection of intellectual property rights."... First, it's not apparent to me that any government can "control" the internet -- and it's even less likely that that control can happen through the DNS. The most that governments will do will be to build walls between nations, requiring their ISPs to point only to approved sites. (China is well on its way to doing this already.) That's not controlling the Internet, that's creating different, national Internets.

An Unsanctioned Whois Database

Mark Jeftovic of easyDNS Technologies Inc. has posted an item on ICANN's "GNSO" registrars' mailing list titled "unsanctioned Whois concepts". In that item he suggests that the control and actual publication of contact information about a domain be put into the zone file itself, a file maintained by the registrant (purchasor) of the domain name.

Lobbying for Whois Privacy

Today a letter was submitted to the President of ICANN, Paul Twomey, at the ICANN Carthage meeting, "asking him to ensure that strong privacy safeguards, based on internationally accepted standards, are established for the WHOIS database." Latest reports indicated that the draft letter had been signed by about 50 nonprofit groups and represented 21 countries on six continents. "Signers of the letter included the American Library Association, the U.S. Association for Computing Machinery, the Australian Council for Civil Liberties, Electronic Frontier Finland, Privacy Ukraine, and the United Kingdom's Foundation for Information Policy Research."

Is Industry Underestimating the Ending Dot?

According to RFC1034, "cnn.com" and "cnn.com." should be the same domain names. However, it doesn't appear that programmers always understand that trailing dots can be added to domain names. Web servers also can't seem to agree what to do with a period at the end of a host name. IIS, thttp, and Akamai's Web server all get confused while Apache doesn't seem to care. How much other software behaves incorrectly because of a trailing period on a domain name? Can spam-filtering software be bypassed with dotted email addresses? Here is a situation when bad things can happen -- "WebShield SMTP infinite loop DoS Attack"...