DEMP: David's Electronic Messaging Protocol

The following is the introduction from the unpublished DEMP 0.10 DRAFT. The complete draft has some errors that will prevent it from being publicly distrubuted. However, this edited introduction should provide and idea of DEMP while the re-write is in progress.

1. Introduction

David's Electronic Messaging Protocol (DEMP) strives to be a complete messaging protocol. In its basic form as described in this memo, DEMP will allows a user to send and receive electronic messages. A user will also be able to store and manipulate messages that are stored locally or on a remote server. This manipulation of message will be similar to that of IMAP [ RFC 2060].

DEMP is a foundation of the future development of other messaging protocols. But at the core, DEMP will support electronic mail (email). DEMP is new. DEMP will not rely on old protocols. However, DEMP will incorporate the features of SMTP [ RFC 821] and IMAP [ RFC 2060]. The more popular POP3 [ RFC 1939] is too simple for the purpose of features to be a model, however, the idea of a quick connect and download Ð sometimes called a "flash" session Ð will be available in DEMP. (This is likely to be a feature of the client, not necessarily specifically addressed in the specification.)

DEMP will boast much of its power, versatility, and extendibility from XML, the extensible markup language. At present, DEMP will be defining its own protocol exchange not using one of the XML Protocols that uses envelopes to encapsulate commands. (For example, DEMP will not be built upon SOAP, which uses HTTP.) Comments on this design decision are welcome as well as discussion. DEMP will exclusively use XML for all its commands and storage.

As stated, DEMP will be a complete protocol. Ideally, DEMP will replace the use of SMTP, POP, and IMAP. A client will be able to accesses his or her email, compose and send a message using this unified protocol. The servers will also speak DEMP and use this same protocol to relay email over the Internet. This will of course depends on the public's acceptance of DEMP as the replacement for the popular mail transport protocol, SMTP. In the interim, the DEMP/SMTP Bridge will have to be implemented. Such a specification will be presented in a later version of DEMP. Conversion of RFC 821/822 mail text messages to and from DEMP is open for public discussion and debate. (Once any details of DEMP are published.)