> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:ietf-dkim- > [EMAIL PROTECTED] On Behalf Of Frank Ellermann > > | Any party, anywhere along the transit path can implement DKIM > | signing. Its use is not confined to the end systems or only > | in a boundary MTA. > > Found in 3.1.2, but chapter starts with "end-to-end", and this > is a critical point of the design. Please explain it, proposal: > > [... as is ...] > | Signatures by intermediaries are also known as third party > | signatures.
I'd like to be a bit more precise. I believe when people refer to 3rd party signature, they mean a signature from an entity not represented in the From header (as in ASP), or possibly also the Reply-to header. In other words, it is not affected by where the signing is done, but rather by what entity is represented by the signature, i.e. the originator could sign with a 3rd party signature, and an intermediary could sign with a (delegated) 1st party signature. Ellen > > If you add "email-arch" as reference maybe use the proper term > "mediators" instead of "intermediaries", or add "(mediators)". > > Frank > > _______________________________________________ > NOTE WELL: This list operates according to > http://mipassoc.org/dkim/ietf-list-rules.html _______________________________________________ NOTE WELL: This list operates according to http://mipassoc.org/dkim/ietf-list-rules.html
