Re: [dmarc-ietf] Comment on draft-ietf-dmarc-psd

2019-12-08 Thread John R Levine
(just a fan of https://www.ietf.org/archive/id/draft-levine-dbound-dns-03.txt) Don't miss https://github.com/jrlevine/bound I found and fixed a bunch of bugs in the spec when I implemented it. Who knew that could happen? On Sun, Dec 8, 2019 at 4:58 PM John Levine wrote: In article you

Re: [dmarc-ietf] Comment on draft-ietf-dmarc-psd

2019-12-08 Thread Tim Wicinski
+1 Tim (just a fan of https://www.ietf.org/archive/id/draft-levine-dbound-dns-03.txt) On Sun, Dec 8, 2019 at 4:58 PM John Levine wrote: > In article q...@mail.gmail.com> you write: > >So we could decide on doing a combinatory of #3 and #1, with the right > >mechanisms. > > Publishing a list of

Re: [dmarc-ietf] Comment on draft-ietf-dmarc-psd

2019-12-08 Thread John Levine
In article you write: >So we could decide on doing a combinatory of #3 and #1, with the right >mechanisms. Publishing a list of PSD superdomains in the DNS is pretty trivial using my dbound scheme, and should typically find out whether any name needs a PSD check with one DNS query. The total z

Re: [dmarc-ietf] Comment on draft-ietf-dmarc-psd

2019-12-08 Thread Tim Wicinski
Scott Instead of thinking one must choose between a locally consumed registry and a lookup service, why not both? In the land of DNSOP we put out RFC7706 which talks about running a copy of the root Nameservers locally to speed lookups. This seems to be so highly useful that we're just finished W