Porn-friendly .xxx domain backer loses suit against federal agencies
The company behind the proposed .xxx top-level domain, which was rejected after the Bush administration intervened, has been trying to dig up embarrassing government documents through a federal lawsuit.
Make that "was trying." A federal judge on March 12 granted summary judgment to the Bush administration in the Freedom of Information Act lawsuit brought by the ICM Registry.
By way of background, ICM Registry had proposed the porn-friendly .xxx domain in 2004 to the Internet Corporation for Assigned Names and Numbers, four years after ICANN rejected the idea the first time. In June 2005, ICANN approved .xxx--but the Bush administration objected two months later, and ICANN's board subsequently reversed itself by a 9-5 vote.
ICM Registry's Stuart Lawley, an indefatigable entrepreneur who made his fortune by founding a U.K. Internet service provider, didn't give up. He filed a FOIA request to learn how conservative groups pressured the Bush administration, and he released the first round of documents in May 2006. But the State Department and Commerce Department withheld others--claiming they were part of an internal "deliberative process"--and those are the documents at issue in the current lawsuit.
Robert Corn-Revere, an attorney at Davis Wright Tremaine who is representing ICM Registry, said a lawsuit against ICANN for denying the .xxx top-level domain is now possible.
"ICM Registry is planning to examine and pursue all of its legal options," Corn-Revere said Tuesday. "We were waiting to see what the outcome of this FOIA litigation was."
ICM had argued that if there's reason to suspect government misconduct such as improper influence by Focus on the Family et al., the documents should be turned over straightaway (this is known as the misconduct exemption).
U.S. District Judge James Robertson in Washington, D.C., sided in part with ICM, saying that argument would be valid if the administration "opposed .xxx for nefarious purposes" but that none had been demonstrated. Robertson, however, didn't actually read the withheld FOIA'd documents for himself, which is something that ICM could raise, if it chooses to appeal.
The key part of Robertson's ruling is:
Whatever the boundaries of the misconduct exception, they cannot be as expansive as ICM declares them to be...Absent some showing that consideration of domain name and Internet policy is outside these departments' and agencies' domains--and none has been made--or that they opposed .xxx for nefarious purposes, their action is not misconduct within the meaning of the exception to the deliberative process privilege.
If the government "leaned on"? ICANN or any other decision maker that it did not directly control, (its) policy choice to do so is discoverable under FOIA. That choice (if it was made) was not "political abuse," however, and so the deliberations that underlay it are properly exempt from disclosure.
Descriptions of some of the documents that were not released certainly make their contents sound intriguing. One is a State Department staffer's response to a Wall Street Journal article about alternatives to the domain name system; others deal with meetings between the State Department and a delegation from Japan.
On the Commerce Department side, the documents--again, these have not been released in full--include:
- Document EP59: This is an e-mail containing a Commerce employee's opinions regarding the effects of a .xxx domain on children's access to pornography.
- Document EP61: This reflects the opinions of Commerce Department employees on the effects of .xxx on children's access to pornography and on what Web sites would be in a .xxx domain.
- Documents EP90-92: These are part of an e-mail chain, and the redactions relate to the opinions of Commerce employees on how to present Commerce's role in making changes to the authoritative root zone file to the public.
Documents EP125-126: These are e-mails, and the redactions include the opinions of a Ms. Atwell on the roles of ICANN and Commerce in the approval of the .xxx domain, and her opinions regarding control of children's access to pornography. (By Atwell, this presumably means Meredith Atwell Baker, then the deputy assistant secretary for communications and information in the National Telecommunications and Information Administration.)
- Documents EP46, EP98: These are e-mails from which questions and opinions of White House employee Helen Domenici have been redacted. These include the status of .xxx approval, as well as opinions regarding approval. (Domenici is listed as Assistant Associate Director for Telecommunications and Information Technology (PDF) in the White House's Office of Science and Technology Policy.)
- Documents 000001-000007: These are all drafts of a document entitled "USG/DOC Options Regarding GAC Consideration of the Proposed .xxx Domain." (Because it's not a final policy and contains options not acted on, the judge ruled, it can't be obtained through FOIA.)
- Documents 000008-000010: These are all drafts of a document entitled "USG Opinions for Including .xxx in the Authoritative Root Zone file."
- Document 000016: This is a draft entitled "USG Procedural Options Regarding the Creation of .xxx"
- Document 000019: This is a draft entitled "The Department of Commerce's Role in Additions to the Internet Domain Name System Authoritative Root Zone File."
To be sure, the Commerce and State Departments did release a good number of documents in redacted and non-redacted form. Corn-Revere said: "I expect we will be releasing the other documents we have."
But those additional files could have provided a valuable glimpse into how much pressure conservative groups applied--and into what the U.S. government thinks of ICANN and its own role in approving new domain name suffixes. Unfortunately, given the limitations of FOIA and a judge who was unwilling to go along with ICM's arguments, we may never know the whole story.
Declan McCullagh, CNET News' chief political correspondent, chronicles the intersection of politics and technology. He has covered politics, technology, and Washington, D.C., for more than a decade, which has turned him into an iconoclast and a skeptic of anyone who says, "We oughta have a new federal law against this." E-mail Declan. 





Surely this should be an international matter. Why should Europeans, for example, be denied an XXX domain just because a US body doesn't want US citizens to have one.
ICANN needs to be both neutral and international in order to serve the wider world interest.
.com, et cetera domains they have spent years building up. If all
"porn" was required to migrate to the XXX top level domain,
who will decide what is "porn"? Who will decide who gets the
appropriate .XXX domain names? Why should we put one type
of content in a ghetto, when it is simply an exercise of
protected speech?
The idea that all porn will migrate to a XXX top level domain is
ludicrous.
This is not about wanting a XXX top level domain. This is about
the guy selling the XXX top level domain wanting to make
money. Money is universal and not limited to the US...
of pornographic sites and parents/businesses who need to filter
content. This would most likely attract the producers of such sites
to migrate their domains just so they can focus their efforts on
their target markets (consumers who LOOK for that type of
content). It would also allow content filtering at the .XXX domain
level for businesses and parents. Am I the only one looking at it
from this perspective??
thing. Kinda like how the masses are stupid but with a sense of superiority.
- define "porn" (careful here - how much nudity counts? Do lingerie sites like Victoria's Secret count as "porn"? How about
artist and photographer sites? Are portrayed/filmed sexual acts
porn? What about simulated acts, like many R rated films? What
about Wikipedia? Are pages like this "porn" - http://en.wikipedia.org/wiki/Sexual_intercourse?)
- define who is responsible for "forcing" "porn" from the .com
domain to the .xxx domain
- define who is responsible for "policing" the .com domain to
ensure there is no "porn" there
Keep in mind that the porn sites have had .com names for a
while now (years and years) and some of them might be
reluctant to give that up (remember that they paid cash money
for a .com domain). I would venture a guess that most of them
would rather make an alias to the .xxx domain and KEEP the
.com name, hence the last 2 points made above (who's going to
force them and who's going to ensure they comply?)
Fuhrer bushit actually got this one right (although I *SERIOUSLY*
doubt he had the right reasons). It's simply unenforceable.
If the domain is set up and allowed for use by porn sites, I would expect that the vast majority, if not all, of the new sites would use it. Many of the existing sites trying to boost traffic would also be likely to switch to it. The remaining successful sites would be much easier to filter, as it would probably be pretty stagnant.
The question of REQUIRING pornography sites to use the xxx domain is a more complicated question, imo. In real life, zoning laws can restrict purveyors of adult entertainment and products to specific areas. Given the global nature of the internet, limiting pornography sites to the xxx domain would not be possible unless enacted as law or regulation by the specific country from which the site operates. Additionally, from the perspective of countries with free speech rights, such a law or regulation may be illegal to enact.
I would expect successful existing pornography sites would want to stick with their current .com or other domain name. However, for a new or struggling site, I would venture that .xxx would help market or popularize the site.
Unfortunately, Bush seems content to have porn sites under the same domain as family sites. Maybe the xxx domain would make it harder for him to hide the sites he visits from Laura...
that domain. We've already bastardized the first amendment in the
U.S. to the point where it applies to everything except what it was
originally intended, political speech. There was can castrate it like
crazy. (Campaign finance). But if you want to take a picture of a
bullwhip up some pervert's ***, that's first amendment.
- Agree-- easier to filter
- by Dæmon March 22, 2008 9:02 PM PDT
- I think it would be best, a restriction should be placed to keep the material off of all domains except for .xxx and then parents/businesses can more easily ban it. On the other hand it proves just how much the porn-industry has grown and how popular it is, having its own domain....
- Like this Reply to this comment
-
(15 Comments)