{"id":54197,"date":"2016-09-30T11:27:00","date_gmt":"2016-09-30T16:27:00","guid":{"rendered":"https:\/\/content.findlaw-admin.com\/ability-legal\/supreme\/legal-commentary\/time-for-a-xxx-internet-domain.html"},"modified":"2016-09-30T11:27:00","modified_gmt":"2016-09-30T16:27:00","slug":"time-for-a-xxx-internet-domain","status":"publish","type":"supreme","link":"https:\/\/supreme.findlaw.com\/legal-commentary\/time-for-a-xxx-internet-domain.html","title":{"rendered":"Time For A .xxx Internet Domain?"},"content":{"rendered":"\n
\n \n
\n
\n \n \n \n \n \n\n \n \n
<\/a><\/td>\n

Time For A .xxx Internet Domain?<\/h1><\/td>\n <\/tr>\n

By ERIC J. SINROD<\/h2><\/a><\/td>\n <\/tr>\n

Thursday, Dec. 29, 2005<\/td>\n\n <\/tr>\n <\/table>\n

Let’s face it — adult content, including explicit sexual pornography, runs rampant on the Internet. Internet users can implement specific searches looking for such content, and normally they will find what they are looking for. Other times, people inadvertently will stumble onto such explicit content when searching for something else; indeed, a domain name may give one the impression that the site is suitable for a general audience of all ages, only to turn out that it displays graphic sexual content that is inappropriate for minors or adults not wishing to view such content. So, what to do?<\/p>\n\n\n\n\n\n\n\n\n

One proposed concept has been a .xxx Internet domain for sexually-oriented Web sites. Just like .com is designed for businesses, .gov for government, and .edu for educational institutions, the idea behind .xxx is that there would be a specific domain name category for adult Web sites with sexual content. In that way, an Internet user easily could judge, based on seeing a .xxx domain name, whether the user truly wanted to visit such a site to view adult content, or if the user wanted to avoid visiting and seeing such content. <\/p>\n\n\n\n

The Internet Corporation of Assigned Names and Numbers (ICANN) is awaiting recommendations from a particular committee that is evaluating this proposal. ICANN had been proceeding with its evaluation of the proposal, until the Commerce Department sought more time to hear objections. ICANN cannot move forward without Commerce Department approval. At this point, it is not clear when the proposal will be fully and finally evaluated. <\/p>\n\n\n\n

The proposal has had its share of critics. Some of them claim that a .xxx domain would provide legitimacy to the pornography industry. Supporters claim that a .xxx domain would make it easier for people to filter out content they do not want. <\/p>\n\n\n\n

Time will tell in terms of where this all is heading. Your humble author believes that information is power. Namely, if one knows in advance the type of content displayed on a Web site by way of a domain name designation, that individual then has the power and free will to decide whether or not to view that content. In your author’s mind, that is better than stumbling onto content that does meet one’s suitability and taste. <\/p>\n\n\n\n<\/span>\n\n\n\n\n\n\n

\n\n

\n\n\n\n\n\n<\/a>\n\nEric Sinrod is a partner in the San Francisco office of Duane Morris (www.duanemorris.com<\/a>), where he focuses on litigation matters of various types, including information technology and intellectual property disputes. His Web site is (www.sinrodlaw.com<\/a>), and he can be reached at ejsinrod@duanemorris.com. To receive a weekly e-mail link to Mr. Sinrod’s columns, please send an e-mail with the word Subscribe in the Subject line to ejsinrod@duanemorris.com. This column is prepared and published for informational purposes only and should not be construed as legal advice. The views expressed in this column are those of the author and do not necessarily reflect the views of the author’s law firm or its individual partners.\n\n

\n\n\n\n<\/p>\n\n\n\n\n\n\n\n\n<\/div>\n\n\n

\n \n Was this helpful?<\/span>\n \n Yes<\/span>\n \n \n \n <\/path>\n <\/g>\n \n \n <\/rect>\n <\/clipPath>\n <\/defs>\n <\/svg>\n <\/i>\n <\/button>\n \n No<\/span>\n \n \n \n \n <\/g>\n \n \n \n <\/clipPath>\n <\/defs>\n <\/svg>\n <\/i>\n <\/button>\n <\/div>\n <\/span>\n