It appears that Richard Clayton <[email protected]> said: >* For two signatures with the same algorithm, consider the signatures > valid if both pass or one passes and the other gives a TEMPERROR.
Sounds like a configuration bug to me. Why would you do that? >* For multiple algorithms insist that ALL signatures pass. For about the 100th time, how are we supposed to add new algorithms? And if you mean you only validate the ones you understand, that strikes me as a meaning of "ALL" with which I am unfamiliar. >* Use MLDSA-44 rather than a hybrid (because then you can sign with > another algorithm if you care). I suppose, but same question. >* Allow all variants of "-sha256" and "-sha512" for tidiness. Better check what the libraries support. >* Continue with the MUST constraint on verifiers that they have to > implement all algorithms and hashes This makes the 101st time. >> * AND/OR under the control of some sender specified flag- supports >> ORing during bring up and ANDing when security is needed though >> w/greater complexity.� > >the flag approach has legs, but would have to be combined with a hard >and fast rule of "OR" for the same algorithm otherwise key rotation >would be impossible without (effectively) dropping down to one algorithm Um, you said "AND" a few bullets back. R's, John _______________________________________________ Ietf-dkim mailing list -- [email protected] To unsubscribe send an email to [email protected]
