Steve Atkins wrote:
> If nobody is ever going to use a piece of information, then expending
a lot of effort and complexity to make it available is a mistake.
Given that, plausible use cases are part of the process of deciding
what to keep and what not to.
...
(I don't see much along those lines with dkim-base, so none of these
issues should slow dkim development and deployment, but I do see
them all over with SSP).
+1
Nicely said.
David Sanchez wrote:
>> Given that, plausible use cases are part of the process of deciding
>> what to keep and what not to.
>
> That's true, but where is the difference between plausible use cases
> and all the use cases in the world?
An entirely fair question, and one that we should all maintain constant
vigilance about, in order to carve away the ones the group feels are not
plausible, not within scope, or otherwise need to be excluded.
> My thought just was about this thread, becoming a little strange
> talking about $, € signs, in MUA and windows popping or something.
There is are two elephants in our room.
One gets acknowledged regularly and the other less often. The first is the
difference between a potential signer's saying what they do, versus a potential
signer's attempting to tell a recipient what to do. I think the wg has
(finally) gotten a stable position on this.
The second elephant is the broadly-held view that some/all of the work of the
DKIM effort is really for end-user consumption. That leads to assumptions about
how the end-user in brought into the mix, particularly in terms of what will be
presented to them. The problem with this elephant is that it is so pervasive
and so entirely appealing, but is so poorly understood (by experts, nevermind by
this working group.) So it repeatedly gets added to the discussion mix.
So my own purpose in citing MUA specifics is to try to get us to keep them out
of the wg's scope...
d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html