Re: [dns-privacy] [Fwd: [EXT] New Version Notification for draft-vandijk-dprive-ds-dot-signal-and-pin-01.txt]

2020-07-20 Thread Peter van Dijk
Hello Paul, On Thu, 2020-07-16 at 15:29 -0400, Paul Wouters wrote: > On Mon, 13 Jul 2020, Peter van Dijk wrote: > > > please find below revision -01 of our proposal for enabling DoT from > > resolver to authoritative. > > DoT can be enabled regardless. This draft is not about enabling DoT. I

Re: [dns-privacy] [Fwd: [EXT] New Version Notification for draft-vandijk-dprive-ds-dot-signal-and-pin-01.txt]

2020-07-20 Thread Peter van Dijk
Hi Duane, On Tue, 2020-07-14 at 22:13 +, Wessels, Duane wrote: > Hi Peter, > > While I remain neutral as to whether or not ds-dot-signal-and-pin is a good > idea overall, you can count me as one that thinks flags=257 is a bad idea. I > don't think anything in 403[345] say that flags can

Re: [dns-privacy] [Fwd: [EXT] New Version Notification for draft-vandijk-dprive-ds-dot-signal-and-pin-01.txt]

2020-07-14 Thread Wessels, Duane
Hi Peter, While I remain neutral as to whether or not ds-dot-signal-and-pin is a good idea overall, you can count me as one that thinks flags=257 is a bad idea. I don't think anything in 403[345] say that flags can be interpreted differently depending on the algorithm or on the value of the

[dns-privacy] [Fwd: [EXT] New Version Notification for draft-vandijk-dprive-ds-dot-signal-and-pin-01.txt]

2020-07-13 Thread Peter van Dijk
Hello, please find below revision -01 of our proposal for enabling DoT from resolver to authoritative. New in this revision: * a lot of clarifying text without changing the underlying protocol * the DNSKEY flags field is now specified to be 257 instead of 0. We know that this goes against the