"william(at)elan.net" <william(_at_)elan(_dot_)net> wrote:
I've argued and will be happy to argue again that SMTP needs to be
replaced with new protocol entirely instead of putting more and more
band-aids on 20 year old protocol that was designed for "simple" mail
transactions.
I'd bet that at least 1/3 of SMTP implementations in existence don't
need anything more than "simple" mail transactions. e.g. internal
corporate mail systems. They're protected by physical and network
security, where there's no need for additional SMTP-layer security.
As for the other 2/3, any new email protocol will end up looking a
whole lot like SMTP.
But creating new mail protocol to replace SMTP would take long time
(both in terms of IETF process to create this new protocol and process
for it to achieve wide-spread adaption)
You don't need the support of the IETF to design and implement a
protocol which is widely deployed. Witness bittorrent.
If someone designs a new SMTP-style protocol, write an
implementation, and make it reasonably backwards compatible with SMTP,
people will test it out. If it's they like it, they'll deploy it,
independent of what the IETF thinks.
Alan DeKok.