Register.com’s Director of Policy Responds to WLS Issue

Register.com has not taken a position for or against WLS. If and when the registry launches this service, Register.com will consider whether to offer it based on the price and conditions attached to the service. We are committed to delivering to our customers the best in class services available. Therefore, the registry's price will be an important factor. Moreover, we are concerned about some of the conditions currently being considered by ICANN - primarily, the "black out period." This is a period of time prior to the final deletion of a name, during which a registrar would be prohibited from selling a WLS subscription on a domain name that it sponsors. We consider this a condition that could confuse consumers and dampen domain name competition.

WLS & Recourse to the DOC

ICANN's recently posted "Seventh Status Report" states: "ICANN's Board of Directors voted 14-1 to take no action in response to the request, on the grounds that the decision to allow the Wait-Listing Service to be offered was not a threat to competition...".

Several firms that currently offer competing services have signaled (pdf) that they are not in agreement with this assessment.

Is WLS the Right Mechanism to Protect Consumers?

The claim that the *only* way that reliable wait listing can be done by *the* registry is not true. The registrars could, as a technical matter, if they chose to do so, "wrap" the registry with a new entity that mediates all acquisitions and releases. Whether this accords with ICANN's hyper intricate contractual scheme or with laws against restraint of trade, I don't know.

Personally I consider WLS to be contrary to the idea that a contract contains an implied covenant of good faith and fair dealing - it seems to me that WLS violates that implied covenant - It is as if my doctor is selling contracts on parts of my body should I die while under his care.

Domain Registrars File Lawsuit Against ICANN

Members of the Domain Justice Coalition filed a lawsuit today requesting a temporary restraining order and other relief against ICANN to block the implementation of a domain name Wait Listing Service (WLS). The WLS was proposed by VeriSign, Inc. (pdf) and approved by ICANN in federal court in Los Angeles. The suit challenges ICANN's failure to comply with its internal decision-making process requirements when it approved implementation of the WLS in the face of opposition from domain name registrars, resellers and consumers.

Moving Target: Spammer Using Over 1000 Home Computers as DNS

Some individual appears to have hijacked more than a 1,000 home computers starting in late June or early July and has been installing a new Trojan Horse program on them. The Trojan allows this person to run a number of small websites on the hijacked home computers. These websites consists of only a few web pages and apparently produce income by directing sign-ups to for-pay porn websites through affiliate programs. Spam emails messages get visitors to come to the small websites.

To make it more difficult for these websites to be shut down, a single home computer is used for only 10 minutes to host a site. After 10 minutes, the IP address of the website is changed to a different home computer...

ICANN Approves At-Large Framework for Latin America

The Internet Corporation for Assigned Names and Numbers (ICANN) recently launched organizing of the individual Internet user community (At-Large) for increasing global participation and representation in ICANN. Under a framework approved by ICANN's Board of Directors, local and regional groups may now form in Latin America to involve their members in critical issues that effect their use of the Internet's domain name system.

Pool.com Launches ICANN Lawsuit Against WLS

Pool.com has launched a lawsuit challenging the right of the Internet Corporation for Assigned Names and Numbers (ICANN) to proceed with a monopolistic new Wait List Service (WLS) this fall.

In a Statement of Claim filed in the Ontario Superior Court of Justice, Pool.com states that the new "WLS proposed by ICANN and Verisign Inc. will have the immediate and total effect of ending all competition among Registrars for dropped or deleted domain names" in the rapidly developing backordering industry. Pool.com seeks a court injunction preventing ICANN from proceeding with the WLS, a declaration that ICANN's actions constitute intentional and wrongful interference with Pool.com's trade and commercial prospects, as well as significant damages.

Juniper’s IPv6 Advocate Tests Mythology

IPv6 advocacy has been tainted by FUD and half-truth. CommsWorld recently interviewed Juniper's Jeff Doyle, who is a strong supporter of IPv6 -- but who also has little patience for IPv6 mythology. Forget security, half-true address crises and QoS: the best reason for the world to run with IPv6 is what's driven the Internet all along -- innovation.

Analyzing The Inbox of a Spammer’s Domain

Consider this scenario: you need a domain name for your site so you go to your favorite domain registrar's website and upon a quick search find that your third choice is actually available! You quickly pull your credit card and register the name. Everything is good and you can't wait to have your new domain start pointing to your site and represent your official email address. But not so fast -- some of the recent events are revealing that, these days, when you are registering a domain name there is one more critical thing you need to do: check under the hood!

Fight Spam With the DNS, Not the CIA

It seems like spam is in the news every day lately, and frankly, some of the proposed solutions seem either completely hare-brained or worse than the problem itself. I'd like to reiterate a relatively modest proposal I first made over a year ago: Require legitimate DNS MX records for all outbound email servers.

MX records are one component of a domain's Domain Name System (DNS) information. They identify IP addresses that accept inbound email for a particular domain name. To get mail to, say, linux.com, a mail server picks an MX record from linux.com's DNS information and attempts to deliver the mail to that IP address. If the delivery fails because a server is out of action, the delivering server may work through the domain's MX records until it finds a server that can accept the mail. Without at least one MX record, mail cannot be delivered to a domain.