Folks,
As long as I am ranting about the need to non-technical -- that is, functional
-- descriptions of use for records that publish signing practices, I might as
well suggest some (relatively) non-technical terminology to use, so that we have
some consistency:
Author:
Creates message content
Mailing-List: Creates message content, based on existing messages
Recipient: End-user who may read the content
Operator:
Transfers messages
Author's
Operator: Controls submission
Recipient's Operator:
Controls delivery
Filter:
Makes contingent handling choices, based on mechanical assessments on a
message and
Operator's Filter:
A handling filter employed by an operator.
Recipient's Filter:
A handling filter operating in the Recipient's MUA.
Domain:
Identity cited in a signing practices record
Author's Domain:
Identity of the domain in the rfc2822.From field
Operator's Domain:
Identity in the rfc2822.Sender field or a Received field.
So, for example, this is a large difference between a practices record that is
set by the author's domain and one that is set by an operator's domain.
Equally, there is a large difference between using practices records for
operator-based filtering than for human recipient decision-making.
d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html