Good work on the updated phrasing, I'd make just a couple of changes to the "tax" suggestion:
On Fri, Mar 19, 2021 at 9:28 AM Alessandro Vesely <[email protected]> wrote: > > *Example* > > Since the algorithm (last word) hasn't been mentioned yet: > > OLD > Defensively registering all variants of "tax" is obviously not a > scalable strategy. The intent of this specification, therefore, is > to enhance the DMARC algorithm by enabling an agent receiving such a > message to be able to determine that a relevant policy is present at > "gov.example", which is precluded by the current DMARC algorithm. > > > NEW > Defensively registering all variants of "tax" is obviously not a > scalable strategy. The intent of this specification, therefore, is > to enhance DMARC discovering method by enabling an agent receiving > such a > message to be able to determine that a relevant policy is present at > "gov.example", which is precluded by the current DMARC specification. > 1 - delete the word "obviously". I really don't think such a statement belongs in a spec and can lead us down infinite rabbit trails. 2 - s/DMARC discovering/DMARC discovery/ --Kurt
_______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
