Enhancements to Internet email to Support Diverse Service Environments (lemonade) --------------------------------------------------------------------------------- Charter Last Modified: 2008-08-21 Current Status: Active Working Group Chair(s): Glenn Parsons Eric Burger Applications Area Director(s): Chris Newman Lisa Dusseault Alexey Melnikov Applications Area Advisor: Chris Newman Secretary(ies): Alexey Melnikov Mailing Lists: General Discussion:lemonade@ietf.org To Subscribe: lemonade-request@ietf.org In Body: in boby 'subscribe' Archive: http://www.ietf.org/mail-archive/web/lemonade/index.html Description of Working Group: Lemonade is tasked to provide a set of enhancements and profiles of Internet email submission, transport, and retrieval protocols to facilitate operation on platforms with constrained resources, or communications links with high latency or limited bandwidth. A primary goal of this work is to ensure that those profiles and enhancements continue to interoperate with the existing Internet email protocols in use on the Internet, so that these environments and more traditional Internet users have access to a seamless service. Lemonade's work is at the crossroads of a body of work related to Internet messaging, in particular work done by the VPIM, FAX, and IMAPEXT IETF working groups. Given the potentially broad scope of activities this group could engage in, the group will focus specifically on the following work items: 0. An informational RFC or RFCs will be produced on LEMONADE architecture and the issues it seeks to address. 1. Enhance the existing IMAP4 message retrieval and message submission (RFC 2476) protocols to satisfy the requirements for handling streaming multimedia content. The existing standards-track CONNEG framework will be used if content negotiation capabilities are needed. The group will employ existing protocols (such as for streaming) with IMAP4 instead of duplicating such functionality within IMAP4. 2. Enhance the existing IMAP4 message retrieval and/or message submission (RFC 2476) protocols to satisfy the requirements for forwarding a message and/or its attachments without downloading the message to the client and subsequently uploading the message to a server. 3. Refine the existing IMAP4 message retrieval protocol to facilitate its use with devices that have limited capabilities such as mobile endpoints. At most one backwards compatible profile of IMAP4 will be produced by this effort. 4. Define a format for message notifications for servers reporting message status information to other servers. Specify the method for delivery of those notifications. 5. Create a specification describing the use of Internet message services in environments where message delivery may take place using either Internet protocols or through an MMS server using WAP to communicate with the receiving user agent. Any protocols defined by this working group will include appopriate security mechanisms, including authentication, privacy, and access control. Mandatory-to-implement security mechanisms will be specified as needed in order to guarantee secure protocol interoperability. The transport area will be consulted to deal with any transport-related issues that arise, especially in regards to items 1-4 above. The IAB is currently working on the specification of general guidelines and requirements for notification services. Once complete this work will be used as input to item 4 above. The working group is aware of several related activities in other groups: - 3GPP TSG T WG2 SWG3 Messaging - W3C Mulitmodal interaction Activity - Open Mobile Alliance - 3GPP2 TSG-X The goal is to coordinate efforts with at least these groups as required. While there is obvious synergy, given the end-of-life of the VPIM and FAX work groups and the similar membership, the working group does not expect to coordinate with these other groups. Goals and Milestones: Done Submit LEMONADE goals and use-cases specification to the IESG Done Submit server to server notification requirements to the IESG Done Submit translation to other messaging systems to the IESG Done Submit IMAP/SUBMIT extensions for forward without download to IESG Done Submit IMAP4 profile for mobile devices to the IESG Done Submit IMAP COMPRESS Extension to the IESG Done Submit Deployment Considerations to the IESG Done Submit IMAP WITHIN Search extension to the IESG Done Submit SASL-IR IMAP4 extension to the IESG Done Submit IMAP CONVERT extension to the IESG Done Submit Quick Reconnect extension to the IESG Done Submit Update to RFC 2192 (IMAP URL) to the IESG Done Submit Message Events to IESG Done Submit contextual mailboxes extension to the IESG Done Submit Body Conversions to IESG Done Submit IMAP Sieve Extensions to IESG Done Submit URLFETCH BINARY Extension to the IESG Done Submit Notification Format to the IESG Done Submit IMAP NOTIFY Extension to the IESG Done Submit Notification Architecture to the IESG Jun 2008 Submit Profile bis document to the IESG Done Submit IMAP4 extensions for streaming multimedia to the IESG Internet-Drafts: Posted Revised I-D Title ------ ------- -------------------------------------------- Jan 2006 Jul 2008 Lemonade Notifications Architecture Jan 2006 Feb 2009 The Lemonade Profile Jun 2006 Nov 2008 Internet Message Store Events Jun 2006 Jan 2009 Streaming Internet Messaging Attachments Nov 2007 Nov 2008 LEMONADE Architecture - Supporting Open Mobile Alliance (OMA) Mobile Email (MEM) using Internet Mail Nov 2007 Sep 2008 Extended URLFETCH for binary and converted parts Oct 2008 Oct 2008 IMAP4 Extensions for Quick Mailbox Resynchronization Request For Comments: RFC Stat Published Title ------- -- ----------- ------------------------------------ RFC4356Standard Jan 2006 Mapping Between the Multimedia Messaging Service (MMS) and Internet Mail RFC4416 I Feb 2006 Goals for Internet Messaging to Support Diverse Service Environments RFC4469 PS Apr 2006 Internet Message Access Protocol (IMAP) CATENATE Extension RFC4467 PS May 2006 Internet Message Access Protocol (IMAP) - URLAUTH Extension RFC4468 PS May 2006 Message Submission BURL Extension RFC4550 PS Jun 2006 Internet Email to Support Diverse Service Environments (Lemonade) Profile RFC4978 PS Aug 2007 The IMAP COMPRESS Extension RFC5032 PS Sep 2007 WITHIN Search extension to the IMAP Protocol RFC5092 PS Nov 2007 IMAP URL Scheme RFC5162 PS Mar 2008 IMAP4 Extensions for Quick Mailbox Resynchronization RFC5259 PS Jul 2008 Internet Message Access Protocol - CONVERT extension RFC5383BCP Oct 2008 Deployment Considerations for Lemonade-Compliant Mobile Email RFC5465 PS Feb 2009 The IMAP NOTIFY Extension RFC5466 PS Feb 2009 IMAP4 Extension for Named Searches (Filters)