Paul Walsh

ICANN doesn’t care about child protection online

 Posted on April 3, 2007 at 12:42 pm |  By Paul Walsh
 Leave a Comment, 4 Comments so far

ICANN logoICANN, the so-called independent organisation responsible for the coordination of the Internet’s system of unique identifiers (i.e. domains such as .com and .org), has refused an application for a new domain that could have helped to protect children from inappropriate content.

ICANN has voted against the introduction of a new domain called .xxx which would have given the adult industry its own domain. The so-called independent body cited a list of reasons why the application was rejected. However, they didn’t cite ‘how’ it failed to meet their requirements. The application has now been put forward and rejected 3 times.

The idea behind the .xxx domain was simple. Each registered Web site using .xxx would use a Content Label to enable browsers and search engines identify adult orientated content. This would help parents protect their children from potentially harmful content by selecting preferences to exclude all .xxx Web sites from search results.

The application received widespread support from those who know more than anyone, how to protect children from inappropriate content and those of us who specialise in content classification to enable more reliable and relevant search for the future.

On March 30th 2007 I received an email from Stephen Balkam, CEO of the Family Online Safety Institute (FOSI, formally known as ICRA) informing me of the bad news. FOSI’s board represents brands such as AOL, Microsoft, AT&T, BT, Cisco, GSM Association and others. Due to project work, I haven’t been able to write about Segala’s position until now.

In order to declare our relationship, Segala has a licence agreement with FOSI for the provision of Segala-verified services to Web sites that carry an ICRA label. This helps users to differentiate between self-labelled and independently verified Web sites.

A recent news release put out by FOSI includes

We are disappointed by ICANN’s decision not to approve the .xxx domain.
We believe it has missed a great opportunity to increase the use of content labels and thus make filtering and other child protection efforts more effective.

We also regret that the voluntary funding of the International Foundation for Online Responsibility from the .xxx registrations will not now become a reality. Contrary to the ICANN resolution, which erroneously asserts that the .xxx proposal avoids the protection of vulnerable members of the community, the proposal was actually an important self-regulatory effort in the field of online safety, and passing it up only hurts parents and children.

- Stephen Balkam, CEO of FOSI.

I think ICANN has not only demonstrated its lack of understanding in how to protect children online, it has also demonstrated that it is not independent and free of political agendas. It has fallen foul to religious commentators who have the ear of one or two seats in the White House. In my opinion, ICANN should not reside in the US, it should reside with the United Nations, which is completely independent.

What is the answer?

Well, current filtering methods are certainly not the answer as they are extremely limited and mostly ineffective. For example, Internet Explorer uses a very old W3C recommendation called PICS (Platform for Internet Content Selection). To the end user, this is called site advisor and can be found in the options section of the browser’s preferences.

Segala amongst others such as FOIS, Vodafone, T-Mobile and others, feel that Content Labels is much more appropriate. Content Labels is currently going through a W3C Full Recommendation Track to ratify the method as *the* standard for content classification and labelling. Content Labels is also being proposed as a replacement for PICS.

You can read what Jemima Kiss’ has to say on her blog at the Guardian.

There are currently 4 Comments on this post
 Leave a Comment   Listen to this Listen to it   Print it Print it   Share it

4 Comments So far, Leave a Comment.

RSS Feed for comments TrackBack URI

  • April 3, 2007 @ 3:54 pm

    I only read the opening paragraph and my heart sank. A XXX TLD was and still is a fantastic idea, fact that ICANN turned down the application is suspect, upsetting and just plain stupid.

    The importance of such a TLD and the impact it could have had on a new user web experience is huge. With a simple browser restriction porn could be filtered, that’s a cost right now (be it very small) that many end users could afford.

    All ICANN was asked to do in favour of the general wider global audience was introduce a red light district online, box off a corner of the web. By doing so they would have provided choice, a choice to visit and a choice to protect, so I can’t see how they feel their decision is in our interest.

  • 4Avatars v0.3.1
    Paul Littlebury
    flag

    April 3, 2007 @ 3:59 pm

    It does seem highly suspect that an obviously practical move is blocked from an organisation that should at the very least be impartial. Since there is very little defence the adult industry can make against this move, without appearing to condone children accessing adult-oriented material, it does raise several questions. The adult entertainment industry is famously secretive, and we have as yet to see any kind of statements from this industry. From a moral standpoint, these measures to protect children from inappropriate content are totally sound. From a business perspective, it might frighten a few industries, that hard sell on the internet, and want their visibility to be as high as possible, and to as wide an audience as possible.

    The adult entertainment industry, as with drinks, tobacco and pharmaceutical industries have a vested interest in the next generation of users. I have no moral issue with the adult entertainment industry per se, but in terms of their sometimes suspect marketing and target groups, I believe the adult entertainment industry would feel it has more to gain from not having these controls on the web.

    I read the reasons behind the ICANN rejection of proposal, and the reason that stood out for me the most was ………….

    “The ICM Application raises significant law enforcement compliance issues because of countries’ varying laws relating to content and practices that define the nature of the application, therefore obligating ICANN to acquire a responsibility related to content and conduct.”

    My first query back to them is how does implementing a .xxx domain extension and content label, conflict with any law, anywhere? We already have domain extensions that are supposed to help identify website intent - .fm, .name, .ws, .gov.uk, not to mention all the country domain extensions. It seems a very weak argument, and indeed highly suspect of a genuinely practical move.

    Assuming subtext of their response, I would say there were other factors affecting their decision-making, and it is highly likely the decision has been influenced from certain quarters. Exactly which quarters, I could only make am educated guess at. These efforts should improve protection on the web for children, without compromising the freedom of the web, should be applauded and encouraged. And maybe now we need a more truly independant body, who is more aware of modern web issues.

  • April 3, 2007 @ 4:04 pm

    Actually Paul, you have struck a cord. How come they gave the green light to the .mobi domain which DOES mandate specific standards compliance. I know this because Segala helped .mobi better understand how to run such a system. They never mentioned ICANN having to run any sort of control, so why is .xxx any different.

    .mobi and ICANN use the same PR company - I wonder if this has helped…

  • 4Avatars v0.3.1
    flag

    April 15, 2007 @ 9:52 am

    Weekly Rewind

    [...] ICANN doesn’t care about child protection online [...]

Leave a comment


We're constantly spammed by people who have as much life as the robots they use. So, we hope you don't mind if we moderate your comment if it's your first time on this blog.

Please note: Comment moderation is enabled and may delay your comment. There is no need to resubmit your comment.

Live Preview of your comment-

 
Close
E-mail It