Enhancements to Internet email to support diverse service environments (lemonade)
---------------------------------------------------------------------------------

Charter
Last Modified: 2006-03-20

Current Status: Active Working Group

Chair(s):
    Glenn Parsons  <[email protected]>
    Eric Burger  <[email protected]>

Applications Area Director(s):
    Ted Hardie  <[email protected]>
    Lisa Dusseault  <[email protected]>

Applications Area Advisor:
    Ted Hardie  <[email protected]>

Mailing Lists:
    General Discussion:[email protected]
    To Subscribe:      [email protected]
        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 <http://www.3gpp.org/TB/T/T2/T2.htm>
- W3C Mulitmodal interaction Activity <http://www.w3.org/2002/mmi/>
- Open Mobile Alliance <http://www.openmobilealliance.org/>
- 3GPP2 TSG-X <http://3gpp2.org/Public_html/X/index.cfm>

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

  Jun 2005       Submit IMAP4 extensions for streaming multimedia to the IESG

  Aug 2005       Submit server to server notification protocol to the IESG


Internet-Drafts:

Posted Revised         I-D Title   <Filename>
------ ------- --------------------------------------------
Jul 2004 Jun 2006   <draft-ietf-lemonade-reconnect-07.txt>
               IMAP4 Extensions for Quick Reconnect

Jul 2004 Mar 2006   <draft-ietf-lemonade-futuredelivery-04.txt>
               SMTP Submission Service Extension for Future Message Release

Oct 2005 May 2006   <draft-ietf-lemonade-rfc2192bis-02.txt>
               IMAP URL Scheme

Oct 2005 Jun 2006   <draft-ietf-lemonade-convert-04.txt>
               CONVERT

Dec 2005 Mar 2006   <draft-ietf-lemonade-imap-sieve-01.txt>
               Support for Sieve in Internet Message Access Protocol (IMAP4)

Jan 2006 Jun 2006   <draft-ietf-lemonade-notifications-03.txt>
               Lemonade notifications and filters

Jan 2006 Jun 2006   <draft-ietf-lemonade-profile-bis-03.txt>
               LEMONADE profile bis

Mar 2006 Mar 2006   <draft-ietf-lemonade-firewall-binding-00.txt>
               Lemonade bindings to cross firewalls and mobile network
               intermediaries

Mar 2006 Jun 2006   <draft-ietf-lemonade-deployments-03.txt>
               Deployment Considerations for lemonade-compliant Mobile Email

Mar 2006 May 2006   <draft-ietf-lemonade-vfolder-01.txt>
               Persistent Virtual Folder extension to the IMAP Protocol

Mar 2006 Jun 2006   <draft-ietf-lemonade-search-within-02.txt>
               WITHIN Search extension to the IMAP Protocol

Mar 2006 Aug 2006   <draft-ietf-lemonade-compress-03.txt>
               The IMAP COMPRESS Extension

Jun 2006 Jun 2006   <draft-ietf-lemonade-msgevent-00.txt>
               Internet Message Store Events

Jun 2006 Jun 2006   <draft-ietf-lemonade-streaming-00.txt>
               Streaming Multimedia Messaging Attachments

Jun 2006 Jul 2006   <draft-ietf-lemonade-reconnect-client-01.txt>
               IMAP4 Extensions for Quick Mailbox Resynchronization

Jun 2006 Jun 2006   <draft-ietf-lemonade-notification-protocol-00.txt>
               Lemonade Notification protocol

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

You are viewing proxied material from ftp.icm.edu.pl. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.