[dns-privacy] Issues with encoding keys in nameserver DNS names

2018-12-10 Thread Mukund Sivaraman
There was some discussion in last night's meeting about encoding keys in the DNS name of a nameserver, similar to DNSCurve. There are at least some issues with it: 1. The RDATA of an NS record has to be a hostname, so it would limit the amount of data that can be encoded within the NSDNAME. As an

[dns-privacy] Sample experiments for resolver->auth privacy transport

2018-12-10 Thread Mukund Sivaraman
Hi all Some ideas on how to practically test resolver->auth secure transport was asked during yesterday's dprive meeting. Here are some examples to test. Simulate the case of queries for names in the DNS that are hosted topologically farthest away from the tester. Assume the test is conducted in

Re: [dns-privacy] DNS PRIVate Exchange (dprive) WG Virtual Meeting: 2018-12-10

2018-12-10 Thread Tim Wicinski
I see dialing info of 1-650-479-3208 Call-in toll number (US/Canada) Access code: 640 873 331 I am digging up alternative numbers. On Mon, Dec 10, 2018 at 9:18 AM Henderson, Karl wrote: > Is there a dial-in number for the dprive webex meeting today? >

Re: [dns-privacy] DPRIVE Phase 2 Milestones and Requirements for WG Virtual Meeting 2018-12-10

2018-12-10 Thread Erik Nygren
On Sat, Dec 8, 2018 at 12:46 PM Benno Overeinder wrote: > > For now, you are invited to review and add content to the wiki page: > https://trac.ietf.org/trac/dprive/wiki/DPriveStage2 > I unfortunately won't be able to attend today due to a prior conflict. After some discussing with some

Re: [dns-privacy] DPRIVE Phase 2 Milestones and Requirements for WG Virtual Meeting 2018-12-10

2018-12-10 Thread Loganaden Velvindron
On Sat, Dec 8, 2018 at 9:47 PM Benno Overeinder wrote: > > [Same email, different header to assure email did not disappear in > original thread. Sorry for spamming.] > > Hi all, > > On 28/11/2018 15:19, Brian Haberman wrote: > > The main focus of this interim will be item #3. Benno & Alex

[dns-privacy] Question regarding RFC 7858

2018-12-10 Thread Hans Carlos Hofmann
Hello, i have try to implement DoT ... but the part of authenticate the Certificate is not consistence. What to hell of Certificate i have to use whit the port 853 tls server? The Problem is: TLS need a Nameserver name to work correct while you need a Ip-Number so Start DNS translation. On

Re: [dns-privacy] [Ext] DNS PRIVate Exchange (dprive) WG Virtual Meeting: 2018-12-10

2018-12-10 Thread Brian Haberman
Hi dkg, On 12/10/18 9:55 AM, Daniel Kahn Gillmor wrote: > On Wed 2018-12-05 10:35:20 -0500, Brian Haberman wrote: >> I think it would be quite useful if someone were to explore the use of >> message layer security in the context of DNS. That could be one of the >> ones you listed above or it

Re: [dns-privacy] DNS PRIVate Exchange (dprive) WG Virtual Meeting: 2018-12-10

2018-12-10 Thread Barry Greene
Will the meeting be recorded? ___ dns-privacy mailing list dns-privacy@ietf.org https://www.ietf.org/mailman/listinfo/dns-privacy

Re: [dns-privacy] DNS PRIVate Exchange (dprive) WG Virtual Meeting: 2018-12-10

2018-12-10 Thread Brian Haberman
On 12/10/18 10:46 AM, Barry Greene wrote: > Will the meeting be recorded? > Yes. I will record the session via Webex and work with the secretariat to get the recording posted. Regards, Brian signature.asc Description: OpenPGP digital signature

Re: [dns-privacy] [Ext] DPRIVE Phase 2 Milestones and Requirements for WG Virtual Meeting 2018-12-10

2018-12-10 Thread Paul Hoffman
On Dec 10, 2018, at 6:37 AM, Erik Nygren wrote: > After some discussing with some colleagues, a few topics that came up which I > added to the wiki for discussion: The changes you added all assumed that TLS was going to be the protocol chosen. I have edited (hopefully politely) to indicate

Re: [dns-privacy] [Ext] DPRIVE Phase 2 Milestones and Requirements for WG Virtual Meeting 2018-12-10

2018-12-10 Thread Benno Overeinder
Thanks all for your input. As a reminder, the virtual call is via webex: https://ietf.webex.com/meet/dprive -- Benno On 10/12/2018 16:50, Paul Hoffman wrote: > On Dec 10, 2018, at 6:37 AM, Erik Nygren wrote: >> After some discussing with some colleagues, a few topics that came up which >> I