Re: [dns-privacy] [Ext] WGLC : draft-ietf-dprive-unilateral-probing

2023-06-08 Thread Philip Homburg
In your letter dated Wed, 7 Jun 2023 23:12:21 + you wrote: >> The experiment could just be to gain operational experience. We can be up= >front >> that we don't know what will happen, and encourage people to be careful. > >That's true with every new protocol from the IETF. It would be good to >

Re: [dns-privacy] [Ext] WGLC : draft-ietf-dprive-unilateral-probing

2023-06-08 Thread Paul Hoffman
On Jun 7, 2023, at 11:42 PM, Florian Obser wrote: > Up-thread Stéphane reported ns1.eu.org as an example. Open resolver on > 853 and authority for eu.org on 53: > > | Also, currently, regarding the possible warning to system > | administrators about the need for 53 and 853 to be in sync, we > | c

Re: [dns-privacy] [Ext] WGLC : draft-ietf-dprive-unilateral-probing

2023-06-08 Thread Paul Hoffman
On Jun 8, 2023, at 6:07 AM, Philip Homburg wrote: > Correct. Port 853 is in use on the addresses used by some > authoritative servers to serve the role of client-facing recursive resolver. > > And that will certainly confuse any recursive resolver that tries to implement > this draft. Thank you

Re: [dns-privacy] [Ext] WGLC : draft-ietf-dprive-unilateral-probing

2023-06-08 Thread Rob Sayre
On Wed, Jun 7, 2023 at 2:05 PM Hollenbeck, Scott wrote: > > On Jun 6, 2023, at 8:42 PM, Rob Sayre wrote > > On Tue, Jun 6, 2023 at 11:23 AM Hollenbeck, Scott 40verisign@dmarc.ietf.org> wrote: > > Measurement of CPU and memory use between Do53 and DoT or DoQ. >> Measurement of query response