• On ZDNet: Why I Will never buy a Mac
March 18, 2008 12:08 PM PDT

Porn-friendly .xxx domain backer loses suit against federal agencies

by Declan McCullagh

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.
Recent posts from Politics and Law
Report: Guilty verdict overturned in MySpace suicide case
Court: MySpace not liable for offline assaults
New dashboard shows where federal IT tax dollars go
China delays rule for Net-screening software
Amazon positioned to win state tax battle
NY mayor: Info to the people will improve gov't
E-mails indicate EPA suppressed report skeptical of global warming
Pirate Bay judge ruled unbiased
Add a Comment (Log in or register) (15 Comments)
  • prev
  • 1
  • next
But the web is global...
by perfectblue97 March 18, 2008 12:43 PM PDT
I find it stupefying that the internet is a global network yet a US based group can dictate what does and doesn't happen to such an extent.

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.
Reply to this comment
Why would anyone want a xxx domain?
by MTGrizzly March 18, 2008 1:04 PM PDT
The people selling porn on the net are not going to desert
.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...
The IDEAL solution would be to use the .XXX domain!
by markbolden March 18, 2008 1:00 PM PDT
It seems that this would be the ideal situation for both producers
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??
Reply to this comment
The is the government we're talking about.
by Breetai March 18, 2008 1:54 PM PDT
They're idiots. It's not a bush thing it's a US government in general
thing. Kinda like how the masses are stupid but with a sense of superiority.
delusional??
by Dalkorian March 18, 2008 3:10 PM PDT
Maybe a few questions/points will illustrate the issue here:

- 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.
View reply
Require or Allow
by tomj1969 March 19, 2008 12:13 PM PDT
Given the many different countries from which porn sites operate, requiring use of the xxx domain is probably not possible. However, I think the domain would be attractive to pornography site operators - xxx is not an actual movie rating, but producers use it because it lets the users know the nature of the product. Otherwise, how would we know that "Rambone" is not just the story of a vigilante military dog!
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.
View reply
XXX is a Bad Idea
by The_Darklady March 18, 2008 3:01 PM PDT
ICM is in this for its own interests and certainly not those of children, surfers, or the content producers and providers that would be forced into the .xxx ghetto. The adult entertainment industry overwhelmingly condemned the idea and yet we're back to arguing over it again? Why? Because some tech ignorant do-gooders with an agenda think it's easier to marginalize erotic material than provide a .kids area where erotic material wouldn't be allowed? Or is it because parental responsibility has gone the way of the dinosaurs and so outside agencies know what's best? I guess my favorite part of the .xxx insanity is the fact it wants to blackmail domain holders by forcing them to pay ridiculously high registration fees -- with money going to sexual abuse services. Spurious links between consuming sexual content and engaging in sex crimes are insulting to the millions of adults who love porn but have never even dreamed of harming anyone -- but apparently they make some people feel superior... and those people are hoping to cash in on it. That's a unique form of morality, IMO.
Reply to this comment
.XXX is Ideal
by David Mech March 19, 2008 7:54 AM PDT
Just as it makes sense to group non-profit, government, and education sites in .org, .gov, and .edu domains, respectively, it makes sense to classify adult sites in the .xxx domain. This would allow parents to block access to .xxx domains through their browsers where only an unlock code could regain access, and it would also allow ISPs to block .xxx domains upon request. Even if an ISP decided to become the 'moral' ISP and block all .xxx domains to all of their customers, the free market theory would hold that other ISPs would enter the market to meet the demand. .XXX is the ideal solution to make adult content available on the internet, while restricting access to children. Everybody wins.
Reply to this comment
I'm with you...
by tomj1969 March 19, 2008 12:05 PM PDT
It would be the online version of having adult clubs and bookstores confined to a "red light" district that could be easily avoided by families. I am at a loss as to why anyone would see identifying these sites with a particular domain would be harmful.

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...
.sex Considered Dangerous
by dlindbergh March 19, 2008 8:05 AM PDT
http://www.ietf.org/rfc/rfc3675.txt
Reply to this comment
The problem is
by b_baggins March 19, 2008 9:16 AM PDT
the second half of your equation. Forcing all porn providers to use
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.
Reply to this comment
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....
Reply to this comment
(15 Comments)
  • prev
  • 1
  • next
advertisement

Making sense of Windows 7 upgrades

faq The basics and the fine print on Microsoft's options for those eyeing the next operating system from Redmond.
• Full Windows 7 coverage

Road Trip 2009: Big Sky Country

CNET News reporter Daniel Terdiman takes his car full of gadgets to the Rockies and the Great Plains in search of tech, science, nature, and more.
• America's Fortress: Cheyenne Mountain

About Politics and Law

News at the intersection of technology, politics, and law, ranging from intellectual property to censorship to tech policy.

Add this feed to your online news reader

Politics and Law topics

advertisement
advertisement

Inside CNET News

Scroll Left Scroll Right