Re: lemonade charter

[ned.freed@mrochek.com]

> (going by what is on the web agenda)

This isn't supposed to be on the agenda yet. Nor is the agenda on the Web
page anywhere near current.

> The milestones are not very clear about what is being
> delivered. Targets that might be appropriate to mention are 00 ID and
> submission to IESG for advancement.

-00 versions of most of these documents already exist as individual submissions
so most of these are "submit to IESG" actions. I'll clarify the milestones
accordingly.

> It might also be good to have the requirements brought to the IESG
> before the other protocol documents are too far advanced.

That's already implied by the milestones.

> I tend to
> get a little bit nervous when folks go off and enhance protocols for
> "limited capabilities devices". While this can sometimes be OK, some
> groups take this to extremes. Dealing with extremes after they are
> well advanced is something to avoid.

Part of the problem is that you're not looking at the current charter.

The only extensions being proposed here are ones that try to eliminate the need
for bulky message data to travel down the IMAP4 pipe in encoded form to a
limited bandwidth device. The idea is to add something to IMAP4 that lets you
direct such content over to an existing protocol capable of handling a media
stream. Additionally, the group wants to consider the long standing problem of
forwarding a message that's in an IMAP4 server out over SMTP.

Both of these items are called out explicitly in the current charter, with
appropriate restrictions (thou shalt not invent a new streaming protocoll,
etc.)

As far as profiling goes, it really is a pure profiling exercise. The intent is
to establish a baseline set of server extensions that these clients need.
And once again, the charter is appropriately restrictive about this.

I'll attach a current copy of the charter below in case you want to review it
now. This is currently under review on the WG mailing list.

				Ned

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

Proposed Charter
================

Lemonade is tasked to provide a set of enhancements and profiles of Internet
email submission, transport, and retrieval protocols to facilitate operation in
environments which use Internet-based technologies but which have link
characteristics, device characteristics, or service environments that are
significantly different from those common on the Internet.  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, IMAPEXT and other 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 will be produced on LEMONADE architecure and
         requirements.

     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.  Profile 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.  Create a message notification protocol for the specific purpose of
         servers reporting message status information to other servers.

     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 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.


Milestones  (document completion)
==========

Apr 2003 - Submit LEMONADE requirements and architecture specification
           to the IESG

May 2003 - Submit server to server notification protocol to the IESG

Jul 2003 - Submit IMAP4 and message submission extensions for streaming
           multimedia to the IESG

Sep 2003 - Submit IMAP4 profile for mobile devices to the IESG

Drafts to be used as input for working group
deliverables (grouped per milestone)
====================================

   LEMONADE requirements

     - draft-vaudreuil-um-issues-00.txt
     - draft-burger-um-reqts-00.txt
     - draft-wong-umcli-00.txt

   Server to server notification protocol

     - draft-shapira-snap-04.txt

   IMAP4 extensions for VM playback

     - draft-burger-imap-chanuse-00.txt
     - draft-nerenberg-imap-channel-01.txt

   IMAP4 extensions for mobile devices

     - draft-neystadt-imap-status-counters-00.txt
     - draft-shveidel-mediasize-00.txt

   Translation to and from other messaging systems

     - draft-vaudreuil-futuredelivery-00.txt