Sent from my iPhone

> On Nov 10, 2023, at 12:02 PM, John R Levine <jo...@taugh.com> wrote:
> 
> 
>> 
>>> I'd like to write a draft that updates RFC 9156 by describing
>>> situations like this that caches could recognize and avoid useless
>>> churn, added to section 2.3 which already suggests special casing
>>> underscored labels.
>> 
>> I must confess that I do not see what is suggested in this thread
>> which is not already in section 2.3. Unbound implements some of the
>> RFC ways, see its iterator/iterator.h (all parameters named
>> *MINIMISE*).
> 
> If you see a name that is four all-digit labels and it's not in in-addr.arpa, 
> stop minimizing and just send the query.  Similar for 18 hex digits not in 
> ip6.arpa.  I realize these are specific cases but at least in the mail world 
> they are very common ones and minimization more than doubles the traffic 
> DNSBLs would otherwise get.

Perhaps the DNSBL operators could individually or collectively operate 
resolvers which do that exact thing? Or make arrangements with one of the large 
public resolver operators to support that or to stand up an instance 
specifically only for this function?

Mail servers might need configuration changes, of course, but this would still 
involve many fewer moving parts than a substantial fraction of the 3M resolvers 
that your request is indirectly asking to make changes.

The mail server set up could be as simple as a caching forwarder with a set of 
forwarding stanzas for DNSBLs plus default forward stanzas to the regular 
resolvers the server uses. 

Iterate updates as suitable resolvers become available.

That setup could be a standalone package optionally suggested by the various 
mail server packages.

The performance of mail servers would likely be improved, so it would be a 
win/win for them and the DNSBL operators.

Brian

> 
> Again, there might be others.  Data eagerly sought.
> 
> Regards,
> John Levine, jo...@taugh.com, Taughannock Networks, Trumansburg NY
> Please consider the environment before reading this e-mail. https://jl.ly
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to