Re: [dns-privacy] New Version Notification for draft-bretelle-dprive-dot-for-insecure-delegations-01.txt

2019-03-28 Thread Tony Finch
> >> This proposal actually reminds me a lot of idea I had that actually > >> used DS records instead of new record type. > >> > >> AFAIK: > >> - DNSsec ignores any such record (unknown algorithm) > >> -> No interference with DNSsec. > >> - CDS does not ignore such records. > >> -> Automated

Re: [dns-privacy] New Version Notification for draft-bretelle-dprive-dot-for-insecure-delegations-01.txt

2019-03-28 Thread Peter van Dijk
Hello, On 24 Mar 2019, at 18:45, manu tman wrote: This proposal actually reminds me a lot of idea I had that actually used DS records instead of new record type. AFAIK: - DNSsec ignores any such record (unknown algorithm) -> No interference with DNSsec. - CDS does not ignore such records.

Re: [dns-privacy] New Version Notification for draft-bretelle-dprive-dot-for-insecure-delegations-01.txt

2019-03-24 Thread Ilari Liusvaara
On Sun, Mar 24, 2019 at 06:45:31PM +0100, manu tman wrote: > Thanks Ilari, > > > > This proposal actually reminds me a lot of idea I had that actually > > used DS records instead of new record type. > > > > AFAIK: > > - DNSsec ignores any such record (unknown algorithm) > > -> No interference

Re: [dns-privacy] New Version Notification for draft-bretelle-dprive-dot-for-insecure-delegations-01.txt

2019-03-24 Thread manu tman
Thanks Ilari, > This proposal actually reminds me a lot of idea I had that actually > used DS records instead of new record type. > > AFAIK: > - DNSsec ignores any such record (unknown algorithm) > -> No interference with DNSsec. > - CDS does not ignore such records. > -> Automated

Re: [dns-privacy] New Version Notification for draft-bretelle-dprive-dot-for-insecure-delegations-01.txt

2019-03-24 Thread Ilari Liusvaara
On Sat, Mar 23, 2019 at 12:58:46AM +, Reed, Jon wrote: > Iā€™m glad to see this proposal, I find it personally preferable to the > dnscurve-esque proposal with the base32-encoded NS names. In both > cases, however, the examples assume that the nameservers are in > bailiwick for the zone. This

Re: [dns-privacy] New Version Notification for draft-bretelle-dprive-dot-for-insecure-delegations-01.txt

2019-03-23 Thread manu tman
gt; > > > > *From: *manu tman > *Date: *Monday, March 11, 2019 at 12:52 PM > *To: *"dns-privacy@ietf.org" > *Subject: *[dns-privacy] New Version Notification for > draft-bretelle-dprive-dot-for-insecure-delegations-01.txt > > > > > > D

Re: [dns-privacy] New Version Notification for draft-bretelle-dprive-dot-for-insecure-delegations-01.txt

2019-03-22 Thread Reed, Jon
From: manu tman Date: Monday, March 11, 2019 at 12:52 PM To: "dns-privacy@ietf.org" Subject: [dns-privacy] New Version Notification for draft-bretelle-dprive-dot-for-insecure-delegations-01.txt During earlier discussion (post virtual meeting), there were a mixture of feeling as to

[dns-privacy] New Version Notification for draft-bretelle-dprive-dot-for-insecure-delegations-01.txt

2019-03-11 Thread manu tman
During earlier discussion (post virtual meeting), there were a mixture of feeling as to where SPKI may be published, here is one proposal bump (through the rush of time) to publish it in the parent zone. Manu ā€”ā€”ā€” A new version of I-D, draft-bretelle-dprive-dot-for-insecure-delegations-01.txt