From lemonade-bounces@ietf.org Sun Jul 01 12:41:05 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I52Tw-0003fM-PF; Sun, 01 Jul 2007 12:41:04 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1I52Tu-0003fH-QM for lemonade-confirm+ok@megatron.ietf.org; Sun, 01 Jul 2007 12:41:02 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I52Tu-0003f9-Go for lemonade@ietf.org; Sun, 01 Jul 2007 12:41:02 -0400 Received: from rufus.isode.com ([62.3.217.251]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I52Tq-0002yq-69 for lemonade@ietf.org; Sun, 01 Jul 2007 12:41:02 -0400 Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id ; Sun, 1 Jul 2007 17:40:49 +0100 Message-ID: <4686E0DD.9000100@isode.com> Date: Sun, 01 Jul 2007 00:01:49 +0100 From: Alexey Melnikov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: en-us, en To: Eric Burger Subject: Re: [lemonade] CONVERT - Clients Do Not Know References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228 Cc: "lemonade@ietf.org" X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org Hi Eric, I will use your message to comment on emerging WG consensus as I see it. Eric Burger wrote: >Said another way, would it be correct to assert conversion was for display >size, audio/video quality, or object format, and NOT for transmission >optimization? > I am mostly agreeing with this assertion, but as previously discussed in this thread: I think the client can also request "return me the image which is less then 100Kb". >I am leaning towards Lyndon's position: since there is no real use case for >SIZE as an estimator, let us let the server only offer it to the client when >it knows the exact value, after conversion. > > I think I hear the consensus for using the exact sizes. Considering that some people still see benefits in downloading a converted bodypart in chunks, the converted size might need to be known before the request for converted bodypart is fetched. So I think what I have in the document already satisfies the requirements. I can add more text stressing out that good servers should cache a converted bodypart to make server performance tolerable for clients. I can also add some text that servers can protect themselves from abuse and can reply with NO response if the client requests too many nearly identical conversions. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Mon Jul 02 15:18:08 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5RPU-0005kB-9N; Mon, 02 Jul 2007 15:18:08 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1I5RPS-0005bI-Dj for lemonade-confirm+ok@megatron.ietf.org; Mon, 02 Jul 2007 15:18:06 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5RPR-0005ZI-VC for lemonade@ietf.org; Mon, 02 Jul 2007 15:18:05 -0400 Received: from repmmg02.bea.com ([66.248.192.39]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5RPJ-0004uC-0a for lemonade@ietf.org; Mon, 02 Jul 2007 15:18:05 -0400 Received: from repmmr01.bea.com (repmmr01.bea.com [10.160.29.71]) by repmmg02.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id l62JHrT8014287; Mon, 2 Jul 2007 12:17:53 -0700 Received: from repbex01.amer.bea.com (repbex01.bea.com [10.160.26.98]) by repmmr01.bea.com (Switch-3.2.7/Switch-3.2.5) with ESMTP id l62JHjB8009138; Mon, 2 Jul 2007 12:17:51 -0700 Received: from 172.24.28.76 ([172.24.28.76]) by repbex01.amer.bea.com ([10.160.26.98]) with Microsoft Exchange Server HTTP-DAV ; Mon, 2 Jul 2007 19:17:51 +0000 User-Agent: Microsoft-Entourage/11.3.3.061214 Date: Mon, 02 Jul 2007 13:24:21 -0400 Subject: Re: [lemonade] Future Release in LEMONADE Profile bis? From: Eric Burger To: "Vaudreuil, Greg M (Greg)" Message-ID: Thread-Topic: [lemonade] Future Release in LEMONADE Profile bis? Thread-Index: AceXdbM+K2vvzBq+QJ6KRE2Xq0stmggvX+cwAGQn/W4AIpCckACf758E In-Reply-To: <89017B166CB7E140BA80577FF744AE19E65FBB@ILEXC2U01.ndc.lucent.com> Mime-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit x-BEA-PMX-Instructions: AV x-BEA-MM: Internal-To-External X-Spam-Score: 0.0 (/) X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b Cc: Enhancements to Internet email to support diverse service enivronments X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org Don't you need to negotiate features anyway? There is no, "Are you a lemonade server / client" query. Either the server advertises Future Delivery or it does not. If you are assuming or know via some non-IMAP method that your client is talking to a "lemaonde server," then you are already in a proprietary environment where you can mandate that magic server also supports Future Delivery. On 6/29/07 9:33 AM, "Vaudreuil, Greg M (Greg)" wrote: > Well.... the point of lemonade was to create a profile with a new > minimum-to-implement set of features that client could assume. The idea > as I understood it was a client could get "skinny" by assuming either > base IMAP or LEMONADE IMAP. By having two distinct levels of > functionality, one could simplify both the user experience and the code > by eliminating or significantly reducing expensive "options". > > The cost of not doing so is that this is one more "option" that may or > may not be present. Most annoyingly, the presence of this option can be > known at composition time only by more icky client configuration or a > client caching the capabilities of the submission server from the last > connect. > > If this is the model, I'd like to include Future Release in that higher > functional tier. > > Greg V. > > -----Original Message----- > From: Eric Burger [mailto:eburger@bea.com] > Sent: Thursday, June 28, 2007 4:35 PM > To: Vaudreuil, Greg M (Greg) > Cc: Enhancements to Internet email to support diverse service > enivronments > Subject: Re: [lemonade] Future Release in LEMONADE Profile bis? > > > I don't see it that way, unless one is creating a "Lemonade client" that > does not follow standard IMAP and assumes features are there, and thus > Future Delivery, if not in the Profile, is clearly a weird thing. > > If one creates clients that happen to implement lemonade, and they want > to > do future delivery, they just do future delivery. > > What could possibly go wrong? > > > On 6/26/07 1:53 PM, "Vaudreuil, Greg M (Greg)" > > wrote: > >> >> I reviewed the minutes and list, but don't see clearly if we agreed > that >> future-release was to be included in the Ph-2 LEMONADE profile. There >> was plenty of debate as to whether the extension should be worked as a >> formal WG item or not, with a flip-flop-flip in the history. That >> document is now done, RFC 4865. >> >> I'd like to suggest that future-release is included in Profile-BIS. > It >> is a simple extension with high utility to a diverse client, > especially >> with intermittent connectivity or subject to unforseen battery >> exhaustion. In general, fewer options are better than more, and this > is >> an extension I expect to be widely implemented regardless of whether > it >> is in LEMONADE or not. Not including simply requires supporting > another >> code-path in the client and another diverse user experience :-( >> >> Greg V. >> >> >> >> _______________________________________________ >> lemonade mailing list >> lemonade@ietf.org >> https://www1.ietf.org/mailman/listinfo/lemonade >> Supplemental Web Site: >> http://www.standardstrack.com/ietf/lemonade > > > Notice: This email message, together with any attachments, may contain > information of BEA Systems, Inc., its subsidiaries and affiliated > entities, that may be confidential, proprietary, copyrighted and/or > legally privileged, and is intended solely for the use of the individual > or entity named in this message. If you are not the intended recipient, > and have received this message in error, please immediately return this > by email and then delete it. > Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Thu Jul 05 15:51:56 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6XMp-0006t9-RP; Thu, 05 Jul 2007 15:51:55 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1I6XMo-0006sv-BS for lemonade-confirm+ok@megatron.ietf.org; Thu, 05 Jul 2007 15:51:54 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6XMo-0006sk-1g for lemonade@ietf.org; Thu, 05 Jul 2007 15:51:54 -0400 Received: from repmmg02.bea.com ([66.248.192.39]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6XMj-0000HP-IK for lemonade@ietf.org; Thu, 05 Jul 2007 15:51:54 -0400 Received: from repmmr02.bea.com (repmmr02.bea.com [10.160.30.72]) by repmmg02.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id l65Jpm9Q032568 for ; Thu, 5 Jul 2007 12:51:48 -0700 Received: from repbex01.amer.bea.com (repbex01.bea.com [10.160.26.98]) by repmmr02.bea.com (Switch-3.2.7/Switch-3.2.5) with ESMTP id l65JpNWm000336 for ; Thu, 5 Jul 2007 12:51:24 -0700 Received: from 172.24.29.29 ([172.24.29.29]) by repbex01.amer.bea.com ([10.160.26.98]) with Microsoft Exchange Server HTTP-DAV ; Thu, 5 Jul 2007 19:51:46 +0000 User-Agent: Microsoft-Entourage/11.3.3.061214 Date: Thu, 05 Jul 2007 15:51:45 -0400 Subject: Re: [lemonade] WGLC reconnect-client From: Eric Burger To: "lemonade@ietf.org" Message-ID: Thread-Topic: [lemonade] WGLC reconnect-client Thread-Index: AcexYGhopt6vTB1TEdysbAAWy4mm/wN3YID4 In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit x-BEA-PMX-Instructions: AV x-BEA-MM: Internal-To-External X-Spam-Score: 0.5 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org Dudes & Dudettes - Stunned by the silence. In this case, unless I hear otherwise, this one is a "go." -- - Eric On 6/18/07 1:23 PM, "Eric Burger" wrote: > We have had a three-month rewrite of reconnect-client, and we got a new > draft last week. > > This is an abbreviated Work Group Last Call, since the document has already > had more than its two weeks' comment period. > > Work Group Last Call ends 25 June 2007. As usual, if the document is just > fine, a brief note saying such would be appreciated. > > http://www.ietf.org/internet-drafts/draft-ietf-lemonade-reconnect-client-05. > txt > > > Notice: This email message, together with any attachments, may contain > information of BEA Systems, Inc., its subsidiaries and affiliated > entities, that may be confidential, proprietary, copyrighted and/or > legally privileged, and is intended solely for the use of the individual or > entity named in this message. If you are not the intended recipient, and have > received this message in error, please immediately return this by email and > then delete it. > > > _______________________________________________ > lemonade mailing list > lemonade@ietf.org > https://www1.ietf.org/mailman/listinfo/lemonade > Supplemental Web Site: > http://www.standardstrack.com/ietf/lemonade Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Thu Jul 05 15:59:06 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6XTm-000708-Gv; Thu, 05 Jul 2007 15:59:06 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1I6XTl-0006wa-DB for lemonade-confirm+ok@megatron.ietf.org; Thu, 05 Jul 2007 15:59:05 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6XTl-0006th-1F for lemonade@ietf.org; Thu, 05 Jul 2007 15:59:05 -0400 Received: from repmmg02.bea.com ([66.248.192.39]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6XTg-0001KW-JQ for lemonade@ietf.org; Thu, 05 Jul 2007 15:59:05 -0400 Received: from repmmr01.bea.com (repmmr01.bea.com [10.160.29.71]) by repmmg02.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id l65Jwxxe006750 for ; Thu, 5 Jul 2007 12:58:59 -0700 Received: from repbex01.amer.bea.com (repbex01.bea.com [10.160.26.98]) by repmmr01.bea.com (Switch-3.2.7/Switch-3.2.5) with ESMTP id l65JwuZb020455 for ; Thu, 5 Jul 2007 12:58:57 -0700 Received: from 172.24.29.29 ([172.24.29.29]) by repbex01.amer.bea.com ([10.160.26.98]) with Microsoft Exchange Server HTTP-DAV ; Thu, 5 Jul 2007 19:58:57 +0000 User-Agent: Microsoft-Entourage/11.3.3.061214 Date: Thu, 05 Jul 2007 15:58:55 -0400 From: Eric Burger To: Message-ID: Thread-Topic: CONVERT - are we done yet? Thread-Index: Ace7/p6AQL0KQ28LTZSphAirPnFXXQDQEw3p In-Reply-To: <4686E0DD.9000100@isode.com> Mime-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit x-BEA-PMX-Instructions: AV x-BEA-MM: Internal-To-External X-Spam-Score: 0.0 (/) X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465 Subject: [lemonade] CONVERT - are we done yet? X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org Work group folks: Do we need stronger text, or can the text stand as is? I think we're really close to being done. Do we need Chicago time on this document? I hope we can finish it all before the meeting (hint, hint). -- - Eric On 6/30/07 7:01 PM, "Alexey Melnikov" wrote: > Hi Eric, > I will use your message to comment on emerging WG consensus as I see it. > > Eric Burger wrote: > >> Said another way, would it be correct to assert conversion was for display >> size, audio/video quality, or object format, and NOT for transmission >> optimization? >> > I am mostly agreeing with this assertion, but as previously discussed in > this thread: I think the client can also request "return me the image > which is less then 100Kb". > >> I am leaning towards Lyndon's position: since there is no real use case for >> SIZE as an estimator, let us let the server only offer it to the client when >> it knows the exact value, after conversion. >> >> > I think I hear the consensus for using the exact sizes. Considering that > some people still see benefits in downloading a converted bodypart in > chunks, the converted size might need to be known before the request for > converted bodypart is fetched. > > So I think what I have in the document already satisfies the > requirements. I can add more text stressing out that good servers should > cache a converted bodypart to make server performance tolerable for > clients. I can also add some text that servers can protect themselves > from abuse and can reply with NO response if the client requests too > many nearly identical conversions. > > > Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Thu Jul 05 16:25:27 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6XtH-0007m0-4Z; Thu, 05 Jul 2007 16:25:27 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1I6XtF-0007lb-1F for lemonade-confirm+ok@megatron.ietf.org; Thu, 05 Jul 2007 16:25:25 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6XtE-0007lQ-NL for lemonade@ietf.org; Thu, 05 Jul 2007 16:25:24 -0400 Received: from repmmg02.bea.com ([66.248.192.39]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I6XtE-00067v-Bd for lemonade@ietf.org; Thu, 05 Jul 2007 16:25:24 -0400 Received: from repmmr01.bea.com (repmmr01.bea.com [10.160.29.71]) by repmmg02.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id l65KOwZH032003 for ; Thu, 5 Jul 2007 13:24:58 -0700 Received: from repbex01.amer.bea.com (repbex01.bea.com [10.160.26.98]) by repmmr01.bea.com (Switch-3.2.7/Switch-3.2.5) with ESMTP id l65KOtPG018478 for ; Thu, 5 Jul 2007 13:24:57 -0700 Received: from 172.24.29.29 ([172.24.29.29]) by repbex01.amer.bea.com ([10.160.26.98]) with Microsoft Exchange Server HTTP-DAV ; Thu, 5 Jul 2007 20:24:56 +0000 User-Agent: Microsoft-Entourage/11.3.3.061214 Date: Thu, 05 Jul 2007 16:24:54 -0400 From: Eric Burger To: "lemonade@ietf.org" Message-ID: Thread-Topic: Drafts' Status as of 070705 Thread-Index: Ace/QovyyqAJjis1EdyiAQAWy4mm/w== Mime-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit x-BEA-PMX-Instructions: AV x-BEA-MM: Internal-To-External X-Spam-Score: 0.5 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa Subject: [lemonade] Drafts' Status as of 070705 X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org Close to done ============= IMAP CONVERT http://tools.ietf.org/html/draft-ietf-lemonade-convert Had WGLC; lots of discussion about exact versus estimated sizes; lots of discussion on being able to request "big" versus "little" objects; consensus is existing text is OK Streaming http://tools.ietf.org/html/draft-ietf-lemonade-streaming Waiting for SIP Expert Review In Progress =========== IMAP Sieve http://tools.ietf.org/html/draft-ietf-lemonade-imap-sieve Waiting for new draft (Leiba) Message Events http://tools.ietf.org/html/draft-ietf-lemonade-msgevent Waiting for new draft (Coates) Lemonade Notifications and Filters http://tools.ietf.org/html/draft-ietf-lemonade-notifications-04 Update draft or roll in to Profile-bis? Profile bis http://tools.ietf.org/html/draft-ietf-lemonade-profile-bis Waiting for everything else. IESG Processing =============== Reconnect Client RFC2192bis Search Within RFC Editor Queue ================ Deployments IMAP COMPRESS Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Thu Jul 05 16:31:42 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6XzJ-0002UK-KJ; Thu, 05 Jul 2007 16:31:41 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1I6XzI-0002UA-Q5 for lemonade-confirm+ok@megatron.ietf.org; Thu, 05 Jul 2007 16:31:40 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6XzI-0002U2-Ev for lemonade@ietf.org; Thu, 05 Jul 2007 16:31:40 -0400 Received: from repmmg02.bea.com ([66.248.192.39]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I6XzI-0006gc-1s for lemonade@ietf.org; Thu, 05 Jul 2007 16:31:40 -0400 Received: from repmmr01.bea.com (repmmr01.bea.com [10.160.29.71]) by repmmg02.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id l65KVcOs006109 for ; Thu, 5 Jul 2007 13:31:38 -0700 Received: from repbex01.amer.bea.com (repbex01.bea.com [10.160.26.98]) by repmmr01.bea.com (Switch-3.2.7/Switch-3.2.5) with ESMTP id l65KVb6f027110 for ; Thu, 5 Jul 2007 13:31:37 -0700 Received: from 172.24.29.29 ([172.24.29.29]) by repbex01.amer.bea.com ([10.160.26.98]) with Microsoft Exchange Server HTTP-DAV ; Thu, 5 Jul 2007 20:31:37 +0000 User-Agent: Microsoft-Entourage/11.3.3.061214 Date: Thu, 05 Jul 2007 16:31:35 -0400 Subject: Re: [lemonade] Drafts' Status as of 070705 From: Eric Burger To: "lemonade@ietf.org" Message-ID: Thread-Topic: [lemonade] Drafts' Status as of 070705 Thread-Index: Ace/QovyyqAJjis1EdyiAQAWy4mm/wAAO8A2 In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit x-BEA-PMX-Instructions: AV x-BEA-MM: Internal-To-External X-Spam-Score: 0.5 (/) X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17 X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org Forgot one: IMAP Context http://tools.ietf.org/html/draft-cridland-imap-context Has been submitted to IESG On 7/5/07 4:24 PM, "Eric Burger" wrote: > Close to done > ============= > IMAP CONVERT > http://tools.ietf.org/html/draft-ietf-lemonade-convert > Had WGLC; lots of discussion about exact versus estimated sizes; lots of > discussion on being able to request "big" versus "little" objects; consensus > is existing text is OK > > Streaming > http://tools.ietf.org/html/draft-ietf-lemonade-streaming > Waiting for SIP Expert Review > > > In Progress > =========== > IMAP Sieve > http://tools.ietf.org/html/draft-ietf-lemonade-imap-sieve > Waiting for new draft (Leiba) > > Message Events > http://tools.ietf.org/html/draft-ietf-lemonade-msgevent > Waiting for new draft (Coates) > > Lemonade Notifications and Filters > http://tools.ietf.org/html/draft-ietf-lemonade-notifications-04 > Update draft or roll in to Profile-bis? > > Profile bis > http://tools.ietf.org/html/draft-ietf-lemonade-profile-bis > Waiting for everything else. > > > IESG Processing > =============== > Reconnect Client > RFC2192bis > Search Within > > > RFC Editor Queue > ================ > Deployments > IMAP COMPRESS > > > Notice: This email message, together with any attachments, may contain > information of BEA Systems, Inc., its subsidiaries and affiliated > entities, that may be confidential, proprietary, copyrighted and/or > legally privileged, and is intended solely for the use of the individual or > entity named in this message. If you are not the intended recipient, and have > received this message in error, please immediately return this by email and > then delete it. > > > _______________________________________________ > lemonade mailing list > lemonade@ietf.org > https://www1.ietf.org/mailman/listinfo/lemonade > Supplemental Web Site: > http://www.standardstrack.com/ietf/lemonade Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Thu Jul 05 19:34:26 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6aq9-0007qE-Ks; Thu, 05 Jul 2007 19:34:25 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1I6aq8-0007q9-5a for lemonade-confirm+ok@megatron.ietf.org; Thu, 05 Jul 2007 19:34:24 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6aq7-0007q1-SB for lemonade@ietf.org; Thu, 05 Jul 2007 19:34:23 -0400 Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6aq3-0005ul-El for lemonade@ietf.org; Thu, 05 Jul 2007 19:34:23 -0400 Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149]) by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l65NYGQ2026892 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 5 Jul 2007 16:34:17 -0700 Received: from [[192.168.1.13]] (dhcp-bldg-l4-72-12.qualcomm.com [129.46.72.235]) by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l65NYFDq001320; Thu, 5 Jul 2007 16:34:16 -0700 Mime-Version: 1.0 Message-Id: In-Reply-To: References: X-Mailer: Eudora for Mac OS X X-message-flag: Warning: Outlook in use. Upgrade to Eudora: Date: Thu, 5 Jul 2007 16:33:12 -0700 To: Eric Burger , "lemonade@ietf.org" From: Randall Gellens Subject: Re: [lemonade] Drafts' Status as of 070705 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Random-Sig-Tag: 1.0b28 X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Cc: X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org At 4:24 PM -0400 7/5/07, Eric Burger wrote: > Message Events > http://tools.ietf.org/html/draft-ietf-lemonade-msgevent > Waiting for new draft (Coates) As far as I know, I'm the editor of the msgevent draft. I have an -03 prepared, which is available as . I plan on submitting it tomorrow afternoon, so if anyone has a chance to read it before then and send me a comment or correction, I'd appreciate it. -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly-selected tag: --------------- Howe's Law: Everyone has a scheme that will not work. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Fri Jul 06 07:58:16 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6mS0-00088z-7H; Fri, 06 Jul 2007 07:58:16 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1I6mRy-00088m-Kb for lemonade-confirm+ok@megatron.ietf.org; Fri, 06 Jul 2007 07:58:14 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6mRy-00088Z-AJ for lemonade@ietf.org; Fri, 06 Jul 2007 07:58:14 -0400 Received: from rufus.isode.com ([62.3.217.251]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I6mRw-0002u0-Dx for lemonade@ietf.org; Fri, 06 Jul 2007 07:58:14 -0400 Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id ; Fri, 6 Jul 2007 12:57:32 +0100 Message-ID: <468E2DC9.3040205@isode.com> Date: Fri, 06 Jul 2007 12:55:53 +0100 From: Alexey Melnikov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: en-us, en To: Randall Gellens Subject: Re: [lemonade] Drafts' Status as of 070705 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Cc: "lemonade@ietf.org" X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org Randall Gellens wrote: > At 4:24 PM -0400 7/5/07, Eric Burger wrote: > >> Message Events >> http://tools.ietf.org/html/draft-ietf-lemonade-msgevent >> Waiting for new draft (Coates) > > As far as I know, I'm the editor of the msgevent draft. Yes. I think Eric is referring to workitem assigned to Peter during the interim. > I have an -03 prepared, which is available as > . > I plan on submitting it tomorrow afternoon, so if anyone has a chance > to read it before then and send me a comment or correction, I'd > appreciate it. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Fri Jul 06 08:05:04 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6mYY-000259-1L; Fri, 06 Jul 2007 08:05:02 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1I6mYV-00024Y-PM for lemonade-confirm+ok@megatron.ietf.org; Fri, 06 Jul 2007 08:04:59 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6mYV-000247-FA for lemonade@ietf.org; Fri, 06 Jul 2007 08:04:59 -0400 Received: from rufus.isode.com ([62.3.217.251]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6mTv-0000M6-2l for lemonade@ietf.org; Fri, 06 Jul 2007 08:00:59 -0400 Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id ; Fri, 6 Jul 2007 13:00:08 +0100 Message-ID: <468E2E6B.5040009@isode.com> Date: Fri, 06 Jul 2007 12:58:35 +0100 From: Alexey Melnikov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: en-us, en To: Eric Burger Subject: Re: [lemonade] CONVERT - are we done yet? References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Cc: lemonade@ietf.org X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org Eric Burger wrote: >Work group folks: > >Do we need stronger text, or can the text stand as is? > I need to review what I currently have in the document. I think some minor editorial additions/changes are needed. >I think we're really close to being done. > > Yes. Mark/Curtis have requested to change syntax to use a new command. I will be doing this over the upcoming weekend. I will submit a new revision before the submission deadline. >Do we need Chicago time on this document? I hope we can finish it all >before the meeting (hint, hint). > > I might need 5 minutes to talk about new syntax. But I don't expect any discussions and I don't have any open issues. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Fri Jul 06 08:27:31 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6muI-00011Z-Mc; Fri, 06 Jul 2007 08:27:30 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1I6muH-00011L-Bb for lemonade-confirm+ok@megatron.ietf.org; Fri, 06 Jul 2007 08:27:29 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6muH-00011D-25 for lemonade@ietf.org; Fri, 06 Jul 2007 08:27:29 -0400 Received: from rufus.isode.com ([62.3.217.251]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6muC-0004z5-FL for lemonade@ietf.org; Fri, 06 Jul 2007 08:27:29 -0400 Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id ; Fri, 6 Jul 2007 13:27:20 +0100 Message-ID: <468E34CB.4080205@isode.com> Date: Fri, 06 Jul 2007 13:25:47 +0100 From: Alexey Melnikov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: en-us, en To: Eric Burger Subject: Re: [lemonade] Drafts' Status as of 070705 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9 Cc: "lemonade@ietf.org" X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org Eric Burger wrote: >Close to done >============= >IMAP CONVERT >http://tools.ietf.org/html/draft-ietf-lemonade-convert >Had WGLC; lots of discussion about exact versus estimated sizes; lots of >discussion on being able to request "big" versus "little" objects; consensus >is existing text is OK > > I will do another revision to address Mark's concert about misusing the FETCH command. Otherwise the document is done. >Streaming >http://tools.ietf.org/html/draft-ietf-lemonade-streaming >Waiting for SIP Expert Review > > >In Progress >=========== >IMAP Sieve >http://tools.ietf.org/html/draft-ietf-lemonade-imap-sieve >Waiting for new draft (Leiba) > >Message Events >http://tools.ietf.org/html/draft-ietf-lemonade-msgevent >Waiting for new draft (Coates) > >Lemonade Notifications and Filters >http://tools.ietf.org/html/draft-ietf-lemonade-notifications-04 >Update draft or roll in to Profile-bis? > >Profile bis >http://tools.ietf.org/html/draft-ietf-lemonade-profile-bis >Waiting for everything else. > > + IMAP NOTIFY _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Fri Jul 06 13:46:05 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6rsY-0008Bi-Ki; Fri, 06 Jul 2007 13:46:02 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1I6rsX-00087x-If for lemonade-confirm+ok@megatron.ietf.org; Fri, 06 Jul 2007 13:46:01 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6rsX-00087o-8W for lemonade@ietf.org; Fri, 06 Jul 2007 13:46:01 -0400 Received: from rufus.isode.com ([62.3.217.251]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I6rsW-0008TC-SI for lemonade@ietf.org; Fri, 06 Jul 2007 13:46:01 -0400 Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id ; Fri, 6 Jul 2007 18:45:56 +0100 Message-ID: <468E7F76.4060503@isode.com> Date: Fri, 06 Jul 2007 18:44:22 +0100 From: Alexey Melnikov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: en-us, en To: Randall Gellens Subject: Re: [lemonade] Drafts' Status as of 070705 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Cc: "lemonade@ietf.org" X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org Randall Gellens wrote: > At 4:24 PM -0400 7/5/07, Eric Burger wrote: > >> Message Events >> http://tools.ietf.org/html/draft-ietf-lemonade-msgevent >> Waiting for new draft (Coates) > > As far as I know, I'm the editor of the msgevent draft. I have an -03 > prepared, which is available as > . > I plan on submitting it tomorrow afternoon, so if anyone has a chance > to read it before then and send me a comment or correction, I'd > appreciate it. In section 1 you've changed NewMessage to MessageRecv, but in section 1.2.1 says that NewMessage became MessageNew? _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Fri Jul 06 14:20:46 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6sQA-0005Jq-DP; Fri, 06 Jul 2007 14:20:46 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1I6sQ8-0005Du-Vj for lemonade-confirm+ok@megatron.ietf.org; Fri, 06 Jul 2007 14:20:45 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6sQ7-00057D-7U for lemonade@ietf.org; Fri, 06 Jul 2007 14:20:43 -0400 Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6sPZ-0002TL-J1 for lemonade@ietf.org; Fri, 06 Jul 2007 14:20:43 -0400 Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149]) by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l66IK6SQ017023 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 6 Jul 2007 11:20:07 -0700 Received: from [[192.168.1.13]] (vpn-10-50-16-38.qualcomm.com [10.50.16.38]) by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l66IK5jr032642; Fri, 6 Jul 2007 11:20:06 -0700 Mime-Version: 1.0 Message-Id: X-Mailer: Eudora for Mac OS X X-message-flag: Warning: Outlook in use. Upgrade to Eudora: Date: Fri, 6 Jul 2007 11:19:45 -0700 To: Eric Burger , "lemonade@ietf.org" From: Randall Gellens Subject: Re: [lemonade] Drafts' Status as of 070705 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Random-Sig-Tag: 1.0b28 X-Spam-Score: 0.0 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Cc: X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org At 4:24 PM -0400 7/5/07, Eric Burger wrote: > Message Events > http://tools.ietf.org/html/draft-ietf-lemonade-msgevent > Waiting for new draft (Coates) > As far as I know, I'm the editor of the msgevent draft. I have an > -03 prepared, which is available as > . > I plan on submitting it tomorrow afternoon, so if anyone has a > chance to read it before then and send me a comment or correction, > I'd appreciate it. Alexey found a bug so I've rev'd it to -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly-selected tag: --------------- Ninety percent of the politicians give the other ten percent a bad name. --Henry Kissinger _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Sun Jul 08 18:15:19 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I7f2E-0007Qt-VQ; Sun, 08 Jul 2007 18:15:18 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1I7f1z-00071B-Ul for lemonade-confirm+ok@megatron.ietf.org; Sun, 08 Jul 2007 18:15:03 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I7f1z-00070g-9f; Sun, 08 Jul 2007 18:15:03 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I7f1y-00038t-LS; Sun, 08 Jul 2007 18:15:03 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 8AB9B2AC7B; Sun, 8 Jul 2007 22:15:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1I7f1y-00027Q-8r; Sun, 08 Jul 2007 18:15:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Sun, 08 Jul 2007 18:15:02 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30 Cc: lemonade@ietf.org Subject: [lemonade] I-D ACTION:draft-ietf-lemonade-msgevent-03.txt X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Enhancements to Internet email to Support Diverse Service Environments Working Group of the IETF. Title : Internet Message Store Events Author(s) : R. Gellens, C. Newman Filename : draft-ietf-lemonade-msgevent-03.txt Pages : 19 Date : 2007-7-8 One of the missing features in the existing Internet mail and messaging standards is a facility for server-to-server and server-to- client event notifications related to message store events. As the scope of Internet mail expands to support more diverse media (such as voice mail), devices (such as cell phones) and to provide rich interactions with other services (such as web portals and legal compliance systems), the need for an interoperable notification system increases. This document attempts to enumerate the types of events which interest real-world consumers of such a system. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-lemonade-msgevent-03.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-lemonade-msgevent-03.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-lemonade-msgevent-03.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-7-8171945.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-lemonade-msgevent-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-lemonade-msgevent-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-7-8171945.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade --NextPart-- From lemonade-bounces@ietf.org Mon Jul 09 11:15:06 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I7ux8-0005dM-7H; Mon, 09 Jul 2007 11:15:06 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1I7ux6-0005c0-7N for lemonade-confirm+ok@megatron.ietf.org; Mon, 09 Jul 2007 11:15:04 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I7ux5-0005aw-5B; Mon, 09 Jul 2007 11:15:03 -0400 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7uwh-0002Fu-Br; Mon, 09 Jul 2007 11:15:03 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id DF30A26E82; Mon, 9 Jul 2007 15:14:38 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1I7uwg-00071j-Ob; Mon, 09 Jul 2007 11:14:38 -0400 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Mon, 09 Jul 2007 11:14:38 -0400 X-Spam-Score: -2.8 (--) X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6 Cc: lemonade mailing list , lemonade chair , Internet Architecture Board , RFC Editor Subject: [lemonade] Protocol Action: 'WITHIN Search extension to the IMAP Protocol' to Proposed Standard X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org The IESG has approved the following document: - 'WITHIN Search extension to the IMAP Protocol ' as a Proposed Standard This document is the product of the Enhancements to Internet email to Support Diverse Service Environments Working Group. The IESG contact persons are Chris Newman and Lisa Dusseault. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-lemonade-search-within-05.txt Technical Summary This document describes the WITHIN extension to IMAP SEARCH. IMAP SEARCH returns messages whose internal date is within or outside a specified interval. The mechanism described here, OLDER and YOUNGER, differs from BEFORE and SINCE in that the client specifies an interval, rather than a date. WITHIN is useful for persistent searches where either the device does not have the capacity to perform the search at regular intervals or the network is of limited bandwidth and thus there is a desire to reduce network traffic from sending repeated requests and redundant responses. Working Group Summary There is consensus in the WG to publish this document. The WG had some difficulty finding text to represent the tension between use of this extension for a single search vs. use of this extension for a persistant search. In the latter case there was WG consensus that the server be permitted to allow updates to lag in order to permit polling-based implementations on the server. Document Quality Virtually all members of the Lemonade WG have reviewed the document. Dave Cridland contributed significant text. Note to RFC Editor In section 1: OLD: subtracting the time interval the client presents. The server then either returnings messages older or younger than the resultant time and date, depending on the search key used. NEW: subtracting the time interval the client presents from the current ^^^^^^^^^^^^^^ date and time of the server. The server then either returns messages ^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^ older or younger than the resultant time and date, depending on the search key used. In Section 3, first paragraph: OLD: The following syntax specification uses the Augmented Backus-Naur Form (ABNF) notation. Elements not defined here can be found in the formal syntax of ABNF [1], IMAP [2], and IMAP Extended ABNF [3] NEW: The following syntax specification uses the Augmented Backus-Naur Form (ABNF) notation. Elements not defined here can be found in the formal syntax of ABNF [3] and IMAP [2]. In section 7: OLD: [3] Melnikov, A. and C. Daboo, "Collected Extensions to IMAP4 ABNF", RFC 4466, April 2006. NEW: [3] Crocker, Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 4234, October 2005. OLD: [4] Melnikov, D. and C. Daboo, "Contexts for IMAP4", draft-cridland-imap-context-02 (work in progress), May 2006. NEW: [4] Cridland, D. and C. King, "Contexts for IMAP4", draft-cridland-imap-context-02 (work in progress), May 2006. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Mon Jul 09 14:16:05 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I7xmG-0005Oy-Pw; Mon, 09 Jul 2007 14:16:04 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1I7xm8-00051M-At for lemonade-confirm+ok@megatron.ietf.org; Mon, 09 Jul 2007 14:15:56 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I7xm6-0004xz-US; Mon, 09 Jul 2007 14:15:55 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I7xm6-0007zH-MQ; Mon, 09 Jul 2007 14:15:54 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 7E7672AC89; Mon, 9 Jul 2007 18:15:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1I7xlG-0006di-7P; Mon, 09 Jul 2007 14:15:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Mon, 09 Jul 2007 14:15:02 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be Cc: lemonade@ietf.org Subject: [lemonade] I-D ACTION:draft-ietf-lemonade-convert-10.txt X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Enhancements to Internet email to Support Diverse Service Environments Working Group of the IETF. Title : IMAP CONVERT extension Author(s) : S. Maes, et al. Filename : draft-ietf-lemonade-convert-10.txt Pages : 0 Date : 2007-7-9 CONVERT defines extensions to IMAP allowing clients to request adaptation and/or transcoding of attachments. Clients can specify the conversion details or allow servers to decide based on knowledge of client capabilities, on user or administrator preferences or its settings. This document also extends IMAP URL schema defined in draft-ietf-lemonade-rfc2192bis-XX.txt with a specifier for a converted bodypart. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-lemonade-convert-10.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-lemonade-convert-10.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-lemonade-convert-10.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-7-9132237.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-lemonade-convert-10.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-lemonade-convert-10.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-7-9132237.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade --NextPart-- From lemonade-bounces@ietf.org Mon Jul 09 16:15:53 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I7zeD-0001D3-BP; Mon, 09 Jul 2007 16:15:53 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1I7ze7-00015W-Jo for lemonade-confirm+ok@megatron.ietf.org; Mon, 09 Jul 2007 16:15:47 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I7ze7-00015I-7q; Mon, 09 Jul 2007 16:15:47 -0400 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7zds-000512-8M; Mon, 09 Jul 2007 16:15:47 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 38AD83289D; Mon, 9 Jul 2007 20:15:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1I7zdO-0002AU-2y; Mon, 09 Jul 2007 16:15:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Mon, 09 Jul 2007 16:15:02 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30 Cc: lemonade@ietf.org Subject: [lemonade] I-D ACTION:draft-ietf-lemonade-msgevent-04.txt X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Enhancements to Internet email to Support Diverse Service Environments Working Group of the IETF. Title : Internet Message Store Events Author(s) : R. Gellens, C. Newman Filename : draft-ietf-lemonade-msgevent-04.txt Pages : 20 Date : 2007-7-9 One of the missing features in the existing Internet mail and messaging standards is a facility for server-to-server and server-to- client event notifications related to message store events. As the scope of Internet mail expands to support more diverse media (such as voice mail), devices (such as cell phones) and to provide rich interactions with other services (such as web portals and legal compliance systems), the need for an interoperable notification system increases. This document attempts to enumerate the types of events which interest real-world consumers of such a system. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-lemonade-msgevent-04.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-lemonade-msgevent-04.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-lemonade-msgevent-04.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-7-9151716.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-lemonade-msgevent-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-lemonade-msgevent-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-7-9151716.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade --NextPart-- From lemonade-bounces@ietf.org Mon Jul 09 17:04:35 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I80PL-0005y6-Og; Mon, 09 Jul 2007 17:04:35 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1I80PJ-0005xQ-IJ for lemonade-confirm+ok@megatron.ietf.org; Mon, 09 Jul 2007 17:04:33 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I80PH-0005wf-4I for lemonade@ietf.org; Mon, 09 Jul 2007 17:04:33 -0400 Received: from repmmg02.bea.com ([66.248.192.39]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I80PG-00025k-No for lemonade@ietf.org; Mon, 09 Jul 2007 17:04:31 -0400 Received: from repmmr02.bea.com (repmmr02.bea.com [10.160.30.72]) by repmmg02.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id l69L3uqm003063 for ; Mon, 9 Jul 2007 14:03:56 -0700 Received: from repbex01.amer.bea.com (repbex01.bea.com [10.160.26.98]) by repmmr02.bea.com (Switch-3.2.7/Switch-3.2.5) with ESMTP id l69L3UjU002729 for ; Mon, 9 Jul 2007 14:03:30 -0700 Received: from 172.24.28.62 ([172.24.28.62]) by repbex01.amer.bea.com ([10.160.26.98]) with Microsoft Exchange Server HTTP-DAV ; Mon, 9 Jul 2007 21:03:55 +0000 User-Agent: Microsoft-Entourage/11.3.3.061214 Date: Mon, 09 Jul 2007 17:03:54 -0400 From: Eric Burger To: "lemonade@ietf.org" Message-ID: Thread-Topic: DRAFT lemonade Agenda Thread-Index: AcfCbKhY5sfT7S5fEdysUwAWy4mm/w== Mime-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit x-BEA-PMX-Instructions: AV x-BEA-MM: Internal-To-External X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c Subject: [lemonade] DRAFT lemonade Agenda X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org Send me comments if you have any. Will be posted in a few days to the IETF 69 meeting materials web site. If you have a presentation, please send it to me as soon as you can. Thanks. Monday, 23 July 2007 Monroe room 1300 - 1310 Greetings, Note Well, Agenda Bashing 1310 - 1330 OMA MEM Status (Dorothy Gellert) 1330 - 1335 IMAP CONVERT (Alexey) http://tools.ietf.org/html/draft-ietf-lemonade-convert 1335 - 1340 Streaming http://tools.ietf.org/html/draft-ietf-lemonade-streaming Waiting for SIP Expert Review; possibility of standard IMAP URI extension (take out one extension defined in the draft) 1340 - 1345 Message Events http://tools.ietf.org/html/draft-ietf-lemonade-msgevent 1345 - 1400 IMAP Sieve http://tools.ietf.org/html/draft-ietf-lemonade-imap-sieve 1400 - 1500 Notifications Lemonade Notifications and Filters http://tools.ietf.org/html/draft-ietf-lemonade-notifications IMAP Notify http://tools.ietf.org/html/draft-gulbrandsen-imap-notify Tuesday, 24 July 2007 Crystal room 1520 - 1530 Greetings, Note Well, Agenda Bashing 1530 - 1615 Notifications (Continued) 1615 - 1700 Profile bis http://tools.ietf.org/html/draft-ietf-lemonade-profile-bis 1700 - 1720 Next Steps Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Mon Jul 09 17:09:24 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I80U0-0000Vb-Fx; Mon, 09 Jul 2007 17:09:24 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1I80Tz-0000Hv-2D for lemonade-confirm+ok@megatron.ietf.org; Mon, 09 Jul 2007 17:09:23 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I80Ty-0000HV-On for lemonade@ietf.org; Mon, 09 Jul 2007 17:09:22 -0400 Received: from repmmg02.bea.com ([66.248.192.39]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I80Tu-0006mX-B0 for lemonade@ietf.org; Mon, 09 Jul 2007 17:09:22 -0400 Received: from repmmr02.bea.com (repmmr02.bea.com [10.160.30.72]) by repmmg02.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id l69L9GRK007997 for ; Mon, 9 Jul 2007 14:09:16 -0700 Received: from repbex01.amer.bea.com (repbex01.bea.com [10.160.26.98]) by repmmr02.bea.com (Switch-3.2.7/Switch-3.2.5) with ESMTP id l69L8nKp007921 for ; Mon, 9 Jul 2007 14:08:50 -0700 Received: from 172.24.28.62 ([172.24.28.62]) by repbex01.amer.bea.com ([10.160.26.98]) with Microsoft Exchange Server HTTP-DAV ; Mon, 9 Jul 2007 21:09:14 +0000 User-Agent: Microsoft-Entourage/11.3.3.061214 Date: Mon, 09 Jul 2007 17:09:12 -0400 From: Eric Burger To: "lemonade@ietf.org" Message-ID: Thread-Topic: Rounding Final Lap Thread-Index: AcfCbWXjpK76EC5gEdysUwAWy4mm/w== Mime-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit x-BEA-PMX-Instructions: AV x-BEA-MM: Internal-To-External X-Spam-Score: 0.5 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Subject: [lemonade] Rounding Final Lap X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org Folks - we are almost there! The end is in sight! I have put up a web page listing the status of *active* drafts. An active draft is a draft that is still in our control. That is, it is NOT in the RFC Editor Queue, not in IESG processing, and not dead. By my count, we have 9-10 documents to go. Of those documents, two just got to the IESG, three are pretty much done, and four are being worked on in earnest. For those who can add to ten, the tenth document is possibly an IMAP URL extension for support of the streaming document. Since we are so close, I will try to manually keep score on-line. Check out: http://www.standardstrack.com/ietf/lemonade/active-status.html Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Tue Jul 10 05:30:37 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I8C3I-00030M-NL; Tue, 10 Jul 2007 05:30:36 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1I8C3G-0002qN-Rj for lemonade-confirm+ok@megatron.ietf.org; Tue, 10 Jul 2007 05:30:34 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I8C3G-0002p1-Br for lemonade@ietf.org; Tue, 10 Jul 2007 05:30:34 -0400 Received: from [2001:838:378:0:2a0:d2ff:fe1b:110f] (helo=turner.dave.cridland.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8C3B-00063o-4W for lemonade@ietf.org; Tue, 10 Jul 2007 05:30:34 -0400 Received: from invsysm1 (shiny.isode.com [62.3.217.250]) by turner.dave.cridland.net (submission) via TCP with ESMTPA id ; Tue, 10 Jul 2007 10:30:24 +0100 Subject: Re: [lemonade] Rounding Final Lap References: In-Reply-To: MIME-Version: 1.0 Message-Id: <6141.1184059798.679822@invsysm1> Date: Tue, 10 Jul 2007 10:29:58 +0100 From: Dave Cridland To: Enhancements to Internet email to support diverse service enivronments Content-Type: multipart/mixed; boundary="6141.1184059798.679566@invsysm1" X-Spam-Score: 0.0 (/) X-Scan-Signature: d2b46e3b2dfbff2088e0b72a54104985 Cc: Philip Guenther X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org --6141.1184059798.679566@invsysm1 Content-Type: text/plain; charset="us-ascii"; format="flowed" On Mon Jul 9 22:09:12 2007, Eric Burger wrote: > earnest. For those who can add to ten, the tenth document is > possibly an > IMAP URL extension for support of the streaming document. Mea culpa. I'll sketch out a draft to do this in time for the meeting, based on stuff I've posted to this list. I'm pretty sure that Philip had something to say on that, but I've forgotten what it was. A reminder for my failing memory would be most welcome. Basically, I'm going to add syntactic glue to be able to make URLFETCH provide a BODYPARTSTRUCTURE (From CONVERT) and provide the result in an identity CTE. This will allow for both Neil Cook's streaming stuff to work, and also URLAUTH-signed conversion requesting URIs. How evil of me. Attached is Neil's reply to my suggestion, so you can avoid digging in your archives. (Message assembled using CATENATE, and then sent via BURL/URLAUTH, of course - my, this dogfood is tasty). Dave. -- Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@jabber.org - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/ - http://dave.cridland.net/ Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade --6141.1184059798.679566@invsysm1 Content-Type: message/rfc822 Content-Disposition: inline Content-Description: Re: [lemonade] Extend URLAUTH to fetch MIME data for bodyparts? Return-Path: <"neil.cook"@noware.co.uk> Received: from turner.dave.cridland.net (turner.dave.cridland.net [/var/run/lmtp]) by turner.dave.cridland.net (Isode M-Box/14.0a0) with LMTP; Thu, 10 May 2007 12:05:41 +0100 (BST) Received: from localhost (localhost.localdomain [127.0.0.1]) by turner.dave.cridland.net (Postfix) with ESMTP id 70EC3498005 for ; Thu, 10 May 2007 12:05:41 +0100 (BST) Received: from turner.dave.cridland.net ([127.0.0.1]) by localhost (turner.dave.cridland.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16709-05 for ; Thu, 10 May 2007 12:05:39 +0100 (BST) Received: from S76018.webhost1.cridland.net (s76018.webhost1.cridland.net [83.138.143.221]) by turner.dave.cridland.net (Postfix) with ESMTP id 282CA498003 for ; Thu, 10 May 2007 12:05:36 +0100 (BST) Received: by S76018.webhost1.cridland.net (Postfix, from userid 503) id D1F017382EE; Thu, 10 May 2007 12:05:35 +0100 (BST) Received: from mail.noware.co.uk (noware.co.uk [82.153.134.193]) by S76018.webhost1.cridland.net (Postfix) with ESMTP id 3BC7F73804D for ; Thu, 10 May 2007 12:05:31 +0100 (BST) Received: by mail.noware.co.uk (Postfix, from userid 1008) id CE28337B3; Thu, 10 May 2007 11:58:52 +0100 (BST) X-CMAE-Analysis: v=1.0 c=1 a=KWikpAkKAAAA:8 a=48vgC7mUAAAA:8 a=bfLuiRfvAAAA:8 a=mjAbWKXCTECz1lwAGbQA:9 a=Y1mpE3KigAs72KIzbKMA:7 a=xE8zCyERFSmN8Mt7AZRoiFQ4qroA:4 Received: from [192.168.0.111] (noware.co.uk [82.153.134.193]) by mail.noware.co.uk (Postfix) with ESMTP id CF26036EC; Thu, 10 May 2007 11:58:51 +0100 (BST) In-Reply-To: <14903.1178787116.488136@peirce.dave.cridland.net> References: <14903.1178787116.488136@peirce.dave.cridland.net> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <25AE0E2A-D0FD-42F3-869F-CF0B9B6C4659@noware.co.uk> Cc: Enhancements to Internet email to support diverse service enivronments Content-Transfer-Encoding: 7bit From: Neil Cook Subject: Re: [lemonade] Extend URLAUTH to fetch MIME data for bodyparts? Date: Thu, 10 May 2007 12:05:24 +0100 To: Dave Cridland X-Mailer: Apple Mail (2.752.3) X-Virus-Scanned: Debian amavisd-new at turner.dave.cridland.net Dave, that seems reasonable to me. Presumably if you did the fetch without specifying binary, you'd get the CTE in the BODYSTRUCTURE,and could thus decode it manually? BTW, I think media servers are probably already used to dealing with CTE, as they can already handle HTTP URLs, which may or may not refer to c-t-e content. However, being able to download the content without CTE is definitely a big plus imo. Neil. On 10 May 2007, at 09:51, Dave Cridland wrote: > On Thu May 10 09:32:51 2007, Neil Cook wrote: >> Now there has been a small amount of discussion in this group on >> how to achieve that without updating those protocols. I've been >> thinking about it, and it seems to me that the best (and most >> generic) fix would be to update the URLAUTH RFC to include an >> option that specifies that the MIME data associated with the >> bodypart should be returned. > You can, of course, pass a URL to the MIME header of the part. > That's doable, but it means passing two URLs to the consumer. > > Otherwise, I'd personally be more interested in decoding the CTE at > source (like BINARY does), and then appending a BODYSTRUCTURE > fragment (or similar) describing MIME headers. > > For example: > > url-full = url-simple / url-extended > ; Changed from RFC4467 > url-simple = astring > ; Containing authimapurlfull > url-extended = "(" url-simple *(SP url-additional) ")" > url-additional = "STRUCTURE" / "BINARY" / iana-token > urlfetch-data = "*" SP "URLFETCH" 1*(SP url-simple [SP "(" url- > additional SP stuff ")"] > SP nstring) > > Now we have the syntactic glue, we can do: > > C: D01 URLFETCH ("imap://[...]" STRUCTURE BINARY) > S: * URLFETCH "imap://[...]" (STRUCTURE ("audio" "mp3" [...])) {~1234} > S: [1234 octets of binary data, containing NUL octets] > S: D01 OK Completed > > Does this seem reasonable? I think it gets the streaming servers > what they need (and at lower impact, since presumably they never > had to deal with CTE before). > > Dave. > -- > Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@jabber.org > - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/ > - http://dave.cridland.net/ > Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade > > > _______________________________________________ > lemonade mailing list > lemonade@ietf.org > https://www1.ietf.org/mailman/listinfo/lemonade > Supplemental Web Site: > http://www.standardstrack.com/ietf/lemonade > --6141.1184059798.679566@invsysm1 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade --6141.1184059798.679566@invsysm1-- From lemonade-bounces@ietf.org Tue Jul 10 12:43:20 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I8Io1-0003OU-EB; Tue, 10 Jul 2007 12:43:17 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1I8Io0-0003O0-A4 for lemonade-confirm+ok@megatron.ietf.org; Tue, 10 Jul 2007 12:43:16 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I8Io0-0003NP-03 for lemonade@ietf.org; Tue, 10 Jul 2007 12:43:16 -0400 Received: from noware.co.uk ([82.153.134.193] helo=mail.noware.co.uk) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8Inz-0002Br-CL for lemonade@ietf.org; Tue, 10 Jul 2007 12:43:15 -0400 Received: by mail.noware.co.uk (Postfix, from userid 1008) id 71F7A37B3; Tue, 10 Jul 2007 17:33:39 +0100 (BST) X-CMAE-Analysis: v=1.0 c=1 a=KWikpAkKAAAA:8 a=48vgC7mUAAAA:8 a=bfLuiRfvAAAA:8 a=2PFVweafb9ZMaNInnIkA:9 a=TD7bGk8wUX7wpIQhMjEA:7 a=jtTyMOV-1cCEYd-0Jo_S9RiynZcA:4 Received: from [192.168.1.3] (host81-129-141-215.range81-129.btcentralplus.com [81.129.141.215]) by mail.noware.co.uk (Postfix) with ESMTP id 24D6236EC; Tue, 10 Jul 2007 17:33:38 +0100 (BST) In-Reply-To: <6141.1184059798.679822@invsysm1> References: <6141.1184059798.679822@invsysm1> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <02A7DD12-06A4-43E9-B7FF-6132A8796514@noware.co.uk> Content-Transfer-Encoding: 7bit From: Neil Cook Subject: Re: [lemonade] Rounding Final Lap Date: Tue, 10 Jul 2007 17:43:08 +0100 To: Dave Cridland X-Mailer: Apple Mail (2.752.3) X-Spam-Score: 0.0 (/) X-Scan-Signature: b22590c27682ace61775ee7b453b40d3 Cc: Enhancements to Internet email to support diverse service enivronments , Philip Guenther X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org Thanks Dave, I will update the streaming draft before the meeting based on the summary below. This removes the need for additional SIP parameter registration etc., and generally makes the draft cleaner. Neil. On 10 Jul 2007, at 10:29, Dave Cridland wrote: > On Mon Jul 9 22:09:12 2007, Eric Burger wrote: >> earnest. For those who can add to ten, the tenth document is >> possibly an >> IMAP URL extension for support of the streaming document. > > Mea culpa. > > I'll sketch out a draft to do this in time for the meeting, based > on stuff I've posted to this list. I'm pretty sure that Philip had > something to say on that, but I've forgotten what it was. A > reminder for my failing memory would be most welcome. > > Basically, I'm going to add syntactic glue to be able to make > URLFETCH provide a BODYPARTSTRUCTURE (From CONVERT) and provide the > result in an identity CTE. This will allow for both Neil Cook's > streaming stuff to work, and also URLAUTH-signed conversion > requesting URIs. How evil of me. > > Attached is Neil's reply to my suggestion, so you can avoid digging > in your archives. (Message assembled using CATENATE, and then sent > via BURL/URLAUTH, of course - my, this dogfood is tasty). > > Dave. > -- > Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@jabber.org > - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/ > - http://dave.cridland.net/ > Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade > > From: Neil Cook > Date: 10 May 2007 12:05:24 BDT > To: Dave Cridland > Cc: Enhancements to Internet email to support diverse service > enivronments > Subject: Re: [lemonade] Extend URLAUTH to fetch MIME data for > bodyparts? > > > Dave, > > that seems reasonable to me. > > Presumably if you did the fetch without specifying binary, you'd > get the CTE in the BODYSTRUCTURE,and could thus decode it manually? > > BTW, I think media servers are probably already used to dealing > with CTE, as they can already handle HTTP URLs, which may or may > not refer to c-t-e content. However, being able to download the > content without CTE is definitely a big plus imo. > > Neil. > > On 10 May 2007, at 09:51, Dave Cridland wrote: > >> On Thu May 10 09:32:51 2007, Neil Cook wrote: >>> Now there has been a small amount of discussion in this group on >>> how to achieve that without updating those protocols. I've been >>> thinking about it, and it seems to me that the best (and most >>> generic) fix would be to update the URLAUTH RFC to include an >>> option that specifies that the MIME data associated with the >>> bodypart should be returned. >> You can, of course, pass a URL to the MIME header of the part. >> That's doable, but it means passing two URLs to the consumer. >> >> Otherwise, I'd personally be more interested in decoding the CTE >> at source (like BINARY does), and then appending a BODYSTRUCTURE >> fragment (or similar) describing MIME headers. >> >> For example: >> >> url-full = url-simple / url-extended >> ; Changed from RFC4467 >> url-simple = astring >> ; Containing authimapurlfull >> url-extended = "(" url-simple *(SP url-additional) ")" >> url-additional = "STRUCTURE" / "BINARY" / iana-token >> urlfetch-data = "*" SP "URLFETCH" 1*(SP url-simple [SP "(" url- >> additional SP stuff ")"] >> SP nstring) >> >> Now we have the syntactic glue, we can do: >> >> C: D01 URLFETCH ("imap://[...]" STRUCTURE BINARY) >> S: * URLFETCH "imap://[...]" (STRUCTURE ("audio" "mp3" [...])) >> {~1234} >> S: [1234 octets of binary data, containing NUL octets] >> S: D01 OK Completed >> >> Does this seem reasonable? I think it gets the streaming servers >> what they need (and at lower impact, since presumably they never >> had to deal with CTE before). >> >> Dave. >> -- >> Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@jabber.org >> - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/ >> - http://dave.cridland.net/ >> Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade >> >> >> _______________________________________________ >> lemonade mailing list >> lemonade@ietf.org >> https://www1.ietf.org/mailman/listinfo/lemonade >> Supplemental Web Site: >> http://www.standardstrack.com/ietf/lemonade >> > > > > _______________________________________________ > lemonade mailing list > lemonade@ietf.org > https://www1.ietf.org/mailman/listinfo/lemonade > Supplemental Web Site: > http://www.standardstrack.com/ietf/lemonade _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Tue Jul 10 15:15:19 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I8LB8-0005Yo-MR; Tue, 10 Jul 2007 15:15:18 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1I8LAt-0004kQ-2t for lemonade-confirm+ok@megatron.ietf.org; Tue, 10 Jul 2007 15:15:03 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I8LAs-0004k8-9e; Tue, 10 Jul 2007 15:15:02 -0400 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8LAs-0008Qx-0G; Tue, 10 Jul 2007 15:15:02 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id E6A5D328A9; Tue, 10 Jul 2007 19:15:01 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1I8LAr-000496-QI; Tue, 10 Jul 2007 15:15:01 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Tue, 10 Jul 2007 15:15:01 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 73734d43604d52d23b3eba644a169745 Cc: lemonade@ietf.org Subject: [lemonade] I-D ACTION:draft-ietf-lemonade-imap-sieve-03.txt X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Enhancements to Internet email to Support Diverse Service Environments Working Group of the IETF. Title : Support for Sieve in Internet Message Access Protocol (IMAP4) Author(s) : B. Leiba Filename : draft-ietf-lemonade-imap-sieve-03.txt Pages : 23 Date : 2007-7-10 Sieve defines an email filtering language that can, in principle, plug into any point in the processing of an email message. As defined in the base specification, it plugs into mail delivery. This document defines how Sieve can plug into points in the IMAP protocol where messages are created or changed, adding the option of user- defined or installation-defined filtering (or, with Sieve extensions, features such as notifications). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-lemonade-imap-sieve-03.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-lemonade-imap-sieve-03.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-lemonade-imap-sieve-03.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-7-10144203.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-lemonade-imap-sieve-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-lemonade-imap-sieve-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-7-10144203.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade --NextPart-- From lemonade-bounces@ietf.org Thu Jul 12 10:04:39 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I8zHb-0003DM-Bw; Thu, 12 Jul 2007 10:04:39 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1I8zHa-0003Ck-3I for lemonade-confirm+ok@megatron.ietf.org; Thu, 12 Jul 2007 10:04:38 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I8zHZ-0003CS-PI; Thu, 12 Jul 2007 10:04:37 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8zHZ-0001tn-Je; Thu, 12 Jul 2007 10:04:37 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 7AA852AC79; Thu, 12 Jul 2007 14:03:47 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1I8zGl-0005je-8i; Thu, 12 Jul 2007 10:03:47 -0400 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Thu, 12 Jul 2007 10:03:47 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Cc: lemonade@ietf.org Subject: [lemonade] Last Call: draft-ietf-lemonade-reconnect-client (IMAP4 Extensions for Quick Mailbox Resynchronization) to Proposed Standard X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ietf@ietf.org List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org The IESG has received a request from the Enhancements to Internet email to Support Diverse Service Environments WG (lemonade) to consider the following document: - 'IMAP4 Extensions for Quick Mailbox Resynchronization ' as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2007-07-26. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-lemonade-reconnect-client-05.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=14857&rfc_flag=0 _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade From lemonade-bounces@ietf.org Sun Jul 15 20:38:12 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAEbL-0004CD-Hi; Sun, 15 Jul 2007 20:38:11 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IAEbK-0004C1-8F for lemonade-confirm+ok@megatron.ietf.org; Sun, 15 Jul 2007 20:38:10 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAEbJ-0004A9-Ql for lemonade@ietf.org; Sun, 15 Jul 2007 20:38:09 -0400 Received: from brmea-mail-3.sun.com ([192.18.98.34]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IAEbJ-0006AW-Ew for lemonade@ietf.org; Sun, 15 Jul 2007 20:38:09 -0400 Received: from fe-amer-01.sun.com ([192.18.108.175]) by brmea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l6G0aO8q000284 for ; Mon, 16 Jul 2007 00:36:24 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 <0JL800A01WTW0A00@mail-amer.sun.com> (original mail from peter.coates@sun.com) for lemonade@ietf.org; Sun, 15 Jul 2007 18:36:24 -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 <0JL8004RDXOLDMH5@mail-amer.sun.com> for lemonade@ietf.org; Sun, 15 Jul 2007 18:36:23 -0600 (MDT) Date: Sun, 15 Jul 2007 17:36:18 -0700 From: Peter Coates To: lemonade@ietf.org Message-id: <003101c7c741$54c4e520$fe4eaf60$%coates@sun.com> MIME-version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Content-language: en-ca Thread-index: AcfHQVBfEfqvh6NCQuCY8bLSqPgyIQ== X-Spam-Score: 0.0 (/) X-Scan-Signature: 155726d2f5fe5eb5c40a9f079fd9e841 Subject: [lemonade] NOTIFY and CONTEXT X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0146380551==" Errors-To: lemonade-bounces@ietf.org This is a multipart message in MIME format. --===============0146380551== Content-type: multipart/alternative; boundary="Boundary_(ID_hcb++UZlSEz/m63kaK5pQQ)" Content-language: en-ca This is a multipart message in MIME format. --Boundary_(ID_hcb++UZlSEz/m63kaK5pQQ) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT It seems to me that there is an unhealthy lack of orthogonally between the NOTIFY and CONTEXT drafts. Both have ways by which a client can request notification of updates of messages meeting a search program. The CONTEXT draft is reasonably consistent and concise: persistent searches or sorts last until reset or until the currently select mailbox is closed. The NOTIFY draft, on the other hand is rather less self consistent. You can specify a search criteria for several notification types, duplicating substantially some of the functionality of CONTEXT. And for NewMessage you can specify both search criteria and fetch-att. The interaction between this and CONTEXT is not specified. The logic of what notifications are sent to the client when a mailbox with complicated notifications specified is clear enough, but a bit surprising requiring some odd manipulation of when message match criteria are used. Lemonade as a whole is pretty heavy on the server, making it more likely that multi server solutions will be adopted. Shared folders become a bit of an issue in multi server deployments. One solution is to direct the initial connection to the server that hosts the user's mailbox and to proxy request for shared folders to the hosting machine. To implement NOTIFY in such an environment is challenging. The functionality offered by NOTIFY (tell me immediately if an update of interest happens, and send me a synopsis of new messages of interest), and CONTEXT (server, please help me maintain search and sort lists) can be maintained with the following changes to both NOTIFY and CONTEXT. (1) get rid of the message-search-criteria from NOTIFY. With CONTEXT this looses no functionality except when associated with the fetch-atts on NewMessage (2) get rid of the fetch-atts on NewMessage in NOTIFY. This looses some important functionality that can be replaced by (3) add optional fetch-atts on the UPDATE option in search in the CONTEXT SPEC. Thus a client can, with a combination of CONTEXT and NOTIFY (a) keep a number of search/sort lists up to date (b) have the server push important attributes of new messages as they are added to these search/sort lists (c) NOTIFY becomes a more manageable draft with far less conditional baggage, and far less overlap with CONTEXT. These search programs are then only ever specified in SEARCH and SORT programs Is there something I'm missing here? This pair of changes massively simplified the implementation of NOTIFY, scarcely complicates CONTEXT, makes the commands much closer to orthogonal, and makes NOTIFY MUCH easier to implement of multi server deployments. Peter --Boundary_(ID_hcb++UZlSEz/m63kaK5pQQ) Content-type: text/html; charset=us-ascii Content-transfer-encoding: 7BIT

It seems to me that there is an unhealthy lack of orthogonally between the NOTIFY and CONTEXT drafts.  Both have ways by which a client can  request notification of updates of messages meeting a search program.

 

The CONTEXT draft is reasonably consistent and concise: persistent searches or sorts last until reset or until the currently select mailbox is closed.

 

The NOTIFY draft, on the other hand is rather less self consistent.  You can specify a search criteria for several notification types, duplicating substantially some of the functionality of CONTEXT.  And for NewMessage you can specify both search criteria and fetch-att.  The interaction between this and CONTEXT is not specified.  The logic of what notifications are sent to the client when a mailbox with complicated notifications specified is clear enough, but a bit surprising requiring some odd manipulation of when message match criteria are used.

 

Lemonade as a whole is pretty heavy on the server, making it more likely that multi server solutions will be adopted.  Shared folders become a bit of an issue in multi server deployments.  One solution is to direct the initial connection to the server that hosts the user’s mailbox and to proxy request for shared folders to the hosting machine.  To implement NOTIFY in such an environment is challenging.

 

The functionality offered by NOTIFY (tell me immediately if an update of interest happens, and send me a synopsis of new messages of interest), and CONTEXT (server, please help me maintain search and sort lists) can be maintained with the following changes to both NOTIFY and CONTEXT.

 

(1)                get rid of the message-search-criteria from NOTIFY.  With CONTEXT this looses no functionality except when associated with the fetch-atts on NewMessage

(2)                get rid of the fetch-atts on NewMessage in NOTIFY.  This looses some important functionality that can be replaced by

(3)                add optional fetch-atts on the UPDATE option in search in the CONTEXT SPEC.

 

Thus a client can, with a combination of CONTEXT and NOTIFY

(a)    keep a number of search/sort lists up to date

(b)   have the server push important attributes of new messages as they are added to these search/sort lists

(c)    NOTIFY becomes a more manageable draft with far less conditional baggage, and far less overlap with CONTEXT.  These search programs are then only ever specified in SEARCH and SORT programs

 

Is there something I’m missing here?  This pair of changes massively simplified the implementation of NOTIFY, scarcely complicates CONTEXT, makes the commands much closer to orthogonal, and makes NOTIFY MUCH easier to implement of multi server deployments.

 

Peter

--Boundary_(ID_hcb++UZlSEz/m63kaK5pQQ)-- --===============0146380551== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade --===============0146380551==-- From lemonade-bounces@ietf.org Thu Jul 19 16:29:01 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IBccO-0003Uy-MO; Thu, 19 Jul 2007 16:29:00 -0400 Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1IBccN-0003Ul-NE for lemonade-confirm+ok@megatron.ietf.org; Thu, 19 Jul 2007 16:28:59 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IBccN-0003Ud-As for lemonade@ietf.org; Thu, 19 Jul 2007 16:28:59 -0400 Received: from repmmg02.bea.com ([66.248.192.39]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IBccL-0004Fw-Vl for lemonade@ietf.org; Thu, 19 Jul 2007 16:28:59 -0400 Received: from repmmr02.bea.com (repmmr02.bea.com [10.160.30.72]) by repmmg02.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id l6JKSt9M031312; Thu, 19 Jul 2007 13:28:55 -0700 Received: from repbex01.amer.bea.com (repbex01.bea.com [10.160.26.98]) by repmmr02.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id l6JKSNi6020196; Thu, 19 Jul 2007 13:28:23 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 19 Jul 2007 13:28:45 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Review of Lemonade Streaming Draft Thread-Index: AcfIxz9RVUFvz4QsQfq1rJc5lC5rugBe5Sdw From: "Eric Burger" To: x-BEA-PMX-Instructions: AV x-BEA-MM: Internal-To-External X-Spam-Score: 0.0 (/) X-Scan-Signature: f5932bfc8385127f631fc458a872feb1 Cc: pkyzivat@cisco.com Subject: [lemonade] FW: Review of Lemonade Streaming Draft X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org If you have comments or questions, send them directly to Paul, as he is not a list subscriber. Paul - Thanks!!! -- Eric -----Original Message----- From: Paul Kyzivat [mailto:pkyzivat@cisco.com] Sent: Tuesday, July 17, 2007 7:07 PM To: Eric Burger Subject: Re: Review of Lemonade Streaming Draft Eric, OK, you twisted my arm enough to go read this draft. (draft-ietf-lemonade-streaming-02). You didn't tell me where to send this. So I guess I will just send it to you for now. If you want me to send it to sipping and/or lemonade just let me know. Or feel free to just forward this to some wg lists if you wish. As a general comment, this looks like a useful capability to have. Beyond that I have some specific comments about parts of the draft. But please take these with a grain of salt, because I know *nothing* of any of the work done by the lemonade wg. I did consult a couple of the referenced documents along the way, but only briefly. Section 2.1: > However, it should be noted that this document proposes an extension > to the SIP Parameter Registry [9], in order to accommodate passing a > content transfer encoding parameter to the Announcement Service. > Additionally two new attributes to the MSCML