From: J C Lawrence <claw(_at_)kanga(_dot_)nu>
Additionally, a proposal for a C/R protocol would be useful. This
would permit interaction between different C/R systems and allow
integration into MTAs and MUAs.
Given that the response portion and the transport used for the response
(email, web, phone, IM, XML/RPC, other) are unstandardisable, that only
leaves the challenge side.
Is there anything required by a challenge that's different from a
vacation bot?
...
I disagree. From the point of view of the sender of the original
message, a challenge and the required response is not unidirectional
like a `vacation` or "out of office" notice, but like an "opt-in
subscription confirmation." A standard for SMTP (or SMTP+HTTP)
confirmation of a bulk mail subscription request would surely look
very similar to an email based C/R system underneath the user interfaces.
Note that opt-in subscriptions to bulk mail can involve other than
email for any or all of the three messages (original request,
confirmation request, and confirmation).
I don't recall where subscription confirmations might be documented.
If they are not, then it might be good to produce a single
challenge-response/opt-in document.
By the way, which RFC contains the documentation of what we all know
a "vacation" notice should and should not be? The only reliable
specification I know of for what it should be is the BSD source.
Where has what it shouldn't be documented, besides in some secret
Outlook specification? (To be fair, lately I've not seen much of the
Outlook out-of-office noise that plagues the main IETF list).
Vernon Schryver vjs(_at_)rhyolite(_dot_)com
Disclaimer: I'm not a fan of C/R systems, and so should not and am
not volunteering to push them.
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg