Hello Andreas, I agree with you, I'm addressing a similar topic than the good old SPF does. However, one point is that the email carries intrinsic data in the envelope that is not obvious to replace, another is the necessity (for me at least) to publish what level of authorization control is performed, if any (through the CRS).
regards E.A. Le jeu. 16 juin 2022 à 21:00, <[email protected]> a écrit : > > Send DNSOP mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.ietf.org/mailman/listinfo/dnsop > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of DNSOP digest..." > > > Today's Topics: > > 1. Re: introducing a couple of RRTypes (CRC/CRS) for B2B > applications (A. Schulze) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 15 Jun 2022 21:35:33 +0200 > From: "A. Schulze" <[email protected]> > To: [email protected] > Subject: Re: [DNSOP] introducing a couple of RRTypes (CRC/CRS) for B2B > applications > Message-ID: <[email protected]> > Content-Type: text/plain; charset=UTF-8; format=flowed > > > > Am 15.06.22 um 18:28 schrieb Eug?ne Adell: > > > https://datatracker.ietf.org/doc/draft-adell-client-roaming/ > > (to me) it looks you like a solution for a problem > solved specifically for email. It's known as SPF / RFC 7208 there ... > > Andreas > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > DNSOP mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/dnsop > > > ------------------------------ > > End of DNSOP Digest, Vol 187, Issue 8 > ************************************* _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
