Kee,
Tuesday, March 25, 2003, 6:34:54 AM, you wrote:
KH> Currently the process of sending email from point a to point b does
KH> not involve any protocols. Yes, the transport does--but from the MUA
KH> to MUA standpoint there is no back and forth protocol. You toss
KH> message over wall. Sometime later, someone gets it. This is
KH> completely one way.
Ahh. So all those services that use one-way UDP mechanisms are not
protocols?
A protocol does not require closed-loop communication. A protocol is a
set of rules for exchange. Nothing requires that the exchange be 2-way.
Anything that involves standardized exchange from an originator to a
recipient is a protocol.
KH> Yes, there are two exceptions to the
KH> rule--bounces and return-receipts.
closed-loop issues also include replies. open-jaw (multi-user)
scenarios include forwarding and redirection.
KH> I've seen a lot of proposals. But I don't believe I've seen any of
KH> them discuss failure modes.
an extremely point to raise. thank you.
adoption sequence (and dependencies) and failure behavior are probably
the two most important perspectives to evaluate for any new scheme. it
is almost always true that the scenario for steady-state operation with
a large-scale set of well-behaved participants is not the challenge.
d/
--
Dave Crocker <mailto:dcrocker(_at_)brandenburg(_dot_)com>
Brandenburg InternetWorking <http://www.brandenburg.com>
Sunnyvale, CA USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg