Comments:ICANN approves .xxx domain for pornography

Back to article

This page is for commentary on the news. If you wish to point out a problem in the article (e.g. factual error, etc), please use its regular collaboration page instead. Comments on this page do not need to adhere to the Neutral Point of View policy. Please remain on topic and avoid offensive or inflammatory comments where possible. Try thought-provoking, insightful, or controversial. Civil discussion and polite sparring make our comments pages a fun and friendly place. Please think of this when posting.

Use the "Start a new discussion" button just below to start a new discussion. If the button isn't there, wait a few seconds and click this link: Refresh.

The Internet is for porn, the internet is for porn,
Grab your dick and double click for PORN PORN PORN,
PORN, PORN, the internet… the internet… the internet is for PORN!!!

http://www.youtube.com/watch?v=T-TA57L0kuc

isolation of xxx materials under the control of dns is consistent with Miller v California

Unfortunately, it's not consistent with the basic principles of the Internet.

I was going to write a long and detailed explanation of why .xxx is a profoundly stupid idea, but RFC 3675: .sex Considered Dangerous has already done it. Anyone who thinks this is okay doesn't understand the Internet. And if they don't understand the Internet, what business do they have making decisions about it? This really should be the last straw for ICANN: they need to pack up shop and be replaced with a group of wise Unixy neckbeard types who won't do stupid stuff like think content filtering can work at the DNS level.

The article says it will be voluntary. And the article you linked to is from 2004; technology has changed a lot in the past 6 years. I for one take comfort in knowing that my kids will have a harder time encountering explicit material than when I grew up.

They won't though. The reasons explained in RFC 3675 are still valid today. Either the filtering will be completely ineffective or it may actually allow one to confuse filtering software by creating phony A records. If filtering software just filters requests to .xxx domains, it is trivially easy to retrieve the IP address of the server from a third-party source and send a request that way, ignoring the DNS altogether. This is why when Wikileaks lost their domain, you could still access it using their IP address.

If it filters by IP and just uses the .xxx zone files to know where to find 'naughty' IPs, then there is a trivial attack one can do: you register a .xxx domain and point it to a third-party site you want to get filtered even though it isn't pornography. Someone will do this and a legitimate site like, I dunno, wikipedia.org or whitehouse.gov will become inaccessible because someone has pointed an unrelated .xxx domain at it.

Trust me, the more you think about .xxx, the sillier it gets. I've been thinking about it since it was first mooted and it really is ridiculous.