[Chapter-delegates] Input Request: DNS Blocking

[Franck Martin]

As there are solutions out there to do it already (opendns), as Internet Society we should tell which solutions are not breaking the infrastructure and which ones do.

A kind of "if you have to do it, this is how it should be done"

As a rights person, then we can point out that blocking is not the solution, and in a manner as "Guns don't kill people, people kill people", indicate that behind a DNS block there is a real person, making a real crime in reality. This is where our efforts should be. Curing the cause and not the symptoms.

One disastrous effect (to be used as example) is the great wall of Australia, which some calculated cost 20k per user to implement (I cannot find the reference anymore but remember it)
http://en.wikipedia.org/wiki/Internet_censorship_in_Australia
http://www.youtube.com/watch?v=-b7vdmFOxyg
http://www.youtube.com/watch?v=0B7Mp8fSvNs

There has been some talk about using DNSBL to also block access to web sites. This has always been discouraged by the email industry.

Franck Martin 
http://www.avonsys.com/ 
http://www.facebook.com/Avonsys 
twitter: FranckMartin Avonsys 

Check your domain reputation: http://gurl.im/b69d4o 


----- Original Message -----
From: "Joly MacFie" <joly at punkcast.com>
To: "Marcin Cieslak" <saper at saper.info>
Cc: "Chapter Delegates" <chapter-delegates at elists.isoc.org>
Sent: Tuesday, 18 January, 2011 10:57:59 AM
Subject: Re: [Chapter-delegates] Input Request: DNS Blocking

Whether filtering/blocking  is desirable or advisable is a matter for
civil societies in sovereign nations. I think the Internet Society has
to recognize that.  We can advocate for freedom but we can't insist.
What we can insist is that such blocking/filtering be done without
monkeying with protocols such as DNS which is, in effect. spoofing.
And suggest, at least, transparency.

j