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.
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.
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 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.
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.
ICANN continues at its snail's pace on introduction of new top-level domains. At the Montreal meeting, staff sprung this RFP for new sponsored TLDs. As if "a few" and "sponsored" weren't limitation enough, it further narrowed the applicant pool to those who had applied unsuccessfully as sponsored TLDs in November 2000.
ICANN has just submitted its seventh status report under ICANN/US Government Memorandum of Understanding to United States Department of Commerce (DoC) titled: "Report by ICANN to United States Department of Commerce Re: Progress Toward Objectives of Memorandum of Understanding". The report provides a review of recent ICANN developments including...
The Internet Corporation for Assigned Names and Numbers (ICANN) concluded its Montreal meeting with a landmark agreement that cements the relationship between ICANN and the worldwide community of country-code top-level domain registries. "Today's agreement represents both a historic achievement for the ICANN process, and a powerful vote of confidence in the newly reformed ICANN 2.0," said Paul Twomey, ICANN's president and CEO.
Finalizing four years of dialogue and negotiation, the creation of the Country-Code Names Supporting Organization (ccNSO) heralds a new era of cooperative and productive relations among ICANN and the country-code domain registries. The structure and rules for ICANN's new ccNSO were endorsed by domain registry organizations and individual managers representing every region and populated continent. "Today's agreement is a testament to how ICANN is seen as a forum the international Top Level Domain administrators can come together and jointly address issues," said Twomey.
John LoGalbo - a "law enforcement" type - is complaining how long it takes him to issue a subpoena. My thought is this: Why should our privacy suffer because his organization can't get its procedural act together?
I am incensed - he is simply stating a conclusion that his targets are "criminals" and that, to go after them, he wants to throw away all legal processes and procedures - so much for the fourth, fifth, sixth, and fourteenth amendments.
I'm going to try something new here. I'm sitting here at the ICANN meeting on whois and I'll try to jot down some of my thoughts as they occur to me in reaction to what is being said:
- What is the "purpose" of whois? When a person acquires a domain name he/she has a decision to make: whether he/she will give the vendor/registrar his/her personal information? (If not, the person might have to forego getting the name, but that's his/her choice.) It seems that that is the context in which we need to evaluate the "purpose" of whois. In other words, the person relinquishes the information for the purpose of acquiring a domain name and not the broad panopoly of uses that have grown around whois.