Wi De X Problem Statement Dean Willis dean
Wi. De. X Problem Statement Dean Willis <dean. willis@softarmor. com> Vlad Stirbu <vlad. stirbu@nokia. com> RUI Bo. F, IETF 63, Paris August 2 nd , 2005 1 IETF 63, Remote UI Bo. F
What is Remote UI? Remote UI Server Remote UI Client UI Semantics Application logic Processed Input Information • A mechanism that enables user interfaces to be rendered on other devices than those that have the application logic. 2 IETF 63, Remote UI Bo. F
Remote UI Alternatives Now • Framebuffer-level – VNC, RDP, Hot Desk • Server framebuffer is copied across the network to a framebuffer on the client • Graphics-level – X Windows • Drawing request to the graphical device interface (GDI) copied across the network • The client is interpreting these commands and renders in its framebuffer 3 IETF 63, Remote UI Bo. F
Ecosystem: Devices 4 IETF 63, Remote UI Bo. F
Ecosystem: User Interfaces 5 IETF 63, Remote UI Bo. F
Highly Diverse Ecosystem • Physical characteristics • screen size and ratio • color depth • User Interface characteristics • windowing system and widget sets • input methods 6 IETF 63, Remote UI Bo. F
Challenges • How to describe the user interface in terms of widgets? e p o c • How to find matches between UI servers and clients? S f o t u • How to start UI remoting sessions? O • How to keep the UI synchronised? 7 IETF 63, Remote UI Bo. F
Some Answers • UI descriptions • W 3 C markup languages: XHTML, XHTML + SVG, etc. • Discovery session setup • IETF: MMUSIC, Zero. Conf 8 IETF 63, Remote UI Bo. F
Wi. De. X Goal & Scope • Specify an open, platform-independent method for use in an IP-based network to convey initialisation, update and eventing information about user-visible objects, i. e. widgets. • Network “plumbing” • Connectivity. e. g. NATs, firewalls • Security • Reliability • UI remoting management • • 9 URI definition Session-Transaction model Synchronisation Events IETF 63, Remote UI Bo. F
Wi. De. X Requirements & Assumptions • Protocol must have a modular architecture • UI semantic independent • Discovery and session setup mechanism independent • Privacy concerns must be addressed, e. g. P 3 P • Protocol must support server initiated updates • Full screen updates • Incremental updates • Protocol must support client initiated updates • The protocol must have support for authentication and secure sessions • Existing protocols should be reused when appropriate 10 IETF 63, Remote UI Bo. F
- Slides: 10