Re: [DNSOP] Draft on censorship, and DNS

2015-05-01 Thread Stephane Bortzmeyer
On Fri, Nov 07, 2014 at 08:39:31AM -0800, Stephane Bortzmeyer wrote a message of 14 lines which said: > There is an Internet-Draft "A Survey of Worldwide Censorship > Techniques" draft-hall-censorship-tech-00 which is on the agenda of > the Security Area Open Meeting next week at IETF 91 Honol

Re: [DNSOP] Draft on censorship, and DNS

2014-11-09 Thread Alejandro Acosta
Hi Stephane, El 11/9/2014 a las #4, Stephane Bortzmeyer escribió: > On Sun, Nov 09, 2014 at 12:09:15AM -0430, > Alejandro Acosta wrote > a message of 45 lines which said: > >> Recently I published a post in my personal blog an article -in >> Spanish- called something like: "The bad idea of b

Re: [DNSOP] Draft on censorship, and DNS

2014-11-09 Thread hellekin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 11/09/2014 06:35 PM, Phillip Hallam-Baker wrote: > > If you want to do anything useful in counter-censorship then you have > to think of using steganography > *** If you use steganography, that probably means you're sending secrets over a cleart

Re: [DNSOP] Draft on censorship, and DNS

2014-11-09 Thread Paul Vixie
> David Conrad > Sunday, November 09, 2014 11:38 AM > Another argument for DNS-over-443. +1. -- Paul Vixie ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop

Re: [DNSOP] Draft on censorship, and DNS

2014-11-09 Thread Phillip Hallam-Baker
If you want to do anything useful in counter-censorship then you have to think of using steganography So don't call it DNS and don't put the parts of the plan designed for counter censorship prominently in the draft Port 443 is loaded with censorship issues. If you want to get your packets pa

Re: [DNSOP] Draft on censorship, and DNS

2014-11-09 Thread David Conrad
Another argument for DNS-over-443. I think the slogan "F* it, just put it into the DNS" should probably be modified to: "F* it, just put it into the DNS over HTTPS" Sigh. Regards, -drc On Nov 8, 2014, at 11:07 PM, dikshie wrote: > Hi, > In Indonesia case: > 1.Government asks everyone that M

Re: [DNSOP] Draft on censorship, and DNS

2014-11-09 Thread dikshie
Hi, In Indonesia case: 1.Government asks everyone that MUST use ISPs' DNS servers. No third party DNS servers are allowed (for example: Google's DNS). Although I am not sure about the real implementation, ISPs will redirect DNS request traffic from customers to their DNS servers. 2.ISPs' DN

Re: [DNSOP] Draft on censorship, and DNS

2014-11-09 Thread Patrik Fältström
> On 9 nov 2014, at 06:13, Danny McPherson wrote: > > As well as in SSAC's SAC056: > > https://www.icann.org/en/system/files/files/sac-056-en.pdf And let me add to this pointed to by Danny also SAC-050 which is a two page document setting a baseline.

Re: [DNSOP] Draft on censorship, and DNS

2014-11-08 Thread Stephane Bortzmeyer
On Sun, Nov 09, 2014 at 12:09:15AM -0430, Alejandro Acosta wrote a message of 45 lines which said: > Recently I published a post in my personal blog an article -in > Spanish- called something like: "The bad idea of blocking Internet". On the censorship via DNS, there is also the very good [

Re: [DNSOP] Draft on censorship, and DNS

2014-11-08 Thread Danny McPherson
On 2014-11-07 09:39, Stephane Bortzmeyer wrote: There is an Internet-Draft "A Survey of Worldwide Censorship Techniques" draft-hall-censorship-tech-00 which is on the agenda of the Security Area Open Meeting next week at IETF 91 Honolulu. I applaud the effort, I've reviewed the DNS part and I fi

Re: [DNSOP] Draft on censorship, and DNS

2014-11-08 Thread Alejandro Acosta
Hi Stephane, Thanks for bringing this up, actually it's a great draft, I was not aware of it. Recently I published a post in my personal blog an article -in Spanish- called something like: "The bad idea of blocking Internet". It's about the problem that is left after performing the blocking, th

[DNSOP] Draft on censorship, and DNS

2014-11-07 Thread Stephane Bortzmeyer
There is an Internet-Draft "A Survey of Worldwide Censorship Techniques" draft-hall-censorship-tech-00 which is on the agenda of the Security Area Open Meeting next week at IETF 91 Honolulu. I applaud the effort, I've reviewed the DNS part and I find it of low quality, with sloppy terminology. I s