next up previous contents index
Next: Making LEAP Widespread Up: LEAP: One Alternative to Previous: LEAP: The Lightweight &   Contents   Index

Subsections

Comparison of LEAP to WAP

In The WAP Trap, we enumerated the characteristics of the WAP specifications that make them wholly unfit to play the role of an enabling industry protocol. These characteristics are summarized in Table 11.1, along with the corresponding characteristics of the LEAP protocols.


Table 11.1: WAP versus LEAP
WAP LEAP
Subject to known patent restrictions Patent-free
Self-published by the WAP Forum Published as Internet RFCs
Revisions subject to change without notice All revisions permanently fixed
Maintained by the WAP Forum Maintained by open working groups
Re-invention of existing protocols Efficiency-optimizing extensions to existing protocols
Tailored to mobile phone user interface characteristics User interface independent
Inherent security vulnerability Imposes no security assumptions
Inconsistent protocol number assignment Consistent protocol number assignment
Initial focus: web browsing Initial focus: messaging



Patent Restrictions

As noted in The WAP Trap, the WAP specifications include patented components. Unlike WAP, the LEAP protocols are entirely patent-free.

Openness of Publication

As noted previously, the LEAP protocols are published as Internet RFCs, ensuring permanent, unrestricted availability of the protocols. The WAP specifications, on the other hand, are self-published by the WAP Forum, and therefore do not carry the same assurances of unrestricted availability. The availability and permanence of the WAP specifications is only as good as that of the WAP Forum itself.

Furthermore, in order to download any particular WAP specification, a user must agree to a license agreement. By contrast, the LEAP protocols may be downloaded and distributed without any restrictions.

In addition, the WAP Forum's publishing philosophy carries no guarantee of stability. As of February 2000, each WAP specification carries on its title page the disclaimer, ``This document is subject to change without notice.'' By virtue of the RFC publication process, on the other hand, individual revisions of the LEAP protocols are permanently fixed.

Openness of Maintenance

LEAP's open maintenance processes are also in sharp contrast to WAP. Participation in the development of the WAP specifications requires payment of the $27,000 WAP Forum membership fee (as of February 2000), and takes place entirely behind closed doors. Unlike WAP, the LEAP protocols are maintained by public maintenance organizations in which anyone is free to participate.

Technical Deficiencies

The WAP protocols also include numerous technical deficiencies. For example, WAP is a broad-scope re-invention of existing protocols. The LEAP protocols, by contrast, consist of a small number of independent protocols that complement existing Internet protocols. Other WAP deficiencies are listed in Table 11.1; for a detailed discussion, see The WAP Trap.

Initial Focus

There are also significant conceptual differences between LEAP and WAP, of which we will mention two here. First, LEAP is primarily oriented towards the mobile messaging (i.e. e-mail) application, whereas WAP is primarily oriented towards mobile web browsing. We believe that this represents a serious misunderstanding of the mobile data communications industry on the part of the WAP Forum. Hand-held mobile devices are extremely well-suited to the e-mail application, whereas their severe user interface limitations render them highly ill-suited to web browsing.

Second, LEAP and WAP take very different approaches to the messaging application. The LEAP approach, embodied in the EMSD protocol, is a complete and efficient submission and delivery model. The WAP approach, on the other hand, is a mailbox access and selective message retrieval model.

A consequence of this is that the WAP protocol has several unresolved issues relating to message delivery. For example, the WAP protocol does not support the ``push'' model of message delivery, in which time-critical messages are actively delivered to the recipient. The LEAP protocol, by contrast, fully supports the ``push'' model.

Hype versus Reality

Figure 11.1: Wireless Internet Hype vs. Reality
Wireless Internet Hype vs. Reality

Our view of the evolution of the wireless Internet industry is illustrated in Figure 11.1. The early history of this industry is already known to us; in recent years the industry has undergone extremely rapid growth. And in the long term, there is general consensus among analysts that the industry is destined for continued strong and sustained growth.

So the early history is known, and the eventual history we can predict with confidence. But what about the more immediate future? Our view is that, largely thanks to the WAP Forum, the industry has been significantly over-hyped, with the result that expectations now greatly exceed realities. Our prediction is that this period of soaring expectation will be followed by a period of general disillusionment and frustration, as these expectations are inevitably disappointed.

Sooner or later the industry must adopt a more realistic understanding of its technological and business challenges. Part of this understanding will consist of the recognition that the wireless industry must adopt a single set of truly open protocols. Only then will the industry be able to undergo stable and sustained growth.

WAP represents the era of hype and disillusionment. LEAP represents the era of realism and maturity.


next up previous contents index
Next: Making LEAP Widespread Up: LEAP: One Alternative to Previous: LEAP: The Lightweight &   Contents   Index