[lemonade] Correction 1 of minutes of lemonade interim 16 May 2007
Peter Coates <peter.coates@sun.com> Tue, 22 May 2007 15:49 UTC
Return-path: <lemonade-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HqWbx-0004Le-FG; Tue, 22 May 2007 11:49:21 -0400
Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1HqWbw-0004KB-EY for lemonade-confirm+ok@megatron.ietf.org; Tue, 22 May 2007 11:49:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HqWbw-0004Je-3X for lemonade@ietf.org; Tue, 22 May 2007 11:49:20 -0400
Received: from brmea-mail-1.sun.com ([192.18.98.31]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqWbt-0002Vb-Go for lemonade@ietf.org; Tue, 22 May 2007 11:49:20 -0400
Received: from fe-amer-10.sun.com ([192.18.108.184]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l4MFnG7Z029530 for <lemonade@ietf.org>; Tue, 22 May 2007 15:49:17 GMT
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0JIG00G0192YZC00@mail-amer.sun.com> (original mail from peter.coates@sun.com) for lemonade@ietf.org; Tue, 22 May 2007 09:49:16 -0600 (MDT)
Received: from kluane ([199.247.238.5]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JIG00KWM9A2SFHZ@mail-amer.sun.com> for lemonade@ietf.org; Tue, 22 May 2007 09:49:16 -0600 (MDT)
Date: Tue, 22 May 2007 08:49:04 -0700
From: Peter Coates <peter.coates@sun.com>
To: lemonade@ietf.org
Message-id: <014501c79c88$ba58b710$2f0a2530$%coates@sun.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-language: en-ca
Thread-index: Acech10V0pWqteSvTtygZFQojL5k3QAASghQ
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e3901bdd61b234d82da85cc76f05a7e8
Subject: [lemonade] Correction 1 of minutes of lemonade interim 16 May 2007
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Enhancements to Internet email to support diverse service enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/lemonade>, <mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/lemonade>, <mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1185486677=="
Errors-To: lemonade-bounces@ietf.org
(sorry about the delay in getting these minutes out. I hope they are an accurate reflection of decisions taken. If not, let me know and I'll correct. Similarly if I missed out a participant. Peter.) In the Room: Eric burger, Bea Peter Coates, Sun Darryl Champagne, Funambol Glenn Parsons, Nortel Brook Hayes, RIM Randy Gellens Pete Resnick Virtually present: Alexey Melnikov Chris Newman Arnt Abhijit Menon-Sen Pvanhoof Cyrus Daboo Dave Cridland Convert: There was more or less a decision to remove strict. IANA registry for transcoding parameters Remove dependency on metadata What about convert to multipart. then how do you get a part of the new multipart? Matter left open. AI Pete: send a message to the list with suggested syntax Open question if IMAP URL can refer to a converted bodypart. Or refer to parts of converted bodypart. Consensus is that once URLs can refer to a converted bodypart, the output can be used in catenate, and the problem goes away What about storage of convert capabilities: metadata, extended capability, or. The consensus is that this is an open issue. For an open issue with no strongly held opinions it was an active debate. Leave the spec asking for metadata for the moment. Strict: There was a long and rather uninformed discussion about this which remarkably converged on an action item on Pete. AI Pete: provide some text to Alexey on conversion. Basically to add a USEDEVICEINFO to give the server permission to be "helpful". Strict gets consigned to the dustbin of history. IANA registration: Open issue use conneg syntax rather than IMAP syntax (rfc 2913) AI Glen: to work out how to map STI parameters on conneg Notifications: AI Peter: Peter accidentally volunteered to update the message events doc AI Glenn & Randy to rework on the notification doc into the arch doc that is needed, will talk to Lisa Dusseault on this. Status: Draft-ietf-lemonade-deployments: Chairs to deal with "discuss" comments. Draft-ietf-lemonade-reconnect-client: new revision coming to address AD comments Draft-ietf-lemonade-search-within: comments Draft-ietf-lemonade-reconnect replaced by Draft-ietf-lemonade-reconnect-client Draft-ietf-lemonade-firewall-binding and Draft-ietf-lemonade-tcp-challenged-environments more than expired: now deemed dead. New doc called for: using convert for encryption, but not add it to -bis. A decision on the urgency of this is to be made by chairs. Draft-ietf-lemonade-convert: new draft and onto WG last call Draft-ietf-lemonade-sieve: news more work. chairs will encourage progress and perhaps adds a co-editor Draft-ietf-lemonade-msgevent: new draft to be produced Draft-ietf-lemonade-notifications: new draft for internal consumption Draft-ietf-lemonade-rfc2192bis: Alexey to produce new draft "quick fix" Draft-ietf-lemonade-streaming: chairs to followup with editors (Eric to fins SIP reviewer) Draft-ietf-lemonade-context: Dave will put sort back, other comments to be included. Then will go to IESG Draft-gulbradsen-imap-notify: will be change to Draft-ietf-lemonade-notify with revisions, then one more revision before WG last call Draft-ietf-lemonade-profile-bis: add sort and enable to -bis plus some minor cleanup
_______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade
- [lemonade] Correction 1 of minutes of lemonade in… Peter Coates