Re: [DNSOP] QNAME minimization: we screwed up but it's your problem

2023-11-11 Thread John R Levine
On Fri, 10 Nov 2023, David Conrad wrote: DNSBLs have been around a lot longer than QNAME minimization. Not sure that’s relevant — I presume you’re not suggesting DNSBLs are a predominant use of the DNS. In the overall Internet, no, but within the e-mail world it's probably the majority of t

Re: [DNSOP] QNAME minimization is bad

2023-11-11 Thread Paul Wouters
On Nov 10, 2023, at 21:02, John Levine wrote: > >> >> A bit misleading subject :P > > It seems to have done the trick. You need to trick people with exaggerations to read your emails? The industry term for that is “clickbait”. I urge everyone not to engage in that in the IETF. > > DNSBLs ha

Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-dnssec-bootstrapping

2023-11-11 Thread Paul Wouters
Subject: Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-dnssec-bootstrapping On 9/19/23 21:48, Tim Wicinski wrote: > > This starts a Working Group Last Call for draft-ietf-dnsop-dnssec-bootstrapping > > Current versions of the draft is available here

Re: [DNSOP] QNAME minimization, we screwed up and it's your problem

2023-11-11 Thread John R Levine
On Sat, 11 Nov 2023, Paul Wouters wrote: DNSBLs have been around a lot longer than QNAME minimization. They work(ed) fine without minimization and I don't think it is reasonable to expect every mail system in the world to change their configuration to work around our performance bug. It is tota

Re: [DNSOP] QNAME minimization, we screwed up and it's your problem

2023-11-11 Thread Paul Wouters
On Sat, 11 Nov 2023, John R Levine wrote: work(ed) fine without minimization and I don't think it is reasonable to expect every mail system in the world to change their configuration to work around our performance bug. It is totally reasonable for protocols and software and configurations

Re: [DNSOP] QNAME minimization, we screwed up and it's your problem

2023-11-11 Thread Rubens Kuhl
> > Note that my original point was that if the current RBL lives at > antispam.rbl-vendor.org, simply moving it to _antispam.rbl-vendor.org > might fix it if the underscore handling mentioned in the minimized query > RFC is actually implemented with some code in the current implementations, > in

Re: [DNSOP] QNAME minimization is bad

2023-11-11 Thread Paul Vixie
Joe Abley wrote on 2023-11-10 23:40: On 10 Nov 2023, at 21:26, Brian Dickson wrote: Perhaps the DNSBL operators could individually or collectively operate resolvers which do that exact thing? I'm not sure why the answer isn't "MTAs should run local resolvers configured in ways that best

Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-dnssec-bootstrapping

2023-11-11 Thread Tim Wicinski
Paul Thank you for this detailed review! When I spoke with Peter on WGLC, I had documented organizational issues. I wasn't sure if my organization suggestions were any better, so I opted to mention this during WGLC and have people much smarter than me assist. I will think out the document organiz

Re: [DNSOP] [Ext] QNAME minimization is bad

2023-11-11 Thread David Conrad
Paul, On Nov 10, 2023, at 11:06 PM, Paul Hoffman wrote: >> On Nov 10, 2023, at 11:55 AM, John Levine wrote: >>> DNSBLs have been around a lot longer than QNAME minimization. >> Not sure that’s relevant — I presume you’re not suggesting DNSBLs are a >> predominant use of the DNS. > DNSBLs are on