Dave Crocker writes: > So perhaps the most useful thing we can do is try to get the wg to > formulate 'needs'
I don't see that we have "needs" here. We know how to do this stuff as long as we can get access to certain non-MTA resources (the DNS, in particular). The thing about "organizational domain" is that depending on how it's defined we may be able to dramatically reduce demand for organizational resources (and for a caching service like DNS, extra-organizational resources) by defining a canonical mapping from authorized Author Domains to an Organizational Domain, which maintains a single organization-wide policy. So it's not a "need", it's a "bone of contention". How about "formulate use cases we would like such a definition to serve"? _______________________________________________ dmarc mailing list dmarc@ietf.org https://www.ietf.org/mailman/listinfo/dmarc
