It appears that Bron Gondwana <[email protected]> said: >> I really like the idea that a sender could say "This [List of Lists] >> tells you that [these parties] are permitted to make [these changes] >> to this message during its transit from the sender to the recipient. >> Maybe [List of Lists] could live in the DNS. Just kite-flying here. > >There's no value in having such information in the DNS. To the point that >this is useful at all, it's more useful to specify "acceptable modifier >domains for this message" on a >message-by-message basis. You can sign it easily enough.
This kind of proposal keeps coming up, but the use cases are hard to find. I can see that if you use Proofpoint or the like to whomp your mail on the way out, you might want to use such a flag, but in practice if the changes are likely to be deliberately not reversible, so you can't verify the original signature. We're back to the previous plan where the whomper has a signing key for the original sender. Another possibility is that the sender puts the flag in mail that's sent to mailing lists. But so what? Receivers already know where the mailing lists are, so why should they care whether the sender knows, too. Or if the receiver's opinion is different, why should it assume the sender knows better? If someone has a non-trivial scalable use model for this thing, please tell us. R's, John PS: There is a long running tension between people who believe that receivers should do what senders tell them, and people who think that's obviously silly. _______________________________________________ Ietf-dkim mailing list -- [email protected] To unsubscribe send an email to [email protected]
