The EMSD Protocol specifications define the protocols between the EMSD Device and the EMSD server. EMSD requires ESROS (Efficient Short - Remote Operation Services). The EMSD specification was the driving force behind the development of the ESROS. However, ESROS was developed to be independent of EMSD.
These goals will prevent, whenever possible, the expense and associated problems of "re-inventing the wheel." The EMSD Protocols make heavy use of existing technology, including the following:
These technologies have been thoroughly tested and have proven to be reliable solutions for the problems they address (e.g. message format, reliable message delivery, encoding and compacting). The EMSD Specifications allow for users who enjoy the advantages of this new technology and at the same time want to be connected to the rest of the existing Internet email. Figure 6 looks at how the Global and EMSD worlds complement one another.
The Messaging Internetwork and its estimated 30 million current users are in the lower half of the figure. This world is connected to the EMSD Internet email.
The EMSD-P&FS consist of three independent components:
EMSD-FS is a non-textual form of compact encoding of Internet email (RFC-822) messages which facilitates efficient transfer of messages. EMSD-FS does not replace RFC-822 in any way. EMSD-FS defines a method of representation of short interpersonal messages. It defines the "Content" encoding (Header + Body). Although EMSD-FS contains end-to-end information its scope is purely point-to-point. EMSD-FS relies on EMSD-P (see 2 below) for the transfer of the content to its recipients.
EMSD-P is responsible for wrapping a limited size message (see 1 above) in a point-to-point envelope and submitting or delivering it. EMSD-P performs the envelope encoding and relies on the services of Efficient Short Remote Operation Services (ESROS) as specified in RFC-2188 [5] for transporting the point-to-point envelope. Some of the services of EMSD-P include: message originator authentication and optional message segmentation and re-assembly. The EMSD-P is expressed in terms of abstract services using the ESROS notation.
ESROS defines a notation and the services provided by an application-service element to support interactive applications in a distributed systems environment. The scope of Efficient Short Remote Operations Services is not Efficient Mail Submission & Delivery. ESROS is designed such that it could support other applications (i.e. finger/limited directory service).
EMSD is designed to fit within the many protocols already in use for messaging, as well as those already in use for networking. Figure 8 illustrates where EMSD fits with the other prominent messaging protocols. The RFCs referenced here are current at the time of this writing, but could be obsoleted or updated at any time.
Figure 9, categorizes the capabilities of SMTP, IMAP, POP and EMSD based on the following functions:
In Figure 9, the number of "X"es in each box attempts to denote to what extent a particular function is supported by a particular protocol.
Figure 9 clearly shows that combinations of these protocols can be used to complement each other in providing rich functionality to the user. For example, a user interested in highly mobile messaging functionalities can use EMSD for "submission and delivery of time critical and important messages" and use IMAP for comprehensive access to his/her mail-box.
For mail submission and delivery of short messages EMSD is much more efficient as compared to SMTP, POP and IMAP.
We have published these protocols the right way as Internet RFCs (RFC-2188 and RFC-2524). The RFC publication is very significant in that it has certain prefered qualities over all other existing publication and distribution mechanisms. These prefered qualities include:
Note, that we deliberately did not include IETF/IESG/IAB blessing as a significant quality of RFC publication. The perception that the RFCs produced or approved by the IETF/IESG/IAB are of a higher quality than other RFCs is a wrong one. When EMSD protocols become widespread, we then intend to put them on standards track and obtain the necessary blessings for them. We believe that legitimacy for a protocol comes from its usage and the market place.
We are promoting and maintaining these protocols the right way, through a completly open model at EMSD.ORG. Participation in evolution of EMSD is open to all. It is not framed as a ``Rich Kids Club'' (e.g., the WAP Forum).
At present, there are no other protocols for two-way paging that come anywhere close to EMSD's quality, maturity or openness.
Visit the "Base Protocol Specifications" section of http://www.emsd.org/ for instructions on how to obtain the EMSD protocols.
Eventhough EMSD protocols are primarily used in wireless data environments, framing EMSD as a Wireless Application Protocol misses the point. As it would be the case with other efficient Internet application protocols.
If one recognizes that:
It then becomes obvious that anything called, Wireless Application Protocol (WAP) Forum is mis-guided.
The last year has seen an explosion of standards organizations in wireless data. A partial count of groups formed in the last two years include:
Outside of wireless subnetwork specific focuses there is no meaningful need for these many standard organization. Each with their own protocol publication mechanisms and each with their own claims of legitimacy and each with their own restrictions and limitations on participation.
The EMSD Organization is focused on the development, maintenance and enhancements to protocols and related technology which addresses the efficiency requirements of Internet Mail Submission and Delivery.
EMSD.ORG is not a standards organization. EMSD protocols are published as Internet RFCs. EMSD.ORG is simply a vehicle to accomodate cooperation on work related to EMSD protocol and technology. It is open to all.
Anyone interested in contributing to the development of EMSD protocols can join EMSD.ORG by visiting the "Joining the EMSD.ORG and Related Mailing List" section of http://www.emsd.org/.
