draft-ietf-lemonade-architecture-04.txt   rfc5442.txt 
LEMONADE Working Group E. Burger Network Working Group E. Burger
Internet-Draft This Space for Sale Request for Comments: 5442 Consultant
Intended status: Informational G. Parsons Category: Informational G. Parsons
Expires: May 7, 2009 Nortel Networks Nortel Networks
November 3, 2008 LEMONADE Architecture - Supporting Open Mobile Alliance (OMA)
Mobile Email (MEM) Using Internet Mail
LEMONADE Architecture - Supporting Open Mobile Alliance (OMA) Mobile
Email (MEM) using Internet Mail
draft-ietf-lemonade-architecture-04
Status of this Memo
By submitting this Internet-Draft, each author represents that any Status of This Memo
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
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering This memo provides information for the Internet community. It does
Task Force (IETF), its areas, and its working groups. Note that not specify an Internet standard of any kind. Distribution of this
other groups may also distribute working documents as Internet- memo is unlimited.
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Copyright Notice
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at Copyright (c) 2009 IETF Trust and the persons identified as the
http://www.ietf.org/ietf/1id-abstracts.txt. document authors. All rights reserved.
The list of Internet-Draft Shadow Directories can be accessed at This document is subject to BCP 78 and the IETF Trust's Legal
http://www.ietf.org/shadow.html. Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
This Internet-Draft will expire on May 7, 2009. This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Abstract Abstract
This document specifies the architecture for mobile email, as This document specifies the architecture for mobile email, as
described by the Open Mobile Alliance (OMA), using Internet Mail described by the Open Mobile Alliance (OMA), using Internet Mail
protocols. This architecture was an important consideration for much protocols. This architecture was an important consideration for much
of the work of the LEMONADE (Enhancements to Internet email to of the work of the LEMONADE (Enhancements to Internet email to
Support Diverse Service Environments) work group in the IETF. This Support Diverse Service Environments) working group in the IETF.
document also describes how the LEMONADE architecture meets the OMA's This document also describes how the LEMONADE architecture meets
requirements for their Mobile Email (MEM) service. OMA's requirements for their Mobile Email (MEM) service.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction ....................................................2
2. OMA Mobile Email (MEM) . . . . . . . . . . . . . . . . . . . . 3 2. OMA Mobile Email (MEM) ..........................................2
2.1. OMA MEM Requirements . . . . . . . . . . . . . . . . . . . 3 2.1. OMA MEM Requirements .......................................2
2.2. OMA MEM Architecture . . . . . . . . . . . . . . . . . . . 3 2.2. OMA MEM Architecture .......................................3
2.2.1. OMA MEM logical Architecture . . . . . . . . . . . . . 3 2.2.1. OMA MEM Logical Architecture ........................3
2.2.2. OMA MEM Deployment Issues . . . . . . . . . . . . . . 5 2.2.2. OMA MEM Deployment Issues ...........................4
2.3. OMA MEM Technical Specification . . . . . . . . . . . . . 6 2.3. OMA MEM Technical Specification ............................6
3. IETF LEMONADE Architecture . . . . . . . . . . . . . . . . . . 6 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 . . . . . . . . . . . . . . . . . . . . . . 8 Architectures ..............................................7
3.2. LEMONADE realization of OMA MEM with non-LEMONADE 3.2. LEMONADE Realization of OMA MEM with
compliant servers . . . . . . . . . . . . . . . . . . . . 9 non-LEMONADE-Compliant Servers .............................9
3.2.1. LEMONADE realization of OMA MEM with non-LEMONADE 3.2.1. LEMONADE Realization of OMA MEM with
IMAP servers . . . . . . . . . . . . . . . . . . . . . 9 non-LEMONADE 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 . . . . . . . . . . . . . . . . . . . . . . . 10 Servers ............................................10
4. Filters and server to client notifications and LEMONADE . . . 11 4. Filters and Server-to-Client Notifications and LEMONADE ........11
5. Security Considerations . . . . . . . . . . . . . . . . . . . 13 5. Security Considerations ........................................13
6. IANA considerations . . . . . . . . . . . . . . . . . . . . . 13 6. Acknowledgements ...............................................13
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13 7. Informative References .........................................13
8. Informative References . . . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14
Intellectual Property and Copyright Statements . . . . . . . . . . 16
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. The LEMONADE work using Internet Mail protocols defined by the IETF. The LEMONADE
group has enhanced many of these protocols for use in the mobile working group has enhanced many of these protocols for use in the
environment. The LEMONADE profile [PROFILE] and its revision mobile environment. The LEMONADE profile [PROFILE] and its revision,
LEMONADE profile bis [PROFILE-bis] summarize such protocols and [PROFILE-bis], summarize such protocols and protocol use. This
protocol use. This document shows how the OMA MEM Requirement document shows how the OMA MEM Requirements document [MEM-req], OMA
document [MEM-req], OMA MEM Architecture [MEM-arch], and OMA MEM MEM Architecture [MEM-arch], and OMA MEM Technical Specification
Technical Specification [MEM-ts] relate to the work of LEMONADE in [MEM-ts] relate to the work of LEMONADE in the IETF.
the IETF.
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 has based much of our LEMONADE has been liaising with them and has based much of its
Internet Mail enhancements based on their input. This section Internet Mail enhancements on their input. This section summarizes
summarizes the output of the OMA. the output of the OMA.
2.1. OMA MEM Requirements 2.1. OMA MEM Requirements
The OMA MEM activity 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 OMA MEM requirements for a Mobile Email (MEM) enabler. The OMA MEM
Requirements [MEM-req] summarizes this work. Some requirements Requirements document [MEM-req] summarizes this work. Some
relates to email protocols, some involve other OMA technologies requirements relate to email protocols, some involve other OMA
outside the scope of IETF and some relate to implementations and technologies outside the scope of the IETF, and some relate to
normative interoperability statements for clients and servers. implementations and normative interoperability statements for clients
and servers.
2.2. OMA MEM Architecture 2.2. OMA MEM Architecture
This section introduces 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 [MEM-req]. A simplification requirements and use cases described in [MEM-req]. A simplification
for illustrative purposes is shown in Figure 1, where arrows indicate for illustrative purposes is shown in Figure 1, where arrows indicate
content flows. content flows.
__________ __________
| Other | | Other |
+---| Mobile |<--+ +---| Mobile |<--+
| | Enablers | | | | Enablers | |
skipping to change at page 4, line 20 skipping to change at page 3, line 34
|ME-4 |ME-3 |ME-4 |ME-3
_v____ ___v____ ________ _v____ ___v____ ________
| |ME-1 | | | | | |ME-1 | | | |
| MEM |-------->| MEM | I2 | Email | | MEM |-------->| MEM | I2 | Email |
|Client| ME-2| Server |<---->| Server | |Client| ME-2| Server |<---->| Server |
|______|<--------|________| |________| |______|<--------|________| |________|
^ ^
|ME-5 |ME-5
| |
Figure 1: Basic OMA MEM logical architecture Figure 1: Basic OMA MEM Logical Architecture
Figure 1 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 that 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 that implements the server-side functionality of
the OMA Mobile Email Enabler (MEM). the OMA Mobile Email (MEM) enabler.
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 in-band 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 and the email server with changes
the MEM client and to send new email from the email server. in the MEM client, and in order to send new email from the email
o Other OMA enablers are needed to directly support the mobile email server.
enabler. They are out of scope of IETF but they may include
support for: o Other OMA enablers that are needed to directly support the Mobile
* Client provisioning and management for over the air Email enabler. They are out of the scope of the IETF but may
include support for:
* 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, the client settings, and revocation of client privileges.
* Messaging enablers for out-of-band notification, where out-of- * Messaging enablers for out-of-band notification, where out-of-
band notifications that are server to client event exchanges band notifications that are server-to-client event exchanges
not transported by the MEM protocol but via other channels, and are not transported by the MEM protocol but via other channels.
* Billing, charging, and so on. * Billing, charging, and so on.
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-3: Out-of-band MEM server interfaces, for example to support o ME-2: Corresponding interface of the MEM server.
generation of server to client notifications.
o ME-4: Out-of-band MEM client interfaces (e.g. to receive server to o ME-3: Out-of-band MEM server interfaces; for example, to support
client notifications). generation of server-to-client notifications.
o ME-4: Out-of-band MEM client interfaces (e.g., to receive server-
to-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 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, we the backend consists of IETF IMAP and SUBMIT servers. However, we
also discuss the relationship to other cases. The I2 interface is an also discuss the relationship to other cases. The I2 interface is 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 [MEM-arch] further identifies The OMA MEM Architecture document [MEM-arch] further identifies
deployment models. deployment models.
2.2.2.1. OMA MEM proxy 2.2.2.1. OMA MEM Proxy
The OMA MEM Architecture document [MEM-arch] identifies OMA MEM The OMA MEM Architecture document [MEM-arch] identifies OMA MEM
server proxies as server components that may be deployed ahead of server proxies as server components that may be deployed ahead of
firewalls to facilitate firewall traversal. 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 the 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 a firewall
that protects the MEM server domain. that protects the MEM server domain.
OMA MEM targets support of configurations where: OMA MEM targets support of configurations where:
o All components are within the same domain, such as in a mobile o All components are within the same domain, such as in a mobile
operator operator.
o MEM client and other enablers are in the mobile operator domain,
there is a MEM proxy, and the MEM server and email server are in
the domain of the email service provider
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
domain of the email service provider
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
server and email server are in the domain of the email service
provider
o MEM client, other enabler and MEM server are in the mobile
operator domain and email server is in the domain of the email
service provider
o MEM client and other enablers are in the mobile operator domain,
MEM server is in a third party service provider domain and the
email server is in the domain of the email service provider
The e-mail service provider can be a third-party service provider, a o The MEM client and other enablers are in the mobile operator
network service provider, or an enterprise e-mail service. domain, there is a MEM proxy, and the MEM server and email server
are in the domain of the email service provider.
o The MEM client and other enablers as well as a MEM proxy are in
the mobile operator domain, and the MEM server and email server
are in the domain of the email service provider.
o The MEM client and other enablers are in the mobile operator
domain, a MEM proxy is in a third-party service provider domain,
and the MEM server and email server are in the domain of the email
service provider.
o The MEM client, other enabler, and MEM server are in the mobile
operator domain, and the email server is in the domain of the
email service provider.
o The MEM client and other enablers are in the mobile operator
domain, the MEM server is in a third-party service provider
domain, and the email server is in the domain of the email service
provider.
The email service provider can be a third-party service provider, a
network service provider, or an enterprise email 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 (MEM) enabler. The ongoing work is in the OMA MEM Technical
Specification [MEM-ts]. LEMONADE is a basis for the mechanism. Specification [MEM-ts]. LEMONADE is a basis for the mechanism.
However, some additional details that are outside the scope of IETF However, some additional details that are outside the scope of the
will also be included. IETF will also 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 out-of-band notification mechanisms, OMA provides enablers to support out-of-band notification mechanisms,
as well as filter specifications (such as XDM), remote device filter specifications (such as XDM), and remote deactivate devices,
deactivation, and other, non-Internet activities. and to perform other non-Internet activities.
3. IETF LEMONADE Architecture 3. IETF LEMONADE Architecture
This section introduces the LEMONADE Architecture. This section introduces the LEMONADE Architecture.
The IETF LEMONADE activity has derived a LEMONADE profile The IETF LEMONADE activity has derived a LEMONADE profile
[PROFILE-bis] with the logical architecture represented in Figure 2, [PROFILE-bis] with the logical architecture represented in Figure 2,
where arrows indicate content flows. where arrows indicate content flows.
______________ ______________
skipping to change at page 7, line 29 skipping to change at page 7, line 4
\ |URLAUTH \ |URLAUTH
\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 [PROFILE] assumes: The LEMONADE profile [PROFILE] assumes:
o IMAP protocol [RFC3501] including LEMONADE profile extensions
[PROFILE] o IMAP protocol [RFC3501], including LEMONADE profile extensions
o SUBMIT protocol [RFC4409], including LEMONADE profile extensions [PROFILE].
o LEMONADE profile compliant IMAP store connected to MTA (Mail
Transfer Agent) via ESMTP [EMAIL] o SUBMIT protocol [RFC4409], including LEMONADE profile extensions.
o LEMONADE profile compliant Submit server connected to an MTA,
often via ESMTP o LEMONADE profile compliant IMAP store connected to an MTA (Mail
o Out-of-band server to client notifications relying on external Transfer Agent) via the ESMTP [EMAIL].
o LEMONADE profile compliant submit server connected to an MTA,
often via the ESMTP.
o Out-of-band 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 the scope of the LEMONADE profile.
o A LEMONADE aware MUA (Mail User Agent). While use of out-of-band
o LEMONADE-aware MUA (Mail User Agent). While use of out-of-band
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 the scope
the LEMONADE specifications. of the LEMONADE specifications.
Further details on the IETF email protocol stack and architecture can Further details on the IETF email protocol stack and architecture can
be found in [MAIL] be found in [MAIL].
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 8, line 40 skipping to change at page 8, line 35
---->| Submit |----------->| MTA | ---->| Submit |----------->| MTA |
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
logical architecture onto the OMA MEM 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 servers. Mapping to the 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, we logically combine the MEM server and email server. profile, we logically combine the MEM server and email server.
However, in lemonade we split them logically into a distinct LEMONADE However, in LEMONADE we split them logically into a distinct LEMONADE
message store and a LEMONADE submit server. ME-2 consists of two message store and a LEMONADE SUBMIT server. ME-2 consists of two
interfaces. ME-2a is IMAP extended according to the LEMONADE interfaces. ME-2a is IMAP extended according to the LEMONADE
profile. ME-2b is 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.
The external notifications mechanism is part of OMA enablers The external notifications mechanism is part of the OMA enablers
specified by the OMA. 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 back- servers. It explicitly identifies the need to support other
ends. This is, of course, outside the scope of the IETF Lemonade backends. This is, of course, outside the scope of the IETF LEMONADE
activity. 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 LEMONADE Figure 4 illustrates the case of IMAP servers that are not LEMONADE-
compliant. In such case, the I2 interface between the MEM server compliant. In such case, the I2 interface between the MEM server
components and the IMAP store and submit server are IMAP and SUBMIT components and the IMAP store and SUBMIT server are IMAP and SUBMIT
without Lemonade extensions. without LEMONADE extensions.
It is important to note the realizations are of a schematic nature It is important to note the realizations are of a schematic nature
and do not dictate actual implementation. For example, one could and do not dictate actual implementation. For example, one could
envision collocating the LEMONADE MEM Enabler Server and the Submit envision collocating the LEMONADE MEM enabler server and the submit
Server shown in Figure 4 in a single instantiation of the server shown in Figure 4 in a single instantiation of the
implementation. Likewise, we consciously label the LEMONADE MEM implementation. Likewise, we consciously label the LEMONADE MEM
Enabler as neither an IMAP Proxy nor an IMAP back-to-back user agent. enabler as neither an IMAP proxy nor an IMAP back-to-back user agent.
LEMAONDE leaves the actual implementation to the developer. LEMONADE leaves the actual implementation to the developer.
______________ ______________
| | | |
_________| Notification | _________| Notification |
| | Mechanism | | | Mechanism |
| |______________| | |______________|
|Notif. ^ |Notif. ^
|Protocol | |Protocol |
| ___|______ _____________ | ___|______ _____________
| | LEMONADE | | | _____ | | LEMONADE | | | _____
skipping to change at page 10, line 29 skipping to change at page 10, line 29
\ |URLAUTH \ |URLAUTH
\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
LEMONADE realization of an OMA MEM enabler with a 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 Post
servers or other proprietary message stores. Office Protocol (POP3) servers or other proprietary message stores.
______________ ______________
| | | |
_________| Notification | _________| Notification |
| | Mechanism | | | Mechanism |
| |______________| | |______________|
|Notif. ^ |Notif. ^
|Protocol | |Protocol |
| ___|______ _____________ | ___|______ _____________
| | LEMONADE | | | _____ | | LEMONADE | | | _____
skipping to change at page 11, line 29 skipping to change at page 11, line 29
\ |URLAUTH \ |URLAUTH
\SUBMIT | \SUBMIT |
\ ____v_____ _____________ \ ____v_____ _____________
\ | | | | _____ \ | | | | _____
\ | 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 back-ends. I2 designates proprietary adapters to the backends.
4. Filters and server to client notifications and LEMONADE 4. Filters and Server-to-Client Notifications and LEMONADE
OMA MEM RD [MEM-req] and AD [MEM-arch] emphasize the need to provide OMA MEM Requirements [MEM-req] and Architecture [MEM-arch] emphasize
mechanisms for server to client notifications of email events and the need to provide mechanisms for server-to-client notifications of
filtering. Figure 6 illustrates how notification and filtering works email events and filtering. Figure 6 illustrates how notification
in the LEMONADE profile [PROFILE]. and filtering works in the LEMONADE profile [PROFILE].
______________ ______________
| | | |
_________| Notification | _________| Notification |
| | Mechanism | | | Mechanism |
| |______________| | |______________|
|Notif. ^ |Notif. ^
|Protocol -------\ _|__ |Protocol -------\ _|__
| ______| ___\>|NF|____ | ______| ___\>|NF|____
| | | ---- | _____ | | | ---- | _____
skipping to change at page 12, line 28 skipping to change at page 12, line 28
\_\_______________|_______| \_\_______________|_______|
\ |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, we define four categories of filters: In Figure 6, we define four categories of filters:
o AF: Administrative Filters - The e-mail service provider usually
o AF: Administrative Filters - The email service provider usually
sets administrative filters. The user typically does not sets administrative filters. The user typically does not
configure AF. AF applies policies covering content filtering, configure AF. AF applies policies covering 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 [SIEVE]. They can emails. They can be defined as SIEVE filters [SIEVE]. They can
include vacation notices [RFC5230]. As SIEVE filters, one can include vacation notices [RFC5230]. As SIEVE filters, one can
administer them using the SIEVE management protocol [MANAGESIEVE]. administer them using the SIEVE management protocol [MANAGESIEVE].
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 [NOTIFICATIONS]. facilities described in [NOTIFICATIONS].
o NF: Notification Filters - Filters that define for what email o NF: Notification Filters - Filters that define for what email
server event an out-of-band notification is sent to the client, as server event an out-of-band notification is sent to the client, as
described in [NOTIFICATIONS]. described in [NOTIFICATIONS].
Refer to the aforementioned references for implementation and Refer to the aforementioned references for implementation and
management of the respective filters. management of the respective filters.
5. Security Considerations 5. Security Considerations
We note there are security risks associated with: We note there are security risks associated with:
skipping to change at page 13, line 8 skipping to change at page 13, line 8
o NF: Notification Filters - Filters that define for what email o NF: Notification Filters - Filters that define for what email
server event an out-of-band notification is sent to the client, as server event an out-of-band notification is sent to the client, as
described in [NOTIFICATIONS]. described in [NOTIFICATIONS].
Refer to the aforementioned references for implementation and Refer to the aforementioned references for implementation and
management of the respective filters. management of the respective filters.
5. Security Considerations 5. Security Considerations
We note there are security risks associated with: We note there are security risks associated with:
o Out-of-band notifications 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 address the need to traverse firewalls
We refer the reader to the relevant Internet Mail, IMAP, SUBMIT, and We refer the reader to the relevant Internet Mail, IMAP, SUBMIT, and
Lemonade documents for how we address these issues. Lemonade documents for how we address these issues.
6. IANA considerations 6. Acknowledgements
None.
7. Acknowledgements
The authors acknowledge and appreciate the work and comments of the The authors acknowledge and appreciate the work and comments of the
IETF LEMONADE working group and the OMA MEM working group. We IETF LEMONADE working group and the OMA MEM working group. We
extracted the contents of this document from sections of extracted the contents of this document from sections of
draft-ietf-lemonade-profile-bis-05.txt by Stephane Maes, Alexey [PROFILE-bis] by Stephane Maes, Alexey Melnikov, and Dave Cridland,
Melnikov and Dave Cridland, as well as sections of as well as sections of [NOTIFICATIONS] by Stephane Maes and Ray
draft-ietf-lemonade-notifications-04.txt by Stephane Maes and Ray
Cromwell. Cromwell.
8. Informative References 7. Informative References
[MEM-arch] [EMAIL] Klensin, J., "Simple Mail Transfer Protocol",
Open Mobile Alliance, "Mobile Email Architecture RFC 5321, October 2008.
Document", June 2007, <http://
member.openmobilealliance.org/ftp/public_documents/mwg/ [MAIL] Crocker, D., "Internet Mail Architecture", Work
MEM/Permanent_documents/ in Progress, October 2008.
OMA-AD-Mobile_Email-V1_0_0-20070614-D.zip>.
[MANAGESIEVE] Melnikov, A. and T. Martin, "A Protocol for Remotely
Managing Sieve Scripts", Work in Progress,
January 2009.
[MEM-arch] Open Mobile Alliance, "Mobile Email Architecture
Document", OMA,
http://member.openmobilealliance.org/ftp/
public_documents/mwg/MEM/Permanent_documents/
OMA-AD-Mobile_Email-V1_0_0-20070614-D.zip,
June 2007.
[MEM-req] Open Mobile Alliance, "Mobile Email Requirements [MEM-req] Open Mobile Alliance, "Mobile Email Requirements
Document", OMA http://www.openmobilealliance.org/, Document", OMA, http://www.openmobilealliance.org/,
Oct 2005. Oct 2005.
[MEM-ts] Open Mobile Alliance, "Mobile Email Technical [MEM-ts] Open Mobile Alliance, "Mobile Email Technical
Specification", OMA (Work in Progress), Specification", OMA, Work in Progress,
http://www.openmobilealliance.org/, Oct 2007. http://www.openmobilealliance.org/, Oct 2007.
[NOTIFICATIONS] Gellens, R. and S. Maes, "Lemonade Notifications
Architecture", Work in Progress, July 2008.
[PROFILE] Maes, S. and A. Melnikov, "Internet Email to Support [PROFILE] Maes, S. and A. Melnikov, "Internet Email to Support
Diverse Service Environments (Lemonade) Profile", Diverse Service Environments (Lemonade) Profile",
RFC 4550, June 2006. RFC 4550, June 2006.
[PROFILE-bis] [PROFILE-bis] Cridland, D., Melnikov, A., and S. Maes, "The
Cridland, D., Melnikov, A., and S. Maes, "The Lemonade Lemonade Profile", Work in Progress, September 2008.
Profile", draft-ietf-lemonade-profile-bis-11 (work in
progress), September 2008.
[RFC3501] Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION
4rev1", RFC 3501, March 2003.
[EMAIL] Klensin, J., "Simple Mail Transfer Protocol", RFC 5321, [RFC3501] Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL -
October 2008. VERSION 4rev1", RFC 3501, March 2003.
[RFC4409] Gellens, R. and J. Klensin, "Message Submission for Mail", [RFC4409] Gellens, R. and J. Klensin, "Message Submission for
RFC 4409, April 2006. Mail", RFC 4409, April 2006.
[RFC5230] Showalter, T. and N. Freed, "Sieve Email Filtering: [RFC5230] Showalter, T. and N. Freed, "Sieve Email Filtering:
Vacation Extension", RFC 5230, January 2008. Vacation Extension", RFC 5230, January 2008.
[SIEVE] Guenther, P. and T. Showalter, "Seive: An Email Filtering [SIEVE] Guenther, P. and T. Showalter, "Seive: An Email
Language", RFC 5528, January 2008, Filtering Language", RFC 5228, January 2008.
<ftp://ftp.isi.edu/in-notes/rfc5528.txt>.
[NOTIFICATIONS]
Gellens, R. and S. Maes, "Lemonade Notifications
Architecture", draft-ietf-lemonade-notifications-10 (work
in progress), July 2008.
[MAIL] Crocker, D., "Internet Mail Architecture",
draft-crocker-email-arch-11 (work in progress),
October 2008.
[MANAGESIEVE]
Melnikov, A. and T. Martin, "A Protocol for Remotely
Managing Sieve Scripts", draft-ietf-sieve-managesieve-01
(work in progress), November 2008.
Authors' Addresses Authors' Addresses
Eric W. Burger Eric W. Burger
This Space for Sale Consultant
New Hampshire New Hampshire
USA USA
Phone: Phone:
Fax: +1 530-267-7447 Fax: +1 530-267-7447
Email: eburger@standardstrack.com EMail: eburger@standardstrack.com
URI: http://www.standardstrack.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
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
 End of changes. 84 change blocks. 
219 lines changed or deleted 241 lines changed or added

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