1 / 11

The Wireless Application Protocol

The Wireless Application Protocol. Initiation of WAP standard. How should connection-oriented and connectionless sessions be supported? Fig – HDTP rested on optional security layer which in turn was on NBS – conflicted with each other. Redundancy was there – both provided data reliability.

keefe
Download Presentation

The Wireless Application Protocol

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Wireless Application Protocol

  2. Initiation of WAP standard • How should connection-oriented and connectionless sessions be supported? • Fig – HDTP rested on optional security layer which in turn was on NBS – conflicted with each other. • Redundancy was there – both provided data reliability. • NBS – offered both connctn-oriented and connectnless abstraction • So security layer was forced to support both • HDTP had to provide 4 configurations • Secure connection • Insecure connection • Secure datagram • Insecure datagram

  3. Initiation of WAP standard • Security layer ran on top of a datagram layer – so susceptible to attack from intruder • Resolution: Resolved in two stages • (1) During fall of 97 all the three protocols were redesigned • HDTP – Wireless Session Protocol (WSP)– similar to HTTP • Security layer – Wireless Transport Layer Security (WTLS) • NBS – Wireless Transport Protocol (WTP) - – reliable datagram, request-response transactions. • (2) During first quarter of 98, WTLS protocol was moved beneath WTP – to enable only secure datagrams • By early 98, first version of WAP standard was nearing completion.

  4. WAP Forum Goes Public • By Jan ‘98, WAP Forum announced that stds were nearly ready • But no n/w operators had yet committed to developing or deploying WAP-based services • Founding members made only vague promises to deliver WAP-based handsets and infrastructure “soon” • Spring 1998 – WAP ‘s initial specification was refined to address addtnl security concerns and fix spec bugs. • In May ‘98 – version 1.0 of WAP standard was published and the WAP Forum became active, inviting new members

  5. Evolution of the WAP standard • By late ‘98s – v1.0 revealed several errors + WAP members wanted some minor enhancements • Liaison activities with W3C and ETSI (European Telecommunications Standard Institute) revealed how WAP –when changed , can enable greater interoperability with other existing stds • But , if these changes were made, backward compatibility with v1.0 would be eliminated • By early ’99, WAP Forum decided to declare v1.0 – obsolete • All initial commercial deployments would adopt a one-time baseline version 1.1 – throughout early ‘99, changes were made and v1.1 was official in May ‘99 • V1.2 – formally in Dec ’99 • A maintenance release V1.2.1 – WAP June 2000 was adopted in June 2000 to improve interoperability • WAP Forum decided to update the std regularly every 6 or 9 months

  6. WAP Forum Today • Nearly 600 members (as of sep 2000) • 2 classes of membership • Full Members • Operators and industry suppliers • Full voting rights • Ability to run for a seat on the Board of Directors • Associate Members • Affiliates of full members • Non-infrastructure suppliers – content suppliers, application developers, tools vendors • Limited rights – can neither run nor vote for the Forum’s BoD • The Forum meets 5 times each year and a week long meeting of BoDs, and all subgroups – to discuss the future of WAP std, its relationships with other std bodies, etc.

  7. Subgroups of WAP Forum • Board of Directors • Elected by the membership • Manages the direction and policies of the Forum • Can sanction various nontech groups – like marketing and commctns expert group • The Specification Committee • Nominated by the BoDs – one per director • Manages the day-to-day technical operations and the Forum’s technical roadmap • Serves as the WAP Interim Naming Authority (WINA) • WINA- assigns global numbers and ids for WAP

  8. Subgroups of WAP Forum • The Architecture Group • Members of the Forum at large • Technical architecture of the Forum’s stds • Ensures that draft stds match the tech architecture • Defines Forum’s relationship with other stds bodies • The Specification Working Groups • Manages various areas of the WAP specs • Six working groups: Architecture, Application, Telephony, Protocol, Security and Inter-operability • Each working group – has several Drafting committees for drafting or maintaining particular specifications

  9. Subgroups of WAP Forum • The Expert Groups • Advisory or monitoring role • Discuss various topics on multiple areas of specifications • Some of the active expert groups are • Carrier Expert Group • Multimedia Expert Group • Smart Card Expert Group • Telematics Expert Group • WAP Developer Expert Group

  10. When a new WAP standard is proposed

  11. The Drafting process – for a New Std

More Related