draft-ietf-lemonade-architecture-03.txt   draft-ietf-lemonade-architecture-04.txt 
LEMONADE Working Group E. Burger LEMONADE Working Group E. Burger
Internet-Draft Internet-Draft This Space for Sale
Intended status: Informational G. Parsons Intended status: Informational G. Parsons
Expires: January 10, 2009 Nortel Networks Expires: May 7, 2009 Nortel Networks
July 9, 2008 November 3, 2008
LEMONADE Architecture - Supporting OMA Mobile Email (MEM) using Internet LEMONADE Architecture - Supporting Open Mobile Alliance (OMA) Mobile
Mail Email (MEM) using Internet Mail
draft-ietf-lemonade-architecture-03.txt draft-ietf-lemonade-architecture-04
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 January 10, 2009. This Internet-Draft will expire on May 7, 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 Open Mobile Alliance (OMA), using Internet Mail
architecture is the basis of the work of the LEMONADE WG and is a protocols. This architecture was an important consideration for much
guideline for the LEMONADE Profile. of the work of the LEMONADE (Enhancements to Internet email to
Support Diverse Service Environments) work group in the IETF. This
document also describes how the LEMONADE architecture meets the OMA's
requirements for their Mobile Email (MEM) service.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. OMA Mobile Email (MEM) . . . . . . . . . . . . . . . . . . . . 3 2. OMA Mobile Email (MEM) . . . . . . . . . . . . . . . . . . . . 3
2.1. OMA MEM Requirements . . . . . . . . . . . . . . . . . . . 3 2.1. OMA MEM Requirements . . . . . . . . . . . . . . . . . . . 3
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 . . . . . . . . . . . . . . 5
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 . . . . . . . . . . . . . . . . . . . . . . 8
3.2. LEMONADE realization of OMA MEM with non-LEMONADE 3.2. LEMONADE realization of OMA MEM with non-LEMONADE
compliant servers . . . . . . . . . . . . . . . . . . . . 9 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 . . . . . . . . . . . . . . . . . . . . . 9 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 . . . 10 4. Filters and server to client notifications and LEMONADE . . . 11
5. Security Considerations . . . . . . . . . . . . . . . . . . . 11 5. Security Considerations . . . . . . . . . . . . . . . . . . . 13
6. IANA considerations . . . . . . . . . . . . . . . . . . . . . 12 6. IANA considerations . . . . . . . . . . . . . . . . . . . . . 13
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13
8. Informative References . . . . . . . . . . . . . . . . . . . . 12 8. Informative References . . . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14
Intellectual Property and Copyright Statements . . . . . . . . . . 15 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 work
group has enhanced many of these protocols for use in the mobile group has enhanced many of these protocols for use in the mobile
environment and are summarized in the LEMONADE profile [PROFILE] and environment. The LEMONADE profile [PROFILE] and its revision
its revision LEMONADE profile bis [PROFILE-bis]. This document shows LEMONADE profile bis [PROFILE-bis] summarize such protocols and
how the OMA MEM Requirement document [MEM-req], OMA MEM Architecture protocol use. This document shows how the OMA MEM Requirement
[MEM-arch], and OMA MEM Technical Specification [MEM-ts] relate to document [MEM-req], OMA MEM Architecture [MEM-arch], and OMA MEM
the work of LEMONADE. Technical Specification [MEM-ts] relate to the work of LEMONADE in
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 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
skipping to change at page 6, line 12 skipping to change at page 6, line 12
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 The e-mail service provider can be a third-party service provider, a
provider, a network service provider, or an enterprise e-mail network service provider, or an enterprise e-mail service.
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 [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 IETF
will also be included. will also be included.
OMA provides ways to perform provisioning via OMA client provisioning OMA provides ways to perform provisioning via OMA client provisioning
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 [RFC2821] Transfer Agent) via ESMTP [EMAIL]
o LEMONADE profile compliant Submit server connected to an MTA, o LEMONADE profile compliant Submit server connected to an MTA,
often via ESMTP often via ESMTP
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.
skipping to change at page 9, line 26 skipping to change at page 9, line 26
servers. It explicitly identifies the need to support other back- servers. It explicitly identifies the need to support other back-
ends. This is, of course, outside the scope of the IETF Lemonade ends. 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
and do not dictate actual implementation. For example, one could
envision collocating the LEMONADE MEM Enabler Server and the Submit
Server shown in Figure 4 in a single instantiation of the
implementation. Likewise, we consciously label the LEMONADE MEM
Enabler as neither an IMAP Proxy nor an IMAP back-to-back user agent.
LEMAONDE leaves the actual implementation to the developer.
______________ ______________
| | | |
_________| 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 11, line 37 skipping to change at page 12, 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 [RFC5230]. include vacation notices [RFC5230]. As SIEVE filters, one can
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].
The MUA can manage the NF and DF filters using the SIEVE management Refer to the aforementioned references for implementation and
protocol [MANAGESIEVE]. 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.
skipping to change at page 13, line 7 skipping to change at page 14, line 9
[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-09 (work in Profile", draft-ietf-lemonade-profile-bis-11 (work in
progress), June 2008. progress), September 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.
[RFC2821] Klensin, J., "Simple Mail Transfer Protocol", RFC 2821, [EMAIL] Klensin, J., "Simple Mail Transfer Protocol", RFC 5321,
April 2001. October 2008.
[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: [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 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-10 (work Architecture", draft-ietf-lemonade-notifications-10 (work
in progress), July 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-11 (work in progress),
February 2008. October 2008.
[MANAGESIEVE] [MANAGESIEVE]
Melnikov, A. and T. Martin, "A Protocol for Remotely Melnikov, A. and T. Martin, "A Protocol for Remotely
Managing Sieve Scripts", draft-martin-managesieve-10 (work Managing Sieve Scripts", draft-ietf-sieve-managesieve-01
in progress), June 2008. (work in progress), November 2008.
Authors' Addresses Authors' Addresses
Eric W. Burger Eric W. Burger
This Space for Sale
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 Full Copyright Statement
 End of changes. 19 change blocks. 
38 lines changed or deleted 52 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/