That is, the 'payload' of DKIM is the delivery of a validated domain name. In the original specification, we failed to properly specify which of the two delivered identifiers (d= and s=) was that promised payload.
These hairs are split too finely for me to understand. The DKIM validator takes the message and the not-API returns a possibly empty list of identifiers. In v2 or whatever we call it, the validator does exactly the same thing.
The main difference I see is that if we call v2 something else, we now have a tedious administrative exercise of finding every place something refers to DKIM and change it to "DKIM or DKIM-plus." This does not strike me as a good use of anyone's time.
Regards, John Levine, [email protected], Taughannock Networks, Trumansburg NY Please consider the environment before reading this e-mail. _______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
