New RFC Considers .sex TLD Dangerous

Posted by michael on Friday March 19, 2004 @11:33AM from the sex-with-sue-almost-as-dangerous dept.

netcentric writes "A post on CircleID has reported about an RFC prepared by Donald E. Eastlake 3rd and Declan McCullagh, CNET News.com's Washington D.C. correspondent, analyzing proposals from various parties to mandate the use of special top level domain names (such as .sex or .xxx) or an IP address bit to flag 'adult' or 'unsafe' material or the like. The analysis explains why these ideas are dangerous and ill considered from legal, philosophical, and technical points of view. Here is the post to this report on CircleID along with some commentaries and link to the entire RFC 3675."

1 of 421 comments (clear)

Min score:

Reason:

Sort:

.cum TLD by glavenoid · 2004-03-19 15:46 · Score: 1, Offtopic

I can't believe someone posted this before me! I've been pushing the .cum TLD with the IETF ever since I discovered that there is porn on the internet... Which was last week... When I felt lonely...
Seriously though, every time one mistypes a URL, one invariably winds up at a pr0n site. If porn had its own TLD, perhaps this might change.
(Pppffffttttt. Yeah right!) At least it might make it easier to find quality porn on the net ;)

--
I, for one, am looking forward to the inevitable /. beta rollout fallout.