From lemonade-bounces@ietf.org Mon Oct 02 10:51:05 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUP87-0004OP-03; Mon, 02 Oct 2006 10:50:51 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUP7r-0003vk-SU; Mon, 02 Oct 2006 10:50:35 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUP7r-0002uf-PL; Mon, 02 Oct 2006 10:50:35 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GUP7o-0005DZ-6Q; Mon, 02 Oct 2006 10:50:35 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 187292AC93; Mon, 2 Oct 2006 14:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GUP7J-0005xx-RR; Mon, 02 Oct 2006 10:50: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: Mon, 02 Oct 2006 10:50:01 -0400 X-Spam-Score: -5.9 (-----) X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8 Cc: lemonade@ietf.org Subject: [lemonade] I-D ACTION:draft-ietf-lemonade-compress-05.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 : The IMAP COMPRESS Extension Author(s) : A. Gulbrandsen Filename : draft-ietf-lemonade-compress-05.txt Pages : 9 Date : 2006-10-2 The COMPRESS extension allows an IMAP connection to be effectively and efficiently compressed. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-lemonade-compress-05.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-compress-05.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-compress-05.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: <2006-10-2093133.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-lemonade-compress-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-lemonade-compress-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-10-2093133.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 --NextPart-- From lemonade-bounces@ietf.org Mon Oct 02 12:03:10 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUQFu-0005Cj-7E; Mon, 02 Oct 2006 12:02:58 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUQFt-0005Ao-1i for lemonade@ietf.org; Mon, 02 Oct 2006 12:02:57 -0400 Received: from mail121.messagelabs.com ([216.82.241.195]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GUQFl-0004Y0-OD for lemonade@ietf.org; Mon, 02 Oct 2006 12:02:57 -0400 X-VirusChecked: Checked X-Env-Sender: tony@att.com X-Msg-Ref: server-4.tower-121.messagelabs.com!1159804969!8179390!1 X-StarScan-Version: 5.5.10.7; banners=-,-,- X-Originating-IP: [134.24.146.67] Received: (qmail 18157 invoked from network); 2 Oct 2006 16:02:49 -0000 Received: from unknown (HELO maillennium.att.com) (134.24.146.67) by server-4.tower-121.messagelabs.com with SMTP; 2 Oct 2006 16:02:49 -0000 Received: from [135.210.40.161] (unknown[135.210.40.161](misconfigured sender)) by maillennium.att.com (mailgw1) with ESMTP id <20061002160248gw100re3g7e> (Authid: tony); Mon, 2 Oct 2006 16:02:48 +0000 Message-ID: <45213825.1050908@att.com> Date: Mon, 02 Oct 2006 12:02:45 -0400 From: Tony Hansen User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: arnt@oryx.com References: In-Reply-To: X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Cc: lemonade@ietf.org Subject: [lemonade] Re: I-D ACTION:draft-ietf-lemonade-compress-05.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 Internet-Drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > Title : The IMAP COMPRESS Extension This draft looks very good. One nit in Section 7: < and another compression is added > and another compression mechanism is added ^^^^^^^^^ Can we LC this now? Tony Hansen tony@att.com _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Mon Oct 02 13:30:26 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GURcM-0004pY-7Z; Mon, 02 Oct 2006 13:30:14 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GURcK-0004nj-PC for lemonade@ietf.org; Mon, 02 Oct 2006 13:30:12 -0400 Received: from kalyani.oryx.com ([195.30.37.30]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GURcJ-0003l7-Bf for lemonade@ietf.org; Mon, 02 Oct 2006 13:30:12 -0400 Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9]) by kalyani.oryx.com (Postfix) with ESMTP id BB9D34ACE5; Mon, 2 Oct 2006 19:29:57 +0200 (CEST) Message-Id: Date: Mon, 2 Oct 2006 19:32:19 +0200 From: Arnt Gulbrandsen To: lemonade@ietf.org Subject: Re: [lemonade] Re: I-D ACTION:draft-ietf-lemonade-compress-05.txt References: <45213825.1050908@att.com> In-Reply-To: <45213825.1050908@att.com> Content-Type: text/plain; format=flowed MIME-Version: 1.0 X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Cc: Tony Hansen 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 Tony Hansen writes: > Internet-Drafts@ietf.org wrote: >> A New Internet-Draft is available from the on-line Internet-Drafts >> directories. >> Title : The IMAP COMPRESS Extension > > This draft looks very good. Thanks. > One nit in Section 7: > > < and another compression is added >> and another compression mechanism is added > ^^^^^^^^^ Fixed. > Can we LC this now? Yes, Eric will do that, probably tomorrow. Arnt _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Mon Oct 02 19:25:54 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUXAN-0004Sa-Tj; Mon, 02 Oct 2006 19:25:43 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUXAN-0004SV-F7 for lemonade@ietf.org; Mon, 02 Oct 2006 19:25:43 -0400 Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUXAM-000785-3w for lemonade@ietf.org; Mon, 02 Oct 2006 19:25:43 -0400 Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150]) by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id k92NPe7I000965 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 2 Oct 2006 16:25:41 -0700 Received: from [loud.qualcomm.com] (loud.qualcomm.com [129.46.172.15]) by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k92NPaX9018196; Mon, 2 Oct 2006 16:25:38 -0700 (PDT) Mime-Version: 1.0 Message-Id: X-Mailer: Eudora for Mac OS X (dev alpha) X-message-flag: Warning: Outlook in use. Upgrade to Eudora: Date: Mon, 2 Oct 2006 16:20:44 -0700 To: arnt@oryx.com From: Randall Gellens 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: 50a516d93fd399dc60588708fd9a3002 Cc: lemonade@ietf.org Subject: [lemonade] Re: I-D ACTION:draft-ietf-lemonade-compress-05.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 One other (besides Tony's) nit in Section 7: unlikely that another compression mechanism algorithm will be added Please delete "algorithm". I know this has been discussed before, and if you're sick of it and want to just leave it as-is that's fine, but I think this wording in Section 3 is awkward: When COMPRESS is combined with TLS or [SASL] layers, the order of processing data to be sent SHALL be to first COMPRESS, then SASL, and finally TLS. When receiving data, the processing order MUST be reversed. This ensures that data is compressed before it is encrypted, independent of the order in which the client issues COMPRESS, AUTHENTICATE, and STARTTLS. It seems strange to me because of the usage of "SASL" and "TLS" as verbs, and the potential ambiguity of "SASL" -- is it the authentication exchange or a security layer? I'd assume a SASL authentication exchange would be compressed if COMPRESS were issued before AUTHENTICATE, and so this text refers to any security layer that was also negotiated in SASL, and I think most implementers would come to the same conclusion (and the initial wording implies this as well), but it might be nice to make it more clear. Perhaps something along the lines of: When COMPRESS is combined with TLS or [SASL] layers, the sending order of the three extensions MUST be first COMPRESS, then SASL, and finally TLS. That is, before data is transmitted it is first compressed. Second, if a SASL security layer has been negotiated, the compressed data is then signed and/or encrypted accordingly. Third, if a TLS security layer has been negotiated, it is signed and/or encrypted accordingly. When receiving data, the processing order MUST be reversed. This ensures that before sending, data is compressed before it is encrypted, independent of the order in which the client issues COMPRESS, AUTHENTICATE, and STARTTLS. -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly-selected tag: --------------- Lansing Residents Can Drop Off Trees --Newspaper headline _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Tue Oct 03 12:26:34 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUn5w-00074M-Mx; Tue, 03 Oct 2006 12:26:12 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUn5v-00074G-5g for lemonade@ietf.org; Tue, 03 Oct 2006 12:26:11 -0400 Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUn5t-0002WC-QI for lemonade@ietf.org; Tue, 03 Oct 2006 12:26:11 -0400 Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151]) by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id k93GQ7mj010788 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 3 Oct 2006 09:26:08 -0700 Received: from [[192.168.1.13]] (vpn-10-50-16-129.qualcomm.com [10.50.16.129]) by crowley.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k93GPwB1021263; Tue, 3 Oct 2006 09:26:01 -0700 (PDT) Mime-Version: 1.0 Message-Id: In-Reply-To: References: X-Mailer: Eudora for Mac OS X (dev alpha) X-message-flag: Warning: Outlook in use. Upgrade to Eudora: Date: Tue, 3 Oct 2006 09:24:33 -0700 To: arnt@oryx.com From: Randall Gellens Subject: [lemonade] Re: I-D ACTION:draft-ietf-lemonade-compress-05.txt 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: bb8f917bb6b8da28fc948aeffb74aa17 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 At 4:20 PM -0700 10/2/06, Randall Gellens wrote: > Perhaps something along the lines of: > > When COMPRESS is combined with TLS or [SASL] layers, the sending > order of the three extensions MUST be first COMPRESS, then SASL, > and finally TLS. That is, before data is transmitted it is first > compressed. Second, if a SASL security layer has been negotiated, > the compressed data is then signed and/or encrypted accordingly. > Third, if a TLS security layer has been negotiated, it is signed > and/or encrypted accordingly. When receiving data, the processing > order MUST be reversed. This ensures that before sending, data is > compressed before it is encrypted, independent of the order in > which the client issues COMPRESS, AUTHENTICATE, and STARTTLS. Perhaps, just to make it somewhat more clear: When COMPRESS is combined with TLS or [SASL] security layers, the sending order of the three extensions MUST be first COMPRESS, then SASL, and finally TLS. That is, before data is transmitted it is first compressed. Second, if a SASL security layer has been negotiated, the compressed data is then signed and/or encrypted accordingly. Third, if a TLS security layer has been negotiated, the data from the second step is signed and/or encrypted accordingly. When receiving data, the processing order MUST be reversed. This ensures that before sending, data is compressed before it is encrypted, independent of the order in which the client issues COMPRESS, AUTHENTICATE, and STARTTLS. -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly-selected tag: --------------- razbliuto (ros-blee-OO-toe; Russian; noun): the feeling a person retains for someone he or she once loved. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Tue Oct 03 14:14:58 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUon2-00043J-1S; Tue, 03 Oct 2006 14:14:48 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUon1-00041S-E7 for lemonade@ietf.org; Tue, 03 Oct 2006 14:14:47 -0400 Received: from rufus.isode.com ([62.3.217.251]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUon0-0006IC-1c for lemonade@ietf.org; Tue, 03 Oct 2006 14:14:47 -0400 Received: from [172.16.2.109] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id ; Tue, 3 Oct 2006 19:14:44 +0100 Message-ID: <4522A891.1050005@isode.com> Date: Tue, 03 Oct 2006 19:14:41 +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] Re: I-D ACTION:draft-ietf-lemonade-compress-05.txt 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: b19722fc8d3865b147c75ae2495625f2 Cc: lemonade@ietf.org, arnt@oryx.com 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:20 PM -0700 10/2/06, Randall Gellens wrote: > >> Perhaps something along the lines of: >> >> When COMPRESS is combined with TLS or [SASL] layers, the sending >> order of the three extensions MUST be first COMPRESS, then SASL, and >> finally TLS. That is, before data is transmitted it is first >> compressed. Second, if a SASL security layer has been negotiated, >> the compressed data is then signed and/or encrypted accordingly. >> Third, if a TLS security layer has been negotiated, it is signed >> and/or encrypted accordingly. When receiving data, the processing >> order MUST be reversed. This ensures that before sending, data is >> compressed before it is encrypted, independent of the order in which >> the client issues COMPRESS, AUTHENTICATE, and STARTTLS. > > Perhaps, just to make it somewhat more clear: > > When COMPRESS is combined with TLS or [SASL] security layers, the > sending order of the three extensions MUST be first COMPRESS, then > SASL, and finally TLS. That is, before data is transmitted it is > first compressed. Second, if a SASL security layer has been > negotiated, the compressed data is then signed and/or encrypted > accordingly. Third, if a TLS security layer has been negotiated, the > data from the second step is signed and/or encrypted accordingly. When > receiving data, the processing order MUST be reversed. This ensures > that before sending, data is compressed before it is encrypted, > independent of the order in which the client issues COMPRESS, > AUTHENTICATE, and STARTTLS. I like this. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Tue Oct 03 14:34:03 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUp5X-00065O-8F; Tue, 03 Oct 2006 14:33:55 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUp5V-000650-SC for lemonade@ietf.org; Tue, 03 Oct 2006 14:33:53 -0400 Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUp5T-0001Xu-H8 for lemonade@ietf.org; Tue, 03 Oct 2006 14:33:53 -0400 Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150]) by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id k93IXmFx000749 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 3 Oct 2006 11:33:50 -0700 Received: from [loud.qualcomm.com] (loud.qualcomm.com [129.46.172.15]) by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k93IXh4g008846; Tue, 3 Oct 2006 11:33:47 -0700 (PDT) Mime-Version: 1.0 Message-Id: In-Reply-To: References: X-Mailer: Eudora for Mac OS X (dev alpha) X-message-flag: Warning: Outlook in use. Upgrade to Eudora: Date: Tue, 3 Oct 2006 11:33:35 -0700 To: arnt@oryx.com From: Randall Gellens Subject: [lemonade] Re: I-D ACTION:draft-ietf-lemonade-compress-05.txt 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: 52e1467c2184c31006318542db5614d5 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 > Perhaps, just to make it somewhat more clear: > > When COMPRESS is combined with TLS or [SASL] security layers, the > sending order of the three extensions MUST be first COMPRESS, then > SASL, and finally TLS. That is, before data is transmitted it is > first compressed. Second, if a SASL security layer has been > negotiated, the compressed data is then signed and/or encrypted > accordingly. Third, if a TLS security layer has been negotiated, > the data from the second step is signed and/or encrypted > accordingly. When receiving data, the processing order MUST be > reversed. This ensures that before sending, data is compressed > before it is encrypted, independent of the order in which the > client issues COMPRESS, AUTHENTICATE, and STARTTLS. One (hopefully last) tweak: change "second step" to "previous step" (since if there is no SASL layer, the previous step is the first, not the second). That would make it: When COMPRESS is combined with TLS or [SASL] security layers, the sending order of the three extensions MUST be first COMPRESS, then SASL, and finally TLS. That is, before data is transmitted it is first compressed. Second, if a SASL security layer has been negotiated, the compressed data is then signed and/or encrypted accordingly. Third, if a TLS security layer has been negotiated, the data from the previous step is signed and/or encrypted accordingly. When receiving data, the processing order MUST be reversed. This ensures that before sending, data is compressed before it is encrypted, independent -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly-selected tag: --------------- The whole dream of democracy is to raise the proletarian to the level of stupidity attained by the bourgeois. --Gustave Flaubert _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Tue Oct 03 15:22:24 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUpqE-0007RB-4i; Tue, 03 Oct 2006 15:22:10 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUpqC-0007R5-42 for lemonade@ietf.org; Tue, 03 Oct 2006 15:22:08 -0400 Received: from kalyani.oryx.com ([195.30.37.30]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUpqA-00018g-NJ for lemonade@ietf.org; Tue, 03 Oct 2006 15:22:08 -0400 Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9]) by kalyani.oryx.com (Postfix) with ESMTP id 1CCE14AD10; Tue, 3 Oct 2006 21:21:50 +0200 (CEST) Message-Id: Date: Tue, 3 Oct 2006 21:21:51 +0200 From: Arnt Gulbrandsen To: lemonade@ietf.org Subject: Re: [lemonade] Re: I-D ACTION:draft-ietf-lemonade-compress-05.txt References: In-Reply-To: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; format=flowed MIME-Version: 1.0 X-Spam-Score: 0.0 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Cc: Randall Gellens 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 writes: > One (hopefully last) tweak: change "second step" to "previous step" > (since if there is no SASL layer, the previous step is the first, not > the second). > > That would make it: =2E.. I used this. Thank you. Arnt _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Wed Oct 04 13:10:45 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVAGT-0006Rn-6s; Wed, 04 Oct 2006 13:10:37 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVAGS-0006Ri-Q0 for lemonade@ietf.org; Wed, 04 Oct 2006 13:10:36 -0400 Received: from rufus.isode.com ([62.3.217.251]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GVAGO-0001O5-Bu for lemonade@ietf.org; Wed, 04 Oct 2006 13:10:36 -0400 Received: from [172.16.2.102] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id ; Wed, 4 Oct 2006 18:10:30 +0100 Message-ID: <4523EAC1.6020503@isode.com> Date: Wed, 04 Oct 2006 18:09:21 +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: Lemonade WG 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: d8ae4fd88fcaf47c1a71c804d04f413d Subject: [lemonade] Invitation to the Lemonade interop event 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 folks, During the Montreal IETF meeting Lemonade WG chairs announced a plan to have Lemonade interop event in October. So with chairs permission I would like to invite people to come to the Lemonade interop testing event, which will be held in Maidenhead, UK (London area) on October 23rd - 25th 2006. A room for the event is booked at Nortel's office in Maidenhead (Thanks to Nortel and Glenn in particular!). The Nortel site is (see (PDF) for directions): Maidenhead Office Park Westacott Way, Maidenhead, Berkshire SL6 3QH England Tel: 01628 432000 There is a cafeteria on site for lunch. There is a phone, and Glenn can have a phone bridge opened for discussion as needed. There is Internet access for at least the Nortel attendees. Glenn is trying to verify external access for everybody else... There is a Nortel shuttle bus from Maidenhead Station to MOP. Please contact Glenn Parsons for more details. Information about suggested hotels is here: * *A couple of important additional comments: 1). If you are planning to come in person, and haven't told me or Glenn, *please* do so ASAP. Glenn has to sign in every visitor, so he need to know names of attendees in advance. 2). There is no fee for participation in the event. 3). This is not an IETF event, as IETF doesn't formally do any interop testing. However many IETFers will be present. Also note that this is in no way a marketing event. 4). Note that it is Ok for people to come to the event just to observe and/or discuss implementation plans. This is even encouraged. 5). Several people have already confirmed that they are coming to the event. There would be at least 3 server vendors present in person. 7). People coming should be prepared to be productive in absence of Internet connectivity. Just in case we encounter some external connectivity problems. (There would be a local network available with DHCP, etc. So if you bring a laptop, that should be sufficient) 7). All attendees are expected to sign NDA in order to participate in the event. This will allow developers to speak freely about implementation details. 8). People coming should bring some giveaways for other participants who find bugs in your software. 9). I will separately send some instructions on how servers need to be configured for the event. Please contact me directly if you have any further questions. Best Regards, Alexey _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Wed Oct 04 13:59:48 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVB20-0007oq-9F; Wed, 04 Oct 2006 13:59:44 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVB1y-0007nz-BY for lemonade@ietf.org; Wed, 04 Oct 2006 13:59:42 -0400 Received: from rufus.isode.com ([62.3.217.251]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GVB1u-0000ZF-2P for lemonade@ietf.org; Wed, 04 Oct 2006 13:59:42 -0400 Received: from [172.16.2.102] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id ; Wed, 4 Oct 2006 18:59:36 +0100 Message-ID: <4523F66C.2010102@isode.com> Date: Wed, 04 Oct 2006 18:59:08 +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 MIME-Version: 1.0 To: Lemonade WG References: <4523EAC1.6020503@isode.com> In-Reply-To: <4523EAC1.6020503@isode.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Subject: [lemonade] Lemonade interop event: agenda and server setup 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 Alexey Melnikov wrote: > Hi folks, > During the Montreal IETF meeting Lemonade WG chairs announced a plan to > have Lemonade interop event in October. > So with chairs permission I would like to invite people to come to the > Lemonade interop testing > event, which will be held in Maidenhead, UK (London area) on October > 23rd - 25th 2006. Tentative agenda for the event: And server setup is described: _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Wed Oct 04 14:07:24 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVB9O-00059y-5F; Wed, 04 Oct 2006 14:07:22 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVB9N-00059t-O9 for lemonade@ietf.org; Wed, 04 Oct 2006 14:07:21 -0400 Received: from rufus.isode.com ([62.3.217.251]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GVB9M-0001Kq-Bn for lemonade@ietf.org; Wed, 04 Oct 2006 14:07:21 -0400 Received: from [172.16.2.102] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id ; Wed, 4 Oct 2006 19:07:19 +0100 Message-ID: <4523F835.2@isode.com> Date: Wed, 04 Oct 2006 19:06:45 +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 MIME-Version: 1.0 To: Lemonade WG Subject: Re: [lemonade] Lemonade interop event: agenda and server setup References: <4523EAC1.6020503@isode.com> <4523F66C.2010102@isode.com> In-Reply-To: <4523F66C.2010102@isode.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab 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 Alexey Melnikov wrote: > Alexey Melnikov wrote: > >> Hi folks, >> During the Montreal IETF meeting Lemonade WG chairs announced a plan to >> have Lemonade interop event in October. >> So with chairs permission I would like to invite people to come to >> the Lemonade interop testing >> event, which will be held in Maidenhead, UK (London area) on October >> 23rd - 25th 2006. > > Tentative agenda for the event: > People who are planning to attend should let me know if there are some extra extensions they would like to test or topics they would like to discuss. Thanks, Alexey _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Thu Oct 05 06:16:30 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVQHA-0000Mc-VO; Thu, 05 Oct 2006 06:16:24 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVQH9-0000MX-UK for lemonade@ietf.org; Thu, 05 Oct 2006 06:16:23 -0400 Received: from pythagoras.zen.co.uk ([212.23.3.140]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GVQH6-0008SN-GH for lemonade@ietf.org; Thu, 05 Oct 2006 06:16:23 -0400 Received: from [217.155.137.60] (helo=turner.dave.cridland.net) by pythagoras.zen.co.uk with esmtp (Exim 4.50) id 1GVQH5-0001TA-J3; Thu, 05 Oct 2006 10:16:19 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by turner.dave.cridland.net (Postfix) with ESMTP id A73ED498005; Thu, 5 Oct 2006 11:20:59 +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 23197-02; Thu, 5 Oct 2006 11:20:47 +0100 (BST) Received: from peirce.dave.cridland.net (unknown [IPv6:2001:4bd0:2029:0:2e0:81ff:fe29:d16a]) by turner.dave.cridland.net (Postfix) with ESMTP id C0987498003; Thu, 5 Oct 2006 11:20:47 +0100 (BST) Date: Thu, 05 Oct 2006 11:16:05 +0100 Subject: Re: [lemonade] Re: I-D ACTION:draft-ietf-lemonade-compress-05.txt References: In-Reply-To: MIME-Version: 1.0 Message-Id: <5897.1160043366.572711@peirce.dave.cridland.net> From: Dave Cridland To: Arnt Gulbrandsen Content-Type: text/plain; charset="us-ascii"; format="flowed" X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at dave.cridland.net X-Originating-Pythagoras-IP: [217.155.137.60] X-Spam-Score: 0.1 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Cc: Randall Gellens , 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 On Tue Oct 3 20:21:51 2006, Arnt Gulbrandsen wrote: > Randall Gellens writes: >> One (hopefully last) tweak: change "second step" to "previous step" >> (since if there is no SASL layer, the previous step is the first, >> not >> the second). >> >> That would make it: > ... > > I used this. Thank you. With SASL, the negotiation takes place above the compression layer, but the security layer (if any) happens below the compression. With TLS, I assume the negotiation happens below the compression layer, if any, not above. I can't find anything that explicitly tells me about this, though. 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 From lemonade-bounces@ietf.org Thu Oct 05 13:49:01 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVXL1-0004Zq-1l; Thu, 05 Oct 2006 13:48:51 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVXL0-0004Zl-9M for lemonade@ietf.org; Thu, 05 Oct 2006 13:48:50 -0400 Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GVXKy-0005Qe-V4 for lemonade@ietf.org; Thu, 05 Oct 2006 13:48:50 -0400 Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148]) by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id k95HmfRI021597 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 5 Oct 2006 10:48:42 -0700 Received: from [[192.168.1.13]] (vpn-10-50-16-148.qualcomm.com [10.50.16.148]) by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k95HmXra010167; Thu, 5 Oct 2006 10:48:35 -0700 (PDT) Mime-Version: 1.0 Message-Id: In-Reply-To: <5897.1160043366.572711@peirce.dave.cridland.net> References: <5897.1160043366.572711@peirce.dave.cridland.net> X-Mailer: Eudora for Mac OS X (dev alpha) X-message-flag: Warning: Outlook in use. Upgrade to Eudora: Date: Thu, 5 Oct 2006 10:48:17 -0700 To: Dave Cridland , Arnt Gulbrandsen From: Randall Gellens Subject: Re: [lemonade] Re: I-D ACTION:draft-ietf-lemonade-compress-05.txt 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: 97adf591118a232206bdb5a27b217034 Cc: Randall Gellens , 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 At 11:16 AM +0100 10/5/06, Dave Cridland wrote: > With SASL, the negotiation takes place above the compression layer, > but the security layer (if any) happens below the compression. The wording I suggested tries to be careful to only talk about a SASL security layer, not the SASL negotiation. If we want to make this more explicit, we could add a one-sentence paragraph to this affect before the text. > With TLS, I assume the negotiation happens below the compression > layer, if any, not above. Do we want to have text recommending the order that clients issue STARTTLS, AUTHENTICATE, and COMPRESS? I know we discussed this a while back, with some difference of opinion as to if authentication should be done before or after compression. If I recall correctly, doing compression before authentication saves bandwidth, but doing it after makes it easier to debug. Presumably, we would add new one-sentence paragraph along the lines of: "Clients making use of TLS, SASL authentication, and compression SHOULD issue these commands in the following order: first STARTTLS, then AUTHENTICATE, and finally COMPRESS." (Or swap COMPRESS and AUTHENTICATE if that is the way we want to go.) -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly-selected tag: --------------- The brain is a wonderful organ; it starts working the moment you get up in the morning, and does not stop until you get to work. --Robert Frost _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Tue Oct 10 16:44:32 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXOSX-0005S0-ES; Tue, 10 Oct 2006 16:44:17 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXOSV-0005Rv-DN for lemonade@ietf.org; Tue, 10 Oct 2006 16:44:15 -0400 Received: from mx.plaxo.com ([66.151.128.13] helo=mx12.plaxo.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXOST-0004rV-MX for lemonade@ietf.org; Tue, 10 Oct 2006 16:44:15 -0400 Received: from bes05.plaxo.com (bes05.plaxo.com [10.1.10.5]) by mx12.plaxo.com (Postfix) with QMQP id 56089C013 for ; Tue, 10 Oct 2006 13:44:13 -0700 (PDT) Message-ID: <1160513053.24073.36128.sendUpdate@mx.plaxo.com> Date: 10 Oct 2006 20:44:13 -0000 From: "Eric Burger" To: "IETF LEMONADE" Precedence: bulk MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_-------==1727423864" X-Spam-Score: 0.9 (/) X-Scan-Signature: 1b82b4ba484bbe86cdae6d5f8b2d2ccb Subject: [lemonade] Staying in touch X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Reply-To: Plaxo Contact Update for Eric Burger 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 This is a multi-part message in MIME format. --_-------==1727423864 Content-Type: multipart/alternative; boundary="_--=======1553857882" --_--=======1553857882 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Dear IETF, I'm updating my address book. Please take a moment to update me with your latest contact info. Click the following link to correct or confirm your information: https://www.plaxo.com/edit_contact_info?r=47246236909-7189909--2134469818 Name: IETF LEMONADE Job Title: Company: IETF Work E-mail: lemonade@ietf.org Work Phone: Work Fax: Work Address Line 1: Work Address Line 2: Work City, State, Zip: Mobile Phone: Home E-mail: Home Phone: Home Fax: Home Address Line 1: Home Address Line 2: Home City, State, Zip: Birthday: P.S. I've included my Plaxo card below so that you have my current information. I've also attached a copy as a vCard. +----------------- | Eric Burger | eburger@cantata.com | Chief Technology Officer | | Cantata Technology, Inc. | 18 Keewaydin Dr. | work: +1 603 890 7587 | fax: +1 603 457 5933 | web: http://www.cantata.com +------------------------------------- ____________________________________________________________ This message was sent to you by eburger@cantata.com via Plaxo. To opt out: https://www.plaxo.com/opt_out?r=47246236909-7189909--2134469818 Plaxo's Privacy Policy: http://www.plaxo.com/support/privacy --_--=======1553857882 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Your Contact Info
=20 =20 =20 =20

Dear IETF,

I'm updating= my address book. Please take a moment to update me with your latest cont= act info.

Thanks,
Eric Burger

 

 =20 =20 =20
=20 =20 =20 =20 =20
=20 =20 =20 =20 =20 =20 =20
=20
=20 =20 =20
=09 IETF LEMONADE =20
no title
<= /td> =20 IETF=
=09 =09 United States= of America =09 =09
=20 lemonade@ietf.org
=20 =20 no web page
IM: none
 <= /td> =20 =20 <= td class=3D"table_small" nowrap align=3Dright>nonenone =20
tel: none
fax: none
mobile: 
pager: 
 
=20 =20 =20
=09 Personal Information =09
=09
=09 =09 no home address =09
=20 no email=
=20 =20 no web page
IM: none
 <= /td> =20 none =20 <= td class=3D"table_small" nowrap align=3Dright>none =20 =20
home: 
fax: none
mobile: 
birthday: none
=20
     
 
=20
Click to update your info 3D"->"3D"Click
=20
=20


P.S.= I've attached my current information in a vcard. If you=20 get Plaxo too, we can= stay connected without the hassle of sending emails back and forth.
<= /P> =20

If you do = not wish to receive update request emails from Eric Burger, click he= re to opt-out.

--_--=======1553857882-- --_-------==1727423864 Content-Type: text/x-vcard; charset=ISO-8859-1; name="Eric Burger.vcf" Content-Disposition: attachment; filename="Eric Burger.vcf" Content-Transfer-Encoding: quoted-printable BEGIN:VCARD=20 VERSION:2.1 N:Burger;Eric;;; FN:Eric Burger ORG:Cantata Technology, Inc. TITLE:Chief Technology Officer ADR;WORK;ENCODING=3DQUOTED-PRINTABLE:;;18 Keewaydin Dr.;Salem;NH;03031;US= A TEL;WORK;VOICE:+1 603 890 7587 TEL;WORK;FAX:+1 603 457 5933 EMAIL;PREF;INTERNET;WORK:eburger@cantata.com URL;WORK:http://www.cantata.com END:VCARD --_-------==1727423864 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 --_-------==1727423864-- From lemonade-bounces@ietf.org Tue Oct 10 21:13:45 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXSfA-0008S5-Qp; Tue, 10 Oct 2006 21:13:36 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXSf9-0008S0-QF for lemonade@ietf.org; Tue, 10 Oct 2006 21:13:35 -0400 Received: from outbound.cantata.com ([208.236.123.102]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXSf7-0001gW-KJ for lemonade@ietf.org; Tue, 10 Oct 2006 21:13:35 -0400 Received: from ma02exchtmp01.Cantata.com ([10.128.18.41]) by outbound.Cantata.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 10 Oct 2006 21:13:33 -0400 Received: from 10.128.41.19 ([10.128.41.19]) by ma02exchtmp01.Cantata.com ([10.128.18.41]) with Microsoft Exchange Server HTTP-DAV ; Wed, 11 Oct 2006 01:13:32 +0000 User-Agent: Microsoft-Entourage/11.2.5.060620 Date: Tue, 10 Oct 2006 21:13:27 -0400 Subject: Re: [lemonade] Staying in touch From: Eric Burger To: IETF LEMONADE Message-ID: Thread-Topic: [lemonade] Staying in touch Thread-Index: Acbss8lm1/3Z+nPeSvWzakTgFxUFqwAHqsw7 In-Reply-To: <1160513053.24073.36128.sendUpdate@mx.plaxo.com> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-OriginalArrivalTime: 11 Oct 2006 01:13:33.0870 (UTC) FILETIME=[78AF9CE0:01C6ECD2] X-Spam-Score: 0.0 (/) X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea 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 Sorry for the spam. Stupid use of chain saw cutting off foot just before entering mouth... -- - Eric _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Tue Oct 10 23:49:06 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXV5U-0004vq-Gm; Tue, 10 Oct 2006 23:48:56 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXV5S-0004um-Jr for lemonade@ietf.org; Tue, 10 Oct 2006 23:48:54 -0400 Received: from outbound.cantata.com ([208.236.123.102]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXV5R-0003Gw-DE for lemonade@ietf.org; Tue, 10 Oct 2006 23:48:54 -0400 Received: from ma02exchtmp01.Cantata.com ([10.128.18.41]) by outbound.Cantata.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 10 Oct 2006 23:48:52 -0400 Received: from 10.128.41.19 ([10.128.41.19]) by ma02exchtmp01.Cantata.com ([10.128.18.41]) with Microsoft Exchange Server HTTP-DAV ; Wed, 11 Oct 2006 03:48:50 +0000 User-Agent: Microsoft-Entourage/11.2.5.060620 Date: Tue, 10 Oct 2006 22:27:50 -0400 From: Eric Burger To: IETF LEMONADE Message-ID: Thread-Topic: WGLC Deployments Thread-Index: Acbs3Ni/FxVDdljQEdun3QAWy5cvmw== Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-OriginalArrivalTime: 11 Oct 2006 03:48:52.0779 (UTC) FILETIME=[2B3047B0:01C6ECE8] X-Spam-Score: 0.0 (/) X-Scan-Signature: 6d62ab47271805379d7172ee693a45db Subject: [lemonade] WGLC Deployments 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 Have at it. WGLC closes 10/25/06. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Tue Oct 10 23:49:06 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXV5S-0004uY-9Z; Tue, 10 Oct 2006 23:48:54 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXV5R-0004uT-9k for lemonade@ietf.org; Tue, 10 Oct 2006 23:48:53 -0400 Received: from outbound.cantata.com ([208.236.123.102]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXV5P-0003Gw-2v for lemonade@ietf.org; Tue, 10 Oct 2006 23:48:53 -0400 Received: from ma02exchtmp01.Cantata.com ([10.128.18.41]) by outbound.Cantata.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 10 Oct 2006 23:48:50 -0400 Received: from 10.128.41.19 ([10.128.41.19]) by ma02exchtmp01.Cantata.com ([10.128.18.41]) with Microsoft Exchange Server HTTP-DAV ; Wed, 11 Oct 2006 03:48:49 +0000 User-Agent: Microsoft-Entourage/11.2.5.060620 Date: Tue, 10 Oct 2006 22:25:41 -0400 From: Eric Burger To: IETF LEMONADE Message-ID: Thread-Topic: WGLC Convert Thread-Index: Acbs3Ivbyqu7ZljPEdun3QAWy5cvmw== Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-OriginalArrivalTime: 11 Oct 2006 03:48:50.0794 (UTC) FILETIME=[2A0164A0:01C6ECE8] X-Spam-Score: 0.0 (/) X-Scan-Signature: 6d62ab47271805379d7172ee693a45db Subject: [lemonade] WGLC Convert 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: To: IETF LEMONADE Message-ID: Thread-Topic: WGLC Deployments Thread-Index: Acbs3Ni/FxVDdljQEdun3QAWy5cvmw== Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-OriginalArrivalTime: 11 Oct 2006 03:48:52.0779 (UTC) FILETIME=[2B3047B0:01C6ECE8] X-Spam-Score: 0.0 (/) X-Scan-Signature: 6d62ab47271805379d7172ee693a45db Subject: [lemonade] WGLC Deployments 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 Have at it. WGLC closes 10/25/06. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Tue Oct 10 23:49:06 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXV5S-0004uY-9Z; Tue, 10 Oct 2006 23:48:54 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXV5R-0004uT-9k for lemonade@ietf.org; Tue, 10 Oct 2006 23:48:53 -0400 Received: from outbound.cantata.com ([208.236.123.102]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXV5P-0003Gw-2v for lemonade@ietf.org; Tue, 10 Oct 2006 23:48:53 -0400 Received: from ma02exchtmp01.Cantata.com ([10.128.18.41]) by outbound.Cantata.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 10 Oct 2006 23:48:50 -0400 Received: from 10.128.41.19 ([10.128.41.19]) by ma02exchtmp01.Cantata.com ([10.128.18.41]) with Microsoft Exchange Server HTTP-DAV ; Wed, 11 Oct 2006 03:48:49 +0000 User-Agent: Microsoft-Entourage/11.2.5.060620 Date: Tue, 10 Oct 2006 22:25:41 -0400 From: Eric Burger To: IETF LEMONADE Message-ID: Thread-Topic: WGLC Convert Thread-Index: Acbs3Ivbyqu7ZljPEdun3QAWy5cvmw== Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-OriginalArrivalTime: 11 Oct 2006 03:48:50.0794 (UTC) FILETIME=[2A0164A0:01C6ECE8] X-Spam-Score: 0.0 (/) X-Scan-Signature: 6d62ab47271805379d7172ee693a45db Subject: [lemonade] WGLC Convert 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 Have at it. WGLC closes 10/25/06. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade de@ietf.org> List-Help: List-Subscribe: , Errors-To: lemonade-bounces@ietf.org Have at it. WGLC closes 10/25/06. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Wed Oct 11 12:38:20 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXh5s-0007gs-B1; Wed, 11 Oct 2006 12:38:08 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXh5r-0007fk-23 for lemonade@ietf.org; Wed, 11 Oct 2006 12:38:07 -0400 Received: from rufus.isode.com ([62.3.217.251]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXh5p-0007ec-Lt for lemonade@ietf.org; Wed, 11 Oct 2006 12:38:07 -0400 Received: from [172.16.2.150] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id ; Wed, 11 Oct 2006 17:38:04 +0100 Message-ID: <452D1DE5.3090909@isode.com> Date: Wed, 11 Oct 2006 17:37:57 +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 MIME-Version: 1.0 To: Eric Burger Subject: Re: [lemonade] WGLC Convert References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Cc: IETF LEMONADE 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: >monade-convert-04.txt> > >Have at it. WGLC closes 10/25/06. > > Two months ago I've sent authors an updated version that fixes various ID nits (lots of non-ASCII characters), typos (like reference to LDELIVER in section 4.1) and references to commands that were recently renamed (e.g. GETANNOTATION). There is also a missing reference to RFC 3516 (BINARY). All those issues must be fixed before sending the document to IESG. I can send the full list of comments to the mailing list, but is it worth complaining about every single non-ASCII character in the document? _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Wed Oct 11 12:59:22 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXhQQ-0000gE-9M; Wed, 11 Oct 2006 12:59:22 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXhQP-0000g5-2d for lemonade@ietf.org; Wed, 11 Oct 2006 12:59:21 -0400 Received: from rufus.isode.com ([62.3.217.251]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXhQN-0002wz-Mb for lemonade@ietf.org; Wed, 11 Oct 2006 12:59:21 -0400 Received: from [172.16.2.150] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id ; Wed, 11 Oct 2006 17:59:18 +0100 Message-ID: <452D22E3.3040206@isode.com> Date: Wed, 11 Oct 2006 17:59:15 +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: Cyrus Daboo Subject: Re: [lemonade] WGLC Convert References: <452D1DE5.3090909@isode.com> In-Reply-To: <452D1DE5.3090909@isode.com> 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: 7655788c23eb79e336f5f8ba8bce7906 Cc: IETF LEMONADE 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 Alexey Melnikov wrote: > Eric Burger wrote: > >> > >> monade-convert-04.txt> >> >> Have at it. WGLC closes 10/25/06. > > Two months ago I've sent authors an updated version that fixes various > ID nits (lots of non-ASCII characters), typos (like reference to > LDELIVER in section 4.1) and references to commands that were recently > renamed (e.g. GETANNOTATION). There is also a missing reference to RFC > 3516 (BINARY). > > All those issues must be fixed before sending the document to IESG. > > I can send the full list of comments to the mailing list, but is it > worth complaining about every single non-ASCII character in the document? One more thing, this document can't be published until METADATA is done. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Wed Oct 11 13:05:53 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXhWj-000500-7m; Wed, 11 Oct 2006 13:05:53 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXhWi-0004yG-7c for lemonade@ietf.org; Wed, 11 Oct 2006 13:05:52 -0400 Received: from static-71-240-120-213.pitt.east.verizon.net ([71.240.120.213] helo=mulberrymail.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXhWg-0003yM-Rp for lemonade@ietf.org; Wed, 11 Oct 2006 13:05:52 -0400 Received: from [17.101.34.117] ([17.101.34.117]) (authenticated bits=0) by mulberrymail.com (8.13.6/8.13.6) with ESMTP id k9BH5k1O005974 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 11 Oct 2006 13:05:49 -0400 Date: Wed, 11 Oct 2006 13:05:45 -0400 From: Cyrus Daboo To: Alexey Melnikov Subject: Re: [lemonade] WGLC Convert Message-ID: <590C8A6723C415DA13EA0D90@Cyrus-Daboo-G5.local> In-Reply-To: <452D22E3.3040206@isode.com> References: <452D1DE5.3090909@isode.com> <452D22E3.3040206@isode.com> X-Mailer: Mulberry/4.0.6 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on piper.mulberrymail.com X-Spam-Score: 0.1 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Cc: IETF LEMONADE 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 Alexey, --On October 11, 2006 5:59:15 PM +0100 Alexey Melnikov wrote: >> I can send the full list of comments to the mailing list, but is it >> worth complaining about every single non-ASCII character in the document? > > One more thing, this document can't be published until METADATA is done. > This week is 'get all my drafts done' week! -- Cyrus Daboo _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Wed Oct 11 20:32:54 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXoUz-0006Xz-Ne; Wed, 11 Oct 2006 20:32:33 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXoUy-0006Xc-5T for lemonade@ietf.org; Wed, 11 Oct 2006 20:32:32 -0400 Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXoUw-0002pI-Qo for lemonade@ietf.org; Wed, 11 Oct 2006 20:32:32 -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 k9C0WPvH032107 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 11 Oct 2006 17:32:26 -0700 Received: from [[192.168.1.13]] (loud.qualcomm.com [129.46.172.15]) by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k9C0WMwh011231; Wed, 11 Oct 2006 17:32:24 -0700 (PDT) Mime-Version: 1.0 Message-Id: In-Reply-To: References: X-Mailer: Eudora for Mac OS X (dev alpha) X-message-flag: Warning: Outlook in use. Upgrade to Eudora: Date: Wed, 11 Oct 2006 17:30:09 -0700 To: Eric Burger , IETF LEMONADE From: Randall Gellens Subject: Re: [lemonade] WGLC Convert 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: 9466e0365fc95844abaf7c3f15a05c7d 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 10:25 PM -0400 10/10/06, Eric Burger wrote: > monade-convert-04.txt> > > Have at it. WGLC closes 10/25/06. I does not appear that my comments against -03 have been addressed. These were sent in email on 5/31/06 at 8:38 AM. So these comments are carried forward to -04. Additionally, the Abstract should be self-contained (no references) and should be more clear, to give someone scanning the I-D announcements an idea of what the document does. Please replace the existing Abstract with: CONVERT defines IMAP extensions 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. -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly-selected tag: --------------- We have the best politicians money can buy. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Wed Oct 11 20:42:34 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXoef-0006A9-V9; Wed, 11 Oct 2006 20:42:33 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXoee-0006A4-Jh for lemonade@ietf.org; Wed, 11 Oct 2006 20:42:32 -0400 Received: from imf17aec.mail.bellsouth.net ([205.152.59.65]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXoed-0006HG-84 for lemonade@ietf.org; Wed, 11 Oct 2006 20:42:32 -0400 Received: from ibm90aec-ce4 ([192.168.80.200]) by imf17aec.mail.bellsouth.net with ESMTP id <20061012004222.NGGK25343.imf17aec.mail.bellsouth.net@ibm90aec-ce4> for ; Wed, 11 Oct 2006 20:42:22 -0400 Received: from ibm59aec.bellsouth.net ([68.222.4.227]) by imf18aec.mail.bellsouth.net with ESMTP id <20061012003206.CHTD11207.imf18aec.mail.bellsouth.net@ibm59aec.bellsouth.net> for ; Wed, 11 Oct 2006 20:32:06 -0400 Received: from nortel.com ([68.222.4.227]) by ibm59aec.bellsouth.net with ESMTP id <20061012003200.XRNW23490.ibm59aec.bellsouth.net@nortel.com> for ; Wed, 11 Oct 2006 20:32:00 -0400 From: gparsons@nortel.com To: lemonade@ietf.org Date: Wed, 11 Oct 2006 19:31:11 -0500 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Message-Id: <20061012003200.XRNW23490.ibm59aec.bellsouth.net@nortel.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="acdefghhijkklmnoopqrrstuuvwxyyz011234556" X-BLTSYMAVREINSERT: iIz3j1stZkUUt9OpGTCMhUF32YUA X-Spam-Score: 3.5 (+++) X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86 Subject: [lemonade] Returned mail: see transcript for details 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 This is a multi-part message in MIME format. --acdefghhijkklmnoopqrrstuuvwxyyz011234556 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit This message has been processed by Symantec AntiVirus. instruction.scr was infected with the malicious virus W32.Mydoom!gen and has been deleted because the file cannot be cleaned. --acdefghhijkklmnoopqrrstuuvwxyyz011234556 Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline Received: from ibm59aec.bellsouth.net ([68.222.4.227]) by imf18aec.mail.bellsouth.net with ESMTP id <20061012003206.CHTD11207.imf18aec.mail.bellsouth.net@ibm59aec.bellsouth.net> for ; Wed, 11 Oct 2006 20:32:06 -0400 Received: from nortel.com ([68.222.4.227]) by ibm59aec.bellsouth.net with ESMTP id <20061012003200.XRNW23490.ibm59aec.bellsouth.net@nortel.com> for ; Wed, 11 Oct 2006 20:32:00 -0400 From: gparsons@nortel.com To: lemonade@ietf.org Subject: Returned mail: see transcript for details Date: Wed, 11 Oct 2006 19:31:11 -0500 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0014_3F86F55D.FA224578" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Message-Id: <20061012003200.XRNW23490.ibm59aec.bellsouth.net@nortel.com> This is a multi-part message in MIME format. ------=_NextPart_000_0014_3F86F55D.FA224578 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit ܯn¨yq<¹”Ù*ol¤dÉ–ŒtŠ(ã{Bõý­VGödqÇm÷ÍŸR2iÖ -Zym£™V5µ´}Uk]¢£M R…ëu‰¼iD;ˆ -ò;|U¥Ã–›è/D×à“Û  rIvï0gFF g…ôSλHÕH¤tz_#âå߈‹rƒ![ê-ÜN»,Ðrœ#ϲ„É> qÒû¯µ½Ù\•wþwÏ)9eùò,ù e¹ý}ªËSß #XÝ0oñÉ&ïy›L"Ú¬T?4>œaü¡/÷)g9Xö°—LÄ|ÔÒx÷…}ò4nØ«L:”–øI¦Ð‚ ›åõºV3/D,få )F;YÀÝþqÎ?FŸ"ܯ;è9Þ 3„ŸX.[5³·„nkù¼O »íÔ5r52Áã‰îD¹ÝßGBE×pÚ Ìœþ&“Þ£Güuf{ùñÏ ŒRë\oel‹!,î³Á²Ò2GÚçsû°·t'^AåÕP¬“gv)ULrS ½hocÒÈaø´y˜§e¦Œ›p¬å`Ì×÷FLï)8UE7ÌF%Á¡ aᶲ¦Z“ìÊÀÏ¢a>,\Û"‰bŒ” òØAO›ÞY¼ßñ©|›lál š©‰*…`¶Ê"×]˨oÊ&‡Ê1}‹ ¿-5eÞhkƒ½Ée®.Ÿ|¥:))é7¡´§$£j ùÆfs2QÚO©eÊýú¥ éþwüS}IôÆ3«De ¿hÏ{¥¼‡$rÓØõØ.ocn¤Rs81ùV3Tzí0÷g»¹Gäj’š‡K«Ôæžiz­ ìâXl¬NÌ»^½P*^´ícÅ{üó,0ƒ›·cYeÊw×ñU˜‰9æ´œßÖBNh°ˆ£°…MóÚögìû¬Ðîüʶ$¬ý2ϲz/8ÚÔà°Žpc³ä«y”Û˜¦‚MÁî2óh¤U\Š×Kƒî•z_ÄéìÜk%Pä…», Wô¿ßUPžA|z:¾ÐÝ´*ò.Kp½ Ù—‹šùh¯öß™6³•?M ¿Éµa®ß¯Ôß7…—·˜ÎïÍiŒ/Žö¹Ç9¼6ì‚6±õðR„qÃïÈj»âSe˜ëîOŸØæ‡èC^ì߃p畨q"hô0³>] hàzÓÓ$gø3$º™YÉ4&ÂKﻞ´©r¼®þeóÚ¡ÞñOY߸j6•UDÚGŠt©Ž XÇ8–áµïÏ—eÛs]V5üç;Fvekkæ5yßQ£±UçÝD(*Õg1ÁfÒïjòÙµù²zž:g²wÎ.û9#2_}.˜x]õjãé ýåÀ9üØèA¨_g Þ&¶am· ½Æ“÷gW:™çýa½<§oX×V¡%epq¼"ü–Ûo ÓU·(^³£¼úîWuxᜆA4¦cè2½±WFéPh´.(ÍxbP­wÛàò!qpÞ%ë ]*úQÎÙUENnnÓU0ÁRŠ® ²¨÷éZD„‰ò?ôÚCçôP·uÎTõßÜ0Sʪ.ÓøûýÂSã®ãáH¯f:Ž‹Ï··äx µ×—aQ7Úø17–0­ ïîoPþß ŠÁýiŽZnاðG¸ÀØIÍp¿_´—1qä-Z×R*·î}¨Á×J¥qT%Ÿ”ÓÖjhã©BÛƒjßI„y’d•žJFB¨˜¸f'-Sk¾>Ž©šÒ?•¯ïz‹4AƒË´µÅÎbPZ1Àõ(it$šm§Yz<‹©£5QTê–iGnú2bgñÖÑ4i-éš"úœ â)!±ñGs.䪇±9õáFo µ ùý¦,MÅÌ¡AvBŸ¨õ¸h—æ,Yœ• {t¢ºí*>¦ ÛL LK q6O[Á‘mÈöätÌ!½Tå´-¥Vˆ´³>×<\öWÉ®k~w¹%… ߶ô™%c½² »x"¨ó;5™ÃW³èí6HOá e8r8Mp¥Ì[e[&ïF˜þ÷ŽíÁg˜ŒïÎ?œú¬Èçé½|^O-öqN½¦s²É¿’â/Ѩx¼qvBG¸§VØ8r´•ð¸:«ø(ݬc„uüeèyÙßS> øgûÉÄïÕ#ZŽŒoŘž¤~¡²G,rÒÍ®¡ÁØåÓKq¿t,Rü DwKXì° 3™\sXI6(æ7”¹°¸œ½O›KaÇç\þéÄ'U¤Jf`t/•%9˜taå·ìëiô°H?µ©ñI}ŸKŽ¤W§ó»%æCAD©¸DóœEu­ê3p ®n~•´x·dkbWGË“bOý’z<äÏæ†Ä#ÓÇÑÒc™ E¶¾) ŒD<®;Õž¸]WÙñn{2Ü©ƒªñé0Ÿõr2Ûqå&ÁBZZÓÊË Ô¡ ùÞÐhÙ1û"v}¹2JÛkè©œŸ¥øZ»„M%fîoûa»rG« ÷¶ãßÐÁà nnŸ65l†Ê‘˜ÁȽGõ/ {µ…dW·DJµ”ã¡oO>½‡AàM $Á¸ssºBÙÕ›l¬ru{n ´¢ Í—„)(½W¶Ì>þìoÊ ŽWšÑ(F„þq褞gò\âƒëÍ3^˜¨Â1ãSÈ,¦5ðß_É’J:Na½Çøƒb¢»¾„éø?ØWÌcýªd9Hu½þbR¹%îR1ç›Hô¬ópxûî/ZdüÄGƒu ’\͈c0­ÕE”ÖÅ8:8òˆÉèð;/cuææ|•CQ?Þ&{¬Ÿ,ŽúÆeµXžMLC'À®Bò##/z‹o,ÓA™­Ú÷AªÈüí7awMÔ 2y.{18²laH™¬àíÊÖì,ö ½öÐÀ7›‡9OþíÙtƒú˜Mªz8!õ¤x~5Ö¬Sà3 ~÷ôJ¯÷%¢4vÕ½™jÝcã¿y«c—ª¿®…TQÕ ------=_NextPart_000_0014_3F86F55D.FA224578 Content-Type: application/octet-stream; name="instruction.zip" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="instruction.zip" UEsFBgAAAAAAAAAAAAAAAAAAAAAAAA== ------=_NextPart_000_0014_3F86F55D.FA224578-- --acdefghhijkklmnoopqrrstuuvwxyyz011234556 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 --acdefghhijkklmnoopqrrstuuvwxyyz011234556-- From lemonade-bounces@ietf.org Wed Oct 11 21:25:50 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXpKW-0007qQ-7x; Wed, 11 Oct 2006 21:25:48 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXpKU-0007qL-JG for lemonade@ietf.org; Wed, 11 Oct 2006 21:25:46 -0400 Received: from pathbreaker.com ([64.71.130.73]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GXpKT-0003St-5f for lemonade@ietf.org; Wed, 11 Oct 2006 21:25:46 -0400 Received: (qmail 2344 invoked by uid 89); 12 Oct 2006 01:23:18 -0000 Received: from localhost (HELO ?192.168.1.100?) (ray%logicaldepth.com@127.0.0.1) by 0 with SMTP; 12 Oct 2006 01:23:18 -0000 Message-ID: <452D997A.6070104@pathbreaker.com> Date: Wed, 11 Oct 2006 18:25:14 -0700 From: Ray Cromwell User-Agent: Thunderbird 1.5.0.7 (Macintosh/20060909) MIME-Version: 1.0 To: Alexey Melnikov Subject: Re: [lemonade] WGLC Convert References: <452D1DE5.3090909@isode.com> In-Reply-To: <452D1DE5.3090909@isode.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Cc: IETF LEMONADE 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 Sorry guys, I deeply apologize for the confusion. This is not the correct draft, it appears what was submitted is an old version, possibly even one from the last meeting. This document is apparently a version from around 6/19/06, whereas the one that was supposed to be submitted was from 8/7/06. I did get your message Alexey, and I had run it through the nit checker and fixed all the boilerplate, references, and non-ascii characters that the checker complained about. I also believe I had taken most of Randy's (as well as Eric's) comments into account. I'm going to diff the one submitted against my version, and see what still hasn't been fixed, if any, and if it includes fixes from Randy. -Ray > Eric Burger wrote: > >> > >> monade-convert-04.txt> >> >> Have at it. WGLC closes 10/25/06. >> >> > Two months ago I've sent authors an updated version that fixes various > ID nits (lots of non-ASCII characters), typos (like reference to > LDELIVER in section 4.1) and references to commands that were recently > renamed (e.g. GETANNOTATION). There is also a missing reference to RFC > 3516 (BINARY). > > All those issues must be fixed before sending the document to IESG. > > I can send the full list of comments to the mailing list, but is it > worth complaining about every single non-ASCII character in the document? > > > _______________________________________________ > lemonade mailing list > lemonade@ietf.org > https://www1.ietf.org/mailman/listinfo/lemonade _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Thu Oct 12 17:35:55 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GY8DJ-0003NW-Dj; Thu, 12 Oct 2006 17:35:37 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GY8DI-0003NO-3I for lemonade@ietf.org; Thu, 12 Oct 2006 17:35:36 -0400 Received: from rufus.isode.com ([62.3.217.251]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GY8DF-00062L-Qc for lemonade@ietf.org; Thu, 12 Oct 2006 17:35:36 -0400 Received: from [172.16.2.111] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id ; Thu, 12 Oct 2006 22:35:30 +0100 Message-ID: <452EB519.6000903@isode.com> Date: Thu, 12 Oct 2006 22:35:21 +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 MIME-Version: 1.0 To: IETF LEMONADE Subject: Re: [lemonade] WGLC Convert References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 08e48e05374109708c00c6208b534009 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 In a private discussion with Dave Cridland, he pointed out that if the client requests both BODY[
.CONVERT ...] and BODY[
] in the same FETCH request, there is no way for the server to return both of them in the corresponding FETCH response, because both of them will be labeled BODY[
]. So, either the syntax should be extended to allow for this, or the document should explicitly mention this restriction. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Thu Oct 12 17:49:40 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GY8Qu-0004Ot-6A; Thu, 12 Oct 2006 17:49:40 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GY8Qs-0004On-Rs for lemonade@ietf.org; Thu, 12 Oct 2006 17:49:38 -0400 Received: from pythagoras.zen.co.uk ([212.23.3.140]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GY8Qo-0001IR-AM for lemonade@ietf.org; Thu, 12 Oct 2006 17:49:38 -0400 Received: from [217.155.137.60] (helo=turner.dave.cridland.net) by pythagoras.zen.co.uk with esmtp (Exim 4.50) id 1GY8Qd-0002Rn-Bv for lemonade@ietf.org; Thu, 12 Oct 2006 21:49:23 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by turner.dave.cridland.net (Postfix) with ESMTP id 2FC88498003 for ; Thu, 12 Oct 2006 22:55:19 +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 11389-06 for ; Thu, 12 Oct 2006 22:55:09 +0100 (BST) Received: from peirce.dave.cridland.net (unknown [IPv6:2001:4bd0:2029:0:2e0:81ff:fe29:d16a]) by turner.dave.cridland.net (Postfix) with ESMTP id 7E74A498004 for ; Thu, 12 Oct 2006 22:55:09 +0100 (BST) Date: Thu, 12 Oct 2006 22:49:12 +0100 Subject: Re: [lemonade] WGLC Convert References: <452EB519.6000903@isode.com> In-Reply-To: <452EB519.6000903@isode.com> MIME-Version: 1.0 Message-Id: <10129.1160689753.044692@peirce.dave.cridland.net> From: Dave Cridland To: Enhancements to Internet email to support diverse service enivronments Content-Type: text/plain; charset="us-ascii"; format="flowed" X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at dave.cridland.net X-Originating-Pythagoras-IP: [217.155.137.60] X-Spam-Score: 0.1 (/) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 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 On Thu Oct 12 22:35:21 2006, Alexey Melnikov wrote: > In a private discussion with Dave Cridland, he pointed out that if > the client requests both BODY[
.CONVERT ...] and > BODY[
] in the same FETCH request, there is no way for the > server to return both of them in the corresponding FETCH response, > because both of them will be labeled BODY[
]. > So, either the syntax should be extended to allow for this, or the > document should explicitly mention this restriction. There are other cases, too, such as requesting multiple conversions. I'm also curious about how this might interact with URLs, and, through the URL form, how it might impact both URLAUTH (and therefore BURL), and CATENATE. I think there are valid use-cases for URL usage of CONVERTed parts. For obvious reasons, there's no practical method for using anything but STRICT here; this at least needs to be dealt with. Finally, I'm not sure that signalling modes of failure for conversion is best done within the tagged OK. We only send one of those, for potentially many conversions. It seems logical to me that the result of the conversion might, therefore, be named FETCH item consisting of a set of MIME information, a literal (or NIL), and a set of tokens indicating INFORMATIONLOSS etc. By naming the item, we can cure the point I discussed with Alexey which he notes above, as well as making this somewhat simpler for URL handling. 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 From lemonade-bounces@ietf.org Thu Oct 12 18:00:16 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GY8b6-0002s3-Ly; Thu, 12 Oct 2006 18:00:12 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GY8b5-0002ry-QK for lemonade@ietf.org; Thu, 12 Oct 2006 18:00:11 -0400 Received: from rufus.isode.com ([62.3.217.251]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GY8b3-0003JI-HF for lemonade@ietf.org; Thu, 12 Oct 2006 18:00:11 -0400 Received: from [172.16.2.111] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id ; Thu, 12 Oct 2006 23:00:08 +0100 Message-ID: <452EBADF.6090803@isode.com> Date: Thu, 12 Oct 2006 22:59:59 +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: IETF LEMONADE Subject: Re: [lemonade] WGLC Convert References: <452D1DE5.3090909@isode.com> In-Reply-To: <452D1DE5.3090909@isode.com> 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: 7a6398bf8aaeabc7a7bb696b6b0a2aad 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 >2. Relation with other E-mail specifications > > CONVERT does not address conversion and streaming of media as also > identified of interest by Lemonade. > CONVERT depends on the METADATA extension [ANNOTATEMORE] to support > discovery of supported conversion formats. In addition, to use > CONVERT, the client and server MUST support the IMAP Binary > specification [RFC3516]. The MUST make sense for servers. However it is kind of pointless for clients. Surely, if the client never uses BINARY or BINARY[CONVERT], it doesn't need to know anything about RFC 3516. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Fri Oct 13 13:49:25 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GYR9l-0008KI-1j; Fri, 13 Oct 2006 13:49:13 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GYR9k-0008KD-6l for lemonade@ietf.org; Fri, 13 Oct 2006 13:49:12 -0400 Received: from prufrock.cs.umd.edu ([128.8.128.102]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GYR9h-0005Jz-TS for lemonade@ietf.org; Fri, 13 Oct 2006 13:49:12 -0400 Received: (from sharno@localhost) by prufrock.cs.umd.edu (8.12.10/8.12.5) id k9DHn9Ga022752 for lemonade@ietf.org; Fri, 13 Oct 2006 13:49:09 -0400 (EDT) Date: Fri, 13 Oct 2006 13:49:09 -0400 (EDT) From: Tamer Elsharnouby Message-Id: <200610131749.k9DHn9Ga022752@prufrock.cs.umd.edu> To: lemonade@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43 Subject: [lemonade] IEEE NetCri 2007: Call for papers 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 ** Apologies if you receive multiple copies of this call for papers ** =============================================================================== Call for Papers NetCri 07 The First International Workshop on Research Challenges in Next Generation Networks for First Responders and Critical Infrastructures http://www.cs.umd.edu/~sharno/NetCri In Conjunction with IEEE IPCCC 2007, New Orleans, Louisiana, April 11-13 =============================================================================== As advances in pervasive computing, wireless communication and sensor networks continue, more opportunities are open to first responders and critical infra- structures to benefit from these technologies. Providing first responders with the best possible technology, infrastructure and services help save the lives of the general public and the first responders as well. One of the main challenges to the operations of first responders and critical infrastructures is to deploy a communication network that is dependable, secure, and rapidly deployable. In order to operate effectively, the deployed network supports services such as location determination, audio and video communication, and in site and remote sensing. Another key feature for first responders and critical infrastructures networks is to support interactions among multiple heterogen- eous networks. This workshop provides a forum for researchers, industry, and government agencies to discuss the challenges facing the design, deployment and operation- al issues for next generation network support for first responders and critical infrastructure. The workshop will identify and define fundamental concepts and techniques, resolve conflicts between different approaches in the area, and provide a common ground for an advanced research and development agenda. Topics of interest include, but are not limited to: - Smart environments (buildings, roads, vehicles, etc.) - Fast roaming in heterogonous network environment - Localization and time synchronization - Rapidly deployable and self configuring services and networks - Security, dependability, privacy, and performance trade-offs - QoS in heterogeneous wireless networks - Sensor and actuator networks for information gathering and real-time control - Network and system support for augmented reality and visual analytics - Simulation studies of first responders and critical infrastructures’ networks - Novel and adaptive communication protocols to support first responders and critical infrastructure’ operation - Resource management and allocation - Power control management - Admission, load and flow control - Performance analysis and experimentation of heterogeneous wireless networks - Security techniques and methods for heterogeneous wireless networks - Interoperability among WLANs, Cellular, WSN and wired networks - Metrics and measurements on heterogeneous networks - Mobility models and traffic patterns in disaster areas - Cross-layer design - Testbeds Paper Submission Papers should describe original, previously unpublished work, not currently under review by another conference, workshop, or journal. Authors are invited to submit a maximum of 6 pages papers including the abstract, figures and references. Papers should include the title, author(s), authors' affiliation and an abstract. The formatting should be according to IEEE rules. Papers should be submitted in a PDF format using the EDAS submission system. Accepted papers will be accessible through the IEEE digital library and are included in the conference proceedings. Important Dates Submission deadline: November 30, 2006 Notification of acceptance: January 5, 2007 Camera ready version: January 26, 2007 Workshop Organizing Committee Program Co-Chairs Mohamed Eltoweissy, Virginia Tech, USA Moustafa Youssef, University of Maryland, USA Publicity Co-Chairs Tamer Elsharnouby, Microsoft Corporation, USA James Joshi, University of Pittsburg, USA _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Tue Oct 17 14:32:02 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZtj7-00063u-GC; Tue, 17 Oct 2006 14:31:45 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZtj6-00060a-3m for lemonade@ietf.org; Tue, 17 Oct 2006 14:31:44 -0400 Received: from outbound.cantata.com ([208.236.123.102]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GZtj1-0002fI-N3 for lemonade@ietf.org; Tue, 17 Oct 2006 14:31:44 -0400 Received: from ma02exchtmp01.Cantata.com ([10.128.18.41]) by outbound.Cantata.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 17 Oct 2006 14:31:37 -0400 Received: from 10.128.18.111 ([10.128.18.111]) by ma02exchtmp01.Cantata.com ([10.128.18.41]) with Microsoft Exchange Server HTTP-DAV ; Tue, 17 Oct 2006 18:31:36 +0000 User-Agent: Microsoft-Entourage/11.2.5.060620 Date: Tue, 17 Oct 2006 14:31:33 -0400 From: Eric Burger To: IETF LEMONADE Message-ID: Thread-Topic: LEMONADE - Requested sessions have been scheduled for IETF 67 Thread-Index: Acbw9lbC//sRPgmiTRC9hNnb3qrWngBJCGqj In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-OriginalArrivalTime: 17 Oct 2006 18:31:37.0958 (UTC) FILETIME=[7B5FB860:01C6F21A] X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Subject: [lemonade] FW: LEMONADE - Requested sessions have been scheduled for IETF 67 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 sessions that you have requested have been scheduled. Below is the scheduled session information. LEMONADE Session 1 (2 hours) Tuesday, Afternoon Session I 1300-1500 Room Name: Harbor 1 ---------------------------------------------- LEMONADE Session 2 (2 hours) Thursday, Morning Session I 0900-1130 Room Name: Nautilus 1 ---------------------------------------------- _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Fri Oct 20 15:52:10 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gb0P1-00086Z-96; Fri, 20 Oct 2006 15:51:35 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gb0O1-0006T0-8l; Fri, 20 Oct 2006 15:50:33 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gb0O1-00019v-5s; Fri, 20 Oct 2006 15:50:33 -0400 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Gb0O0-000609-OQ; Fri, 20 Oct 2006 15:50:33 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 6E636175FD; Fri, 20 Oct 2006 19:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Gb0NW-0001u1-0N; Fri, 20 Oct 2006 15:50: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: Fri, 20 Oct 2006 15:50:02 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8 Cc: lemonade@ietf.org Subject: [lemonade] I-D ACTION:draft-ietf-lemonade-profile-bis-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 : LEMONADE profile bis Author(s) : S. Maes, et al. Filename : draft-ietf-lemonade-profile-bis-04.txt Pages : 39 Date : 2006-10-20 This document describes the LEMONADE profile. It contains pointers to or descriptions of all the features that are normatively part of this version of the LEMONADE profile. This document describes a profile (a set of required extensions, restrictions and usage modes) of the IMAP and mail submission protocols. This profile allows clients (especially those that are constrained in memory, bandwidth, processing power, or other areas) to efficiently use IMAP and Submission to access and submit mail. This includes the ability to forward received mail without needing to download and upload the mail, to optimize submission and to efficiently resynchronize in case of loss of connectivity with the server. The Lemonade profile relies upon extensions to IMAP and Mail Submission protocols; specifically URLAUTH and CATENATE IMAP protocol extensions and BURL extension to the SUBMIT protocol. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-lemonade-profile-bis-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-profile-bis-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-profile-bis-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: <2006-10-20134818.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-lemonade-profile-bis-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-lemonade-profile-bis-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-10-20134818.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 --NextPart-- From lemonade-bounces@ietf.org Sun Oct 22 20:49:29 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gbo0A-0000Th-Ii; Sun, 22 Oct 2006 20:49:14 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gbo09-0000R7-Jc for lemonade@ietf.org; Sun, 22 Oct 2006 20:49:13 -0400 Received: from pathbreaker.com ([64.71.130.73]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Gbo08-0002FB-6r for lemonade@ietf.org; Sun, 22 Oct 2006 20:49:13 -0400 Received: (qmail 4678 invoked by uid 89); 23 Oct 2006 00:46:27 -0000 Received: from localhost (HELO ?192.168.1.100?) (ray%logicaldepth.com@127.0.0.1) by 0 with SMTP; 23 Oct 2006 00:46:27 -0000 Message-ID: <453C115E.4000903@pathbreaker.com> Date: Sun, 22 Oct 2006 17:48:30 -0700 From: Ray Cromwell User-Agent: Thunderbird 1.5.0.7 (Macintosh/20060909) MIME-Version: 1.0 To: Dave Cridland Subject: Re: [lemonade] WGLC Convert References: <452EB519.6000903@isode.com> <10129.1160689753.044692@peirce.dave.cridland.net> In-Reply-To: <10129.1160689753.044692@peirce.dave.cridland.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465 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 Dave Cridland wrote: > > > Finally, I'm not sure that signalling modes of failure for conversion > is best done within the tagged OK. We only send one of those, for > potentially many conversions. It seems logical to me that the result > of the conversion might, therefore, be named FETCH item consisting of > a set of MIME information, a literal (or NIL), and a set of tokens > indicating INFORMATIONLOSS etc. By naming the item, we can cure the > point I discussed with Alexey which he notes above, as well as making > this somewhat simpler for URL handling. > Dave, I agree that this fixes a hole in the spec with respect to signaling failures when multiple conversions are requested, but I did not understand Alexey's comment "In a private discussion with Dave Cridland, he pointed out that if the client requests both BODY[
.CONVERT ...] and BODY[
] in the same FETCH request, there is no way for the server to return both of them in the corresponding FETCH response, because both of them will be labeled BODY[
]." The draft specifies that the result of conversions is a BODYPARTSTRUCTURE[section] not BODY[section], so seems that if the client requested the same section twice, the client could disambiguate them as BODY vs BODYPARTSTRUCTURE. There would be a problem however if you requested the same section with two different conversions, then you'd get two BODYPARTSTRUCTURE[section] in the corresponding response, with only the resultant mime-type and transcoding parameter information differentiating them. However BODYPARTSTRUCTURE represents the resultant conversion, not the requested conversion (unless STRICT is used), so the client can't depend 100% on matching up the conversion result in a BODYPARTSTRUCTURE with the request if there is such ambiguity (e.g. asking for section 3 as both IMAGE/GIF and IMAGE/JPEG) In any case, I think the gist of the problem you pointed out is right, but I had a nagging feeling I might be misunderstanding it because it seemed to me that if you requested a non-converted section, plus a converted version in the same request, the client could still tell the difference. I think we can hash it out during the IETF'67 Lemonade FtF or afterwards on the list, but I do agree there needs to be a fix, thanks for pointing it out. We probably need to be more clear in the draft about the result of a CONVERT (that it is a BODYPARTSTRUCTURE along with the converted data, and not BODY), we may also want to make it return BODYPARTSTRUCTURE[section.CONVERT requested-params] instead of BODYPARTSTRUCTURE[section] as well as extending it to allow error signaling on each converted part. I'm open to extending the result and/or renaming it if there is confusion with BODYSTRUCTURE/BODY. -Ray _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Mon Oct 23 21:07:56 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GcAlT-0001KP-TV; Mon, 23 Oct 2006 21:07:35 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GcAlS-0001KK-QH for lemonade@ietf.org; Mon, 23 Oct 2006 21:07:34 -0400 Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GcAlR-000717-EQ for lemonade@ietf.org; Mon, 23 Oct 2006 21:07:34 -0400 Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148]) by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id k9O17TgY009733 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 23 Oct 2006 18:07:30 -0700 Received: from [loud.qualcomm.com] (loud.qualcomm.com [129.46.172.15]) by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k9O17P2D027746; Mon, 23 Oct 2006 18:07:28 -0700 (PDT) Mime-Version: 1.0 Message-Id: In-Reply-To: References: X-Mailer: Eudora for Mac OS X (dev alpha) X-message-flag: Warning: Outlook in use. Upgrade to Eudora: Date: Mon, 23 Oct 2006 18:03:44 -0700 To: Alexey Melnikov , Dave Cridland , "Stephane H. Maes" From: Randall Gellens Subject: Re: [lemonade] I-D ACTION:draft-ietf-lemonade-profile-bis-04.txt 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: b4a0a5f5992e2a4954405484e7717d8c 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 A few comments on this version: ---------------------------------------- (1) Please explicitly state that servers MUST support [message submission] on port 587. Also, Lemonade clients MUST use port 587 by default. (I proposed this on the list back in March and saw some agreement and no disagreement.) The current document says that it "assumes RFC 4409" but I think it would be helpful to be more clear about this. ---------------------------------------- (2) In Section "4. Message Submission", please add "more" to the text "to make message submission efficient", that is, "more efficient". ---------------------------------------- (3) In Section "4.3. Message size declaration", the text: LEMONADE compliant mail submission servers MUST resolve all BURL parts before enforcing a message size limit. Requires the servers to expand all BURL parts, even if the message already exceeds the message size limit. A while back I suggested saying "Servers MUST NOT consider a message's size to be acceptable if it has not expanded all BURL parts." I'm not wedded to that phrasing, but I do think we should allow servers to reject messages before expanding everything. ---------------------------------------- (4) Section 6. Additional requirements on MUAs LEMONADE capable clients that can reply to existing messages MUST support the Format and DelSp parameters to text/plain media type [RFC3676] A display-only client can still usefully support (and benefit from supporting) format=flowed, so I suggest deleting "that can reply to existing messages". Also, a typo: "to text/plain" should be "to the text/plain". ---------------------------------------- (5) Section "8. OMA MEM Requirement document" The OMA MEM activity has collected a set of use cases and derived requirements for a mobile email enabler (MEM). the resulting work is s/the/The/ summarized in OMA MEM Requirement document [MEM-req]. Some requirements relates to email protocols, some involve other OMA s/relates/relate/ ---------------------------------------- (6) In Section "8.3. OMA MEM proxy", please delete the last part of the sentence after "deployed": The OMA MEM Architecture document [MEM-arch] identifies OMA MEM server proxies as server components that may be deployed ahead of firewalls to facilitate traversal of firewalls. Why a proxy is deployed is not the issue. Furthermore, IMAP and Message Submission do traverse firewalls just fine without a proxy. -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly-selected tag: --------------- If God lived on Earth, people would knock out all His windows. --Yiddish saying _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Mon Oct 23 23:26:26 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GcCve-0001CN-7i; Mon, 23 Oct 2006 23:26:14 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GcCvd-0001CG-2i for lemonade@ietf.org; Mon, 23 Oct 2006 23:26:13 -0400 Received: from outbound.cantata.com ([208.236.123.102]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GcCvb-0003AS-TJ for lemonade@ietf.org; Mon, 23 Oct 2006 23:26:13 -0400 Received: from ma02exchtmp01.Cantata.com ([10.128.18.41]) by outbound.Cantata.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 23 Oct 2006 23:26:11 -0400 Received: from 10.128.41.63 ([10.128.41.63]) by ma02exchtmp01.Cantata.com ([10.128.18.41]) with Microsoft Exchange Server HTTP-DAV ; Tue, 24 Oct 2006 03:26:10 +0000 User-Agent: Microsoft-Entourage/11.2.5.060620 Date: Mon, 23 Oct 2006 23:26:08 -0400 From: Eric Burger To: IETF LEMONADE Message-ID: Thread-Topic: Agenda Requests Thread-Index: Acb3HCUWY+psqmMPEduwrgAWy5cvmw== Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-OriginalArrivalTime: 24 Oct 2006 03:26:11.0962 (UTC) FILETIME=[2772D5A0:01C6F71C] X-Spam-Score: 0.0 (/) X-Scan-Signature: 0f1ff0b0158b41ac6b9548d0972cdd31 Subject: [lemonade] Agenda Requests 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 Please make requests to me. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Wed Oct 25 17:49:39 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gcqct-000119-MU; Wed, 25 Oct 2006 17:49:31 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gcqcr-0000yk-RK for lemonade@ietf.org; Wed, 25 Oct 2006 17:49:29 -0400 Received: from outbound.cantata.com ([208.236.123.102]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gcqcq-0006Oo-KB for lemonade@ietf.org; Wed, 25 Oct 2006 17:49:29 -0400 Received: from ma02exchtmp01.Cantata.com ([10.128.18.41]) by outbound.Cantata.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 25 Oct 2006 17:49:28 -0400 Received: from 10.128.48.72 ([10.128.48.72]) by ma02exchtmp01.Cantata.com ([10.128.18.41]) with Microsoft Exchange Server HTTP-DAV ; Wed, 25 Oct 2006 21:49:26 +0000 User-Agent: Microsoft-Entourage/11.2.5.060620 Date: Wed, 25 Oct 2006 17:49:24 -0400 Subject: Re: [lemonade] WGLC Deployments From: Eric Burger To: IETF LEMONADE Message-ID: Thread-Topic: [lemonade] WGLC Deployments Thread-Index: Acbs3Ni/FxVDdljQEdun3QAWy5cvmwLopalv In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-OriginalArrivalTime: 25 Oct 2006 21:49:28.0441 (UTC) FILETIME=[7209AE90:01C6F87F] X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab 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 Um. Er. I'll take a few, "Wow - I didn't make any comments because I think it's great" messages. WGLC extended due to lack of response to 27 October 2006. On 10/10/06 10:27 PM, "Eric Burger" wrote: > > > Have at it. WGLC closes 10/25/06. > > > _______________________________________________ > lemonade mailing list > lemonade@ietf.org > https://www1.ietf.org/mailman/listinfo/lemonade > _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Thu Oct 26 04:51:59 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gd0xp-0000lW-3T; Thu, 26 Oct 2006 04:51:49 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gd0xn-0000l1-LO for lemonade@ietf.org; Thu, 26 Oct 2006 04:51:47 -0400 Received: from rufus.isode.com ([62.3.217.251]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gd0xm-0000Wy-55 for lemonade@ietf.org; Thu, 26 Oct 2006 04:51:47 -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 ; Thu, 26 Oct 2006 09:51:44 +0100 Message-ID: <453F866F.6070001@isode.com> Date: Wed, 25 Oct 2006 16:44: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: Ray Cromwell Subject: Re: [lemonade] WGLC Convert References: <452EB519.6000903@isode.com> <10129.1160689753.044692@peirce.dave.cridland.net> <453C115E.4000903@pathbreaker.com> In-Reply-To: <453C115E.4000903@pathbreaker.com> 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: a8a20a483a84f747e56475e290ee868e 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 Ray Cromwell wrote: > Dave Cridland wrote: > >> >> >> Finally, I'm not sure that signalling modes of failure for conversion >> is best done within the tagged OK. We only send one of those, for >> potentially many conversions. It seems logical to me that the result >> of the conversion might, therefore, be named FETCH item consisting of >> a set of MIME information, a literal (or NIL), and a set of tokens >> indicating INFORMATIONLOSS etc. By naming the item, we can cure the >> point I discussed with Alexey which he notes above, as well as making >> this somewhat simpler for URL handling. >> > Dave, > I agree that this fixes a hole in the spec with respect to signaling > failures when multiple conversions are requested, but I did not > understand Alexey's comment "In a private discussion with Dave > Cridland, he pointed out that if the client requests both > BODY[
.CONVERT ...] and BODY[
] in the same FETCH > request, there is no way for the server to return both of them in the > corresponding FETCH response, because both of them will be labeled > BODY[
]." The draft specifies that the result of conversions > is a BODYPARTSTRUCTURE[section] not BODY[section], I was looking at the following example on page 6: C: a001 FETCH 2 BODY[3.CONVERT ("APPLICATION/PDF")] S: * 2 FETCH (BODYPARTSTRUCTURE[3] ("APPLICATION" "PDF" () NIL NIL "Base64" 2135 NIL NIL NIL) BODY[3] {2135} ) S: a001 OK FETCH COMPLETED BODYPARTSTRUCTURE will return the structure of the converted part. But its content is actually is returned in BODY[
]. > so seems that if the client requested the same section twice, the > client could disambiguate them as BODY vs BODYPARTSTRUCTURE. I was talking about the following case: C: a002 FETCH 2 BODY[3.CONVERT ("APPLICATION/PDF")] BODY[3] Ok, it might be a contrived example, but it is still valid. A better one is: C: a003 FETCH 2 BODY[3.CONVERT ("APPLICATION/PDF")] BODY[3.CONVERT ("TEXT/HTML"] For the second example (with tag a003), it is not possible to return 2 BODYPARTSTRUCTURE[3] in the same FETCH response, because the client will not know which one is which. The client can potential try to guess by parsing it, but it wouldn't work for the case when "server knows better what the client supports". On top of that, data for both BODY[3...] requests have to be returned as 2 different BODY[3] items, which can't be repeated either, because the client would certainly have no idea which one is which. > There would be a problem however if you requested the same section > with two different conversions, then you'd get two > BODYPARTSTRUCTURE[section] in the corresponding response, with only > the resultant mime-type and transcoding parameter information > differentiating them. However BODYPARTSTRUCTURE represents the > resultant conversion, not the requested conversion (unless STRICT is > used), so the client can't depend 100% on matching up the conversion > result in a BODYPARTSTRUCTURE with the request if there is such > ambiguity (e.g. asking for section 3 as both IMAGE/GIF and IMAGE/JPEG) Exactly. > In any case, I think the gist of the problem you pointed out is right, > but I had a nagging feeling I might be misunderstanding it because it > seemed to me that if you requested a non-converted section, plus a > converted version in the same request, the client could still tell the > difference. > > I think we can hash it out during the IETF'67 Lemonade FtF or > afterwards on the list, but I do agree there needs to be a fix, thanks > for pointing it out. We probably need to be more clear in the draft > about the result of a CONVERT (that it is a BODYPARTSTRUCTURE along > with the converted data, and not BODY), we may also want to make it > return BODYPARTSTRUCTURE[section.CONVERT requested-params] instead of > BODYPARTSTRUCTURE[section] I was about to propose the same. So the first example becomes: C: a001 FETCH 2 BODY[3.CONVERT ("APPLICATION/PDF")] S: * 2 FETCH (BODYPARTSTRUCTURE[3.CONVERT ("APPLICATION/PDF")] ("APPLICATION" "PDF" () NIL NIL "Base64" 2135 NIL NIL NIL) BODY[3.CONVERT ("APPLICATION/PDF")] {2135} ) S: a001 OK FETCH COMPLETED > as well as extending it to allow error signaling on each converted > part. I'm open to extending the result and/or renaming it if there is > confusion with BODYSTRUCTURE/BODY. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Thu Oct 26 04:52:07 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gd0y7-00010P-NL; Thu, 26 Oct 2006 04:52:07 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gd0y6-0000uV-NF for lemonade@ietf.org; Thu, 26 Oct 2006 04:52:06 -0400 Received: from rufus.isode.com ([62.3.217.251]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gd0y5-0000Yn-C3 for lemonade@ietf.org; Thu, 26 Oct 2006 04:52:06 -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 ; Thu, 26 Oct 2006 09:52:04 +0100 Message-ID: <453FB28E.1090500@isode.com> Date: Wed, 25 Oct 2006 19:53:02 +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 MIME-Version: 1.0 To: Randall Gellens Subject: Re: [lemonade] I-D ACTION:draft-ietf-lemonade-profile-bis-04.txt References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248 Cc: lemonade@ietf.org, "Stephane H. Maes" 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: > A few comments on this version: > > > ---------------------------------------- > (1) Please explicitly state that servers MUST support [message > submission] on port 587. Also, Lemonade clients MUST use port 587 by > default. (I proposed this on the list back in March and saw some > agreement and no disagreement.) The current document says that it > "assumes RFC 4409" but I think it would be helpful to be more clear > about this. Tell me which section should say that. > ---------------------------------------- > (2) In Section "4. Message Submission", please add "more" to the text > "to make message submission efficient", that is, "more efficient". Done. > ---------------------------------------- > (3) In Section "4.3. Message size declaration", the text: > LEMONADE compliant mail submission servers MUST resolve all BURL > parts before enforcing a message size limit. > > Requires the servers to expand all BURL parts, even if the message > already exceeds the message size limit. A while back I suggested > saying "Servers MUST NOT consider a message's size to be acceptable if > it has not expanded all BURL parts." I'm not wedded to that phrasing, > but I do think we should allow servers to reject messages before > expanding everything. I am not exactly happy with your replacement text, this might be too subtle for people to notice. I need to think about better alternatives. > ---------------------------------------- > (4) Section 6. Additional requirements on MUAs > LEMONADE capable clients that can reply to existing messages MUST > support the Format and DelSp parameters to text/plain media type > [RFC3676] > > A display-only client can still usefully support (and benefit from > supporting) format=flowed, so I suggest deleting "that can reply to > existing messages". Done. > Also, a typo: "to text/plain" should be "to the text/plain". Fixed. > ---------------------------------------- > (5) Section "8. OMA MEM Requirement document" > > The OMA MEM activity has collected a set of use cases and derived > requirements for a mobile email enabler (MEM). the resulting work is > s/the/The/ > > summarized in OMA MEM Requirement document [MEM-req]. Some > requirements relates to email protocols, some involve other OMA > s/relates/relate/ Both fixed. > ---------------------------------------- > (6) In Section "8.3. OMA MEM proxy", please delete the last part of > the sentence after "deployed": > > The OMA MEM Architecture document [MEM-arch] identifies OMA MEM > server proxies as server components that may be deployed ahead of > firewalls to facilitate traversal of firewalls. > > Why a proxy is deployed is not the issue. Furthermore, IMAP and > Message Submission do traverse firewalls just fine without a proxy. Done. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Thu Oct 26 10:50:45 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gd6Z3-00068A-0B; Thu, 26 Oct 2006 10:50:37 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gd6Yy-00067O-DP; Thu, 26 Oct 2006 10:50:32 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gd6Yy-00082w-Bb; Thu, 26 Oct 2006 10:50:32 -0400 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Gd6Yy-0007vN-2M; Thu, 26 Oct 2006 10:50:32 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id C338E175D7; Thu, 26 Oct 2006 14:50:01 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Gd6YT-0000WE-Cf; Thu, 26 Oct 2006 10:50: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: Thu, 26 Oct 2006 10:50:01 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1 Cc: lemonade@ietf.org Subject: [lemonade] I-D ACTION:draft-ietf-lemonade-convert-05.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 : CONVERT Author(s) : S. Maes, R. Cromwell Filename : draft-ietf-lemonade-convert-05.txt Pages : 16 Date : 2006-10-26 CONVERT defines IMAP extensions 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. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-lemonade-convert-05.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-05.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-05.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: <2006-10-26095637.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-lemonade-convert-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-lemonade-convert-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-10-26095637.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 --NextPart-- From lemonade-bounces@ietf.org Fri Oct 27 07:21:13 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdPlm-00006J-UY; Fri, 27 Oct 2006 07:21:02 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdPlm-000064-0k for lemonade@ietf.org; Fri, 27 Oct 2006 07:21:02 -0400 Received: from smarthost.yourcomms.net ([195.8.160.124]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GdPlh-0005Yr-UX for lemonade@ietf.org; Fri, 27 Oct 2006 07:21:01 -0400 Received: from svr-exchange.avocado.emccsoft.com ([212.248.196.12]) by smarthost.yourcomms.net (8.11.7p3+Sun/8.11.6) with ESMTP id k9RB80G19169 for ; Fri, 27 Oct 2006 12:08:01 +0100 (BST) 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: quoted-printable Subject: RE: [lemonade] WGLC Deployments Date: Fri, 27 Oct 2006 12:19:32 +0100 Message-ID: <22C8A0D5D5E095449AB509FE777B5F80030A0AC8@svr-exchange.avocado.emccsoft.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [lemonade] WGLC Deployments Thread-Index: Acbs3Ni/FxVDdljQEdun3QAWy5cvmwLopalvAE4WUMA= From: "Ben Last" To: "Eric Burger" , "IETF LEMONADE" X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c 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 I didn't make any comments because I read it on a plane, made comments as I went along and then found that they had all been anticipated (ie, stuff about not using tcp keepalive). Thus it passes all my criteria for wonderfulness :) More seriously: in the note in 6.1 "Firewall Traversal" about use of http as a bearer, is it appropriate to reference the P-IMAP draft that expresses a preference for HTTP as a bearer? (draft-maes-lemonade-p-imap-12, Appendix A)? Regards Ben Ben Last R&D Manager EMCC Software -----Original Message----- From: Eric Burger [mailto:eburger@cantata.com]=20 Sent: 25 October 2006 22:49 To: IETF LEMONADE Subject: Re: [lemonade] WGLC Deployments Um. Er. I'll take a few, "Wow - I didn't make any comments because I think it's great" messages. WGLC extended due to lack of response to 27 October 2006. On 10/10/06 10:27 PM, "Eric Burger" wrote: >=20 >=20 > Have at it. WGLC closes 10/25/06. >=20 >=20 > _______________________________________________ > lemonade mailing list > lemonade@ietf.org > https://www1.ietf.org/mailman/listinfo/lemonade >=20 _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Fri Oct 27 07:45:50 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdQ9e-0001BG-10; Fri, 27 Oct 2006 07:45:42 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdQ9c-0001B6-Ly for lemonade@ietf.org; Fri, 27 Oct 2006 07:45:40 -0400 Received: from outbound.cantata.com ([208.236.123.102]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GdQ9Y-00082Q-7l for lemonade@ietf.org; Fri, 27 Oct 2006 07:45:40 -0400 Received: from ma02exchtmp01.Cantata.com ([10.128.18.41]) by outbound.Cantata.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 27 Oct 2006 07:45:36 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [lemonade] WGLC Deployments Date: Fri, 27 Oct 2006 07:45:34 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [lemonade] WGLC Deployments Thread-Index: Acbs3Ni/FxVDdljQEdun3QAWy5cvmwLopalvAE4WUMAAAWgZXA== From: "Burger, Eric" To: "Ben Last" , "IETF LEMONADE" X-OriginalArrivalTime: 27 Oct 2006 11:45:36.0411 (UTC) FILETIME=[6AE426B0:01C6F9BD] X-Spam-Score: 0.1 (/) X-Scan-Signature: 995b2e24d23b953c94bac5288c432399 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: , Content-Type: multipart/mixed; boundary="===============1255003212==" Errors-To: lemonade-bounces@ietf.org This is a multi-part message in MIME format. --===============1255003212== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6F9BD.6977A4AB" This is a multi-part message in MIME format. ------_=_NextPart_001_01C6F9BD.6977A4AB Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Good point on the reference. That will slow publication, so we can put = in a note to take out the reference. -- Sent from my wireless device. Sorry if terse. Can't wait for lemonade! = What is lemonade? See -----Original Message----- From: Ben Last [mailto:Ben.Last@emccsoft.com] Sent: Friday, October 27, 2006 07:20 AM Eastern Standard Time To: Burger, Eric; IETF LEMONADE Subject: RE: [lemonade] WGLC Deployments I didn't make any comments because I read it on a plane, made comments as I went along and then found that they had all been anticipated (ie, stuff about not using tcp keepalive). Thus it passes all my criteria for wonderfulness :) More seriously: in the note in 6.1 "Firewall Traversal" about use of http as a bearer, is it appropriate to reference the P-IMAP draft that expresses a preference for HTTP as a bearer? (draft-maes-lemonade-p-imap-12, Appendix A)? Regards Ben Ben Last R&D Manager EMCC Software -----Original Message----- From: Eric Burger [mailto:eburger@cantata.com]=20 Sent: 25 October 2006 22:49 To: IETF LEMONADE Subject: Re: [lemonade] WGLC Deployments Um. Er. I'll take a few, "Wow - I didn't make any comments because I think it's great" messages. WGLC extended due to lack of response to 27 October 2006. On 10/10/06 10:27 PM, "Eric Burger" wrote: >=20 >=20 > Have at it. WGLC closes 10/25/06. >=20 >=20 > _______________________________________________ > lemonade mailing list > lemonade@ietf.org > https://www1.ietf.org/mailman/listinfo/lemonade >=20 _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade ------_=_NextPart_001_01C6F9BD.6977A4AB Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable RE: [lemonade] WGLC Deployments

Good point on the reference. That will slow = publication, so we can put in a note to take out the reference.

--
Sent from my wireless device. Sorry if terse. Can't wait for = lemonade!  What is lemonade? See <http://flyingfox.canta= ta.com/i-d/lemonade>

 -----Original Message-----
From:   Ben Last [mailto:Ben.Last@emccsoft.com] Sent:   Friday, October 27, 2006 07:20 AM Eastern Standard = Time
To:     Burger, Eric; IETF LEMONADE
Subject:        RE: [lemonade] WGLC = Deployments

I didn't make any comments because I read it on a plane, made = comments
as I went along and then found that they had all been anticipated = (ie,
stuff about not using tcp keepalive).  Thus it passes all my = criteria
for wonderfulness :)

More seriously: in the note in 6.1 "Firewall Traversal" about = use of
http as a bearer, is it appropriate to reference the P-IMAP draft = that
expresses a preference for HTTP as a bearer?
(draft-maes-lemonade-p-imap-12, Appendix A)?

Regards
Ben

Ben Last
R&D Manager
EMCC Software

-----Original Message-----
From: Eric Burger [mailto:eburger@cantata.com]
Sent: 25 October 2006 22:49
To: IETF LEMONADE
Subject: Re: [lemonade] WGLC Deployments

Um. Er. I'll take a few, "Wow - I didn't make any comments because = I
think it's great" messages.

WGLC extended due to lack of response to 27 October 2006.


On 10/10/06 10:27 PM, "Eric Burger" = <eburger@cantata.com> wrote:

>
<http://tools.ietf.org/wg/lemonade/draft-ietf-lemonade-deployments/dra= ft
-ietf-le
monade-deployments-03.txt>
>
> Have at it.  WGLC closes 10/25/06.
>
>
> _______________________________________________
> lemonade mailing list
> lemonade@ietf.org
> https://www1.iet= f.org/mailman/listinfo/lemonade
>



_______________________________________________
lemonade mailing list
lemonade@ietf.org
https://www1.iet= f.org/mailman/listinfo/lemonade

------_=_NextPart_001_01C6F9BD.6977A4AB-- --===============1255003212== 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 --===============1255003212==-- From lemonade-bounces@ietf.org Fri Oct 27 08:50:50 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdRAc-0006WN-El; Fri, 27 Oct 2006 08:50:46 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdRAa-0006TU-KO for lemonade@ietf.org; Fri, 27 Oct 2006 08:50:44 -0400 Received: from outbound.cantata.com ([208.236.123.102]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GdRAW-0006kL-3i for lemonade@ietf.org; Fri, 27 Oct 2006 08:50:44 -0400 Received: from ma02exchtmp01.Cantata.com ([10.128.18.41]) by outbound.Cantata.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 27 Oct 2006 08:50:39 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [lemonade] WGLC Deployments Date: Fri, 27 Oct 2006 08:50:37 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [lemonade] WGLC Deployments Thread-Index: Acbs3Ni/FxVDdljQEdun3QAWy5cvmwLopalvAE4WUMAAAWgZXAACRbHv From: "Burger, Eric" To: "Ben Last" , "IETF LEMONADE" X-OriginalArrivalTime: 27 Oct 2006 12:50:39.0940 (UTC) FILETIME=[81936840:01C6F9C6] X-Spam-Score: 0.1 (/) X-Scan-Signature: a743e34ab8eb08259de9a7307caed594 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: , Content-Type: multipart/mixed; boundary="===============0597957235==" Errors-To: lemonade-bounces@ietf.org This is a multi-part message in MIME format. --===============0597957235== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6F9C6.8044D20B" This is a multi-part message in MIME format. ------_=_NextPart_001_01C6F9C6.8044D20B Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Whoops - it looks like I was saying, "Put in the reference." I was = thinking that you were asking if we should take it out, not put it in. We should NOT put in the reference. Sorry for the confusion. -- Sent from my wireless device. Sorry if terse. Can't wait for lemonade! = What is lemonade? See -----Original Message----- From: Burger, Eric Sent: Friday, October 27, 2006 07:45 AM Eastern Standard Time To: 'Ben Last'; 'IETF LEMONADE' Subject: RE: [lemonade] WGLC Deployments Good point on the reference. That will slow publication, so we can put = in a note to take out the reference. -- Sent from my wireless device. Sorry if terse. Can't wait for lemonade! = What is lemonade? See -----Original Message----- From: Ben Last [mailto:Ben.Last@emccsoft.com] Sent: Friday, October 27, 2006 07:20 AM Eastern Standard Time To: Burger, Eric; IETF LEMONADE Subject: RE: [lemonade] WGLC Deployments I didn't make any comments because I read it on a plane, made comments as I went along and then found that they had all been anticipated (ie, stuff about not using tcp keepalive). Thus it passes all my criteria for wonderfulness :) More seriously: in the note in 6.1 "Firewall Traversal" about use of http as a bearer, is it appropriate to reference the P-IMAP draft that expresses a preference for HTTP as a bearer? (draft-maes-lemonade-p-imap-12, Appendix A)? Regards Ben Ben Last R&D Manager EMCC Software -----Original Message----- From: Eric Burger [mailto:eburger@cantata.com]=20 Sent: 25 October 2006 22:49 To: IETF LEMONADE Subject: Re: [lemonade] WGLC Deployments Um. Er. I'll take a few, "Wow - I didn't make any comments because I think it's great" messages. WGLC extended due to lack of response to 27 October 2006. On 10/10/06 10:27 PM, "Eric Burger" wrote: >=20 >=20 > Have at it. WGLC closes 10/25/06. >=20 >=20 > _______________________________________________ > lemonade mailing list > lemonade@ietf.org > https://www1.ietf.org/mailman/listinfo/lemonade >=20 _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade ------_=_NextPart_001_01C6F9C6.8044D20B Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable RE: [lemonade] WGLC Deployments

Whoops - it looks like I was saying, "Put in the = reference." I was thinking that you were asking if we should take = it out, not put it in.

We should NOT put in the reference.

Sorry for the confusion.

--
Sent from my wireless device. Sorry if terse. Can't wait for = lemonade!  What is lemonade? See <http://flyingfox.canta= ta.com/i-d/lemonade>

 -----Original Message-----
From:   Burger, Eric
Sent:   Friday, October 27, 2006 07:45 AM Eastern Standard = Time
To:     'Ben Last'; 'IETF LEMONADE'
Subject:        RE: [lemonade] WGLC = Deployments

Good point on the reference. That will slow publication, so we can put = in a note to take out the reference.

--
Sent from my wireless device. Sorry if terse. Can't wait for = lemonade!  What is lemonade? See <http://flyingfox.canta= ta.com/i-d/lemonade>

 -----Original Message-----
From:   Ben Last [mailto:Ben.Last@emccsoft.com] Sent:   Friday, October 27, 2006 07:20 AM Eastern Standard = Time
To:     Burger, Eric; IETF LEMONADE
Subject:        RE: [lemonade] WGLC = Deployments

I didn't make any comments because I read it on a plane, made = comments
as I went along and then found that they had all been anticipated = (ie,
stuff about not using tcp keepalive).  Thus it passes all my = criteria
for wonderfulness :)

More seriously: in the note in 6.1 "Firewall Traversal" about = use of
http as a bearer, is it appropriate to reference the P-IMAP draft = that
expresses a preference for HTTP as a bearer?
(draft-maes-lemonade-p-imap-12, Appendix A)?

Regards
Ben

Ben Last
R&D Manager
EMCC Software

-----Original Message-----
From: Eric Burger [mailto:eburger@cantata.com]
Sent: 25 October 2006 22:49
To: IETF LEMONADE
Subject: Re: [lemonade] WGLC Deployments

Um. Er. I'll take a few, "Wow - I didn't make any comments because = I
think it's great" messages.

WGLC extended due to lack of response to 27 October 2006.


On 10/10/06 10:27 PM, "Eric Burger" = <eburger@cantata.com> wrote:

>
<http://tools.ietf.org/wg/lemonade/draft-ietf-lemonade-deployments/dra= ft
-ietf-le
monade-deployments-03.txt>
>
> Have at it.  WGLC closes 10/25/06.
>
>
> _______________________________________________
> lemonade mailing list
> lemonade@ietf.org
> https://www1.iet= f.org/mailman/listinfo/lemonade
>



_______________________________________________
lemonade mailing list
lemonade@ietf.org
https://www1.iet= f.org/mailman/listinfo/lemonade

------_=_NextPart_001_01C6F9C6.8044D20B-- --===============0597957235== 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 --===============0597957235==-- From lemonade-bounces@ietf.org Fri Oct 27 15:26:33 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdXLZ-0007FH-9y; Fri, 27 Oct 2006 15:26:29 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdXLV-0006be-T5 for lemonade@ietf.org; Fri, 27 Oct 2006 15:26:25 -0400 Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GdX6E-0006ZP-IO for lemonade@ietf.org; Fri, 27 Oct 2006 15:10:42 -0400 Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148]) by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id k9RJAGVh002763 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 27 Oct 2006 12:10:17 -0700 Received: from [loud.qualcomm.com] (loud.qualcomm.com [129.46.172.15]) by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k9RJABNH027709; Fri, 27 Oct 2006 12:10:14 -0700 (PDT) Mime-Version: 1.0 Message-Id: In-Reply-To: <22C8A0D5D5E095449AB509FE777B5F80030A0AC8@svr-exchange.avocado.emccsof t.com> References: <22C8A0D5D5E095449AB509FE777B5F80030A0AC8@svr-exchange.avocado.emccsof t.com> X-Mailer: Eudora for Mac OS X (dev alpha) X-message-flag: Warning: Outlook in use. Upgrade to Eudora: Date: Fri, 27 Oct 2006 12:08:21 -0700 To: "Ben Last" , "Eric Burger" , "IETF LEMONADE" From: Randall Gellens Subject: RE: [lemonade] WGLC Deployments 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: 9466e0365fc95844abaf7c3f15a05c7d 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 12:19 PM +0100 10/27/06, Ben Last wrote: > I didn't make any comments because I read it on a plane, made comments > as I went along and then found that they had all been anticipated (ie, > stuff about not using tcp keepalive). Thus it passes all my criteria > for wonderfulness :) Thank you. > More seriously: in the note in 6.1 "Firewall Traversal" about use of > http as a bearer, is it appropriate to reference the P-IMAP draft that > expresses a preference for HTTP as a bearer? > (draft-maes-lemonade-p-imap-12, Appendix A)? Reference in what way? As an example of a draft that does what the text says not to do? I don't think an example is really needed, so I don't see that adding a reference improves this document. If you think an example would help, it would be better to point to a published document, I think. -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly-selected tag: --------------- As you know, any depiction of nasal mucus brings with it problems for our sales division. --ABC's Broadcast Standards & Practices board, to producers of the cartoon "Bump in the Night" _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Mon Oct 30 04:40:40 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GeTdA-0007av-Jm; Mon, 30 Oct 2006 04:40:32 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GeTLm-0003qs-Au for lemonade@ietf.org; Mon, 30 Oct 2006 04:22:34 -0500 Received: from smarthost.yourcomms.net ([195.8.160.124]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GeTIm-0000FQ-M9 for lemonade@ietf.org; Mon, 30 Oct 2006 04:19:32 -0500 Received: from svr-exchange.avocado.emccsoft.com ([212.248.196.12]) by smarthost.yourcomms.net (8.11.7p3+Sun/8.11.6) with ESMTP id k9U96LG25107 for ; Mon, 30 Oct 2006 09:06:21 GMT 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: quoted-printable Subject: RE: [lemonade] WGLC Deployments Date: Mon, 30 Oct 2006 09:17:53 -0000 Message-ID: <22C8A0D5D5E095449AB509FE777B5F80030A0D04@svr-exchange.avocado.emccsoft.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [lemonade] WGLC Deployments Thread-Index: Acb5+2p6El+9bHsUSouNo+Q2CXGxWwCCH0AA From: "Ben Last" To: "Randall Gellens" , "Eric Burger" , "IETF LEMONADE" X-Spam-Score: 0.0 (/) X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 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 From: Randall Gellens [mailto:randy@qualcomm.com]=20 I wrote: >> More seriously: in the note in 6.1 "Firewall Traversal" about use of >> http as a bearer, is it appropriate to reference the P-IMAP draft that =20 >> expresses a preference for HTTP as a bearer? >> (draft-maes-lemonade-p-imap-12, Appendix A)? >Reference in what way? As an example of a draft that does what the text says not to do? >I don't think an example is really needed, so I don't see that adding a reference improves >this document. If you think an example would help, it would be better to point to a >published document, I think. Perhaps "reference" is the wrong word, but the P-IMAP drafts (which I acknowledge are unpublished but which are implemented in a commercial product) do set our arguments for the use of HTTP. Since the document argues against its use, I wondered whether some better collation of the arguments might make things clearer. Though that may not be appropriate for this document; feel free to consider my comment a note in passing and freely ignorable. Regards Ben _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Mon Oct 30 17:20:13 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GefUG-0001nF-Fb; Mon, 30 Oct 2006 17:20:08 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GefQg-0008Fv-5G for lemonade@ietf.org; Mon, 30 Oct 2006 17:16:26 -0500 Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GefIk-00080u-Jz for lemonade@ietf.org; Mon, 30 Oct 2006 17:08:19 -0500 Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150]) by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id k9UM8AOc027972 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 30 Oct 2006 14:08:13 -0800 Received: from [loud.qualcomm.com] (loud.qualcomm.com [129.46.172.15]) by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k9UM87Dx020241; Mon, 30 Oct 2006 14:08:09 -0800 (PST) Mime-Version: 1.0 Message-Id: In-Reply-To: <453FB28E.1090500@isode.com> References: <453FB28E.1090500@isode.com> X-Mailer: Eudora for Mac OS X X-message-flag: Warning: Outlook in use. Upgrade to Eudora: Date: Mon, 30 Oct 2006 14:06:16 -0800 To: Alexey Melnikov From: Randall Gellens Subject: Re: [lemonade] I-D ACTION:draft-ietf-lemonade-profile-bis-04.txt 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: 244a2fd369eaf00ce6820a760a3de2e8 Cc: lemonade@ietf.org, "Stephane H. Maes" 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 7:53 PM +0100 10/25/06, Alexey Melnikov wrote: > Randall Gellens wrote: > >> A few comments on this version: >> >> >> ---------------------------------------- >> (1) Please explicitly state that servers MUST support [message >> submission] on port 587. Also, Lemonade clients MUST use port 587 >> by default. (I proposed this on the list back in March and saw >> some agreement and no disagreement.) The current document says >> that it "assumes RFC 4409" but I think it would be helpful to be >> more clear about this. > > Tell me which section should say that. I was thinking either a short new paragraph at the end of either Section 3.5 "Normative statements related to forward without download", or, if you prefer, Section 6 "Additional requirements on MUAs". >> ---------------------------------------- >> (3) In Section "4.3. Message size declaration", the text: >> LEMONADE compliant mail submission servers MUST resolve all BURL >> parts before enforcing a message size limit. >> >> Requires the servers to expand all BURL parts, even if the message >> already exceeds the message size limit. A while back I suggested >> saying "Servers MUST NOT consider a message's size to be >> acceptable if it has not expanded all BURL parts." I'm not wedded >> to that phrasing, but I do think we should allow servers to reject >> messages before expanding everything. > > I am not exactly happy with your replacement text, this might be > too subtle for people to notice. I need to think about better > alternatives. If you'd like to make the situation very explicit and clear, how about: Interoperability problems and user confusion would result from submission servers accepting a message with a 2xx result code, and then, after expanding BURL parts, determining that the final size of the message is too large. In such cases, the submission server would then generate an DSN bounce, which the client would need to receive and process during some subsequent mail check. Correct matching of the DSN to the original message is difficult, subject to unpredictable delay, and much user annoyance. If the bounce contains the expanded BURL parts, it's size could make it difficult for the client to receive it. Therefore, servers MUST NOT consider a message's size to be acceptable before all of its BURL parts have not been expanded. Servers MAY reject a message as being too large before expanding all BURL parts, and it is RECOMMENDED that servers check the message's size after expanding each BURL, to guard against denial of service attacks. -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly-selected tag: --------------- If you lend someone $20, and never see that person again, it was probably worth it. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Mon Oct 30 18:09:48 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GegG4-0005aC-9b; Mon, 30 Oct 2006 18:09:32 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GegG3-0005a4-3M for lemonade@ietf.org; Mon, 30 Oct 2006 18:09:31 -0500 Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GegFz-0001f2-Oh for lemonade@ietf.org; Mon, 30 Oct 2006 18:09:31 -0500 Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149]) by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id k9UN9PUv023638 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 30 Oct 2006 15:09:26 -0800 Received: from [loud.qualcomm.com] (loud.qualcomm.com [129.46.172.15]) by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k9UN9LSh003248; Mon, 30 Oct 2006 15:09:23 -0800 (PST) Mime-Version: 1.0 Message-Id: In-Reply-To: References: <453FB28E.1090500@isode.com> X-Mailer: Eudora for Mac OS X X-message-flag: Warning: Outlook in use. Upgrade to Eudora: Date: Mon, 30 Oct 2006 15:09:15 -0800 To: Alexey Melnikov From: Randall Gellens Subject: Re: [lemonade] I-D ACTION:draft-ietf-lemonade-profile-bis-04.txt 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: 68c8cc8a64a9d0402e43b8eee9fc4199 Cc: lemonade@ietf.org, "Stephane H. Maes" 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 bounce contains the expanded BURL parts, it's size could make > it difficult for the client to receive it. s/it's/its/ -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly-selected tag: --------------- Democracy is also a form of worship. It is the worship of Jackals by Jackasses. --H. L. Mencken _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Tue Oct 31 08:29:22 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Getfu-0004ti-Ln; Tue, 31 Oct 2006 08:29:06 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Getfq-0004rr-8L for lemonade@ietf.org; Tue, 31 Oct 2006 08:29:04 -0500 Received: from mgw-ext12.nokia.com ([131.228.20.171]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Getfm-00051g-Is for lemonade@ietf.org; Tue, 31 Oct 2006 08:29:02 -0500 Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-ext12.nokia.com (Switch-3.1.10/Switch-3.1.10) with ESMTP id k9VDSrIW012724; Tue, 31 Oct 2006 15:28:56 +0200 Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 31 Oct 2006 15:28:55 +0200 Received: from esebe199.NOE.Nokia.com ([172.21.138.143]) by esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 31 Oct 2006 15:28:55 +0200 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: quoted-printable Subject: RE: [lemonade] I-D ACTION:draft-ietf-lemonade-profile-bis-04.txt Date: Tue, 31 Oct 2006 15:28:01 +0200 Message-ID: <0FA975F2D8295A448BE3ADC1612446570185DA64@esebe199.NOE.Nokia.com> In-Reply-To: <453FB28E.1090500@isode.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [lemonade] I-D ACTION:draft-ietf-lemonade-profile-bis-04.txt Thread-Index: Acb43EvE62hYqhbZSIOqRRIDG4MrLAEEqF6w From: To: , X-OriginalArrivalTime: 31 Oct 2006 13:28:55.0569 (UTC) FILETIME=[83879810:01C6FCF0] X-eXpurgate-Category: 1/0 X-eXpurgate-ID: 149371::061031152856-2CA2EBB0-4F531CA2/0-0/0-1 X-Nokia-AV: Clean X-Spam-Score: 0.2 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 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 >> ---------------------------------------- >> (3) In Section "4.3. Message size declaration", the text: >> LEMONADE compliant mail submission servers MUST resolve all BURL >> parts before enforcing a message size limit. >> >> Requires the servers to expand all BURL parts, even if the message=20 >> already exceeds the message size limit. A while back I suggested=20 >> saying "Servers MUST NOT consider a message's size to be=20 >acceptable if=20 >> it has not expanded all BURL parts." I'm not wedded to that=20 >phrasing,=20 >> but I do think we should allow servers to reject messages before=20 >> expanding everything. > >I am not exactly happy with your replacement text, this might=20 >be too subtle for people to notice. I need to think about=20 >better alternatives. I would prefer writing it down as well. I am not sure how to put it though. Here is another attempt: LEMONADE compliant mail submission servers MUST resolve all BURL parts before enforcing a message size limit and MUST NOT reject email messages where the total size of the email message reassembled from BURL parts is smaller than the message size limit. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Tue Oct 31 09:23:26 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GeuWP-0003Ce-RK; Tue, 31 Oct 2006 09:23:21 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GeuWM-00039L-Qr for lemonade@ietf.org; Tue, 31 Oct 2006 09:23:21 -0500 Received: from mgw-ext14.nokia.com ([131.228.20.173]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GeuWE-0005TX-UK for lemonade@ietf.org; Tue, 31 Oct 2006 09:23:18 -0500 Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143]) by mgw-ext14.nokia.com (Switch-3.1.10/Switch-3.1.10) with ESMTP id k9VEN45K029140; Tue, 31 Oct 2006 16:23:09 +0200 Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 31 Oct 2006 16:23:02 +0200 Received: from esebe199.NOE.Nokia.com ([172.21.138.143]) by esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 31 Oct 2006 16:23:02 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [lemonade] I-D ACTION:draft-ietf-lemonade-compress-05.txt - comments Date: Tue, 31 Oct 2006 16:22:08 +0200 Message-ID: <0FA975F2D8295A448BE3ADC1612446570185DB47@esebe199.NOE.Nokia.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [lemonade] I-D ACTION:draft-ietf-lemonade-compress-05.txt - comments Thread-Index: AcbmMncfdcLrA/kmQmKoSt41wyZuxAWv2sxw From: To: X-OriginalArrivalTime: 31 Oct 2006 14:23:02.0461 (UTC) FILETIME=[12D3FED0:01C6FCF8] X-eXpurgate-Category: 1/0 X-eXpurgate-ID: 149371::061031162309-6F97ABB0-0A87E081/0-0/0-0 X-Nokia-AV: Clean X-Spam-Score: 0.2 (/) X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c 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 I hope it's not too late. 1. Typo in section 2: When a TLS librarly 2. Wording change suggestion in section 2: all protocols that use TLS automatically are compressed to: all protocols that use TLS are automatically compressed 3. Wording change suggestion in section 3: OK The server will compress its responses and expects the client to = compress its commands. to: OK The server and the client will compress all data that it may send 4. Wording change suggestion in section 3: The client MUST NOT send any further commands until it has seen the = result of COMPRESS. to: After the client has sent the COMPRESS command, the client MUST NOT send = any commands until it has seen the result of COMPRESS. 5. Clarification/wording change suggestion in section 3: (Responses issued by the server before the OK response will, of course, = still be uncompressed.) to: Therefore, responses issued by the server before the OK response will = all be uncompressed, and delayed client requests that have been sent = uncompressed (before turning compression on) may result in compressed = responses. 6. Typo in section 4: so any compression algorith 7. Wording change suggestion in section 4: the same way as is recommended for servers the same way as it is recommended for servers later 8. Question/suggestion in section 4: Multiple occurances of "base-64" - this is BASE64 as in RFC4648, right? = If so, I would suggest correction (base-64 -> BASE64) and adding a = reference. 9. Question in section 5: capability =3D/ "COMPRESS=3D" algorithm ;; multiple COMPRESS capabilities allowed So, if I had multiple algorithms, would it be COMPRESS=3D1,2,3 or = COMPRESS=3D1,COMPRESS=3D2,COMPRESS=3D3? I would guess the second. 10. Question in section 6: Should we add ZLIB here? ZLIB already had some history... 11. Wording change suggestion in section 7: The IANA is requested to add COMPRESS=3DDEFLATE the list to: The IANA is requested to add COMPRESS=3DDEFLATE to the list 12. Wording change suggestion in section 7: and another compression is added at that time, it would then be = appropriate to create a registry to: and any additional compression algorithms are introduced at that time, = then the registry should be created Thank You. Best regards: Zolt=E1n =D6rd=F6gh E-mail: zoltan dot ordogh at nokia dot com Phone: +358 50 386 0566 =20 >-----Original Message----- >From: ext lemonade-bounces@ietf.org [mailto:lemonade-bounces@ietf.org]=20 >Sent: 02 October, 2006 17:50 >To: i-d-announce@ietf.org >Cc: lemonade@ietf.org >Subject: [lemonade] I-D ACTION:draft-ietf-lemonade-compress-05.txt=20 > >A New Internet-Draft is available from the on-line=20 >Internet-Drafts directories. >This draft is a work item of the Enhancements to Internet=20 >email to support diverse service environments Working Group of=20 >the IETF. > > Title : The IMAP COMPRESS Extension > Author(s) : A. Gulbrandsen > Filename : draft-ietf-lemonade-compress-05.txt > Pages : 9 > Date : 2006-10-2 >=09 >The COMPRESS extension allows an IMAP connection to be effectively > and efficiently compressed. > >A URL for this Internet-Draft is: >http://www.ietf.org/internet-drafts/draft-ietf-lemonade-compress-05.txt > >To remove yourself from the I-D Announcement list, send a=20 >message to i-d-announce-request@ietf.org with the word=20 >unsubscribe in the body of the message.=20 >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=20 >with the username "anonymous" and a password of your e-mail=20 >address. After logging in, type "cd internet-drafts" and then=20 >"get draft-ietf-lemonade-compress-05.txt". > >A list of Internet-Drafts directories can be found in=20 >http://www.ietf.org/shadow.html or=20 >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-compress-05.txt". >=09 >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=20 >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=20 >reader implementation to automatically retrieve the ASCII=20 >version of the Internet-Draft. > _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Tue Oct 31 09:33:50 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Geug8-0000fI-Tu; Tue, 31 Oct 2006 09:33:24 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Geug6-0000ev-Qe for lemonade@ietf.org; Tue, 31 Oct 2006 09:33:23 -0500 Received: from mgw-ext12.nokia.com ([131.228.20.171]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Geug5-0006oj-BW for lemonade@ietf.org; Tue, 31 Oct 2006 09:33:22 -0500 Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-ext12.nokia.com (Switch-3.1.10/Switch-3.1.10) with ESMTP id k9VEX4lM001423; Tue, 31 Oct 2006 16:33:18 +0200 Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 31 Oct 2006 16:33:17 +0200 Received: from esebe199.NOE.Nokia.com ([172.21.138.143]) by esebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 31 Oct 2006 16:33:16 +0200 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: quoted-printable Subject: RE: [lemonade] I-D ACTION:draft-ietf-lemonade-profile-bis-04.txt Date: Tue, 31 Oct 2006 16:32:23 +0200 Message-ID: <0FA975F2D8295A448BE3ADC1612446570185DB6F@esebe199.NOE.Nokia.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [lemonade] I-D ACTION:draft-ietf-lemonade-profile-bis-04.txt Thread-Index: Acb3CR0NAxv/7c6kQe+4EltdGjv4LwF8CP+A From: To: , , X-OriginalArrivalTime: 31 Oct 2006 14:33:16.0665 (UTC) FILETIME=[80EC1690:01C6FCF9] X-Nokia-AV: Clean X-Spam-Score: 0.2 (/) X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de 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 >---------------------------------------- >(1) Please explicitly state that servers MUST support [message=20 >submission] on port 587. Also, Lemonade clients MUST use port=20 >587 by default. (I proposed this on the list back in March=20 >and saw some agreement and no disagreement.) The current=20 >document says that it "assumes RFC 4409" but I think it would=20 >be helpful to be more clear about this. > I saw the port number stated in the deployment draft, section 3 - as MUSTs. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Tue Oct 31 09:42:13 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Geuof-0004Bk-83; Tue, 31 Oct 2006 09:42:13 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Geuoc-0004Bd-Kt for lemonade@ietf.org; Tue, 31 Oct 2006 09:42:12 -0500 Received: from heisenberg.zen.co.uk ([212.23.3.141]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GeuoW-0007zh-5P for lemonade@ietf.org; Tue, 31 Oct 2006 09:42:10 -0500 Received: from [217.155.137.60] (helo=turner.dave.cridland.net) by heisenberg.zen.co.uk with esmtp (Exim 4.50) id 1GeuoU-0005Jl-N4; Tue, 31 Oct 2006 14:42:02 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by turner.dave.cridland.net (Postfix) with ESMTP id 53ADE498006; Tue, 31 Oct 2006 14:51:07 +0000 (GMT) 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 22419-07; Tue, 31 Oct 2006 14:50:53 +0000 (GMT) Received: from peirce.dave.cridland.net (unknown [IPv6:2001:4bd0:2029:0:2e0:81ff:fe29:d16a]) by turner.dave.cridland.net (Postfix) with ESMTP id F1902498005; Tue, 31 Oct 2006 14:50:52 +0000 (GMT) Date: Tue, 31 Oct 2006 14:41:46 +0000 Subject: RE: [lemonade] I-D ACTION:draft-ietf-lemonade-compress-05.txt - comments References: <0FA975F2D8295A448BE3ADC1612446570185DB47@esebe199.NOE.Nokia.com> In-Reply-To: <0FA975F2D8295A448BE3ADC1612446570185DB47@esebe199.NOE.Nokia.com> MIME-Version: 1.0 Message-Id: <11923.1162305707.785552@peirce.dave.cridland.net> From: Dave Cridland To: "Zoltan.Ordogh@nokia.com" Content-Type: text/plain; charset="us-ascii"; format="flowed" X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at dave.cridland.net X-Originating-Heisenberg-IP: [217.155.137.60] X-Spam-Score: 0.5 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Cc: Enhancements to Internet email to support diverse service enivronments , Arnt Gulbrandsen 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 On Tue Oct 31 14:22:08 2006, Zoltan.Ordogh@nokia.com wrote: > 3. Wording change suggestion in section 3: > OK The server will compress its responses and expects the client to > compress its commands. > to: > OK The server and the client will compress all data that it may send > > Most of these suggestions don't bother me either way, but this one strikes me as potentially misleading. One might read this as meaning that only literals and strings were compressed, rather than the entire protocol stream. It depends on what is meant by "data". The current wording is less confusing than this, and I think it's fine. 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 From lemonade-bounces@ietf.org Tue Oct 31 09:57:34 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gev3O-0003dO-Ir; Tue, 31 Oct 2006 09:57:26 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gev3L-0003d4-9a for lemonade@ietf.org; Tue, 31 Oct 2006 09:57:23 -0500 Received: from mgw-ext14.nokia.com ([131.228.20.173]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gev3B-0001x6-1N for lemonade@ietf.org; Tue, 31 Oct 2006 09:57:23 -0500 Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-ext14.nokia.com (Switch-3.1.10/Switch-3.1.10) with ESMTP id k9VEuvws016377; Tue, 31 Oct 2006 16:57:07 +0200 Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 31 Oct 2006 16:56:58 +0200 Received: from esebe199.NOE.Nokia.com ([172.21.138.143]) by esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 31 Oct 2006 16:56:58 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [lemonade] WGLC Deployments Date: Tue, 31 Oct 2006 16:56:03 +0200 Message-ID: <0FA975F2D8295A448BE3ADC1612446570185DBB4@esebe199.NOE.Nokia.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [lemonade] WGLC Deployments Thread-Index: Acbs3Ni/FxVDdljQEdun3QAWy5cvmwQHBWvQ From: To: , X-OriginalArrivalTime: 31 Oct 2006 14:56:58.0199 (UTC) FILETIME=[D038F670:01C6FCFC] X-eXpurgate-Category: 1/0 X-eXpurgate-ID: 149371::061031165707-399B5BB0-73B75214/0-0/0-0 X-Nokia-AV: Clean X-Spam-Score: 0.2 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 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 I guess it's too late... But anyway: 1. Section 2+general: "The IETF lemonade group" "lemonade-compliant" And generally "lemonade" all over the draft. So, it means that we have an agreement the lemonade will be always small = caps, right? 2. Wording change suggestion in section 3: "It should be noted that systems which don't support TCP on arbitrary = ports aren't full Internet clients." to: "Noted that systems which do not support TCP on arbitrary ports are not = considered full Internet clients." 3. Missing reference in section 4: "The requirements and advice in [HOST-REQUIREMENTS] SHOULD be followed." I do not have a clue what it includes, so I cannot really comment on it = apart from adding the reference, but I think that this sounds better: [HOST-REQUIREMENTS] includes a collection of requirements and advices, = which SHOULD be followed and considered by all lemonade depoyments. 4. Incorrect reference in section 4.1 as permitted by the protocol (see [SUBMISSION] or [PROFILE]) PROFILE does not describe it - well, at least I could not find it. While at it, You might want to add to the references the correct RFC = number, PROFILE is still referenced as a draft. Thank You. Best regards: Zolt=E1n =D6rd=F6gh E-mail: zoltan dot ordogh at nokia dot com Phone: +358 50 386 0566 =20 >-----Original Message----- >From: ext Eric Burger [mailto:eburger@cantata.com]=20 >Sent: 11 October, 2006 05:28 >To: IETF LEMONADE >Subject: [lemonade] WGLC Deployments > >nts/draft-iet >f-lemonade-deployments-03.txt> > >Have at it. WGLC closes 10/25/06. > > >_______________________________________________ >lemonade mailing list >lemonade@ietf.org >https://www1.ietf.org/mailman/listinfo/lemonade > _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Tue Oct 31 10:01:38 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gev7S-0004fi-7Z; Tue, 31 Oct 2006 10:01:38 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gev7Q-0004fd-Ee for lemonade@ietf.org; Tue, 31 Oct 2006 10:01:36 -0500 Received: from mgw-ext14.nokia.com ([131.228.20.173]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gev7L-0002fw-8v for lemonade@ietf.org; Tue, 31 Oct 2006 10:01:36 -0500 Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143]) by mgw-ext14.nokia.com (Switch-3.1.10/Switch-3.1.10) with ESMTP id k9VF1SeY028260; Tue, 31 Oct 2006 17:01:29 +0200 Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 31 Oct 2006 17:00:24 +0200 Received: from esebe199.NOE.Nokia.com ([172.21.138.143]) by esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 31 Oct 2006 17:00:24 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [lemonade] I-D ACTION:draft-ietf-lemonade-compress-05.txt - comments Date: Tue, 31 Oct 2006 16:59:30 +0200 Message-ID: <0FA975F2D8295A448BE3ADC1612446570185DBD3@esebe199.NOE.Nokia.com> In-Reply-To: <11923.1162305707.785552@peirce.dave.cridland.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [lemonade] I-D ACTION:draft-ietf-lemonade-compress-05.txt - comments Thread-Index: Acb8+vILM1Hx9ZMdQcOV7unUyKRcJAAAd7EQ From: To: X-OriginalArrivalTime: 31 Oct 2006 15:00:24.0934 (UTC) FILETIME=[4B723860:01C6FCFD] X-eXpurgate-Category: 1/0 X-eXpurgate-ID: 149371::061031170129-4A2B2BB0-641C251B/0-0/0-1 X-Nokia-AV: Clean X-Spam-Score: 0.2 (/) X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9 Cc: lemonade@ietf.org, arnt@oryx.com 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 Well, we can put anything You like there - the reason I changed it = because I did not like "expects". Once compression is on, it will be compressed, right? The word "expects" = to me hints that this is not the case. Best regards: Zolt=E1n =D6rd=F6gh E-mail: zoltan dot ordogh at nokia dot com Phone: +358 50 386 0566 =20 >-----Original Message----- >From: ext Dave Cridland [mailto:dave@cridland.net]=20 >Sent: 31 October, 2006 16:42 >To: Ordogh Zoltan (Nokia-TP-MSW/Tampere) >Cc: Enhancements to Internet email to support diverse service=20 >enivronments; Arnt Gulbrandsen >Subject: RE: [lemonade] I-D=20 >ACTION:draft-ietf-lemonade-compress-05.txt - comments > >On Tue Oct 31 14:22:08 2006, Zoltan.Ordogh@nokia.com wrote: >> 3. Wording change suggestion in section 3: >> OK The server will compress its responses and expects the client to=20 >> compress its commands. >> to: >> OK The server and the client will compress all data that it may send >>=20 >>=20 >Most of these suggestions don't bother me either way, but this=20 >one strikes me as potentially misleading. One might read this=20 >as meaning that only literals and strings were compressed,=20 >rather than the entire protocol stream. It depends on what is=20 >meant by "data". > >The current wording is less confusing than this, and I think it's fine. > >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 From lemonade-bounces@ietf.org Tue Oct 31 14:33:13 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GezM7-0003Po-0l; Tue, 31 Oct 2006 14:33:03 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GezM5-0003Nm-Jq for lemonade@ietf.org; Tue, 31 Oct 2006 14:33:01 -0500 Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GezM4-0002Ye-8E for lemonade@ietf.org; Tue, 31 Oct 2006 14:33:01 -0500 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 k9VJWwUR013581 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 31 Oct 2006 11:32:59 -0800 Received: from [loud.qualcomm.com] (vpn-10-50-16-107.qualcomm.com [10.50.16.107]) by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k9VJWt12009629; Tue, 31 Oct 2006 11:32:57 -0800 (PST) Mime-Version: 1.0 Message-Id: In-Reply-To: <0FA975F2D8295A448BE3ADC1612446570185DA64@esebe199.NOE.Nokia.com> References: <0FA975F2D8295A448BE3ADC1612446570185DA64@esebe199.NOE.Nokia.com> X-Mailer: Eudora for Mac OS X X-message-flag: Warning: Outlook in use. Upgrade to Eudora: Date: Tue, 31 Oct 2006 11:22:48 -0800 To: , From: Randall Gellens Subject: RE: [lemonade] I-D ACTION:draft-ietf-lemonade-profile-bis-04.txt 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: 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 Hi Zoltan, At 3:28 PM +0200 10/31/06, wrote: > >> ---------------------------------------- >>> (3) In Section "4.3. Message size declaration", the text: >>> LEMONADE compliant mail submission servers MUST resolve all BURL >>> parts before enforcing a message size limit. >>> >>> Requires the servers to expand all BURL parts, even if the message >>> already exceeds the message size limit. A while back I suggested >>> saying "Servers MUST NOT consider a message's size to be >>acceptable if >>> it has not expanded all BURL parts." I'm not wedded to that >>phrasing, >>> but I do think we should allow servers to reject messages before >>> expanding everything. >> >>I am not exactly happy with your replacement text, this might >>be too subtle for people to notice. I need to think about >>better alternatives. > I would prefer writing it down as well. I am not sure how to put it > though. Here is another attempt: > LEMONADE compliant mail submission servers MUST resolve all BURL parts > before enforcing a message size limit and MUST NOT reject email messages > where the total size of the email message reassembled from BURL parts is > smaller than the message size limit. The problem with that text is that the first sentence is identical to the original text and thus doesn't fix the flaw that I discuss (see the quoted text from me, above). The new suggested text I sent in yesterday does fix it and also addresses Alexey's concerns. Also, the second sentence in your text doesn't permit servers to reject messages for any reason other than size, which I'm sure isn't your intent :-) -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly-selected tag: --------------- I make a fortune from criticizing the policy of the government, and then hand it over to the government in taxes to keep it going. --George Bernard Shaw _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Tue Oct 31 15:21:18 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gf06n-0007vQ-Su; Tue, 31 Oct 2006 15:21:17 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gf06n-0007vE-8B for lemonade@ietf.org; Tue, 31 Oct 2006 15:21:17 -0500 Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gf06k-0003K9-0U for lemonade@ietf.org; Tue, 31 Oct 2006 15:21:17 -0500 Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148]) by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id k9VKLBp8001810 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 31 Oct 2006 12:21:12 -0800 Received: from [loud.qualcomm.com] (loud.qualcomm.com [129.46.172.15]) by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k9VKL4d6016257; Tue, 31 Oct 2006 12:21:06 -0800 (PST) Mime-Version: 1.0 Message-Id: In-Reply-To: <0FA975F2D8295A448BE3ADC1612446570185DB47@esebe199.NOE.Nokia.com> References: <0FA975F2D8295A448BE3ADC1612446570185DB47@esebe199.NOE.Nokia.com> X-Mailer: Eudora for Mac OS X X-message-flag: Warning: Outlook in use. Upgrade to Eudora: Date: Tue, 31 Oct 2006 12:20:51 -0800 To: , From: Randall Gellens Subject: RE: [lemonade] I-D ACTION:draft-ietf-lemonade-compress-05.txt - comments Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Random-Sig-Tag: 1.0b28 X-Spam-Score: 0.6 (/) X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac 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 At 4:22 PM +0200 10/31/06, wrote: > 3. Wording change suggestion in section 3: > OK The server will compress its responses and expects the client to > compress its commands. > to: > OK The server and the client will compress all data that it may send "data that it may send" sounds funny. The original text is very clear about which side compresses what (commands versus responses). Is there something about it you don't like? > 4. Wording change suggestion in section 3: > The client MUST NOT send any further commands until it has seen the > result of COMPRESS. > to: > After the client has sent the COMPRESS command, the client MUST NOT > send any commands until it has seen the result of COMPRESS. I think the original wording is better as it is more compact and says what it needs to. But perhaps I'm missing something. What about it don't you like? > 5. Clarification/wording change suggestion in section 3: > (Responses issued by the server before the OK response will, of > course, still be uncompressed.) > to: > Therefore, responses issued by the server before the OK response > will all be uncompressed, and delayed client requests that have > been sent uncompressed (before turning compression on) may result > in compressed responses. What are "delayed client requests"? Do you mean commands sent by the client before it sent COMPRESS that were delayed by underlying network (perhaps routed differently)? Or do you mean something else? If the server receives uncompressed commands after it has sent the OK to COMPRESS, will it interpret them correctly? The original text implies no, but your suggested text states yes. > 7. Wording change suggestion in section 4: > the same way as is recommended for servers > the same way as it is recommended for servers later Why do you want to change "as is" to "as it is"? The suggested wording sounds awkward to me, and implies that a source other than this draft is doing the recommending. > 9. Question in section 5: > capability =/ "COMPRESS=" algorithm > ;; multiple COMPRESS capabilities allowed > So, if I had multiple algorithms, would it be COMPRESS=1,2,3 or > COMPRESS=1,COMPRESS=2,COMPRESS=3? I would guess the second. That's correct, and matches what has been done for some other extensions. Note that the ABNF for your first alternate would be "COMPRESS=" algorithm *( "," algorithm ) > 12. Wording change suggestion in section 7: > and another compression is added at that time, it would then be > appropriate to create a registry > to: > and any additional compression algorithms are introduced at that > time, then the registry should be created This looks good to me. -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly-selected tag: --------------- If you don't care where you are, then you ain't lost. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Tue Oct 31 16:24:41 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gf15q-00083o-B2; Tue, 31 Oct 2006 16:24:22 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gf15o-00083Z-BS for lemonade@ietf.org; Tue, 31 Oct 2006 16:24:21 -0500 Received: from smtp-out.sendmail.com ([209.246.26.45]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gf15m-0001zJ-Ud for lemonade@ietf.org; Tue, 31 Oct 2006 16:24:20 -0500 Received: from vanye.mho.net (adsl-64-58-1-252.mho.net [64.58.1.252] (may be forged)) (authenticated bits=0) by foon.sendmail.com (Switch-3.2.5/Switch-3.2.0) with ESMTP id k9VLNoFE023766 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 31 Oct 2006 13:23:53 -0800 X-DKIM: Sendmail DKIM Filter v0.5.1 foon.sendmail.com k9VLNoFE023766 DKIM-Signature: a=rsa-sha1; c=relaxed/simple; d=sendmail.com; s=tls.dkim; t=1162329839; bh=l0Tuz/9hKeljjqtFG4wrWdRzWdM=; h=X-DomainKeys: DomainKey-Signature:Date:From:X-X-Sender:To:cc:Subject:In-Reply-To: Message-ID:References:MIME-Version:Content-Type; b=bASnEj2mWEaqRK0I 9o273H0UQP3HTUoZbLaDMG5oCmMBkj6Eu0Oy2rTSkgHE5Rp4fm+HVljwFsq8kI5TQUf X+HWCX5gqqMQf9q4k4zHTvvmHtsSqnVlg59q5bKBvFkyW4dI63DXVursVB2WNE0LRBS Pvr8m7JF1WSP7p3UJ49No= X-DomainKeys: Sendmail DomainKeys Filter v0.4.1 foon.sendmail.com k9VLNoFE023766 DomainKey-Signature: a=rsa-sha1; s=tls; d=sendmail.com; c=nofws; q=dns; h=date:from:x-x-sender:to:cc:subject:in-reply-to:message-id: references:mime-version:content-type; b=lNWYhWQu22Nc3GeOAHoiC1CznDZJW62sJscVmUIHmHuJeyLgUmyg1nyW6GiroCaz/ xX6P9UWhTsKBzC2q8SHNxOZ9takZjW0tLF3rj4VWa5qh4P1KnXkuHYxFu1I5CS318k7 tHszvDGQtBtZSgOfdx04DdkHqdlZAh3N9Je9XPc= Date: Tue, 31 Oct 2006 14:23:50 -0700 From: Philip Guenther X-X-Sender: guenther@vanye.mho.net To: Randall Gellens Subject: RE: [lemonade] I-D ACTION:draft-ietf-lemonade-compress-05.txt - comments In-Reply-To: Message-ID: References: <0FA975F2D8295A448BE3ADC1612446570185DB47@esebe199.NOE.Nokia.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Cc: lemonade@ietf.org, Zoltan.Ordogh@nokia.com 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 On Tue, 31 Oct 2006, Randall Gellens wrote: > At 4:22 PM +0200 10/31/06, wrote: ... >> 5. Clarification/wording change suggestion in section 3: >> (Responses issued by the server before the OK response will, of course, >> still be uncompressed.) >> to: >> Therefore, responses issued by the server before the OK response will all >> be uncompressed, and delayed client requests that have been sent >> uncompressed (before turning compression on) may result in compressed >> responses. > > What are "delayed client requests"? Do you mean commands sent by the client > before it sent COMPRESS that were delayed by underlying network (perhaps > routed differently)? Or do you mean something else? If the server receives > uncompressed commands after it has sent the OK to COMPRESS, will it interpret > them correctly? The original text implies no, but your suggested text states > yes. I think he's referring to commands that were sent before the COMPRESS command but that the server decided to process after the COMPRESS command. I suppose the client could pipeline CAPABILITY and COMPRESS commands together, in that order, and the server could handle them out of order. But I don't see why specific text is needed for this. For the server to client directory, everything received before a tagged OK response to the COMPRESS command is uncompressed. Everything after that is uncompressed. There are no exceptions. The more text we use here the more likely someone will think an exception is being described. ... >> So, if I had multiple algorithms, would it be COMPRESS=1,2,3 or >> COMPRESS=1,COMPRESS=2,COMPRESS=3? I would guess the second. It would be COMPRESS=1 COMPRESS=2 COMPRESS=3. Capabilities are separated by spaces, not commas. c.f. RFC 3501 page 25 for an example involving multiple AUTH= capabilities. Philip Guenther _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Tue Oct 31 16:48:43 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gf1Of-0002Db-0j; Tue, 31 Oct 2006 16:43:49 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gf1OZ-00028D-Nx for lemonade@ietf.org; Tue, 31 Oct 2006 16:43:43 -0500 Received: from kalyani.oryx.com ([195.30.37.30]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gf1J8-00034X-UO for lemonade@ietf.org; Tue, 31 Oct 2006 16:38:09 -0500 Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9]) by kalyani.oryx.com (Postfix) with ESMTP id 9DA1B4ACEC; Tue, 31 Oct 2006 22:37:59 +0100 (CET) Message-Id: Date: Tue, 31 Oct 2006 22:40:22 +0100 From: Arnt Gulbrandsen To: lemonade@ietf.org Subject: Re: [lemonade] I-D ACTION:draft-ietf-lemonade-compress-05.txt - comments References: <0FA975F2D8295A448BE3ADC1612446570185DB47@esebe199.NOE.Nokia.com> In-Reply-To: Content-Type: text/plain; format=flowed MIME-Version: 1.0 X-Spam-Score: 0.0 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Cc: Randall Gellens , Guenther , Philip, Zoltan.Ordogh@nokia.com 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 Philip Guenther writes: > On Tue, 31 Oct 2006, Randall Gellens wrote: >> At 4:22 PM +0200 10/31/06, wrote: > ... >>> 5. Clarification/wording change suggestion in section 3: >>> (Responses issued by the server before the OK response will, of >>> course, still be uncompressed.) >>> to: >>> Therefore, responses issued by the server before the OK response >>> will all be uncompressed, and delayed client requests that have >>> been sent uncompressed (before turning compression on) may result >>> in compressed responses. >> >> What are "delayed client requests"? Do you mean commands sent by the >> client before it sent COMPRESS that were delayed by underlying >> network (perhaps routed differently)? Or do you mean something >> else? If the server receives uncompressed commands after it has sent >> the OK to COMPRESS, will it interpret them correctly? The original >> text implies no, but your suggested text states yes. > > I think he's referring to commands that were sent before the COMPRESS > command but that the server decided to process after the COMPRESS > command. Or to commands/responses that the client/server has sent, but whose TCP segments were delayed en route. Since the receiver's TCP layer sorts that out I don't want to add text about it. Arnt _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Tue Oct 31 17:50:12 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gf2Qi-0002UO-9N; Tue, 31 Oct 2006 17:50:00 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gf2Qc-0002Th-1F for lemonade@ietf.org; Tue, 31 Oct 2006 17:49:54 -0500 Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gf2Qa-0002cA-Kt for lemonade@ietf.org; Tue, 31 Oct 2006 17:49:54 -0500 Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148]) by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id k9VMnod6025786 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 31 Oct 2006 14:49:51 -0800 Received: from [loud.qualcomm.com] (loud.qualcomm.com [129.46.172.15]) by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k9VMnjjj001585; Tue, 31 Oct 2006 14:49:49 -0800 (PST) Mime-Version: 1.0 Message-Id: In-Reply-To: References: <0FA975F2D8295A448BE3ADC1612446570185DB47@esebe199.NOE.Nokia.com> X-Mailer: Eudora for Mac OS X X-message-flag: Warning: Outlook in use. Upgrade to Eudora: Date: Tue, 31 Oct 2006 14:49:23 -0800 To: Philip Guenther From: Randall Gellens Subject: RE: [lemonade] I-D ACTION:draft-ietf-lemonade-compress-05.txt - comments 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: 69a74e02bbee44ab4f8eafdbcedd94a1 Cc: lemonade@ietf.org, Zoltan.Ordogh@nokia.com 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 2:23 PM -0700 10/31/06, Philip Guenther wrote: > On Tue, 31 Oct 2006, Randall Gellens wrote: >> At 4:22 PM +0200 10/31/06, wrote: > ... >>> 5. Clarification/wording change suggestion in section 3: >>> (Responses issued by the server before the OK response will, of >>> course, still be uncompressed.) >>> to: >>> Therefore, responses issued by the server before the OK response >>> will all be uncompressed, and delayed client requests that have >>> been sent uncompressed (before turning compression on) may result >>> in compressed responses. >> >> What are "delayed client requests"? Do you mean commands sent by >> the client before it sent COMPRESS that were delayed by underlying >> network (perhaps routed differently)? Or do you mean something >> else? If the server receives uncompressed commands after it has >> sent the OK to COMPRESS, will it interpret them correctly? The >> original text implies no, but your suggested text states yes. > > I think he's referring to commands that were sent before the > COMPRESS command but that the server decided to process after the > COMPRESS command. I suppose the client could pipeline CAPABILITY > and COMPRESS commands together, in that order, and the server could > handle them out of order. But I don't see why specific text is > needed for this. For the server to client directory, everything > received before a tagged OK response to the COMPRESS command is > uncompressed. Everything after that is uncompressed. There are no > exceptions. The more text we use here the more likely someone will > think an exception is being described. I agree. -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly-selected tag: --------------- Sorry, please try again. Thank you for taking the Turing test. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Tue Oct 31 17:50:17 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gf2Qi-0002VK-FN; Tue, 31 Oct 2006 17:50:00 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gf2Qc-0002U1-2r for lemonade@ietf.org; Tue, 31 Oct 2006 17:49:54 -0500 Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gf2Qa-0002cB-Kt for lemonade@ietf.org; Tue, 31 Oct 2006 17:49:54 -0500 Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148]) by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id k9VMnmqw025783 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 31 Oct 2006 14:49:49 -0800 Received: from [loud.qualcomm.com] (loud.qualcomm.com [129.46.172.15]) by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k9VMnjjh001585; Tue, 31 Oct 2006 14:49:47 -0800 (PST) Mime-Version: 1.0 Message-Id: In-Reply-To: <0FA975F2D8295A448BE3ADC1612446570185DBD3@esebe199.NOE.Nokia.com> References: <0FA975F2D8295A448BE3ADC1612446570185DBD3@esebe199.NOE.Nokia.com> X-Mailer: Eudora for Mac OS X X-message-flag: Warning: Outlook in use. Upgrade to Eudora: Date: Tue, 31 Oct 2006 14:49:15 -0800 To: , From: Randall Gellens Subject: RE: [lemonade] I-D ACTION:draft-ietf-lemonade-compress-05.txt - comments Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" ; format="flowed" Content-Transfer-Encoding: quoted-printable X-Random-Sig-Tag: 1.0b28 X-Spam-Score: 0.6 (/) X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac Cc: lemonade@ietf.org, arnt@oryx.com 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:59 PM +0200 10/31/06, wrote: > Well, we can put anything You like there - the=20 > reason I changed it because I did not like=20 > "expects". > Once compression is on, it will be compressed,=20 > right? The word "expects" to me hints that this=20 > is not the case. Good point. I read the use of "expects" as being=20 literally true: since the server expects that all=20 subsequent client commands are compressed, it=20 will decompress them before reading them. Keep in mind that the text we are discussing is=20 comment text in a server response, as opposed to=20 normative statements in the draft. As such, it=20 makes sense that it is written from the server's=20 point of view. A server could just as validly=20 say "OK foo bar gork" or "OK All my responses=20 will be compressed and you better compress all=20 your commands". > > Best regards: Zolt=E1n =D6rd=F6gh > E-mail: zoltan dot ordogh at nokia dot com > Phone: +358 50 386 0566 > > > >>-----Original Message----- >>From: ext Dave Cridland [mailto:dave@cridland.net] >>Sent: 31 October, 2006 16:42 >>To: Ordogh Zoltan (Nokia-TP-MSW/Tampere) >>Cc: Enhancements to Internet email to support diverse service >>enivronments; Arnt Gulbrandsen >>Subject: RE: [lemonade] I-D >>ACTION:draft-ietf-lemonade-compress-05.txt - comments >> >>On Tue Oct 31 14:22:08 2006, Zoltan.Ordogh@nokia.com wrote: >>> 3. Wording change suggestion in section 3: > >> OK The server will compress its responses and expects the client to > >> compress its commands. >>> to: >>> OK The server and the client will compress all data that it may send >>> >>> >>Most of these suggestions don't bother me either way, but this >>one strikes me as potentially misleading. One might read this >>as meaning that only literals and strings were compressed, >>rather than the entire protocol stream. It depends on what is >>meant by "data". >> >>The current wording is less confusing than this, and I think it's fine. >> >>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 -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly-selected tag: --------------- Program complexity grows until it exceeds the capability of the programmer who must maintain it. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Tue Oct 31 18:12:38 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gf2mc-00074W-1o; Tue, 31 Oct 2006 18:12:38 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gf2mZ-00074N-E9 for lemonade@ietf.org; Tue, 31 Oct 2006 18:12:35 -0500 Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gf2ls-0004qb-RZ for lemonade@ietf.org; Tue, 31 Oct 2006 18:12:35 -0500 Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151]) by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id k9VNBR6S030648 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Tue, 31 Oct 2006 15:11:52 -0800 Received: from [loud.qualcomm.com] (loud.qualcomm.com [129.46.172.15]) by crowley.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k9VN9iJ4017510; Tue, 31 Oct 2006 15:09:46 -0800 (PST) Mime-Version: 1.0 Message-Id: In-Reply-To: <0FA975F2D8295A448BE3ADC1612446570185DBB4@esebe199.NOE.Nokia.com> References: <0FA975F2D8295A448BE3ADC1612446570185DBB4@esebe199.NOE.Nokia.com> X-Mailer: Eudora for Mac OS X X-message-flag: Warning: Outlook in use. Upgrade to Eudora: Date: Tue, 31 Oct 2006 15:06:26 -0800 To: , , From: Randall Gellens Subject: RE: [lemonade] WGLC Deployments 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: 7baded97d9887f7a0c7e8a33c2e3ea1b 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:56 PM +0200 10/31/06, wrote: > 2. Wording change suggestion in section 3: > "It should be noted that systems which don't support TCP on > arbitrary ports aren't full Internet clients." > to: > "Noted that systems which do not support TCP on arbitrary ports are > not considered full Internet clients." Why? > 3. Missing reference in section 4: > "The requirements and advice in [HOST-REQUIREMENTS] SHOULD be followed." > I do not have a clue what it includes, so I cannot really comment > on it apart from adding the reference, but I think that this sounds > better: > [HOST-REQUIREMENTS] includes a collection of requirements and > advices, which SHOULD be followed and considered by all lemonade > depoyments. How is the reference missing? It's there. However, I have moved it from Informative to Normative. > 4. Incorrect reference in section 4.1 > as permitted by the protocol (see [SUBMISSION] or [PROFILE]) > PROFILE does not describe it - well, at least I could not find it. > While at it, You might want to add to the references the correct > RFC number, PROFILE is still referenced as a draft. Thank you. I've corrected the reference here to be IMAP, not PROFILE. I also updated PROFILE to refer to the RFC instead of saying "RFC Editor's queue". -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly-selected tag: --------------- A Sunday school is a prison in which children do penance for the evil conscience of their parents. --H. L. Mencken _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade