On Mon, Oct 20, 2014 at 06:10:08PM -0700,
Paul Vixie p...@redbarn.org wrote
a message of 383 lines which said:
there are three points in the dns communication mesh where surveillance
is possible:
1. stub to recursive
2. recursive to authoritative
3. zone maintainance
I am not happy
[Copy to dnsop since the qname minimisation draft is now a WG item at
dnsop.]
On Thu, Oct 23, 2014 at 10:21:57AM -0700,
David Conrad d...@virtualized.org wrote
a message of 56 lines which said:
http://www.google.com/patents/EP266A1?cl=en
Well, some resolvers (the programs which will
On Oct 25, 2014, at 2:03 PM, Phillip Hallam-Baker ph...@hallambaker.com
wrote:
The claims are broad, not specific to one field of use.
But there isn't a patent yet and they may have been waiting to file after
grant.
It is possible for someone other than the IPR holder to file but
stephane, you make a very important distinction:
Stephane Bortzmeyer mailto:bortzme...@nic.fr
Saturday, October 25, 2014 2:03 AM
On Mon, Oct 20, 2014 at 06:10:08PM -0700,
Paul Vixie p...@redbarn.org wrote
a message of 383 lines which said:
there are three points in the dns communication
Stephane Bortzmeyer mailto:bortzme...@nic.fr
Saturday, October 25, 2014 2:24 AM
[Copy to dnsop since the qname minimisation draft is now a WG item at
dnsop.]
On Thu, Oct 23, 2014 at 10:21:57AM -0700,
David Conrad d...@virtualized.org wrote
http://www.google.com/patents/EP266A1?cl=en
Paul,
It is a VeriSign patent, its just being shown on the Google patent serach
engine
On Sat, Oct 25, 2014 at 1:53 PM, Paul Vixie p...@redbarn.org wrote:
Stephane Bortzmeyer bortzme...@nic.fr
Saturday, October 25, 2014 2:24 AM
[Copy to dnsop since the qname minimisation draft is now a
On Friday, October 17, 2014, Warren Kumari war...@kumari.net wrote:
Dear DPRIVE WG,
This starts a Call for Adoption for draft-bortzmeyer-dnsop-dns-privacy.
[ Please note: I am assuming that Stephane and DNSOP are both OK with
us adopting this. It is referenced in our charter, and so might
Dear all,
Let's imagine that we actually want to make it hard for anyone to
figure out what data is being requested via DNS. DNSCurve won't work:
the nameservers involved learn what the request is and who made it.
Combining it with DNSSEC+ISP cache also won't work: the ISP learns
what you
On Sat, Oct 25, 2014 at 10:35 PM, Watson Ladd watsonbl...@gmail.com wrote:
On Sat, Oct 25, 2014 at 7:04 PM, Phillip Hallam-Baker
i...@hallambaker.com wrote:
I think that we have to go back to the original goal, to reduce leakage
of
information so that we only disclose where there is a need
