draft-ietf-lemonade-architecture-02.txt   draft-ietf-lemonade-architecture-03.txt 
LEMONADE Working Group E. Burger LEMONADE Working Group E. Burger
Internet-Draft Internet-Draft
Intended status: Informational G. Parsons Intended status: Informational G. Parsons
Expires: November 17, 2008 Nortel Networks Expires: January 10, 2009 Nortel Networks
May 16, 2008 July 9, 2008
LEMONADE Architecture - Supporting OMA Mobile Email (MEM) using Internet LEMONADE Architecture - Supporting OMA Mobile Email (MEM) using Internet
Mail Mail
draft-ietf-lemonade-architecture-02.txt draft-ietf-lemonade-architecture-03.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 November 17, 2008. This Internet-Draft will expire on January 10, 2009.
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
guideline for the LEMONADE Profile. guideline for the LEMONADE Profile.
Table of Contents Table of Contents
skipping to change at page 4, line 40 skipping to change at page 4, line 40
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, 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, and its settings and revocation,
* 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. not transported by the MEM protocol but via other channels, and
* 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-2: Corresponding interface of the MEM server
o ME-3: Out-of-band MEM server interfaces, for example to support o ME-3: Out-of-band MEM server interfaces, for example to support
generation of server to client notifications. generation of server to client notifications.
o ME-4: Out-of-band MEM client interfaces (e.g. to receive server to o ME-4: Out-of-band 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 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
skipping to change at page 5, line 40 skipping to change at page 5, line 41
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 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 a 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, 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 there is a MEM proxy, and the MEM server and email server are in
the domain of the email service provider the 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
skipping to change at page 7, line 35 skipping to change at page 7, line 35
| 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 o IMAP protocol [RFC3501] including LEMONADE profile extensions
[PROFILE] [PROFILE]
o SUBMIT protocol [RFC4409], including LEMONADE profile extensions o SUBMIT protocol [RFC4409], 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 [RFC1861] Transfer Agent) via ESMTP [RFC2821]
o LEMONADE profile compliant Submit server connected to MTA via o LEMONADE profile compliant Submit server connected to an MTA,
ESMTP often via ESMTP
o Lemonade profile message store / submit server protocols (URLAUTH,
BURL, CATENATE) (see lemonade Profile [PROFILE]).
o Out-of-band server to client notifications relying on external 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 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 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 scope of
the LEMONADE specifications. 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]
skipping to change at page 11, line 37 skipping to change at page 11, line 37
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 e-mail 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. include vacation notices [RFC5230].
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].
The MUA can manage the NF and DF filters using the SIEVE management The MUA can manage the NF and DF filters using the SIEVE management
protocol. protocol [MANAGESIEVE].
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
skipping to change at page 13, line 7 skipping to change at page 13, line 7
[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.
[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 Lemonade Cridland, D., Melnikov, A., and S. Maes, "The Lemonade
Profile", draft-ietf-lemonade-profile-bis-08 (work in Profile", draft-ietf-lemonade-profile-bis-09 (work in
progress), February 2008. progress), June 2008.
[RFC3501] Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION [RFC3501] Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION
4rev1", RFC 3501, March 2003. 4rev1", RFC 3501, March 2003.
[RFC1861] Gwinn, R., "Simple Network Paging Protocol - Version 3 [RFC2821] Klensin, J., "Simple Mail Transfer Protocol", RFC 2821,
-Two-Way Enhanced", RFC 1861, October 1995. April 2001.
[RFC4409] Gellens, R. and J. Klensin, "Message Submission for Mail", [RFC4409] Gellens, R. and J. Klensin, "Message Submission for Mail",
RFC 4409, April 2006. RFC 4409, April 2006.
[RFC5230] Showalter, T. and N. Freed, "Sieve Email Filtering:
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 Filtering
Language", RFC 5528, January 2008, Language", RFC 5528, January 2008,
<ftp://ftp.isi.edu/in-notes/rfc5528.txt>. <ftp://ftp.isi.edu/in-notes/rfc5528.txt>.
[NOTIFICATIONS] [NOTIFICATIONS]
Gellens, R. and S. Maes, "Lemonade Notifications Gellens, R. and S. Maes, "Lemonade Notifications
Architecture", draft-ietf-lemonade-notifications-08 (work Architecture", draft-ietf-lemonade-notifications-10 (work
in progress), April 2008. in progress), July 2008.
[MAIL] Crocker, D., "Internet Mail Architecture", [MAIL] Crocker, D., "Internet Mail Architecture",
draft-crocker-email-arch-10 (work in progress), draft-crocker-email-arch-10 (work in progress),
February 2008. February 2008.
[MANAGESIEVE]
Melnikov, A. and T. Martin, "A Protocol for Remotely
Managing Sieve Scripts", draft-martin-managesieve-10 (work
in progress), June 2008.
Authors' Addresses Authors' Addresses
Eric W. Burger Eric W. Burger
New Hampshire New Hampshire
USA USA
Phone: Phone:
Fax: 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
 End of changes. 16 change blocks. 
22 lines changed or deleted 28 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/