Re: [DNSOP] Clarifying motivation for Compact DoE

2023-08-08 Thread Paul Vixie
see inline. Shumon Huque wrote on 2023-08-08 12:13: At any rate, as I've remarked before, I'm not convinced that the optimizations offered in Compact DoE were actually necessary as an operational matter. But I'll leave it to our colleagues at Cloudflare to argue that case. My interest in publi

Re: [DNSOP] Clarifying motivation for Compact DoE

2023-08-08 Thread Shumon Huque
On Tue, Aug 8, 2023 at 11:50 AM Paul Wouters wrote: > On Tue, 8 Aug 2023, Ben Schwartz wrote: > > > If this is correct, then I'm not sure the complexity of solving the ENT > problem is worthwhile. > I'm not sure which "ENT" problem Ben is referring to solving here. The draft proposes ways to pre

Re: [DNSOP] Clarifying motivation for Compact DoE

2023-08-08 Thread Shumon Huque
On Tue, Aug 8, 2023 at 10:45 AM Ben Schwartz wrote: > Hi DNSOP, > > draft-ietf-dnsop-compact-denial-of-existence currently says the following > about RFC 4470: > >The response for a non-existent name requires up to 2 signed NSEC >records or up to 3 signed NSEC3 records (and for online sig

Re: [DNSOP] Clarifying motivation for Compact DoE

2023-08-08 Thread Paul Wouters
On Tue, 8 Aug 2023, Ben Schwartz wrote: If this is correct, then I'm not sure the complexity of solving the ENT problem is worthwhile. At $dayjob, I had to add bogus TXT records to our zones because of ENT issues with Amazon Route53, which Amazon knows about and has refused to fix for years.