Re: [DNSOP] Last Call: (The .onion Special-Use Domain Name) to Proposed Standard

2015-08-07 Thread Jacob Appelbaum
On 8/7/15, Edward Lewis wrote: > On 8/7/15, 10:29, "DNSOP on behalf of Wendy Seltzer" > wrote: > >>You might find https://spec.torproject.org/ helpful as a listing of >>various tor specs and design documents, if you prefer that to a git >>repository. > > That's the site I've been using. > What d

Re: [DNSOP] reservations on reservations, was Barry Leiba's Abstain

2015-09-01 Thread Jacob Appelbaum
On 9/1/15, John R Levine wrote: >>> In any event, from the point of the DNS, a reservation that just says >>> don't resolve .onion would be quite adequate. >> >> You may consider the privacy leakage issues of no consequence. Others do >> not. > > Please do not put words in my mouth. They're

Re: [DNSOP] a long way from reservations on reservations, was Barry Leiba's Abstain

2015-09-01 Thread Jacob Appelbaum
On 9/1/15, John R Levine wrote: >>> Please do not put words in my mouth. They're important but they're not >>> a >>> DNS problem. >> >> I think reasonable people might disagree? > > Not really. It's a layering issue. It is a design flaw from an era when fax machines roamed the earth. >> In my

Re: [DNSOP] a long way from reservations on reservations, was Barry Leiba's Abstain

2015-09-01 Thread Jacob Appelbaum
On 9/1/15, John R Levine wrote: > Speaking of which ... > >> It is a critical flaw that fails open. The DNS continues to work but >> users are put into harm's way. ... > >>> Also please keep in mind that we're having this discussion because of >>> design tradeoffs in the implementation of Tor. If

Re: [DNSOP] DNS privacy, recursive-to-authoritative

2015-09-03 Thread Jacob Appelbaum
On 9/2/15, Paul Vixie wrote: > > > John R Levine wrote: >> ... >> >> Tor is one approach to query security that seems to work pretty well >> give or take side channel leakage. Dunno if there are any others, but >> it is clearly a very hard problem, and not one we're going to solve >> any time soo

Re: [DNSOP] DNS privacy, recursive-to-authoritative

2015-09-03 Thread Jacob Appelbaum
On 9/3/15, John R Levine wrote: >> Until the invention of quantum computers, we can protect data from >> being instantly available to most of these groups most of the time. > > Aw, come on. There are root servers in China. > I'm much more worried about the root servers run by people who also dep

Re: [DNSOP] Some thoughts on special-use names, from an application standpoint

2015-11-29 Thread Jacob Appelbaum
On 11/29/15, Philip Homburg wrote: >>.onion was the chosen approach precisely because nothing else but lookup >> and s >>ubsequent routing has to change; there are no other application-level >> decision >>s about .onion, and that's a feature. HTTP still works, TLS still works >> (once >>you can ge

Re: [DNSOP] Some thoughts on special-use names, from an application standpoint

2015-11-29 Thread Jacob Appelbaum
Hi, On 11/29/15, Philip Homburg wrote: >>> The purpose of the domain name system is to name things. We have IP >>> addresses and we want to refer to them using names. We do the same thing >>> with mail domains, etc. >> >>That is not the sole purpose - we use DNS for keys, for time stamps, >>for d

Re: [DNSOP] [internet-dra...@ietf.org: I-D Action: draft-grothoff-iesg-special-use-p2p-names-00.txt]

2013-12-06 Thread Jacob Appelbaum
SM: > Hi Stephane, > At 09:53 01-12-2013, Stephane Bortzmeyer wrote: >> RFC 6761 does not say anything about that. Do note a TLD has already >> been registered under RFC 6761, .local. Some people may say that, when >> you are a big US company, just hijack the TLD, deploy the software, >> and the IE

[DNSOP] discussion for draft-appelbaum-dnsop-onion-tld-00.txt

2015-03-16 Thread Jacob Appelbaum
--- Forwarded message -- > From: internet-dra...@ietf.org > Date: Fri, 06 Mar 2015 17:25:10 -0800 > Subject: New Version Notification for draft-appelbaum-dnsop-onion-tld-00.txt > To: Jacob Appelbaum , Alec Muffett > > > A new version of I-D, draft-appelbaum-dnsop-onion-t