I do not think 'consent' really has anything to do with a definition of
'spam'
in the context of this problem. I feel that consent with respect to
messaging
is TOTALLY subjective and what a real definition addresses is the issue
of
policy or 'consent' enforcement after solicitation. I think enforcement
comes
via the technical solution we come up with.
OK, consent is subjective. Definition of spam is subjective.
These are not blockers.
Classification of a message is not impossible.
(There are many deployed systems that do this with varying degrees of
"accuracy") Expression of a subjects preferences is not beyond us.
We don't need to define spam. All we will ever need to do is say that
"this set of message classes does | doesn't have consent for delivery to
this subject."
--
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg