As we are new to the IETF process, we welcome any suggestions
pointing out potential improvements as well as deficiencies in the draft.
The following DiffMail project website and our related paper in SRUTI'05
might also be of interest.
http://www.cs.fsu.edu/~duan/projects/diffmail/diffmail.htm
I'm surprised you don't cite IM2000
Thanks for pointing out. Yes we are aware of IM2000 and have indeed
referred to it as the closest work to DMTP in our tech report on the website
above. In the draft, actually there isn't much reference to any
prior work as we perhaps got too focused detailing DMTP.
Yes, we will add related citations to the draft as well mentioning
IM2000 and others efforts.
We had first set out to design a new architecture from scratch
but soon realized that incremental deployability
would be a key factor in success. In our understanding, the key
differences between DMTP and IM2000 are
(1) DMTP tries to maintain the advantage of the sender-push model
of SMTP where its beneficial (in communication with trusted MTAs)
and resorts to pull-based model only when the credentials are
suspect (with unclassified MTAs). With IM2000,
pull-based model appears to underlie all communications.
(2) DMTP provides an incremental extension to SMTP, can interoperate
with legacy SMTPs and there is no need to change any other entities
such as MUAs or POP3/IMAP servers. IM2000 appears to re-design
all components from scratch with a completely new protocol.
Latter is not necessarily a bad thing, but DMTP's focus has been
incremental extension to SMTP.
In fact DMTP could act as a bridge in transitioning from the
current simple push-based model of SMTP to completely
new models (like pull-based IM2000) -- at present there appears a
great chasm in crossing over from SMTP to any substantially
different architecture.
- Kartik
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg