This use case is actually the intention of (the extremely poorly worded) https://trac.ietf.org/trac/dmarc/ticket/59
To the earlier conversation, this is all simplified dramatically if we define organizational domain (or whatever it's renamed) discovery in a separate I-D that DMARC just inherits... On Wed, Nov 11, 2020 at 1:30 PM John R Levine <jo...@taugh.com> wrote: > On Wed, 11 Nov 2020, Dave Crocker wrote: > > Just to invoke a bit of ancient history, here, you are saying that if > there > > was the domain name: > > > > engineering.sun.com > > > > people would be surprised that the organization domain is > > > > oracle.com > > In a DMARC context, that would be quite surprising. I am aware that > Oracke bought Sun quite a while ago. > > Regards, > John Levine, jo...@taugh.com, Taughannock Networks, Trumansburg NY > Please consider the environment before reading this e-mail. https://jl.ly > > _______________________________________________ > dmarc mailing list > dmarc@ietf.org > https://www.ietf.org/mailman/listinfo/dmarc > -- *Seth Blank* | VP, Standards and New Technologies *e:* s...@valimail.com *p:* 415.273.8818 This email and all data transmitted with it contains confidential and/or proprietary information intended solely for the use of individual(s) authorized to receive it. If you are not an intended and authorized recipient you are hereby notified of any use, disclosure, copying or distribution of the information included in this transmission is prohibited and may be unlawful. Please immediately notify the sender by replying to this email and then delete it from your system.
_______________________________________________ dmarc mailing list dmarc@ietf.org https://www.ietf.org/mailman/listinfo/dmarc
