draft-ietf-lemonade-architecture-00.txt   draft-ietf-lemonade-architecture-01.txt 
LEMONADE Working Group E. Burger LEMONADE Working Group E. Burger
Internet-Draft BEA Internet-Draft BEA Systems, Inc.
Intended status: Informational G. Parsons Intended status: Informational G. Parsons
Expires: May 15, 2008 Nortel Expires: July 1, 2008 Nortel Networks
November 12, 2007 December 29, 2007
LEMONADE Architecture - Supporting OMA Mobile Email (MEM) using Internet LEMONADE Architecture - Supporting OMA Mobile Email (MEM) using Internet
Mail Mail
draft-ietf-lemonade-architecture-00.txt draft-ietf-lemonade-architecture-01.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 36 skipping to change at page 1, line 36
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 15, 2008. This Internet-Draft will expire on July 1, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document specifies the architecture for mobile email, as This document specifies the architecture for mobile email, as
described by the OMA, using Internet Mail protocols. This described by the OMA, using Internet Mail protocols. This
architecture is the basis of the work of the LEMONADE WG and is a architecture is the basis of the work of the LEMONADE WG and is a
guidleine for the LEMONADE Profile. guideline for the LEMONADE Profile.
Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [1].
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. OMA Mobile Email (MEM) . . . . . . . . . . . . . . . . . . . . 5 2. OMA Mobile Email (MEM) . . . . . . . . . . . . . . . . . . . . 3
2.1. OMA MEM Requirements . . . . . . . . . . . . . . . . . . . 5 2.1. OMA MEM Requirements . . . . . . . . . . . . . . . . . . . 3
2.2. OMA MEM Architecture . . . . . . . . . . . . . . . . . . . 5 2.2. OMA MEM Architecture . . . . . . . . . . . . . . . . . . . 3
2.2.1. OMA MEM logical Architecture . . . . . . . . . . . . . 5 2.2.1. OMA MEM logical Architecture . . . . . . . . . . . . . 3
2.2.2. OMA MEM Deployment Issues . . . . . . . . . . . . . . 7 2.2.2. OMA MEM Deployment Issues . . . . . . . . . . . . . . 5
2.3. OMA MEM Technical Specification . . . . . . . . . . . . . 8 2.3. OMA MEM Technical Specification . . . . . . . . . . . . . 6
3. IETF LEMONADE Architecture . . . . . . . . . . . . . . . . . . 9 3. IETF LEMONADE Architecture . . . . . . . . . . . . . . . . . . 6
3.1. Relationship between the OMA MEM and LEMONADE logical 3.1. Relationship between the OMA MEM and LEMONADE logical
architectures . . . . . . . . . . . . . . . . . . . . . . 10 architectures . . . . . . . . . . . . . . . . . . . . . . 8
3.2. LEMONADE realization of OMA MEM with non-LEMONADE 3.2. LEMONADE realization of OMA MEM with non-LEMONADE
compliant servers . . . . . . . . . . . . . . . . . . . . 12 compliant servers . . . . . . . . . . . . . . . . . . . . 9
3.2.1. LEMONADE realization of OMA MEM with non-LEMONADE 3.2.1. LEMONADE realization of OMA MEM with non-LEMONADE
IMAP servers . . . . . . . . . . . . . . . . . . . . . 12 IMAP servers . . . . . . . . . . . . . . . . . . . . . 9
3.2.2. LEMONADE realization of OMA MEM with non-IMAP 3.2.2. LEMONADE realization of OMA MEM with non-IMAP
servers . . . . . . . . . . . . . . . . . . . . . . . 13 servers . . . . . . . . . . . . . . . . . . . . . . . 10
4. Filters and server to client notifications and LEMONADE . . . 14 4. Filters and server to client notifications and LEMONADE . . . 10
5. Notifications objectives . . . . . . . . . . . . . . . . . . . 16 5. Security Considerations . . . . . . . . . . . . . . . . . . . 11
6. Security considerations . . . . . . . . . . . . . . . . . . . 17 6. IANA considerations . . . . . . . . . . . . . . . . . . . . . 12
7. IANA considerations . . . . . . . . . . . . . . . . . . . . . 18 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12
8. Version history . . . . . . . . . . . . . . . . . . . . . . . 19 8. Informative References . . . . . . . . . . . . . . . . . . . . 12
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Intellectual Property and Copyright Statements . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 23
Intellectual Property and Copyright Statements . . . . . . . . . . 24
1. Introduction 1. Introduction
This document describes the architecture of OMA mobile email (MEM) This document describes the architecture of OMA mobile email (MEM)
using Internet Mail protocols defined by the IETF. Many of these using Internet Mail protocols defined by the IETF. The LEMONADE work
protocols have been enhanced by the LEMONADE work group for use in group has enhanced many of these protocols for use in the mobile
the mobile environment and are summarized in the LEMONADE profile [5] environment and are summarized in the LEMONADE profile [4] and its
and its revision LEMONADE profile bis [6]. This document shows how revision LEMONADE profile bis [5]. This document shows how the OMA
the OMA MEM Requirement document [3] , OMA MEM Architecture [2] and MEM Requirement document [2], OMA MEM Architecture [1], and OMA MEM
OMA MEM Technical Specification [4] relate to the work of LEMONADE. Technical Specification [3] relate to the work of LEMONADE.
2. OMA Mobile Email (MEM) 2. OMA Mobile Email (MEM)
The OMA Mobile Email (MEM) sub-working group has spent some time The OMA Mobile Email (MEM) sub-working group has spent some time
studying the requirements and architecture of mobile email. IETF studying the requirements and architecture of mobile email. IETF
LEMONADE has been liaising with them and have based much of our LEMONADE has been liaising with them and has based much of our
Internet Mail enhancements based on their input. This section Internet Mail enhancements based on their input. This section
summarizes the output of the OMA. summarizes the output of the OMA.
2.1. OMA MEM Requirements 2.1. OMA MEM Requirements
The OMA MEM activity has collected a set of use cases and derived The OMA MEM activity collected a set of use cases and derived
requirements for a mobile email enabler (MEM). the resulting work is requirements for a mobile email enabler (MEM). The OMA MEM
summarized in OMA MEM Requirements [3]. Some requirements relates to Requirements [2] summarizes this work. Some requirements relates to
email protocols, some involve other OMA technologies outside the email protocols, some involve other OMA technologies outside the
scope of IETF and some relate to implementations and normative scope of IETF and some relate to implementations and normative
interoperability statements for clients and servers. interoperability statements for clients and servers.
2.2. OMA MEM Architecture 2.2. OMA MEM Architecture
This section gives a brief introduction to the OMA MEM Architecture. This section introduces the OMA MEM Architecture.
2.2.1. OMA MEM logical Architecture 2.2.1. OMA MEM logical Architecture
The OMA MEM activity has derived a logical architecture from the The OMA MEM activity has derived a logical architecture from the
requirements and use cases described in [3]. A simplification for requirements and use cases described in [2]. A simplification for
illustrative purposes is shown inFigure 1, where arrows indicate illustrative purposes is shown inFigure 1, where arrows indicate
content flows. content flows.
__________ __________
| Other | | Other |
----| Mobile |<--- +---| Mobile |<--+
| | Enablers | | | | Enablers | |
| |__________| | | |__________| |
|ME-4 |ME-3 |ME-4 |ME-3
_v____ ___v____ ________ _v____ ___v____ ________
| | | | | | | |ME-1 | | | |
| MEM |ME-1 | MEM | I2 | Email | | MEM |-------->| MEM | I2 | Email |
|Client|<------->| Server |<---->| Server | |Client| ME-2| Server |<---->| Server |
|______| ME-2|________| |________| |______|<--------|________| |________|
^ ^
|ME-5 |ME-5
| |
Figure 1: Basic OMA MEM logical architecture Figure 1: Basic OMA MEM logical architecture
It identifies the following elements: Figure 1 identifies the following elements:
o The MEM client that implements the client-side functionality of
o The MEM client which implements the client-side functionality of
the OMA Mobile Email Enabler. It is also responsible for the OMA Mobile Email Enabler. It is also responsible for
providing the mobile email user experience and interface to the providing the mobile email user experience and interface to the
user and storing the email and data to be sent to the MEM server user and storing the email and data to be sent to the MEM server
when not connected. when not connected.
o The MEM server that implements the server-side functionality of
o The MEM server which implements the server-side functionality of
the OMA Mobile Email Enabler (MEM). the OMA Mobile Email Enabler (MEM).
o The MEM protocol between the MEM Client and MEM Server. It is o The MEM protocol between the MEM Client and MEM Server. It is
responsible for all the inband data exchanges that take place responsible for all the in-band data exchanges that take place
between the MEM client and server in order to update the MEM between the MEM client and server in order to update the MEM
client with email server changes, the email server with changes in client with email server changes, the email server with changes in
the MEM client and to send new email from the email server. the MEM client and to send new email from the email server.
o Other OMA enablers are needed to directly support the mobile email o Other OMA enablers are needed to directly support the mobile email
enabler. They are out of scope of IETF but they may include enabler. They are out of scope of IETF but they may include
support for: support for:
* Client provisioning and management for over the air * Client provisioning and management for over the air
installation of the MEM client on the device, provisioning of installation of the MEM client on the device, provisioning of
its settings and revocation its settings and revocation, and
* Messaging enablers for out-of-band notification, where out-of-
* Messaging enablers for outband notification, where outband band notifications that are server to client event exchanges
notifications that are server to client event exchanges not not transported by the MEM protocol but via other channels.
transported by the MEM protocol but via other channels.
OMA identifies different interfaces: OMA identifies different interfaces:
o ME-1: MEM client interface to interact via the MEM protocol with o ME-1: MEM client interface to interact via the MEM protocol with
the MEM server the MEM server
o ME-2: Corresponding interface of the MEM server o ME-2: Corresponding interface of the MEM server
o ME-3: Out-of-band MEM server interfaces, for example to support
generation of server to client notifications.
o ME-3: Outband MEM server interfaces (e.g. to support generation of o ME-4: Out-of-band MEM client interfaces (e.g. to receive server to
server to client notifications).
o ME-4: Outband MEM client interfaces (e.g. to receive server to
client notifications). client notifications).
o ME-5: Interface for management of MEM enabler server settings, o ME-5: Interface for management of MEM enabler server settings,
user preferences and filters (globally and per account) user preferences, and filters, globally and per account.
The MEM server enables an email server. In a particular The MEM server enables an email server. In a particular
implementation, the email server may be packaged with (internal to implementation, the email server may be packaged with (internal to
it) the MEM server or be in a separate component. In such cases, it) the MEM server or be a separate component. In such cases,
interfaces to the email server are out of scope of the OMA MEM interfaces to the email server are out of scope of the OMA MEM
specifications. In the present document, we focus on the case where specifications. In the present document, we focus on the case where
the backend consists of IETF IMAP and Submit servers. However, the backend consists of IETF IMAP and Submit servers. However, we
relationship to other cases are also discussed. The I2 interface is also discuss the relationship to other cases. The I2 interface is an
an OMA notation to designate protocol / interfaces that are not OMA notation to designate protocol / interfaces that are not
specified by the MEM enabler but may be standardized elsewhere. specified by the MEM enabler but may be standardized elsewhere.
2.2.2. OMA MEM Deployment Issues 2.2.2. OMA MEM Deployment Issues
The OMA MEM Architecture document [2] further identifies deployment The OMA MEM Architecture document [1] further identifies deployment
models. models.
2.2.2.1. OMA MEM proxy 2.2.2.1. OMA MEM proxy
The OMA MEM Architecture document [2] identifies OMA MEM server The OMA MEM Architecture document [1] identifies OMA MEM server
proxies as server components that may be deployed ahead of firewalls proxies as server components that may be deployed ahead of firewalls
to facilitate traversa of firewalls. to facilitate firewall traversal.
2.2.2.2. OMA MEM deployment cases 2.2.2.2. OMA MEM deployment cases
OMA MEM identifies that each component (MEM client, MEM servers, OMA MEM identifies that each component (MEM client, MEM servers,
Other enablers and email server) may be deployed in different other enablers, and the email server) may be deployed in different
domains, possibly separated by firewalls and other network domains, possibly separated by firewalls and other network
intermediaries. MEM proxies may be involved in front of firewall intermediaries. MEM proxies may be involved in front of firewall
that protects the MEM server domain. that protects the MEM server domain.
OMA MEM target support of configurations where: OMA MEM targets support of configurations where:
o All components are within a same domain, such as in a mobile
o All components are within a same domain (Mobile operator) operator
o MEM client and other enablers are in the mobile operator domain,
o MEM client and other enablers are in the mobile operator domain, a there is a MEM proxy, and the MEM server and email server are in
MEM proxy is involved and MEM server and email server are in the the domain of the email service provider
domain of the email service provider
o MEM client and other enablers as well as a MEM proxy are in the o MEM client and other enablers as well as a MEM proxy are in the
mobile operator domain, MEM server and email server are in the mobile operator domain, MEM server and email server are in the
domain of the email service provider domain of the email service provider
o MEM client and other enablers are in the mobile operator domain, a o MEM client and other enablers are in the mobile operator domain, a
MEM proxy is in a third party service provider domain and MEM MEM proxy is in a third party service provider domain and MEM
server and email server are in the domain of the email service server and email server are in the domain of the email service
provider provider
o MEM client, other enabler and MEM server are in the mobile o MEM client, other enabler and MEM server are in the mobile
operator domain and email server is in the domain of the email operator domain and email server is in the domain of the email
service provider service provider
o MEM client and other enablers are in the mobile operator domain, o MEM client and other enablers are in the mobile operator domain,
MEM server is in a third party service provider domain and the MEM server is in a third party service provider domain and the
email server is in the domain of the email service provider email server is in the domain of the email service provider
The e-mail service provider can be either a third-party service
provider, a network service provider, or an enterprise e-mail
service.
2.3. OMA MEM Technical Specification 2.3. OMA MEM Technical Specification
The OMA MEM activity will conclude with a specification for a mobile The OMA MEM activity will conclude with a specification for a mobile
email enabler (MEM). The ongoing work is in OMA MEM Technical email enabler (MEM). The ongoing work is in OMA MEM Technical
Specification [4]. LEMONADE is a basis for the mechanism, however, Specification [3]. LEMONADE is a basis for the mechanism. However,
some additional details that are outside the scope of IETF will also some additional details that are outside the scope of IETF will also
be included. be included.
OMA provides ways to perform provisioning via OMA client provisioning OMA provides ways to perform provisioning via OMA client provisioning
and device management. Other provisioning specifications are and device management. Other provisioning specifications are
available (e.g. SMS based). available (e.g., SMS based).
OMA provides enablers to support outband notifications: the outband OMA provides enablers to support out-of-band notification mechanisms,
notification mechanisms. Also, OMA XDM may be considered also for as well as filter specifications (such as XDM), remote device
outband filter changes. . deactivation, and other, non-Internet activities.
3. IETF LEMONADE Architecture 3. IETF LEMONADE Architecture
This section gives a brief introduction to the LEMONADE Architecture. This section introduces the LEMONADE Architecture.
The IETF LEMONADE activity has derived a LEMONADE profile [5] with The IETF LEMONADE activity has derived a LEMONADE profile [4] with
the logical architecture represented in Figure 2, where arrows the logical architecture represented in Figure 2, where arrows
indicate content flows. indicate content flows.
______________ ______________
| | | |
_________| Notification | _________| Notification |
| | Mechanism | | | Mechanism |
| |______________| | |______________|
|Notif. ^ |Notif. ^
|Protocol | |Protocol |
skipping to change at page 9, line 38 skipping to change at page 7, line 30
\SUBMIT | \SUBMIT |
\ ____v_____ \ ____v_____
\ | | _____ \ | | _____
\ | LEMONADE | ESMTP | | \ | LEMONADE | ESMTP | |
---->| Submit |--------------->| MTA | ---->| Submit |--------------->| MTA |
| Server | |_____| | Server | |_____|
|__________| |__________|
Figure 2: LEMONADE logical architecture Figure 2: LEMONADE logical architecture
The LEMONADE profile [5] assumes: The LEMONADE profile [4] assumes:
o IMAP protocol [6] including LEMONADE profile extensions [4]
o IMAP protocol [7] including LEMONADE profile extensions [5] o SUBMIT protocol [8], including LEMONADE profile extensions
o SUBMIT protocol (SMTP [9], ...) including LEMONADE profile
extensions
o LEMONADE profile compliant IMAP store connected to MTA (Mail o LEMONADE profile compliant IMAP store connected to MTA (Mail
Transfer Agent) via ESMTP [8] Transfer Agent) via ESMTP [7]
o LEMONADE profile compliant Submit server connected to MTA via o LEMONADE profile compliant Submit server connected to MTA via
ESMTP ESMTP
o Lemonade profile message store / submit server protocols (URLAUTH,
o Lemonade profile message store / submit server protocols (URLAUTH) BURL, CATENATE) (see lemonade Profile [4]).
(see [5]). o Out-of-band server to client notifications relying on external
o Outband server to client notifications relying on external
notification mechanisms (and notification protocols) that may be notification mechanisms (and notification protocols) that may be
out of scope of the LEMONADE profile. out of scope of the LEMONADE profile.
o A LEMONADE aware MUA (Mail User Agent). While use of out-of-band
o A LEMONADE aware MUA (Mail User Agent). While use of outband
notification is described in the LEMONADE profile, support for the notification is described in the LEMONADE profile, support for the
underlying notifications mechanisms/protocols is out of scope of underlying notifications mechanisms/protocols is out of scope of
the LEMONADE specifications. the LEMONADE specifications.
Further details on the IETF email protcol stack and architecture can Further details on the IETF email protocol stack and architecture can
be found in [16] be found in [10]
3.1. Relationship between the OMA MEM and LEMONADE logical 3.1. Relationship between the OMA MEM and LEMONADE logical
architectures architectures
Figure 3 illustrates the mapping of the IETF LEMONADE logical Figure 3 illustrates the mapping of the IETF LEMONADE logical
architecture on the OMA MEM logical architecture. architecture on the OMA MEM logical architecture.
_____________________ _____________________
| Other_Mob. Enablers | | Other_Mob. Enablers |
| |--------------| | | |--------------| |
_________| Notification | | _________| Notification | |
| | | Mechanism | | | | | Mechanism | |
| | |______________| | | | |______________| |
|Notif. |____________^________| |Notif. |____________^________|
|Protocol ______|__________ |Protocol ______|__________
ME-4 | | ___|_ME-3_ | ME-4 | | ___|_ME-3_ |
___|____ | | | | _____ ___|____ | | | | _____
skipping to change at page 11, line 36 skipping to change at page 8, line 41
ME-2b | | Server | | |_____| ME-2b | | Server | | |_____|
| |__________| | | |__________| |
|MEM Email | |MEM Email |
|Server Server| |Server Server|
|_________________| |_________________|
^ ^
|ME-5 |ME-5
| |
Figure 3: Mapping of LEMONADE logical architecture onto the OMA MEM Figure 3: Mapping of LEMONADE logical architecture onto the OMA MEM
logical architecture. logical architecture
As described in Section 3, the LEMONADE profile assumes LEMONADE As described in Section 3, the LEMONADE profile assumes LEMONADE
profile compliant IMAP stores and Submit servers. Because the profile compliant IMAP stores and Submit servers. Because the
LEMONADE profile extends the IMAP store and the submit server, the LEMONADE profile extends the IMAP store and the submit server, the
mobile enablement of email provided by the LEMONADE profile is mobile enablement of email provided by the LEMONADE profile is
directly provided in these server. Mapped to OMA MEM logical directly provided in these servers. Mapping to the OMA MEM logical
architecture, for the case considered and specified by the LEMONADE architecture, for the case considered and specified by the LEMONADE
profile, the MEM server and email server logically combined. They profile, we logically combine the MEM server and email server.
are however split into distinct LEMONADE message store and LEMONADE However, in lemonade we split them logically into a distinct LEMONADE
submit server. ME-2 consists of two interfaces ME-2a and ME-2b message store and a LEMONADE submit server. ME-2 consists of two
associated respectively to IMAP extended according to the LEMONADE interfaces. ME-2a is IMAP extended according to the LEMONADE
profile and SUBMIT extended according to the LEMONADE profile. profile. ME-2b is SUBMIT extended according to the LEMONADE profile.
The MUA is part of the MEM client. The MUA is part of the MEM client.
External notifications mechanism can be part of the other OMA enabler The external notifications mechanism is part of OMA enablers
specified by OMA (or other activities). specified by the OMA.
3.2. LEMONADE realization of OMA MEM with non-LEMONADE compliant 3.2. LEMONADE realization of OMA MEM with non-LEMONADE compliant
servers servers
The OMA MEM activity is not limited to enabling Lemonade compliant The OMA MEM activity is not limited to enabling Lemonade compliant
servers. It explicitly identifies the need to support other servers. It explicitly identifies the need to support other back-
backends. ends. This is, of course, outside the scope of the IETF Lemonade
activity.
3.2.1. LEMONADE realization of OMA MEM with non-LEMONADE IMAP servers 3.2.1. LEMONADE realization of OMA MEM with non-LEMONADE IMAP servers
Figure 4 illustrates the case of IMAP servers that are not (yet) Figure 4 illustrates the case of IMAP servers that are not LEMONADE
LEMONADE compliant. In such case, the I2 interface between the MEM compliant. In such case, the I2 interface between the MEM server
server components and the IMAP store and submit server are IMAP and components and the IMAP store and submit server are IMAP and SUBMIT
SUBMIT. without Lemonade extensions.
______________ ______________
| | | |
_________| Notification | _________| Notification |
| | Mechanism | | | Mechanism |
| |______________| | |______________|
|Notif. ^ |Notif. ^
|Protocol | |Protocol |
| ___|______ _____________ | ___|______ _____________
| | LEMONADE | | | _____ | | LEMONADE | | | _____
__v__ IMAP | MEM | IMAP |NON-LEMONADE | ESMTP | | __v__ IMAP | MEM | IMAP |NON-LEMONADE | ESMTP | |
skipping to change at page 12, line 45 skipping to change at page 10, line 4
\SUBMIT | \SUBMIT |
\ ____v_____ _____________ \ ____v_____ _____________
\ | | | | _____ \ | | | | _____
\ | LEMONADE | SUBMIT |NON-LEMONADE | ESMTP | | \ | LEMONADE | SUBMIT |NON-LEMONADE | ESMTP | |
-->| MEM | |Submit | | | -->| MEM | |Submit | | |
| Enabler |------->|Server |------>| MTA | | Enabler |------->|Server |------>| MTA |
ME-2b | Server | | | |_____| ME-2b | Server | | | |_____|
|__________| |_____________| |__________| |_____________|
Figure 4: Architecture to support non-LEMONADE IMAP servers with a Figure 4: Architecture to support non-LEMONADE IMAP servers with a
LEMONADE realization of OMA MEM enabler. LEMONADE realization of an OMA MEM enabler
3.2.2. LEMONADE realization of OMA MEM with non-IMAP servers 3.2.2. LEMONADE realization of OMA MEM with non-IMAP servers
Figure 5 illustrates the cases where the message store and submit Figure 5 illustrates the cases where the message store and submit
servers are not IMAP store or submit servers. They may be POP3 servers are not IMAP store or submit servers. They may be POP3
servers or other proprietary message stores. servers or other proprietary message stores.
______________ ______________
| | | |
_________| Notification | _________| Notification |
| | Mechanism | | | Mechanism |
| |______________| | |______________|
|Notif. ^ |Notif. ^
|Protocol | |Protocol |
| ___|______ _____________ | ___|______ _____________
| | LEMONADE | | | _____ | | LEMONADE | | | _____
__v__ IMAP | MEM | I2 |Proprietary | ESMTP | | __v__ IMAP | MEM | I2 |Proprietary | ESMTP | |
skipping to change at page 13, line 38 skipping to change at page 10, line 38
\ | | | | _____ \ | | | | _____
\ | LEMONADE | I2 |Proprietary | ESMTP | | \ | LEMONADE | I2 |Proprietary | ESMTP | |
-->| MEM | |Submit | | | -->| MEM | |Submit | | |
| Enabler |------->|Server |------>| MTA | | Enabler |------->|Server |------>| MTA |
ME-2b | Server | | | |_____| ME-2b | Server | | | |_____|
|__________| |_____________| |__________| |_____________|
Figure 5: Architecture to support non-IMAP servers with a LEMONADE Figure 5: Architecture to support non-IMAP servers with a LEMONADE
realization of OMA MEM enabler. realization of OMA MEM enabler.
I2 designates proprietary adapters to the backends. They may invoved I2 designates proprietary adapters to the back-ends.
functions performed in the message stores or submit server as well as
in the MEM enabler server.
4. Filters and server to client notifications and LEMONADE 4. Filters and server to client notifications and LEMONADE
OMA MEM RD [3] and AD [2] emphasize the need to provide mechanisms OMA MEM RD [2] and AD [1] emphasize the need to provide mechanisms
for server to client notifications of email events and filtering. for server to client notifications of email events and filtering.
Figure 6 illustrates how notification and filterings are introduced Figure 6 illustrates how notification and filtering works in the
in LEMONADE profile [5]. LEMONADE profile [4].
______________ ______________
| | | |
_________| Notification | _________| Notification |
| | Mechanism | | | Mechanism |
| |______________| | |______________|
|Notif. ^ |Notif. ^
|Protocol -------\ _|_ |Protocol -------\ _|__
| ______| ___\>|NF|____ | ______| ___\>|NF|____
| | | ---- | _____ | | | ---- | _____
__v__| IMAP |__ LEMONADE |___ ESMTP __| | __v__| IMAP |__ LEMONADE |___ ESMTP __| |
| |<-------->|VF| IMAP |DF |<--------|AF| MTA | | |<-------->|VF| IMAP |DF |<--------|AF| MTA |
| MUA |\ ME-2a |-- Store |-^- --|_____| | MUA |\ ME-2a |-- Store |--- --|_____|
|_____| \ |_____________| | |_____| \ |_____________| ^
\_\_______________|_______| \_\_______________|_______|
\ |URLAUTH \ |URLAUTH
\SUBMIT | \SUBMIT |
\ ____v_____ \ ____v_____
\ | | _____ \ | | _____
\ | LEMONADE | ESMTP | | \ | LEMONADE | ESMTP | |
---->| Submit |--------------->| MTA | ---->| Submit |--------------->| MTA |
ME-2b | Server | |_____| ME-2b | Server | |_____|
|__________| |__________|
Figure 6: Filtering mechanism defined in LEMONADE architecture Figure 6: Filtering mechanism defined in LEMONADE architecture
In Figure 6, four categories of filters are defined: In Figure 6, we define four categories of filters:
o AF: Administrative Filters - The e-mail service provider usually
o AF: Administrative Filters - Set up by email service provider. AF sets administrative filters. The user typically does not
are typically not configured by the user and set to apply policies configure AF. AF applies policies covering content filtering,
content filtering, virus protection, spam filtering etc... virus protection, spam filtering, etc.
o DF: Deposit Filters - Filters that are executed on deposit of new o DF: Deposit Filters - Filters that are executed on deposit of new
emails. They can be defined as SIEVE filters [10]. They can emails. They can be defined as SIEVE filters [9]. They can
include vacation notices. include vacation notices.
o VF: View Filters - Filters that define which emails are visible to o VF: View Filters - Filters that define which emails are visible to
the MUA. View filters can be performed via IMAP using the the MUA. View filters can be performed via IMAP using the
facilities described in [6]. facilities described in [5].
o NF: Notification Filters - Filters that define for what email o NF: Notification Filters - Filters that define for what email
server event an outband notification is sent to the client, as server event an out-of-band notification is sent to the client, as
described in [6]. described in [5].
The filters are manageable from the MUA:
o NF and DF: via SIEVE management protocol
5. Notifications objectives
According to these analyses, there is a need to support: # Mechanisms
for event-based (server to client) synchronization: * Defines the
relationship between notification mechanisms and the IMAP4 protocol -
To minimize the latency observed for email events on the email server
to be reflected in the email client. - To avoid unnecessary polling
and requests from the e-mail clients: . To reduce the total amount
of data to be exchanged between email server and client, e.g. by
allowing the email client to select which messages to synchronize and
how to synchronize. . To reduce the amount of transactions. * Needs
to cope with possible lost or delayed notifications * Support in-band
(within IMAP band) and out-band notifications (Exchanged via other
servers / enablers). - Specified in ways that are network transport
independent but may contain some bindings to particular notification
channels (e.g. SMS binary, WAP Push, SIP Notification, ...) - When
the email client is connected to the email server, only inband
notifications is expected take place * Defines notification payload
for inband and outband mechanisms. # Server-side filtering to decide
which messages will be accessible by the email client. * Filtering
results into the following logical types: - Type A: Messages filtered
out and not accessible by the email client (no notification, no
header access, no access) - Type B: Messages that are accessible by
the mobile e-mail enabler client but no outband notification takes
place. Inband notification might however take place if email client
is already connected to email server. - Type C: Messages that are
accessible by the e-mail client for which notifications (outband or
inband) are always sent to the email client. # Notions of Filters: *
View filters: Filters that determine which email messages are of type
B and C or A * Notification filters: Filters that determine which
email messages are of type C or B * Event filters: Filters that
determines what events are to be notified to the client # Mechanisms
to allow the user to update the filters from the email client #
Mechanisms to allow configuration and exchange of settings between
the client and the server in band or outband: - Server to client:
e.g. server ID, account name, policies, ... - Client to server: e.g.
rules filters vacation notices, notification channel, ...
6. Security considerations
This specification provides no security measures beyond those in the The MUA can manage the NF and DF filters using the SIEVE management
referenced Internet Mail and LEMONADE documents. protocol.
We note however that there are security risks associated to: 5. Security Considerations
o Outband notifications We note there are security risks associated with:
o Out-of-band notifications
o Server configuration by client o Server configuration by client
o Client configuration by server o Client configuration by server
o Presence of MEM proxy servers o Presence of MEM proxy servers
o Presence of MEM servers as intermediaries o Presence of MEM servers as intermediaries
o Measures to address the need to traverse firewalls
o Measures to addess the need to traverse firewalls We refer the reader to the relevant Internet Mail, IMAP, SUBMIT, and
Lemonade documents for how we address these issues.
7. IANA considerations 6. IANA considerations
No specific IANA considerations have been identified that are not None.
covered by the different drafts and RFCs included in the realization
described in this document.
8. Version history 7. Acknowledgements
Version 0: This document was extracted from sections of The authors acknowledge and appreciate the work and comments of the
IETF LEMONADE working group and the OMA MEM working group. We
extracted the contents of this document from sections of
draft-ietf-lemonade-profile-bis-05.txt and draft-ietf-lemonade-profile-bis-05.txt and
draft-ietf-lemonade-notifications-04.txt. draft-ietf-lemonade-notifications-04.txt.
9. Acknowledgements 8. Informative References
The authors acknowledge and appreciate the work and comments of the
IETF LEMONADE working group and the OMA MEM working group.
10. References
[1] Bradner, S., "Key words for use in RFCs to Indicate
Requirements Levels", RFC 2119, BCP 14, March 1997.
[2] "Mobile Email Architecture Document", [1] Open Mobile Alliance, "Mobile Email Architecture Document",
OMA http://www.openmobilealliance.org/, June 2007. June 2007, <http://member.openmobilealliance.org/ftp/
public_documents/mwg/MEM/Permanent_documents/
OMA-AD-Mobile_Email-V1_0_0-20070614-D.zip>.
[3] "Mobile Email RequirementS Document", [2] Open Mobile Alliance, "Mobile Email RequirementS Document",
OMA http://www.openmobilealliance.org/, Oct 2005. OMA http://www.openmobilealliance.org/, Oct 2005.
[4] "Mobile Email Technical Specification", OMA (Work in Progress), [3] Open Mobile Alliance, "Mobile Email Technical Specification",
http://www.openmobilealliance.org/, Oct 2007. OMA (Work in Progress), http://www.openmobilealliance.org/,
Oct 2007.
[5] Maes, S. and A. Melnikov, "LEMONADE profile", RFC 4550.
[6] Maes, S. and A. Melnikov, "LEMONADE profile bis",
draft-ietf-lemonade-profile-bis-0x (work in progress).
[7] Crispin, M., "IMAP4, Internet Message Access Protocol Version 4
rev1", RFC 3501, March 2003.
[8] Klensin, J., "SMTP Service Extensions", RFC 1861,
November 1995.
[9] Klensin, J., "Simple Mail Transfer Protocol", RFC 2821,
April 2001.
[10] "SIEVE", Internet Draft draft-ietf-sieve-3028bis-12.
[11] Leiba, B., "IMAP4 IDLE command", RFC 2177, June 1997. [4] Maes, S. and A. Melnikov, "Internet Email to Support Diverse
Service Environments (Lemonade) Profile", RFC 4550, June 2006.
[12] Newman, C., "Internet Message Store Events", [5] Cridland, D., Melnikov, A., and S. Maes, "The Lemonade
draft-newman-lemonade-msgevent-0x (work in progress). Profile", draft-ietf-lemonade-profile-bis-07 (work in
progress), November 2007.
[13] "Open Mobile Alliance Email Notification Version 1.0", [6] Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION
OMA http://www.openmobilealliance.org/, August 2002. 4rev1", RFC 3501, March 2003.
[14] Maes, S. and et Al., "CONVERT", draft-ietf-lemonade-convert-0x [7] Gwinn, R., "Simple Network Paging Protocol - Version 3 -Two-Way
(work in progress). Enhanced", RFC 1861, October 1995.
[15] Melnikov, A. and et Al., "IMAP URL Scheme", [8] Gellens, R. and J. Klensin, "Message Submission for Mail",
draft-ietf-lemonade-rfc2192bis-0x (work in progress). RFC 4409, April 2006.
[16] Crocker, D., "Internet Mail Architecture", [9] Guenther, P. and T. Showalter, "Seive: An Email Filtering
draft-crocker-email-arch-0x (work in progress). Language", October 2007, <http://www.ietf.org/internet-drafts/
draft-ietf-sieve-3028bis-13.txt>.
[17] Melnikov, A. and et Al., "IMAP4 extension for quick reconnect", [10] Crocker, D., "Internet Mail Architecture",
draft-ietf-lemonade-reconnect-0x (work in progress). draft-crocker-email-arch-09 (work in progress), May 2007.
Authors' Addresses Authors' Addresses
Eric Burger Eric W. Burger
BEA Systems, Inc. BEA Systems, Inc.
Boston, MA 4 Van de Graaf Dr.
Burlington, MA 01803
USA USA
Phone: +1 781 993 7437 Phone: +1 781 993 7437
Email: eburger@bea.com Fax:
Email: eric.burger@bea.com
URI: http://www.standardstrack.com
Glenn Parsons Glenn Parsons
Nortel Networks Nortel Networks
3500 Carling Avenue 3500 Carling Avenue
Ottawa, ON K2H 8E9 Ottawa, ON K2H 8E9
Canada Canada
Phone: +1 613 763 7582 Phone: +1 613 763 7582
Email: gparsons@nortel.com Email: gparsons@nortel.com
 End of changes. 97 change blocks. 
260 lines changed or deleted 167 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/