Enhancements to Internet email to Support Diverse Service Environments (lemonade)

In addition to this official charter maintained by the IETF Secretariat, there is additional information about this working group on the Web at:

       Additional LEMONADE Web Page

Last Modified: 2008-05-01

Additional information is available at tools.ietf.org/wg/lemonade

Chair(s):

  • Eric Burger <eburger@bea.com>

  • Glenn Parsons <gparsons@nortel.com>

    Applications Area Director(s):

  • Chris Newman <chris.newman@sun.com>
  • Lisa Dusseault <lisa@osafoundation.org>

    Applications Area Advisor:

  • Chris Newman <chris.newman@sun.com>

    Secretary(ies):

  • Alexey Melnikov <alexey.melnikov@isode.com>

    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 <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
    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
    Apr 2007  Submit Notification Protocol Suite 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
    May 2008  Submit URLFETCH BINARY Extension to the IESG
    May 2008  Submit Notification Format to the IESG
    May 2008  Submit IMAP NOTIFY Extension to the IESG
    Jun 2008  Submit Notification Architecture to the IESG
    Jun 2008  Submit IMAP4 extensions for streaming multimedia to the IESG
    Jun 2008  Submit Profile bis document to the IESG

    Internet-Drafts:

    IMAP CONVERT extension (62251 bytes)
    Support for Sieve in Internet Message Access Protocol (IMAP4) (38944 bytes)
    Lemonade Notifications Architecture (35667 bytes)
    The Lemonade Profile (76434 bytes)
    Deployment Considerations for lemonade-compliant Mobile Email (33872 bytes)
    Internet Message Store Events (38729 bytes)
    Streaming Internet Messaging Attachments (52845 bytes)
    The IMAP NOTIFY Extension (44356 bytes)
    LEMONADE Architecture - Supporting OMA Mobile Email (MEM) using Internet Mail (28898 bytes)

    Request For Comments:

    Mapping Between the Multimedia Messaging Service (MMS) and Internet Mail (RFC 4356) (69427 bytes)
    Goals for Internet Messaging to Support Diverse Service Environments (RFC 4416) (93676 bytes)
    Internet Message Access Protocol (IMAP) CATENATE Extension (RFC 4469) (21822 bytes) updates RFC 3501,RFC 3502
    Internet Message Access Protocol (IMAP) - URLAUTH Extension (RFC 4467) (36714 bytes) updated by RFC 5092
    Message Submission BURL Extension (RFC 4468) (28614 bytes) updates RFC 3463
    Internet Email to Support Diverse Service Environments (Lemonade) Profile (RFC 4550) (48790 bytes)
    The IMAP COMPRESS Extension (RFC 4978) (17554 bytes)
    WITHIN Search extension to the IMAP Protocol (RFC 5032) (8921 bytes) updates RFC 3501
    IMAP URL Scheme (RFC 5092) (65197 bytes) obsoletes RFC 2192/ updates RFC 4467
    IMAP4 Extensions for Quick Mailbox Resynchronization (RFC 5162) (51620 bytes)
    IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.

    Return to working group directory.

    Return to IETF home page.