Lemonade and Mobile e- mail Stéphane H. Maes – Lemonade Intermediate meeting Vancouver, BC October 2004

Motivation Mobile / high level use cases Main Challenges Deployment patterns Architecture and mappings Scope / objectives for Lemonade

Mobile Mobile Access to while mobile Main Expectations: To receive quasi-instantaneous notification of new e- mails when within coverage (if setup this way) To reflect quasi-instantaneously new or server events in the mobile client when within coverage To send quasi-instantaneously composed on mobile client from appropriate server when within coverage or as soon that coverage is established otherwise To efficiently manipulate s / drafts / attachment as needed or as preferred End-to-end secure when needed Low or at least bearable cost of usage

Mobile Additional considerations: Format adaptation (attachments) DRM rules Provisioning / setup Charging Synchronization with other clients: Peer to peer vs. with server Relationship to PIM (agenda / Address Book)

Mobile Main actors: User Operator service provider: Service provider (e.g. Operator, other server provider) Enterprise Other players in ecosystem: Device Manufacturers Client software providers server manufacturers: server Mobile enablement

Challenges (incomplete) Devices: Constrained memory / processing power (always improving): Wide range to support Limited battery life (will remain a problem for a long time): Constrains processing capability Constrains connectivity patterns (not always fully connected but may be awaken via outband notifications…) Constraints acceptable bandwidth More exotic platforms: Sometimes proprietary or closed Challenging or controlled software distribution channels: Installing, provisioning, supporting, upgrading, … E.g. DRM trusted clients Wide range of control models by: device manufacturer, operator, enterprise, user

Challenges (incomplete) Networks: (and operators) Different underlying network technologies / bearers with different behavior / capabilities Intermittent connectivity: Loss of coverage Nature of mobility (e.g. radio turned off in planes) Temporary IP addresses Unreliable delivery (Connection) Out band notification schemes Unreliable But can be used as wake up / notification scheme Limited bandwidth: Limited capabilities shared across all users Roaming within and across domain / operators / technologies

Challenges (incomplete) Cost: Multiple cost models (free, unlimited, per packet, per service / type of service, …) In general, … Costly Controlled: Wall guarded: Inbound and outbound traffic Internal traffic With its own authentication mechanisms etc… Regulated: QoS Privacy Exchanged data Reachability Logging Accountability …

Challenges (incomplete) Enterprises (and other SPs): Wall guarded intranets: Firewalls, VPN, … IT Corporate security guidelines: Wide range – in general VERY conservative e.g. Require end-to-end security Allowed applications / usages / content Firewalls / ports / protocols No storage of company data outside intranet (in clear or not) Regulated: E.g. Journaling / Storage of all corporate s Control usage costs Need to integrate with existing IT infrastructure

Deployment patterns 1.Mobile by operators: operator hosted service Device in network Mobile enabled server in Operators Domain Roaming across compatible networks / operators 2.Mobile by service provider (enterprise, ISP): Device in operator network (including roaming) Mobile enabled server in service provider 3.Outsourced mobile enablement of service provider: 1.By Operator (operator hosted) 2.By other third party service provider Device in operator network (including roaming) server in other domain

Generic Logical Architecture and Protocols to deal with Mobile Client Mobile Enabling Server Server (Firewalls) Mobile enablers IMAP Mobile Protocol Outband Notifications, Provisioning, … Connector (Firewalls)

Mapped on deployment models: 1 Mobile Client Mobile Enabling Server Server (Firewalls) Mobile enablers IMAP Mobile Protocol Outband Notifications, Provisioning, … Connector (Firewalls) Operator

Mapped on deployment models: 2 Mobile Client Mobile Enabling Server Server (Firewalls) Mobile enablers IMAP Mobile Protocol Outband Notifications, Provisioning, … Connector (Firewalls) Operator Service Provider

Mapped on deployment models: 3.1 Mobile Client Mobile Enabling Server Server (Firewalls) Mobile enablers IMAP Mobile Protocol Outband Notifications, Provisioning, … Connector (Firewalls) Operator Service Provider

Mapped on deployment models: 3.2 Mobile Client Mobile Enabling Server Server (Firewalls) Mobile enablers IMAP Mobile Protocol Outband Notifications, Provisioning, … Connector (Firewalls) Operator Service ProviderThird Party Service Provider

Scope / Objectives for Lemonade Will lemonade specify the mobile protocol or specify a set of IMAP optimizations inspired from mobile but not necessarily addressing all these issues.