Re: RE: [Asrg] Consent Proposal

> 
> How is any of this consent/filtering related to the usual IETF purpose
> such as protocol documents (RFCs, etc), network engineering, and not
> just some ad hoc User Interface Engineering?
> 
> 
> It seems to me the consent proposals (getting any attention) thus far
> require no change to any existing protocols or standards, and don't
> seem to imply any new protocols or standards.
> 
> Where in the stack would any of this fit and why does this group need
> to be involved?

It's seems quite likely that distributed consent mechanisms
(by which I mean that policy origination and enforcement
need not occur at the same place) will require publication of new standards
and protocols. If, that is, we're to expect inter-"vendor" applications.
Some mechanisms which support consent (eg C/R) have a strong requirement
for interoperability standards etc.

Equally, there's scope for producing useful documents covering any class of
anti-spam system which need not actually specify protocols: BCP, "Some
considerations regarding..." etc. You'll be aware that many RFCs do not
specify any protocol.

--

_______________________________________________
Asrg mailing list
Asrg@ietf.org
https://www1.ietf.org/mailman/listinfo/asrg