On 1/4/2020 8:03 PM, Keith Moore wrote:
I suspect ietf-smtp would do better to define the behavior of a
submission service that is designed to accept inbound email from devices
in such an environment
The clients in such an environment appear to simply be MUAs. The
submission server appears simply to be an MSA.
I gather what makes them distinctive is methods of identification and
authentication -- notably reliance on network address rather than domain
names -- rather than anything involving email semantics or basic
protocol details (beyond ID & Auth)?
What else is distinctive?
and forward such email to a "smarthost"
What are the differences from a classic originating MTA?
From your note, the reliance on IP Address and boundary security rather
than encryption appear to be the primary points of distinction.
In any event, I suspect it would be helpful to create an Informational
RFC that discusses design, administration and operations issues that are
noteworthy in common IoT environments. Sounds like it doesn't need to
be lengthy of complicated, but formulating a discrete set of statements
and getting community consensus on it could facilitate detailed wg
decision-making, here and elsewhere.
d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp