-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In message <[email protected]>, Michael Thomas <[email protected]> writes
> Well, I guess that gets to my other post the other day. If this can > be an update to STD 76, shouldn't it be? There is a huge installed > base of DKIM so a software update to it would probably get adopted > a lot faster than something truly new. The things in the charter > don't seem to necessitate it being a completely new something since > it looks like it would require some new tags in the signature block > and/or header fields. new tags will not address the issue of error handling for intermediaries which DKIM2 addresses by changing where DSNs are sent (and requiring them to be passed back along the chain as needed). Similarly it will not address the backscatter issue (viz it will allow accept and reject strategies that are not currently practicable). - -- richard Richard Clayton Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. Benjamin Franklin 11 Nov 1755 -----BEGIN PGP SIGNATURE----- Version: PGPsdk version 1.7.1 iQA/AwUBZ32pgWHfC/FfW545EQJ5UgCgpogt9Pqu5yiYlU39tRQuCVbCN08AnRQn qI/JdJWf/DIoXF355CaYzpQh =6OT4 -----END PGP SIGNATURE----- _______________________________________________ Ietf-dkim mailing list -- [email protected] To unsubscribe send an email to [email protected]
