On Mar 10, 2006, at 9:08 AM, Dave Crocker wrote:
Hmmm...
>... I find it very easy to understand
things when talking about books. An author creates a book. A
publisher
introduces the book to the world in a presentable format. A Bookstore
make the book available to the public. Using Bill's suggestion:
email books
author author
originator publisher
operator bookstore
I noted your earlier use of 'publisher' and it bothered me quite a
bit.
However I am warming to the model you describe.
1. It is an extremely well-established model.
2. It pertains to salient responsibilities in an information
transfer sequence.
(Given that multiple operators can be in a sequence, I'd suggest
'distributor' rather than 'bookstore'.)
It scares me quite a bit to have my email operator be vested with
apparent responsibility for the content of my email, but, alas, I
guess that really is what the anti-abuse work is about.
What do other folks think?
DKIM is not about defining the author of the message and would
conflict with the charter. Only when the signing-domain coincides
with that of the email-address, are _assumptions_ possible.
Assignment of accountability does not scale down to the user, and
DKIM itself offers no protection beyond the domain. Rather than
seeing this as a trail that starts with the author, these roles are
better broken down into MTA functions that have already been
established, MSA, Mediator, MDA.
-Doug
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html