All this is IMHO (with H being Humble )
> 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.
Agreed
> 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?
My thought just was about this thread, becoming a little
strange
talking about $, € signs, in MUA and windows popping or
something.
In my humble opinion this specific thread was getting too
much into
implementation details, that has to the best of my knowledge
little to
do within a standard.
> Also, if there's a dependency on other standards for
some functionality
> (for example, a third party accreditation system of
some sort) then that
> dependency needs to be understood, so as to make sure
that they
> are flexible enough to work with some subset of
reasonable systems.
IMHO this not apply to current thread.
There is a lot of real world use cases to discuss before
getting into
MUA GUI details, i think.
> (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).
> Cheers,
> Steve
>
> _______________________________________________
> 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
|