From lemonade-bounces@ietf.org  Wed Oct  1 11:31:01 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 708873A6A7D;
	Wed,  1 Oct 2008 11:31:01 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 39CF13A6917
	for <lemonade@core3.amsl.com>; Wed,  1 Oct 2008 11:31:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id YEIK-dAvJUWx for <lemonade@core3.amsl.com>;
	Wed,  1 Oct 2008 11:30:58 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19b.inmotionhosting.com
	[66.117.3.189]) by core3.amsl.com (Postfix) with ESMTP id 74D0A3A6A33
	for <lemonade@ietf.org>; Wed,  1 Oct 2008 11:30:17 -0700 (PDT)
Received: from [64.115.208.2] (port=31365 helo=[10.0.0.43])
	by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.68) (envelope-from <eburger@standardstrack.com>)
	id 1Kl6SQ-0004LL-JD
	for lemonade@ietf.org; Wed, 01 Oct 2008 11:29:56 -0700
Message-Id: <017628E4-F698-4FE4-A3B7-8BB8AF81C651@standardstrack.com>
From: Eric Burger <eburger@standardstrack.com>
To: lemonade@ietf.org
In-Reply-To: <EE9C5353-63ED-4D6A-8A72-BBFCCC619115@noware.co.uk>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 1 Oct 2008 14:29:57 -0400
References: <67980E1E-10BD-419D-9989-2FA1F176C022@noware.co.uk>
	<13073304-D8ED-443D-8712-0EAD560F993A@standardstrack.com>
	<E2vzVloFHx1bdtPVpD7xHQ.md5@lochnagar.oryx.com>
	<4D9EBFB3-7FBF-407B-9239-58475DFAECA0@noware.co.uk>
	<tNasjzU+8A9iOtNviybCCw.md5@lochnagar.oryx.com>
	<144F118B-9A41-405E-9EB9-18F3FB60405B@noware.co.uk>
	<E989572A-EF04-4930-A776-33F043FE82E4@standardstrack.com>
	<EE9C5353-63ED-4D6A-8A72-BBFCCC619115@noware.co.uk>
X-Mailer: Apple Mail (2.929.2)
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Subject: [lemonade] "submit+" versus "stream+"
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0349353894=="
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org


--===============0349353894==
Content-Type: multipart/signed; boundary=Apple-Mail-46--234538176; micalg=sha1; protocol="application/pkcs7-signature"


--Apple-Mail-46--234538176
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

Below is a thread discussing the relative merits of considering the  
semantics of "submit+" URLAUTH use. The key positions:

POSITION 1: "submit+" really means "the client gets a pawn ticket for  
an object for the client to give to someone else".

POSITION 2: "submit+" means "the client gets a pawn ticket for the  
purposes of fetching for submission", which means that for streaming,  
we will need a "streaming+", which means "the client gets a pawn  
ticket for the purposes of fetching for streaming", and when someone  
comes up with another reason for getting a pawn ticket for passing to  
someone else, someone will have to create a new "mumble+" prefix for  
URLAUTH.

Pro's of POSITION 2:
The client is somewhat explicit on why it is requesting a URLAUTH  
token, and when the third party accesses the IMAP store, the IMAP  
store (which generated the ticket) can do separate ACL processing or  
logging based on the purpose of the URLAUTH token (e.g., submit versus  
streaming versus mumble).

There was some discussion that an IMAP server might restrict the kinds  
of MIME types it would release to a streaming server versus a submit  
server. However, in practice it is clear there is no distinction.  
Other than filtering viruses, a streaming server actually can stream  
most any type. For example, an open office document could be spoken as  
text-to-speech and an image could be rendered as a streaming video to  
a video phone.

Pro's of POSITION 1:
The client does not need to consider why it is grabbing a URLAUTH  
token; it just grabs one. This is not an issue today with POSITION 2:  
a client that is composing a message knows to request a submit+ token  
and a client that wants streaming will request a stream+ token. The  
problem comes in when a new application wants to have access to an  
IMAP body part that is neither for submit processing nor streaming.  
The likelihood of the application developers going through the process  
of writing an RFC to register a new mumble+ token and then getting the  
entire IMAP Server community to adopt it is virtually zero. Moreover,  
while POSITION 1 offers the ability for the IMAP server to do  
something "special" for submit+ versus stream+, it is not clear the  
IMAP server will (or can) do anything different in practice. In  
addition, there is no protocol mechanism to prevent an application  
from using submit+ for another purpose. Thus in practice there is no  
distinction between submit+ versus stream+, which means wasted,  
duplicated code that does no useful work.

To be clear: What we are talking about here is expanding the semantic  
of "submit+" to mean "request from a thrid-party client on behalf of  
the client."

<With Chair hat off>
I'm against writing code that never gets used.

<With Chair hat on>
RFC 4467 is done. Using something other than "submit+" for streaming  
means a much longer cycle on getting streaming done. If there is no  
difference in protocol, scale, or security, our preference as Chairs  
is to take the path of least resistance.

PLEASE REGISTER YOUR CHOICE OR AMBIVALENCE SOON

Note: given the text currently says "submit+", what we are looking for  
here is one of:
[ ] I like "submit+" means "third-party request"
[ ] I like the idea of "submit+" meaning "third-party request", but I  
am not comfortable with the token being called "submit"
[ ] I don't like the idea of "submit+" meaning "third-party request",  
but I can live with it
[ ] I just realized the reason why "submit+" meaning "third-party  
request" will damage the Internet
[ ] Here is the reason "stream+" is the only way to go

On Sep 25, 2008, at 8:40 AM, Neil Cook wrote:

> Eric,
>
> I'm not sure I agree with the specifics of some of your arguments,  
> but I do agree with your conclusions - see below.
>
> Neil
>
> On 24 Sep 2008, at 23:55, Eric Burger wrote:
>
>> What we are talking about here is not "Who may fetch parts for the  
>> purposes of submission?" versus "Who may fetch parts for the  
>> purposes of streaming?", but rather "Who may fetch parts?" From the  
>> perspective of the IMAP Server, the protocol interaction, and  
>> physics, these three questions are identical and collapse down to  
>> "Who may fetch parts?" As far as the IMAP server is concerned, some  
>> third-party server connects to the IMAP Server and asks for a bunch  
>> of bytes. Since there IS NO PROGRAMATIC WAY to prevent a Submit  
>> Server from streaming the fetched IMAP part or to PREVENT a  
>> Streaming (Media) Server from submitting the data, there is no  
>> sensible distinction between the two.
>>
>
> This is not absolutely true. The submit+ prefix means that the URL  
> can only be retrieved by  those entities that, when logged in to the  
> IMAP server have a "submit+" authorization level. Similarly the  
> stream+ prefix means that the URL can only be retrieved by those  
> entities that have a "stream+" authorization level.
>
> So this absolutely *does* programmatically prevent a submit server  
> from retrieving the content specified by a URL that contains the  
> stream+ prefix. It could fetch content specified with a URL that  
> contains the submit+ prefix, and choose to stream that it if wished.  
> Similarly a streaming media server would not have the "submit" role  
> on the IMAP server.
>
> But the point you are making is that once the content has been  
> fetched, there is nothing preventing the retriever of that content  
> from doing whatever they like with it, which is a fair point.
>
>> If I am an evil Media Server, and you request me to fetch  
>> something, then I can steal your content because you asked me to  
>> fetch something. I don't see how specifying the purpose of the  
>> content fetch to be streaming changes anything. Whether I  
>> legitimately stream the data, I stream the data and steal a copy,  
>> or I just steal the copy, is something that I do NOT see a  
>> cryptographic (or naming convention, for that matter) way to fix.
>
> "stream+" (and indeed submit+) does more than specify the purpose of  
> the content fetch. It specifically restricts such fetching to  
> entities that have established a prior trust relationship with the  
> IMAP server for the purposes of fetching data to be streamed. But  
> again I see your point - is there anything fundamentally different  
> about the trust relationship with submit+ servers and stream+  
> servers? Probably not.
>
>>
>> I would offer one of three solutions. The first solution is to just  
>> state, "submit+" means the IMAP server MUST validate the source of  
>> the request. In plain English, the Media Server must be in some ACL  
>> at the IMAP Server. The second solution is to create a "stream+"  
>> prefix, which is a 100% cut-and-paste of "submit", substituting  
>> "message submission entity" with "streaming entity." The third is  
>> to punt entirely and state in the Security Considerations section  
>> that the IMAP Server and the Media Server SHOULD have some trust  
>> relationship, such as an ACL, host certificates, or physical  
>> security, because bad things can happen if you don't.
>>
>> Creating a "stream+" prefix duplicates a bunch of text and  
>> semantics. These semantics have no distinction in the real world.  
>> Thus I welcome $100 bets this duplication of text and semantics,  
>> without any distinction in the real world, will generate errors in  
>> the RFC and interoperability problems in the real world.
>>
>> In short, I offer we mention in the Streaming draft we use the  
>> submit+ mechanism to let the IMAP Server authenticate the Media  
>> Server. We issue an RFC Errata saying when we said "message  
>> submission entity" in RFC 4467, we meant "entity."
>>
>> Some may object, saying "submit+" does not look like "trusted_entity 
>> +". I would offer the following. We are talking about the octet  
>> stream 73 74 72 65 61 6d, which, by sheer coincidence, spells  
>> "submit", but really is just a unique octet stream that means  
>> "trusted entity." Second, RFC 4467 is done and does not need any  
>> changes to make a Media Server, or other trusted third-party- 
>> trusted server, work.
>
> The main reasons I can see for distinguishing betweeen "submit+" and  
> "stream+" are administrative in nature, such as IMAP server  
> administrators being able to track the statistics for URLs retrieved  
> for streaming purposes separately from those retrieved for submit  
> purposes.
>
> In short however, I think administrative benefits are probably not  
> worth the effort of adding "stream+", so I agree with the proposal  
> to use submit+, and to modify the semantics of that prefix to mean  
> "trusted entity". This also solves the problem more generically, as  
> I'm sure there will be further uses of IMAP URLs in the future that  
> require a way to indicate that access should be restricted to  
> trusted entities.
>
> Actually, I just had an idea - the submit+ syntax specifies that a  
> username follows it, even though that username is ignored by the  
> IMAP server. I could simply recommend that clients use the username  
> "stream", as a hint for admins.
>
> Neil
>
>>
>> Thoughts?
>>
>>
>> --
>> - Eric
>>
>>
>> On Sep 24, 2008, at 10:00 AM, Neil Cook wrote:
>>
>>> Arnt,
>>>
>>> Access to the media server is via SIP, which already has has  
>>> mechanisms to restrict access to authorized users, such as by  
>>> requesting authentication. For example, media servers might allow  
>>> unauthenticated access from clients in the same administrative  
>>> domain, but request credentials (or deny access) from clients in a  
>>> different administrative domain.
>>>
>>> In my opinion, the above mechanisms (policies for which would be  
>>> in place regardless of streaming) would be enough to make such  
>>> attacks as you describe below extremely difficult/unlikely. Media  
>>> servers are extremely unlikely to allow access to the resources  
>>> from any old network, and if they did, they probably wouldn't  
>>> qualify to be included in the list of trusted servers. However, I  
>>> think the possibility of this type of attack should be mentioned  
>>> in the Security Considerations section.
>>>
>>> Neil
>>>
>>> On 24 Sep 2008, at 13:35, Arnt Gulbrandsen wrote:
>>>
>>>> Neil Cook writes:
>>>>> The concern is about trust in the media server, i.e. that the  
>>>>> client  is passing a URI to a media server that may or may not  
>>>>> be trusted to  do the right thing with the content. What this  
>>>>> proposes is a way to  restrict the URL from being used by media  
>>>>> servers that are not trusted  by the IMAP server.
>>>>
>>>> An untrusted malevolent media server can use the data if it can  
>>>> guess the name of an a trusted media server.
>>>>
>>>> An innocent end user requests stream from an untrusted media  
>>>> server, which turns around, guesses a trusted server, connects to  
>>>> it, forwards the request and the stream and does something evil  
>>>> while forwarding.
>>>>
>>>> This attack breaks down if either a) media servers tend to be  
>>>> secure against MITM attacks or b) guessing the name of the  
>>>> trusted media server is really difficult.
>>>>
>>>> I guess I'm for or against the change depending on whether this  
>>>> attack works or not.
>>>>
>>>> Arnt
>>>
>>
>


--Apple-Mail-46--234538176
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGPTCCBjkw
ggUhoAMCAQICEC+VK1RLWxrF8KJZDR9k8p8wDQYJKoZIhvcNAQEFBQAwga4xCzAJBgNVBAYTAlVT
MQswCQYDVQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VS
VFJVU1QgTmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQD
Ey1VVE4tVVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwwHhcNMDgwODEz
MDAwMDAwWhcNMDkwODEzMjM1OTU5WjCB4TE1MDMGA1UECxMsQ29tb2RvIFRydXN0IE5ldHdvcmsg
LSBQRVJTT05BIE5PVCBWQUxJREFURUQxRjBEBgNVBAsTPVRlcm1zIGFuZCBDb25kaXRpb25zIG9m
IHVzZTogaHR0cDovL3d3dy5jb21vZG8ubmV0L3JlcG9zaXRvcnkxHzAdBgNVBAsTFihjKTIwMDMg
Q29tb2RvIExpbWl0ZWQxFDASBgNVBAMTC0VyaWMgQnVyZ2VyMSkwJwYJKoZIhvcNAQkBFhplYnVy
Z2VyQHN0YW5kYXJkc3RyYWNrLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMTF
RRoA4LgOACMFph0aomRC/UpqoA5C/d6DUTOvTMrYSEqkjwnU4zxDtBcHlcB4AxKAov00MYsUvEU4
loz7BHjfDjv76AIkcwu33VYQbzGmarVnyaXsVb6f/cyRL3fPT0VOVO2tQAEEgwg//CX0jN8Kn2jH
uXD/HEvko7cmpL3Pwevf3+DwB61v7ca79PpEZfn/WhaqRKA4uVNPj/JbieeaLo2v/0RJzrEElZK0
pHCqxiD3mQ8ossPkA9fUCSxLlbdMcPU3be5x8vt8Q8mYTXF5Z3d9RZmYrmNkvTQtdzVpfYWr/hgV
Xqm9tByOOAR+hoN3FKbubR/OrAHL9yDAd4sCAwEAAaOCAhwwggIYMB8GA1UdIwQYMBaAFImCZ33E
nSZwAEu0UEh83j2uBG59MB0GA1UdDgQWBBRDWgutb7b8R/L7G3Y3D+molAA3VzAOBgNVHQ8BAf8E
BAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggrBgEFBQcDBAYLKwYBBAGyMQEDBQIwEQYJ
YIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQEBMCswKQYIKwYBBQUHAgEW
HWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMIGlBgNVHR8EgZ0wgZowTKBKoEiGRmh0dHA6
Ly9jcmwuY29tb2RvY2EuY29tL1VUTi1VU0VSRmlyc3QtQ2xpZW50QXV0aGVudGljYXRpb25hbmRF
bWFpbC5jcmwwSqBIoEaGRGh0dHA6Ly9jcmwuY29tb2RvLm5ldC9VVE4tVVNFUkZpcnN0LUNsaWVu
dEF1dGhlbnRpY2F0aW9uYW5kRW1haWwuY3JsMGwGCCsGAQUFBwEBBGAwXjA2BggrBgEFBQcwAoYq
aHR0cDovL2NydC5jb21vZG9jYS5jb20vVVROQUFBQ2xpZW50Q0EuY3J0MCQGCCsGAQUFBzABhhho
dHRwOi8vb2NzcC5jb21vZG9jYS5jb20wJQYDVR0RBB4wHIEaZWJ1cmdlckBzdGFuZGFyZHN0cmFj
ay5jb20wDQYJKoZIhvcNAQEFBQADggEBAGeBR7NPCvrY3GQoIi49JOuciatY2r4st905Jw1etp6J
umFFWlaCBl11tFSclk/3S45B+lUv3SEvG4CEjUByPScprVmCqHR+y8BAQaB/CV+N1y14x3MbhJ+Z
8XDGKeUXuuyGd9w0l3/t/QPid6TRXQjQFrLPFs1IALuNpNiFMHEF/xFbMG1Z2vznR/gSPlePekoZ
TqcExIDBNZTBebpZqwAXzPpedNNOclbMLFLWDMOAozVRpkfjI0eiFsk8SF1Ho1Gb9Bx8DeG4peE2
KRVOR9FFnZZgBpFjXYRcglsMOSKCY8HgE+NGvbbqbrMoBV/BlYyxRXwfti71RL9Zs2Cq1eQxggP8
MIID+AIBATCBwzCBrjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExh
a2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8v
d3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkNH2TynzAJBgUrDgMCGgUAoIICDTAYBgkqhkiG
9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wODEwMDExODI5NThaMCMGCSqGSIb3
DQEJBDEWBBTorjrI2yAB9uispI4tHG9yxB7rIDCB1AYJKwYBBAGCNxAEMYHGMIHDMIGuMQswCQYD
VQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVU
aGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2
MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhAv
lStUS1saxfCiWQ0fZPKfMIHWBgsqhkiG9w0BCRACCzGBxqCBwzCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVU
Ti1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkN
H2TynzANBgkqhkiG9w0BAQEFAASCAQCz8zb29zxH6S81UV5kj9zaq2K9Kq7FRYijGhAQiW1WLIar
CMIJ13ZqISmFtRoxlylwz2MB60xx6xLM3ioEDS8Id3YGG5bHHfwo2LUwomNCIG7TAifZIoXzgE0f
WOVPa/Si0HfQRmNuz0XXDJZyQA0pZZtmnnRSfu0Wc2kgPt/mHXEcvVetbbiDlZ2W86Mq1+uShmiE
1x/OW1zWN4+nKSNUQRpdOYuk/hzzKB5TfwfD0gSpNDb2M5pft5CRQ1dINQ8Fz4+IXUNwY7NX9/lK
+FEFRhOQPqOmeZuNwZizcyZg/z7Znsvw/mRP4hdJAKLgj2k7GJ6MhIokLRUVhIT5+siiAAAAAAAA

--Apple-Mail-46--234538176--

--===============0349353894==
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://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade
--===============0349353894==--


From lemonade-bounces@ietf.org  Wed Oct  1 12:08:27 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9606E3A6909;
	Wed,  1 Oct 2008 12:08:27 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9059A3A6909
	for <lemonade@core3.amsl.com>; Wed,  1 Oct 2008 12:08:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id R8fIC8+nMsFT for <lemonade@core3.amsl.com>;
	Wed,  1 Oct 2008 12:08:25 -0700 (PDT)
Received: from zcars04f.nortel.com (zcars04f.nortel.com [47.129.242.57])
	by core3.amsl.com (Postfix) with ESMTP id 00BC23A6405
	for <lemonade@ietf.org>; Wed,  1 Oct 2008 12:08:24 -0700 (PDT)
Received: from zcarhxm0.corp.nortel.com (zcarhxm0.corp.nortel.com
	[47.129.230.95])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m91J5Ir09130 for <lemonade@ietf.org>; Wed, 1 Oct 2008 19:05:18 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 1 Oct 2008 15:05:14 -0400
Message-ID: <085091CB2CA14E4B8B163FFC37C84E9D16A2836D@zcarhxm0.corp.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WGLC: The Lemonade Profile
Thread-Index: AcjzODTLBhWoqWS7TwKKe6RDcbgnDgwvvw2w
From: "Glenn Parsons" <gparsons@nortel.com>
To: <lemonade@ietf.org>
Subject: [lemonade] WGLC: The Lemonade Profile
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

Folks,

After years of hard work, the end is in sight :-)  With all of our
documents either completed or in IESG processing, it is time to conclude
on the definitive WG document.

This is the initiation of a two week WG last call on LEMONADE
Profile-bis.  The WGLC will close on Oct 16th.

The document details are:

	Title           : The Lemonade Profile
	Author(s)       : D. Cridland, et al.
	Filename        : draft-ietf-lemonade-profile-bis-11.txt
	Pages           : 37
	Date            : 2008-09-30

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 several extensions to IMAP and Mail
Submission protocols.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-lemonade-profile-bis-11.t
xt 


Cheers,
Glenn.
_______________________________________________
lemonade mailing list
lemonade@ietf.org
https://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade


From lemonade-bounces@ietf.org  Wed Oct  1 12:18:41 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 98CE43A68D3;
	Wed,  1 Oct 2008 12:18:41 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AB7053A68D3
	for <lemonade@core3.amsl.com>; Wed,  1 Oct 2008 12:18:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id JoDJb9kxMWAX for <lemonade@core3.amsl.com>;
	Wed,  1 Oct 2008 12:18:39 -0700 (PDT)
Received: from zrtps0kn.nortel.com (zrtps0kn.nortel.com [47.140.192.55])
	by core3.amsl.com (Postfix) with ESMTP id 7BD193A686E
	for <lemonade@ietf.org>; Wed,  1 Oct 2008 12:18:39 -0700 (PDT)
Received: from zcarhxm0.corp.nortel.com (zcarhxm0.corp.nortel.com
	[47.129.230.95])
	by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m91JIwY29743 for <lemonade@ietf.org>; Wed, 1 Oct 2008 19:18:59 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 1 Oct 2008 15:18:08 -0400
Message-ID: <085091CB2CA14E4B8B163FFC37C84E9D16A283B4@zcarhxm0.corp.nortel.com>
In-Reply-To: <085091CB2CA14E4B8B163FFC37C84E9D16A2836D@zcarhxm0.corp.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [lemonade] WGLC: The Lemonade Profile
Thread-Index: AcjzODTLBhWoqWS7TwKKe6RDcbgnDgwvvw2wAACL0eA=
References: <085091CB2CA14E4B8B163FFC37C84E9D16A2836D@zcarhxm0.corp.nortel.com>
From: "Glenn Parsons" <gparsons@nortel.com>
To: <lemonade@ietf.org>
Subject: Re: [lemonade] WGLC: The Lemonade Profile
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

Folks,

Here are some editorial comments I have on
<draft-ietf-lemonade-profile-bis-11.txt>:

 - add to the top left front page header either (I prefer the first)
   Obsoletes: 4550    or   Updates: 4550

 - I would update the abstract to read:
  "...), dubbed Lemonade, of the IMAP and Internet Mail submission
protocols."

 - sort the extensions listed in the tables in section 3 by the section
that they are described in, or reorder the section based on their
listing in the tables of section 3...

 - given there is MUA description in 7, there should be a section 3.4
table summary.  It should list IMAP and SUBMIT ... Or we could list a
table of SHOULDs since that is what is in section 7.

 - in section 5.2:  in turns -> in turn

 - in section 5.4:  ransforms -> transforms

 - in section 5.4:  PUSH -> "push email"

 - is it i;unicode-casemap as in 6 _or_ comparator-i;unicode-casemap as
in 3?

 - we should add some of the history of the Lemonade name in an
informative section at the end ... as someone (not me) correctly
recorded on Wikipedia...
   http://en.wikipedia.org/wiki/Lemonade_Profile
    Actually, this would probably go better at the end of an
informational document like Lemonade architecture... But here is fine as
well.

 - And on that point, we need to add Lemonade architecture --
[LEMONADE-ARCH] <draft-ietf-lemonade-architecture-03.txt> to the
information references.  And then add this sentence to the end of 2 to
introduce it:
 "The LEMONADE WG used the architecture shown in [LEMONADE-ARCH] to
develop the Lemonade Profile."

 - Also add [LEMONADE-NOTIFICATIONS]
<draft-ietf-lemonade-notifications-10.txt > to the informative
references.  And then add this sentence to the end of the first
paragraph of 5.4:
 "The LEMONADE WG used the notifications architecture shown in
[LEMONADE-NOTIFICATIONS] to develop the Lemonade Profile."

Finally, given this has been a significant effort of the LEMONADE WG,
you should note that this is the definitive output of the LEMONADE WG,
again near the end.  And you could even add add that the LEMONADE WG was
chaired by Eric and I. :-)
 
Cheers,
Glenn.

-----Original Message-----
From: lemonade-bounces@ietf.org [mailto:lemonade-bounces@ietf.org] On
Behalf Of Parsons, Glenn (CAR:1A14)
Sent: Wednesday, October 01, 2008 3:05 PM
To: lemonade@ietf.org
Subject: [lemonade] WGLC: The Lemonade Profile

Folks,

After years of hard work, the end is in sight :-)  With all of our
documents either completed or in IESG processing, it is time to conclude
on the definitive WG document.

This is the initiation of a two week WG last call on LEMONADE
Profile-bis.  The WGLC will close on Oct 16th.

The document details are:

	Title           : The Lemonade Profile
	Author(s)       : D. Cridland, et al.
	Filename        : draft-ietf-lemonade-profile-bis-11.txt
	Pages           : 37
	Date            : 2008-09-30

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 several extensions to IMAP and Mail
Submission protocols.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-lemonade-profile-bis-11.t
xt 


Cheers,
Glenn.
_______________________________________________
lemonade mailing list
lemonade@ietf.org
https://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade
_______________________________________________
lemonade mailing list
lemonade@ietf.org
https://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade


From lemonade-bounces@ietf.org  Thu Oct  2 04:25:38 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CA60F3A6CCA;
	Thu,  2 Oct 2008 04:25:38 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C4A193A6CCA
	for <lemonade@core3.amsl.com>; Thu,  2 Oct 2008 04:25:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[AWL=0.113, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Ksx-PyZznxhq for <lemonade@core3.amsl.com>;
	Thu,  2 Oct 2008 04:25:37 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251])
	by core3.amsl.com (Postfix) with ESMTP id E9A9F3A6CB3
	for <lemonade@ietf.org>; Thu,  2 Oct 2008 04:25:13 -0700 (PDT)
Received: from [172.16.2.129] (shiny.isode.com [62.3.217.250]) 
	by rufus.isode.com (submission channel) via TCP with ESMTPA 
	id <SOSvrwAxOVEV@rufus.isode.com>; Thu, 2 Oct 2008 12:25:35 +0100
Message-ID: <48E4AF8C.7030904@isode.com>
Date: Thu, 02 Oct 2008 12:25:00 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
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: Glenn Parsons <gparsons@nortel.com>
References: <085091CB2CA14E4B8B163FFC37C84E9D16A2836D@zcarhxm0.corp.nortel.com>
	<085091CB2CA14E4B8B163FFC37C84E9D16A283B4@zcarhxm0.corp.nortel.com>
In-Reply-To: <085091CB2CA14E4B8B163FFC37C84E9D16A283B4@zcarhxm0.corp.nortel.com>
MIME-Version: 1.0
Cc: lemonade@ietf.org
Subject: Re: [lemonade] WGLC: The Lemonade Profile
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

Hi Glenn,
I've either applied or in the process of applying all your changes but 
this one:

Glenn Parsons wrote:

> - is it i;unicode-casemap as in 6 _or_ comparator-i;unicode-casemap as
>in 3?
>  
>
This is not a bug: Sieve declares required comparators using 
"comparator-<comparator-name>".

_______________________________________________
lemonade mailing list
lemonade@ietf.org
https://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade


From lemonade-bounces@ietf.org  Thu Oct  2 04:50:04 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A722E28C1F4;
	Thu,  2 Oct 2008 04:50:04 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 165ED28C1EA
	for <lemonade@core3.amsl.com>; Thu,  2 Oct 2008 04:50:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.518
X-Spam-Level: 
X-Spam-Status: No, score=-2.518 tagged_above=-999 required=5 tests=[AWL=0.081, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id UeASgztiFMX7 for <lemonade@core3.amsl.com>;
	Thu,  2 Oct 2008 04:50:02 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251])
	by core3.amsl.com (Postfix) with ESMTP id E7CD83A6B51
	for <lemonade@ietf.org>; Thu,  2 Oct 2008 04:50:01 -0700 (PDT)
Received: from [172.16.2.129] (shiny.isode.com [62.3.217.250]) 
	by rufus.isode.com (submission channel) via TCP with ESMTPA 
	id <SOS1eAAxOSwE@rufus.isode.com>; Thu, 2 Oct 2008 12:50:16 +0100
Message-ID: <48E4B559.3060309@isode.com>
Date: Thu, 02 Oct 2008 12:49:45 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
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: Timo Sirainen <tss@iki.fi>
References: <20080922143001.5C6F43A6811@core3.amsl.com>
	<1222104404.21673.783.camel@hurina>
	<im/3N5GlsDYfThr0udPI1Q.md5@lochnagar.oryx.com>
	<1222107091.21673.800.camel@hurina>
In-Reply-To: <1222107091.21673.800.camel@hurina>
MIME-Version: 1.0
Cc: lemonade@ietf.org
Subject: [lemonade] Is draft-melnikov-imapext-filters-06.txt ready for
	publication?
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

Timo,
apart from the date error in an example, are you otherwise happy with 
the latest version?

_______________________________________________
lemonade mailing list
lemonade@ietf.org
https://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade


From lemonade-bounces@ietf.org  Thu Oct  2 05:39:45 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BF1C93A6847;
	Thu,  2 Oct 2008 05:39:45 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 347783A6C6F
	for <lemonade@core3.amsl.com>; Thu,  2 Oct 2008 05:39:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id sEICw-9tIDQU for <lemonade@core3.amsl.com>;
	Thu,  2 Oct 2008 05:39:44 -0700 (PDT)
Received: from zrtps0kn.nortel.com (zrtps0kn.nortel.com [47.140.192.55])
	by core3.amsl.com (Postfix) with ESMTP id 56B003A6832
	for <lemonade@ietf.org>; Thu,  2 Oct 2008 05:39:44 -0700 (PDT)
Received: from zcarhxm0.corp.nortel.com (zcarhxm0.corp.nortel.com
	[47.129.230.95])
	by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m92CcK115359; Thu, 2 Oct 2008 12:38:20 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 2 Oct 2008 08:38:19 -0400
Message-ID: <085091CB2CA14E4B8B163FFC37C84E9D16A287BA@zcarhxm0.corp.nortel.com>
In-Reply-To: <48E4AF8C.7030904@isode.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [lemonade] WGLC: The Lemonade Profile
Thread-Index: AckkgaFpCmkqjF7pQueIa1F4Clr/gQACYfQA
References: <085091CB2CA14E4B8B163FFC37C84E9D16A2836D@zcarhxm0.corp.nortel.com>
	<085091CB2CA14E4B8B163FFC37C84E9D16A283B4@zcarhxm0.corp.nortel.com>
	<48E4AF8C.7030904@isode.com>
From: "Glenn Parsons" <gparsons@nortel.com>
To: "Alexey Melnikov" <alexey.melnikov@isode.com>
Cc: lemonade@ietf.org
Subject: Re: [lemonade] WGLC: The Lemonade Profile
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

Alexey,

My point is that if it is "comparator-<comparator-name>" then the text
in 6 needs fixing:

   Lemonade Message Delivery Agents MUST support the i;unicode-casemap
comparator
   in Sieve [UNICODE-CASEMAP].  

Or are you saying that "i;unicode-casemap comparator" and
"comparator-i;unicode-casemap" are equivalent?

Cheers,
Glenn.

-----Original Message-----
From: Alexey Melnikov [mailto:alexey.melnikov@isode.com] 
Sent: Thursday, October 02, 2008 7:25 AM
To: Parsons, Glenn (CAR:1A14)
Cc: lemonade@ietf.org
Subject: Re: [lemonade] WGLC: The Lemonade Profile

Hi Glenn,
I've either applied or in the process of applying all your changes but
this one:

Glenn Parsons wrote:

> - is it i;unicode-casemap as in 6 _or_ comparator-i;unicode-casemap as

>in 3?
>  
>
This is not a bug: Sieve declares required comparators using
"comparator-<comparator-name>".

_______________________________________________
lemonade mailing list
lemonade@ietf.org
https://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade


From lemonade-bounces@ietf.org  Thu Oct  2 05:40:43 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E5A5A3A69DA;
	Thu,  2 Oct 2008 05:40:43 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CF2BE3A69DA
	for <lemonade@core3.amsl.com>; Thu,  2 Oct 2008 05:40:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.529
X-Spam-Level: 
X-Spam-Status: No, score=-2.529 tagged_above=-999 required=5 tests=[AWL=0.071, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id AHxhGpWcI7yj for <lemonade@core3.amsl.com>;
	Thu,  2 Oct 2008 05:40:42 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251])
	by core3.amsl.com (Postfix) with ESMTP id 9BD293A68E3
	for <lemonade@ietf.org>; Thu,  2 Oct 2008 05:40:41 -0700 (PDT)
Received: from [172.16.2.129] (shiny.isode.com [62.3.217.250]) 
	by rufus.isode.com (submission channel) via TCP with ESMTPA 
	id <SOTBEAAxORot@rufus.isode.com>; Thu, 2 Oct 2008 13:39:44 +0100
Message-ID: <48E4C0EF.7030801@isode.com>
Date: Thu, 02 Oct 2008 13:39:11 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
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: Glenn Parsons <gparsons@nortel.com>
References: <085091CB2CA14E4B8B163FFC37C84E9D16A2836D@zcarhxm0.corp.nortel.com>
	<085091CB2CA14E4B8B163FFC37C84E9D16A283B4@zcarhxm0.corp.nortel.com>
	<48E4AF8C.7030904@isode.com>
	<085091CB2CA14E4B8B163FFC37C84E9D16A287BA@zcarhxm0.corp.nortel.com>
In-Reply-To: <085091CB2CA14E4B8B163FFC37C84E9D16A287BA@zcarhxm0.corp.nortel.com>
MIME-Version: 1.0
Cc: lemonade@ietf.org
Subject: Re: [lemonade] WGLC: The Lemonade Profile
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

Glenn Parsons wrote:

>Alexey,
>
>My point is that if it is "comparator-<comparator-name>" then the text
>in 6 needs fixing:
>
>   Lemonade Message Delivery Agents MUST support the i;unicode-casemap
>comparator
>   in Sieve [UNICODE-CASEMAP].  
>
>Or are you saying that "i;unicode-casemap comparator" and
>"comparator-i;unicode-casemap" are equivalent?
>  
>
Yes. The latter is the name of the Sieve capability for the former.

>Cheers,
>Glenn.
>
>-----Original Message-----
>From: Alexey Melnikov [mailto:alexey.melnikov@isode.com] 
>Sent: Thursday, October 02, 2008 7:25 AM
>To: Parsons, Glenn (CAR:1A14)
>Cc: lemonade@ietf.org
>Subject: Re: [lemonade] WGLC: The Lemonade Profile
>
>Hi Glenn,
>I've either applied or in the process of applying all your changes but
>this one:
>
>Glenn Parsons wrote:
>
>  
>
>>- is it i;unicode-casemap as in 6 _or_ comparator-i;unicode-casemap as
>>    
>>
>
>  
>
>>in 3?
>> 
>>
>>    
>>
>This is not a bug: Sieve declares required comparators using
>"comparator-<comparator-name>".
>
>  
>

_______________________________________________
lemonade mailing list
lemonade@ietf.org
https://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade


From lemonade-bounces@ietf.org  Thu Oct  2 07:03:17 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6F2203A6C11;
	Thu,  2 Oct 2008 07:03:17 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4004C3A6A0C
	for <lemonade@core3.amsl.com>; Thu,  2 Oct 2008 07:03:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.25
X-Spam-Level: 
X-Spam-Status: No, score=-6.25 tagged_above=-999 required=5 tests=[AWL=0.349, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 5tkX4iGaGPLq for <lemonade@core3.amsl.com>;
	Thu,  2 Oct 2008 07:03:15 -0700 (PDT)
Received: from dovecot.org (dovecot.org [82.118.211.50])
	by core3.amsl.com (Postfix) with ESMTP id 681103A6C40
	for <lemonade@ietf.org>; Thu,  2 Oct 2008 07:03:15 -0700 (PDT)
Received: from [192.168.10.2] (xdsl-177-118.nblnetworks.fi [217.30.177.118])
	by dovecot.org (Postfix) with ESMTP id 07EF11647259;
	Thu,  2 Oct 2008 17:03:13 +0300 (EEST)
From: Timo Sirainen <tss@iki.fi>
To: Alexey Melnikov <alexey.melnikov@isode.com>
In-Reply-To: <48E4B559.3060309@isode.com>
References: <20080922143001.5C6F43A6811@core3.amsl.com>
	<1222104404.21673.783.camel@hurina>
	<im/3N5GlsDYfThr0udPI1Q.md5@lochnagar.oryx.com>
	<1222107091.21673.800.camel@hurina>  <48E4B559.3060309@isode.com>
Date: Thu, 02 Oct 2008 17:03:13 +0300
Message-Id: <1222956193.21673.902.camel@hurina>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.3.1 
Cc: lemonade@ietf.org
Subject: Re: [lemonade] Is draft-melnikov-imapext-filters-06.txt ready
	for	publication?
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0146823278=="
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org


--===============0146823278==
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-d2jnTUPaV63xrxgfLrJq"


--=-d2jnTUPaV63xrxgfLrJq
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Thu, 2008-10-02 at 12:49 +0100, Alexey Melnikov wrote:
> Timo,
> apart from the date error in an example, are you otherwise happy with=20
> the latest version?

Yes. Although I guess it would be nice if it showed an example about
listing filters, but that'd require knowing how the new metadata spec
does it.


--=-d2jnTUPaV63xrxgfLrJq
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEABECAAYFAkjk1KEACgkQyUhSUUBViskoqQCfTMQHV5NjjmuNB2FcGe5pKXC/
IzAAoKMyAYmRhwhjy7x6mkSjcB+pxOfV
=8XZl
-----END PGP SIGNATURE-----

--=-d2jnTUPaV63xrxgfLrJq--


--===============0146823278==
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://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade
--===============0146823278==--



From lemonade-bounces@ietf.org  Thu Oct  2 07:21:54 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9C4863A6960;
	Thu,  2 Oct 2008 07:21:54 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B3DA03A687B;
	Thu,  2 Oct 2008 07:21:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id gSEz6fTTVZWs; Thu,  2 Oct 2008 07:21:52 -0700 (PDT)
Received: from mta03.zimbra.com (mta03.zimbra.com [66.163.172.82])
	by core3.amsl.com (Postfix) with ESMTP id 035983A67E4;
	Thu,  2 Oct 2008 07:21:52 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mta03.zimbra.com (Postfix) with ESMTP id 08D5178315;
	Thu,  2 Oct 2008 07:21:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at 
Received: from mta03.zimbra.com ([127.0.0.1])
	by localhost (mta03.zimbra.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ip-NHp4vQxJg; Thu,  2 Oct 2008 07:21:26 -0700 (PDT)
Received: from dogfood.zimbra.com (dogfood.zimbra.com [207.126.229.140])
	by mta03.zimbra.com (Postfix) with ESMTP id A737A782B4;
	Thu,  2 Oct 2008 07:21:26 -0700 (PDT)
Date: Thu, 2 Oct 2008 07:21:24 -0700 (PDT)
From: Dan Karp <dkarp@zimbra.com>
To: Internet-Drafts@ietf.org
Message-ID: <666249820.6061222957284617.JavaMail.root@dogfood.zimbra.com>
In-Reply-To: <20080922143001.5C6F43A6811@core3.amsl.com>
MIME-Version: 1.0
X-Mailer: Zimbra 5.0.10_GA_2634.RHEL4_64 (ZimbraWebClient - SAF3
	(Win)/5.0.10_GA_2634.RHEL4_64)
Cc: lemonade@ietf.org, i-d-announce@ietf.org
Subject: Re: [lemonade] I-D Action:draft-melnikov-imapext-filters-06.txt
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

> 	Title           : IMAP4 extension for named searches (filters)
> 	Author(s)       : A. Melnikov, C. King
> 	Filename        : draft-melnikov-imapext-filters-06.txt
> 	Pages           : 11
> 	Date            : 2008-09-22
> 
> The document defines a way to persistently store named IMAP (RFC
> 3501) searches on the server.  Such named searches can be
> subsequently referenced in a SEARCH or any other command that accepts
> a search criteria as a parameter.

Quick question -- Do you really want to be storing filters in public
server metadata entries?  I know that it's the fallback and not the
default location to look, but what's the real-world use case?

Also, this should probably wait for publication until METADATA is out.
_______________________________________________
lemonade mailing list
lemonade@ietf.org
https://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade


From lemonade-bounces@ietf.org  Thu Oct  2 07:28:53 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 26BED3A6C6F;
	Thu,  2 Oct 2008 07:28:53 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4BB433A69E7
	for <lemonade@core3.amsl.com>; Thu,  2 Oct 2008 07:28:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id UosgxKAssy7d for <lemonade@core3.amsl.com>;
	Thu,  2 Oct 2008 07:28:51 -0700 (PDT)
Received: from mta03.zimbra.com (mta03.zimbra.com [66.163.172.82])
	by core3.amsl.com (Postfix) with ESMTP id 9BD7C3A6C11
	for <lemonade@ietf.org>; Thu,  2 Oct 2008 07:28:51 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mta03.zimbra.com (Postfix) with ESMTP id A06C178350
	for <lemonade@ietf.org>; Thu,  2 Oct 2008 07:22:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at 
Received: from mta03.zimbra.com ([127.0.0.1])
	by localhost (mta03.zimbra.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id le7imh7ktFjH for <lemonade@ietf.org>;
	Thu,  2 Oct 2008 07:22:30 -0700 (PDT)
Received: from dogfood.zimbra.com (dogfood.zimbra.com [207.126.229.140])
	by mta03.zimbra.com (Postfix) with ESMTP id 49D987833F
	for <lemonade@ietf.org>; Thu,  2 Oct 2008 07:22:30 -0700 (PDT)
Date: Thu, 2 Oct 2008 07:22:28 -0700 (PDT)
From: Dan Karp <dkarp@zimbra.com>
To: Enhancements to Internet email to support diverse service enivronments
	<lemonade@ietf.org>
Message-ID: <549368728.6181222957348441.JavaMail.root@dogfood.zimbra.com>
In-Reply-To: <666249820.6061222957284617.JavaMail.root@dogfood.zimbra.com>
MIME-Version: 1.0
X-Mailer: Zimbra 5.0.10_GA_2634.RHEL4_64 (ZimbraWebClient - SAF3
	(Win)/5.0.10_GA_2634.RHEL4_64)
Subject: Re: [lemonade] I-D Action:draft-melnikov-imapext-filters-06.txt
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

> > 	Title           : IMAP4 extension for named searches (filters)
> > 	Author(s)       : A. Melnikov, C. King
> > 	Filename        : draft-melnikov-imapext-filters-06.txt
> > 	Pages           : 11
> > 	Date            : 2008-09-22
> >
> > The document defines a way to persistently store named IMAP (RFC
> > 3501) searches on the server.  Such named searches can be
> > subsequently referenced in a SEARCH or any other command that
> accepts
> > a search criteria as a parameter.
> 
> Quick question -- Do you really want to be storing filters in public
> server metadata entries?  I know that it's the fallback and not the
> default location to look, but what's the real-world use case?
> 
> Also, this should probably wait for publication until METADATA is out.

Ah, crap, forgot to trim the CCs on that one.  Sorry.
_______________________________________________
lemonade mailing list
lemonade@ietf.org
https://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade


From lemonade-bounces@ietf.org  Thu Oct  2 09:43:27 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 731EA28C1A5;
	Thu,  2 Oct 2008 09:43:27 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CCE0428C111;
	Thu,  2 Oct 2008 09:43:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[AWL=0.063, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id eauriuETBX1Z; Thu,  2 Oct 2008 09:43:25 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251])
	by core3.amsl.com (Postfix) with ESMTP id 761DA28C102;
	Thu,  2 Oct 2008 09:43:24 -0700 (PDT)
Received: from [172.16.2.129] (shiny.isode.com [62.3.217.250]) 
	by rufus.isode.com (submission channel) via TCP with ESMTPA 
	id <SOT6HAAxOV26@rufus.isode.com>; Thu, 2 Oct 2008 17:43:08 +0100
Message-ID: <48E4F9ED.3050105@isode.com>
Date: Thu, 02 Oct 2008 17:42:21 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
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: Dan Karp <dkarp@zimbra.com>
References: <666249820.6061222957284617.JavaMail.root@dogfood.zimbra.com>
In-Reply-To: <666249820.6061222957284617.JavaMail.root@dogfood.zimbra.com>
MIME-Version: 1.0
Cc: lemonade@ietf.org, Internet-Drafts@ietf.org, i-d-announce@ietf.org
Subject: Re: [lemonade] I-D Action:draft-melnikov-imapext-filters-06.txt
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

Dan Karp wrote:

>>	Title           : IMAP4 extension for named searches (filters)
>>	Author(s)       : A. Melnikov, C. King
>>	Filename        : draft-melnikov-imapext-filters-06.txt
>>	Pages           : 11
>>	Date            : 2008-09-22
>>
>>The document defines a way to persistently store named IMAP (RFC
>>3501) searches on the server.  Such named searches can be
>>subsequently referenced in a SEARCH or any other command that accepts
>>a search criteria as a parameter.
>>    
>>
>Quick question -- Do you really want to be storing filters in public
>server metadata entries?  I know that it's the fallback and not the
>default location to look, but what's the real-world use case?
>  
>
I am thinking about corporate wide filters.
I think the document already has enough warnings on possible dangers of 
using them.

>Also, this should probably wait for publication until METADATA is out.
>  
>
Yes, I would ask for this document to be sent to IESG together with the 
METADATA document.

_______________________________________________
lemonade mailing list
lemonade@ietf.org
https://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade


From lemonade-bounces@ietf.org  Thu Oct  9 09:10:40 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0B0AA3A6C9F;
	Thu,  9 Oct 2008 09:10:40 -0700 (PDT)
X-Original-To: lemonade@ietf.org
Delivered-To: lemonade@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30)
	id EFE3D3A6C95; Thu,  9 Oct 2008 09:10:36 -0700 (PDT)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <20081009161036.EFE3D3A6C95@core3.amsl.com>
Date: Thu,  9 Oct 2008 09:10:36 -0700 (PDT)
Cc: lemonade@ietf.org
Subject: [lemonade] Last Call: draft-ietf-lemonade-imap-notify (The IMAP
 NOTIFY Extension) to Proposed Standard
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

The IESG has received a request from the Enhancements to Internet email 
to Support Diverse Service Environments WG (lemonade) to consider the 
following document:

- 'The IMAP NOTIFY Extension '
   <draft-ietf-lemonade-imap-notify-07.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2008-10-23. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-lemonade-imap-notify-07.txt



IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=16414&rfc_flag=0

_______________________________________________
lemonade mailing list
lemonade@ietf.org
https://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade


From lemonade-bounces@ietf.org  Thu Oct  9 12:19:40 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4652F28C1C4;
	Thu,  9 Oct 2008 12:19:40 -0700 (PDT)
X-Original-To: lemonade@ietf.org
Delivered-To: lemonade@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30)
	id 0397428C163; Thu,  9 Oct 2008 12:19:38 -0700 (PDT)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <20081009191939.0397428C163@core3.amsl.com>
Date: Thu,  9 Oct 2008 12:19:39 -0700 (PDT)
Cc: lemonade@ietf.org
Subject: [lemonade] Last Call: draft-cridland-urlfetch-binary (Extended
 URLFETCH for binary and converted parts) to Proposed Standard
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

The IESG has received a request from the Enhancements to Internet email 
to Support Diverse Service Environments WG (lemonade) to consider the 
following document:

- 'Extended URLFETCH for binary and converted parts '
   <draft-cridland-urlfetch-binary-03.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2008-10-23. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-cridland-urlfetch-binary-03.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=16703&rfc_flag=0

_______________________________________________
lemonade mailing list
lemonade@ietf.org
https://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade


From lemonade-bounces@ietf.org  Sat Oct 11 02:41:49 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A4E7F3A6889;
	Sat, 11 Oct 2008 02:41:49 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DEC4D3A6889
	for <lemonade@core3.amsl.com>; Sat, 11 Oct 2008 02:41:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Xhor4B3W-utA for <lemonade@core3.amsl.com>;
	Sat, 11 Oct 2008 02:41:47 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251])
	by core3.amsl.com (Postfix) with ESMTP id 7DBF63A67A3
	for <lemonade@ietf.org>; Sat, 11 Oct 2008 02:41:47 -0700 (PDT)
Received: from [92.40.49.53] (92.40.49.53.sub.mbb.three.co.uk [92.40.49.53]) 
	by rufus.isode.com (submission channel) via TCP with ESMTPA 
	id <SPB0uQAq93=j@rufus.isode.com>; Sat, 11 Oct 2008 10:41:14 +0100
Message-ID: <48F074B2.70104@isode.com>
Date: Sat, 11 Oct 2008 10:41:06 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12)
	Gecko/20050915
X-Accept-Language: en-us, en
To: Eric Burger <eburger@standardstrack.com>
References: <67980E1E-10BD-419D-9989-2FA1F176C022@noware.co.uk>
	<13073304-D8ED-443D-8712-0EAD560F993A@standardstrack.com>
	<E2vzVloFHx1bdtPVpD7xHQ.md5@lochnagar.oryx.com>
	<4D9EBFB3-7FBF-407B-9239-58475DFAECA0@noware.co.uk>
	<tNasjzU+8A9iOtNviybCCw.md5@lochnagar.oryx.com>
	<144F118B-9A41-405E-9EB9-18F3FB60405B@noware.co.uk>
	<E989572A-EF04-4930-A776-33F043FE82E4@standardstrack.com>
	<EE9C5353-63ED-4D6A-8A72-BBFCCC619115@noware.co.uk>
	<017628E4-F698-4FE4-A3B7-8BB8AF81C651@standardstrack.com>
In-Reply-To: <017628E4-F698-4FE4-A3B7-8BB8AF81C651@standardstrack.com>
MIME-Version: 1.0
Cc: lemonade@ietf.org
Subject: Re: [lemonade] "submit+" versus "stream+"
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

Eric Burger wrote:

> Below is a thread discussing the relative merits of considering the  
> semantics of "submit+" URLAUTH use. The key positions:
>
> POSITION 1: "submit+" really means "the client gets a pawn ticket for  
> an object for the client to give to someone else".

I think this is a bit too generic (as it covers all other URLAUTH 
prefixes). I think you meant "the client gets a pawn ticket for  an 
object for the client to give to another service, that has to 
authenticate to retrieve the content".

> POSITION 2: "submit+" means "the client gets a pawn ticket for the  
> purposes of fetching for submission", which means that for streaming,  
> we will need a "streaming+", which means "the client gets a pawn  
> ticket for the purposes of fetching for streaming", and when someone  
> comes up with another reason for getting a pawn ticket for passing to  
> someone else, someone will have to create a new "mumble+" prefix for  
> URLAUTH.
>
> Pro's of POSITION 2:
> The client is somewhat explicit on why it is requesting a URLAUTH  
> token, and when the third party accesses the IMAP store, the IMAP  
> store (which generated the ticket) can do separate ACL processing or  
> logging based on the purpose of the URLAUTH token (e.g., submit 
> versus  streaming versus mumble).
>
> There was some discussion that an IMAP server might restrict the 
> kinds  of MIME types it would release to a streaming server versus a 
> submit  server. However, in practice it is clear there is no 
> distinction.  Other than filtering viruses, a streaming server 
> actually can stream  most any type. For example, an open office 
> document could be spoken as  text-to-speech and an image could be 
> rendered as a streaming video to  a video phone.
>
> Pro's of POSITION 1:
> The client does not need to consider why it is grabbing a URLAUTH  
> token; it just grabs one. This is not an issue today with POSITION 2:  
> a client that is composing a message knows to request a submit+ token  
> and a client that wants streaming will request a stream+ token. The  
> problem comes in when a new application wants to have access to an  
> IMAP body part that is neither for submit processing nor streaming.  
> The likelihood of the application developers going through the 
> process  of writing an RFC to register a new mumble+ token and then 
> getting the  entire IMAP Server community to adopt it is virtually zero.

As a side note: while the last sentence is certainly true, there are 
some other cases when the client can easily decide on URLAUTH type it 
wants to use.
For example a client that wants to store a private bookmark, will always 
use "user+". If the client wants to store a public bookmark, it can use 
"anonymous" or "authuser".

> Moreover,  while POSITION 1 offers the ability for the IMAP server to 
> do  something "special" for submit+ versus stream+, it is not clear 
> the  IMAP server will (or can)

An IMAP server certainly can. It might be used by a specialized application.
We certainly can't control "will", but "can" is the most important part 
here.

> do anything different in practice. In  addition, there is no protocol 
> mechanism to prevent an application  from using submit+ for another 
> purpose. Thus in practice there is no  distinction between submit+ 
> versus stream+, which means wasted,  duplicated code that does no 
> useful work.
>
> To be clear: What we are talking about here is expanding the semantic  
> of "submit+" to mean "request from a thrid-party client on behalf of  
> the client."
>
> <With Chair hat off>
> I'm against writing code that never gets used.

So much for a neutral description of the 2 choices ;-).

> <With Chair hat on>
> RFC 4467 is done. Using something other than "submit+" for streaming  
> means a much longer cycle on getting streaming done.

Are you sure?

> If there is no  difference in protocol, scale, or security, our 
> preference as Chairs  is to take the path of least resistance.
>
> PLEASE REGISTER YOUR CHOICE OR AMBIVALENCE SOON
>
> Note: given the text currently says "submit+", what we are looking 
> for  here is one of:
> [ ] I like "submit+" means "third-party request"
> [ ] I like the idea of "submit+" meaning "third-party request", but I  
> am not comfortable with the token being called "submit"
> [ ] I don't like the idea of "submit+" meaning "third-party request",  
> but I can live with it

I am somewhere between the last 2.

As a server developer I can tell you that adding stream+ is not going to 
be difficult, at least in the case of our server.
M-Box is using a special group "submit" for verifying who is allowed to 
use submit+ URLs. We do support multiple groups, so defining a new one 
is easy.

> [ ] I just realized the reason why "submit+" meaning "third-party  
> request" will damage the Internet
> [ ] Here is the reason "stream+" is the only way to go


_______________________________________________
lemonade mailing list
lemonade@ietf.org
https://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade


From lemonade-bounces@ietf.org  Sun Oct 12 04:02:14 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6DC763A697A;
	Sun, 12 Oct 2008 04:02:14 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4F9473A692F
	for <lemonade@core3.amsl.com>; Sun, 12 Oct 2008 04:02:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.437
X-Spam-Level: 
X-Spam-Status: No, score=-5.437 tagged_above=-999 required=5
	tests=[AWL=-0.697, BAYES_20=-0.74, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id WJ1lvfFX5dKb for <lemonade@core3.amsl.com>;
	Sun, 12 Oct 2008 04:02:12 -0700 (PDT)
Received: from dovecot.org (dovecot.org [82.118.211.50])
	by core3.amsl.com (Postfix) with ESMTP id 6EECD3A67A8
	for <lemonade@ietf.org>; Sun, 12 Oct 2008 04:02:12 -0700 (PDT)
Received: from [192.168.10.2] (xdsl-177-118.nblnetworks.fi [217.30.177.118])
	by dovecot.org (Postfix) with ESMTP id 0C8551647344
	for <lemonade@ietf.org>; Sun, 12 Oct 2008 14:02:36 +0300 (EEST)
From: Timo Sirainen <tss@iki.fi>
To: lemonade@ietf.org
Date: Sun, 12 Oct 2008 14:02:36 +0300
Message-Id: <1223809356.27703.233.camel@hurina>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.3.1 
Subject: [lemonade] QRESYNC again
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1040422818=="
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org


--===============1040422818==
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-Uv99gI1jyFq4f6wMC2lX"


--=-Uv99gI1jyFq4f6wMC2lX
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

I think we decided two things when QRESYNC is enabled:

1) FETCH replies will always contain UID
2) CLOSE doesn't send HIGHESTMODSEQ and it's recommended against using
it at all.

But I'm not really sure if anything was decided about the 3rd issue
where:

C1: a EXPUNGE
S1: * VANISHED 1234
S1: a ok [highestmodseq 2]

C2: b STORE 1 -FLAGS \Seen
S2: * 1 fetch (flags () modseq 3)
S2: b ok
[[Client 2 disconnects]]

Client 2 loses the VANISHED reply. My idea was that server would be able
to detect this and send just before the "b ok":

* OK [HIGHESTMODSEQ 1]

Which would tell the client that it doesn't know all the modseqs yet.


--=-Uv99gI1jyFq4f6wMC2lX
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEABECAAYFAkjx2UwACgkQyUhSUUBViskuPACdGhleDPCwod99AfB7zPRHeDMV
wfwAnA76q0ZX1k9Gf0HckQ19CkemZ/33
=d3cm
-----END PGP SIGNATURE-----

--=-Uv99gI1jyFq4f6wMC2lX--


--===============1040422818==
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://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade
--===============1040422818==--



From lemonade-bounces@ietf.org  Sun Oct 12 04:11:37 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B7BB73A6995;
	Sun, 12 Oct 2008 04:11:37 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 99B443A6995
	for <lemonade@core3.amsl.com>; Sun, 12 Oct 2008 04:11:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.192
X-Spam-Level: 
X-Spam-Status: No, score=-6.192 tagged_above=-999 required=5 tests=[AWL=0.407, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id qNIKceAb-SZW for <lemonade@core3.amsl.com>;
	Sun, 12 Oct 2008 04:11:35 -0700 (PDT)
Received: from dovecot.org (dovecot.org [82.118.211.50])
	by core3.amsl.com (Postfix) with ESMTP id B79663A698D
	for <lemonade@ietf.org>; Sun, 12 Oct 2008 04:11:35 -0700 (PDT)
Received: from [192.168.10.2] (xdsl-177-118.nblnetworks.fi [217.30.177.118])
	by dovecot.org (Postfix) with ESMTP id 74D0616472CC
	for <lemonade@ietf.org>; Sun, 12 Oct 2008 14:12:26 +0300 (EEST)
From: Timo Sirainen <tss@iki.fi>
To: lemonade@ietf.org
In-Reply-To: <1223809356.27703.233.camel@hurina>
References: <1223809356.27703.233.camel@hurina>
Date: Sun, 12 Oct 2008 14:12:25 +0300
Message-Id: <1223809945.27703.243.camel@hurina>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.3.1 
Subject: Re: [lemonade] QRESYNC again
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1382959440=="
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org


--===============1382959440==
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-sbFSgKToxChEJk6u+7yR"


--=-sbFSgKToxChEJk6u+7yR
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Sun, 2008-10-12 at 14:02 +0300, Timo Sirainen wrote:
> Client 2 loses the VANISHED reply. My idea was that server would be able
> to detect this and send just before the "b ok":
>=20
> * OK [HIGHESTMODSEQ 1]

And as a small optimization alternatively the [HIGHESTMODSEQ] could be
added to the tagged reply's resp-text-code as long as it didn't already
have a resp-text-code.

I've implemented this HIGHESTMODSEQ sending generically to all commands,
which also means I haven't added extra special code for EXPUNGE
handling. Any thoughts on of this would be ok:

Client 1 first expunges UID 1234 with modseq=3D2 and then updates UID 1
flags with modseq=3D3. Client 2 then does EXPUNGE:

a EXPUNGE
* VANISHED 1234
* 1 FETCH (FLAGS (\Seen) MODSEQ 3)
a OK

HIGHESTMODSEQ 3 wouldn't be sent because MODSEQ 3 already told the
client to update the modseq.

I guess it doesn't really even violate RFC 5162 because the EXPUNGE
command itself didn't really expunge anything, it just showed what
another session did.

--=-sbFSgKToxChEJk6u+7yR
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEABECAAYFAkjx25kACgkQyUhSUUBVisn4TgCgmX7jKDZfQTTCIZxwCRmouGHX
HIYAnjLMcGnkCzm0tuwEt0Bq0tRpRZVM
=q6PB
-----END PGP SIGNATURE-----

--=-sbFSgKToxChEJk6u+7yR--


--===============1382959440==
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://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade
--===============1382959440==--



From lemonade-bounces@ietf.org  Mon Oct 13 05:21:55 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F241F28C0EC;
	Mon, 13 Oct 2008 05:21:54 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 27D1E28C0EC
	for <lemonade@core3.amsl.com>; Mon, 13 Oct 2008 05:21:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Ufj4A3pUWwm5 for <lemonade@core3.amsl.com>;
	Mon, 13 Oct 2008 05:21:53 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19b.inmotionhosting.com
	[66.117.3.189]) by core3.amsl.com (Postfix) with ESMTP id 2456028C0CE
	for <lemonade@ietf.org>; Mon, 13 Oct 2008 05:21:53 -0700 (PDT)
Received: from [75.68.119.237] (port=61189 helo=[192.168.15.103])
	by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.68) (envelope-from <eburger@standardstrack.com>)
	id 1KpMR9-0001JI-Gy
	for lemonade@ietf.org; Mon, 13 Oct 2008 05:22:12 -0700
Message-Id: <CC25F8DC-921E-4D9C-ABA3-F7DA8CD6CB54@standardstrack.com>
From: Eric Burger <eburger@standardstrack.com>
To: lemonade@ietf.org
In-Reply-To: <48F074B2.70104@isode.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 13 Oct 2008 08:22:10 -0400
References: <67980E1E-10BD-419D-9989-2FA1F176C022@noware.co.uk>
	<13073304-D8ED-443D-8712-0EAD560F993A@standardstrack.com>
	<E2vzVloFHx1bdtPVpD7xHQ.md5@lochnagar.oryx.com>
	<4D9EBFB3-7FBF-407B-9239-58475DFAECA0@noware.co.uk>
	<tNasjzU+8A9iOtNviybCCw.md5@lochnagar.oryx.com>
	<144F118B-9A41-405E-9EB9-18F3FB60405B@noware.co.uk>
	<E989572A-EF04-4930-A776-33F043FE82E4@standardstrack.com>
	<EE9C5353-63ED-4D6A-8A72-BBFCCC619115@noware.co.uk>
	<017628E4-F698-4FE4-A3B7-8BB8AF81C651@standardstrack.com>
	<48F074B2.70104@isode.com>
X-Mailer: Apple Mail (2.929.2)
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Subject: Re: [lemonade] "submit+" versus "stream+"
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1103416358=="
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org


--===============1103416358==
Content-Type: multipart/signed; boundary=Apple-Mail-3-780194713; micalg=sha1; protocol="application/pkcs7-signature"


--Apple-Mail-3-780194713
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

Any other opinions out there?

Anyone else care?

Hello... Hello... anyone out there?!?!?


On Oct 11, 2008, at 5:41 AM, Alexey Melnikov wrote:

> Eric Burger wrote:
>
>> Below is a thread discussing the relative merits of considering  
>> the  semantics of "submit+" URLAUTH use. The key positions:
>>
>> POSITION 1: "submit+" really means "the client gets a pawn ticket  
>> for  an object for the client to give to someone else".
>
> I think this is a bit too generic (as it covers all other URLAUTH  
> prefixes). I think you meant "the client gets a pawn ticket for  an  
> object for the client to give to another service, that has to  
> authenticate to retrieve the content".
>
>> POSITION 2: "submit+" means "the client gets a pawn ticket for the   
>> purposes of fetching for submission", which means that for  
>> streaming,  we will need a "streaming+", which means "the client  
>> gets a pawn  ticket for the purposes of fetching for streaming",  
>> and when someone  comes up with another reason for getting a pawn  
>> ticket for passing to  someone else, someone will have to create a  
>> new "mumble+" prefix for  URLAUTH.
>>
>> Pro's of POSITION 2:
>> The client is somewhat explicit on why it is requesting a URLAUTH   
>> token, and when the third party accesses the IMAP store, the IMAP   
>> store (which generated the ticket) can do separate ACL processing  
>> or  logging based on the purpose of the URLAUTH token (e.g., submit  
>> versus  streaming versus mumble).
>>
>> There was some discussion that an IMAP server might restrict the  
>> kinds  of MIME types it would release to a streaming server versus  
>> a submit  server. However, in practice it is clear there is no  
>> distinction.  Other than filtering viruses, a streaming server  
>> actually can stream  most any type. For example, an open office  
>> document could be spoken as  text-to-speech and an image could be  
>> rendered as a streaming video to  a video phone.
>>
>> Pro's of POSITION 1:
>> The client does not need to consider why it is grabbing a URLAUTH   
>> token; it just grabs one. This is not an issue today with POSITION  
>> 2:  a client that is composing a message knows to request a submit+  
>> token  and a client that wants streaming will request a stream+  
>> token. The  problem comes in when a new application wants to have  
>> access to an  IMAP body part that is neither for submit processing  
>> nor streaming.  The likelihood of the application developers going  
>> through the process  of writing an RFC to register a new mumble+  
>> token and then getting the  entire IMAP Server community to adopt  
>> it is virtually zero.
>
> As a side note: while the last sentence is certainly true, there are  
> some other cases when the client can easily decide on URLAUTH type  
> it wants to use.
> For example a client that wants to store a private bookmark, will  
> always use "user+". If the client wants to store a public bookmark,  
> it can use "anonymous" or "authuser".
>
>> Moreover,  while POSITION 1 offers the ability for the IMAP server  
>> to do  something "special" for submit+ versus stream+, it is not  
>> clear the  IMAP server will (or can)
>
> An IMAP server certainly can. It might be used by a specialized  
> application.
> We certainly can't control "will", but "can" is the most important  
> part here.
>
>> do anything different in practice. In  addition, there is no  
>> protocol mechanism to prevent an application  from using submit+  
>> for another purpose. Thus in practice there is no  distinction  
>> between submit+ versus stream+, which means wasted,  duplicated  
>> code that does no useful work.
>>
>> To be clear: What we are talking about here is expanding the  
>> semantic  of "submit+" to mean "request from a thrid-party client  
>> on behalf of  the client."
>>
>> <With Chair hat off>
>> I'm against writing code that never gets used.
>
> So much for a neutral description of the 2 choices ;-).
>
>> <With Chair hat on>
>> RFC 4467 is done. Using something other than "submit+" for  
>> streaming  means a much longer cycle on getting streaming done.
>
> Are you sure?
>
>> If there is no  difference in protocol, scale, or security, our  
>> preference as Chairs  is to take the path of least resistance.
>>
>> PLEASE REGISTER YOUR CHOICE OR AMBIVALENCE SOON
>>
>> Note: given the text currently says "submit+", what we are looking  
>> for  here is one of:
>> [ ] I like "submit+" means "third-party request"
>> [ ] I like the idea of "submit+" meaning "third-party request", but  
>> I  am not comfortable with the token being called "submit"
>> [ ] I don't like the idea of "submit+" meaning "third-party  
>> request",  but I can live with it
>
> I am somewhere between the last 2.
>
> As a server developer I can tell you that adding stream+ is not  
> going to be difficult, at least in the case of our server.
> M-Box is using a special group "submit" for verifying who is allowed  
> to use submit+ URLs. We do support multiple groups, so defining a  
> new one is easy.
>
>> [ ] I just realized the reason why "submit+" meaning "third-party   
>> request" will damage the Internet
>> [ ] Here is the reason "stream+" is the only way to go
>
>


--Apple-Mail-3-780194713
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGPTCCBjkw
ggUhoAMCAQICEC+VK1RLWxrF8KJZDR9k8p8wDQYJKoZIhvcNAQEFBQAwga4xCzAJBgNVBAYTAlVT
MQswCQYDVQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VS
VFJVU1QgTmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQD
Ey1VVE4tVVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwwHhcNMDgwODEz
MDAwMDAwWhcNMDkwODEzMjM1OTU5WjCB4TE1MDMGA1UECxMsQ29tb2RvIFRydXN0IE5ldHdvcmsg
LSBQRVJTT05BIE5PVCBWQUxJREFURUQxRjBEBgNVBAsTPVRlcm1zIGFuZCBDb25kaXRpb25zIG9m
IHVzZTogaHR0cDovL3d3dy5jb21vZG8ubmV0L3JlcG9zaXRvcnkxHzAdBgNVBAsTFihjKTIwMDMg
Q29tb2RvIExpbWl0ZWQxFDASBgNVBAMTC0VyaWMgQnVyZ2VyMSkwJwYJKoZIhvcNAQkBFhplYnVy
Z2VyQHN0YW5kYXJkc3RyYWNrLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMTF
RRoA4LgOACMFph0aomRC/UpqoA5C/d6DUTOvTMrYSEqkjwnU4zxDtBcHlcB4AxKAov00MYsUvEU4
loz7BHjfDjv76AIkcwu33VYQbzGmarVnyaXsVb6f/cyRL3fPT0VOVO2tQAEEgwg//CX0jN8Kn2jH
uXD/HEvko7cmpL3Pwevf3+DwB61v7ca79PpEZfn/WhaqRKA4uVNPj/JbieeaLo2v/0RJzrEElZK0
pHCqxiD3mQ8ossPkA9fUCSxLlbdMcPU3be5x8vt8Q8mYTXF5Z3d9RZmYrmNkvTQtdzVpfYWr/hgV
Xqm9tByOOAR+hoN3FKbubR/OrAHL9yDAd4sCAwEAAaOCAhwwggIYMB8GA1UdIwQYMBaAFImCZ33E
nSZwAEu0UEh83j2uBG59MB0GA1UdDgQWBBRDWgutb7b8R/L7G3Y3D+molAA3VzAOBgNVHQ8BAf8E
BAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggrBgEFBQcDBAYLKwYBBAGyMQEDBQIwEQYJ
YIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQEBMCswKQYIKwYBBQUHAgEW
HWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMIGlBgNVHR8EgZ0wgZowTKBKoEiGRmh0dHA6
Ly9jcmwuY29tb2RvY2EuY29tL1VUTi1VU0VSRmlyc3QtQ2xpZW50QXV0aGVudGljYXRpb25hbmRF
bWFpbC5jcmwwSqBIoEaGRGh0dHA6Ly9jcmwuY29tb2RvLm5ldC9VVE4tVVNFUkZpcnN0LUNsaWVu
dEF1dGhlbnRpY2F0aW9uYW5kRW1haWwuY3JsMGwGCCsGAQUFBwEBBGAwXjA2BggrBgEFBQcwAoYq
aHR0cDovL2NydC5jb21vZG9jYS5jb20vVVROQUFBQ2xpZW50Q0EuY3J0MCQGCCsGAQUFBzABhhho
dHRwOi8vb2NzcC5jb21vZG9jYS5jb20wJQYDVR0RBB4wHIEaZWJ1cmdlckBzdGFuZGFyZHN0cmFj
ay5jb20wDQYJKoZIhvcNAQEFBQADggEBAGeBR7NPCvrY3GQoIi49JOuciatY2r4st905Jw1etp6J
umFFWlaCBl11tFSclk/3S45B+lUv3SEvG4CEjUByPScprVmCqHR+y8BAQaB/CV+N1y14x3MbhJ+Z
8XDGKeUXuuyGd9w0l3/t/QPid6TRXQjQFrLPFs1IALuNpNiFMHEF/xFbMG1Z2vznR/gSPlePekoZ
TqcExIDBNZTBebpZqwAXzPpedNNOclbMLFLWDMOAozVRpkfjI0eiFsk8SF1Ho1Gb9Bx8DeG4peE2
KRVOR9FFnZZgBpFjXYRcglsMOSKCY8HgE+NGvbbqbrMoBV/BlYyxRXwfti71RL9Zs2Cq1eQxggP8
MIID+AIBATCBwzCBrjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExh
a2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8v
d3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkNH2TynzAJBgUrDgMCGgUAoIICDTAYBgkqhkiG
9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wODEwMTMxMjIyMTBaMCMGCSqGSIb3
DQEJBDEWBBSlGEVSbgi48aqDnbAweoCqYmP87TCB1AYJKwYBBAGCNxAEMYHGMIHDMIGuMQswCQYD
VQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVU
aGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2
MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhAv
lStUS1saxfCiWQ0fZPKfMIHWBgsqhkiG9w0BCRACCzGBxqCBwzCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVU
Ti1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkN
H2TynzANBgkqhkiG9w0BAQEFAASCAQB9qbqDrGZH1SV4mWrsHAhb3fUI3jznePVKtMkjz67drhWq
0VKNjA2Khw/QdzJjGaRZIPu+wxnAnBFv5xVl4kVps0FXYX4IvT1MpyvNX22NcjJP/89seKyqnCvW
6PzUSPa8hieouQXvv6ay88M1eylqLaSf5ZCXtog/Vt2gPAYKhvmWHG09PCLQ4bYIfE0Qsz0atxoT
N1hYuvtHw8zw29soMpCd8ROW9Mf8I+3fbHK9J1H8WlHJQOhZXHt1EKeXMqVazj0rogAXFKuS3DG+
zGgJ/SrmtoIg7+qPDKW+p052PolOHm4I+T2KqXapQX5Gff+vD8BG4Zd4r7r6efNp6Eo/AAAAAAAA

--Apple-Mail-3-780194713--

--===============1103416358==
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://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade
--===============1103416358==--


From lemonade-bounces@ietf.org  Mon Oct 13 18:22:35 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 556C83A6AC5;
	Mon, 13 Oct 2008 18:22:35 -0700 (PDT)
X-Original-To: lemonade@ietf.org
Delivered-To: lemonade@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30)
	id 622923A6AC5; Mon, 13 Oct 2008 18:22:33 -0700 (PDT)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <20081014012233.622923A6AC5@core3.amsl.com>
Date: Mon, 13 Oct 2008 18:22:33 -0700 (PDT)
Cc: lemonade@ietf.org
Subject: [lemonade] Last Call: draft-ietf-lemonade-architecture (LEMONADE
 Architecture - Supporting OMA Mobile Email (MEM) using Internet Mail) to
 Informational RFC
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

The IESG has received a request from the Enhancements to Internet email 
to Support Diverse Service Environments WG (lemonade) to consider the 
following document:

- 'LEMONADE Architecture - Supporting OMA Mobile Email (MEM) using 
   Internet Mail '
   <draft-ietf-lemonade-architecture-03.txt> as an Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2008-10-27. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-lemonade-architecture-03.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=16645&rfc_flag=0

_______________________________________________
lemonade mailing list
lemonade@ietf.org
https://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade


From lemonade-bounces@ietf.org  Tue Oct 14 02:10:03 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D7E113A6A2B;
	Tue, 14 Oct 2008 02:10:03 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5946D3A6A2B
	for <lemonade@core3.amsl.com>; Tue, 14 Oct 2008 02:10:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.627
X-Spam-Level: 
X-Spam-Status: No, score=-0.627 tagged_above=-999 required=5
	tests=[AWL=-0.496, BAYES_00=-2.599, DATE_IN_PAST_12_24=0.992,
	FH_HOST_EQ_D_D_D_D=0.765, HELO_MISMATCH_NET=0.611, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id BWX+S3dcI9CH for <lemonade@core3.amsl.com>;
	Tue, 14 Oct 2008 02:10:01 -0700 (PDT)
Received: from turner.dave.cridland.net (dsl-217-155-137-60.zen.co.uk
	[217.155.137.60])
	by core3.amsl.com (Postfix) with ESMTP id 0D9603A67EE
	for <lemonade@ietf.org>; Tue, 14 Oct 2008 02:10:00 -0700 (PDT)
Received: from peirce.dave.cridland.net ([217.155.137.61]) by
	turner.dave.cridland.net (submission)
	via TCP with ESMTPA id <SPNEzwAStHGa@turner.dave.cridland.net>;
	Mon, 13 Oct 2008 13:53:35 +0100
References: <67980E1E-10BD-419D-9989-2FA1F176C022@noware.co.uk>
	<13073304-D8ED-443D-8712-0EAD560F993A@standardstrack.com>
	<E2vzVloFHx1bdtPVpD7xHQ.md5@lochnagar.oryx.com>
	<4D9EBFB3-7FBF-407B-9239-58475DFAECA0@noware.co.uk>
	<tNasjzU+8A9iOtNviybCCw.md5@lochnagar.oryx.com>
	<144F118B-9A41-405E-9EB9-18F3FB60405B@noware.co.uk>
	<E989572A-EF04-4930-A776-33F043FE82E4@standardstrack.com>
	<EE9C5353-63ED-4D6A-8A72-BBFCCC619115@noware.co.uk>
	<017628E4-F698-4FE4-A3B7-8BB8AF81C651@standardstrack.com>
In-Reply-To: <017628E4-F698-4FE4-A3B7-8BB8AF81C651@standardstrack.com>
MIME-Version: 1.0
Message-Id: <7729.1223902415.288805@peirce.dave.cridland.net>
Date: Mon, 13 Oct 2008 13:53:35 +0100
From: Dave Cridland <dave@cridland.net>
To: Enhancements to Internet email to support diverse service enivronments
	<lemonade@ietf.org>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>
Subject: Re: [lemonade] "submit+" versus "stream+"
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

On Wed Oct  1 19:29:57 2008, Eric Burger wrote:
> RFC 4467 is done. Using something other than "submit+" for  
> streaming  means a much longer cycle on getting streaming done. If  
> there is no  difference in protocol, scale, or security, our  
> preference as Chairs  is to take the path of least resistance.

Two things, from which you can derive a tickbox opinion.

First, RFC 4467 is indeed done, and specifies what submit+ means:

   The "submit+" access identifier prefix, followed by a userid,
   indicates that only a userid authorized as a message submission
   entity on behalf of the specified userid is permitted to use this
   URL.  The IMAP server does not validate the specified userid but  
does
   validate that the IMAP session has an authorization identity that  
is
   authorized as a message submission entity.  The authorized message
   submission entity MUST validate the userid prior to contacting the
   IMAP server.

So by saying "Hey, and you can use it for streaming servers too",  
then you are changing this meaning, which, I think, technically  
requires this streaming RFC to Update RFC 4467, which in turn  
requires it to go Standards Track, etc. So reusing submit+ is not a  
standardization shortcut, and using that as an argument is therefore  
counter-productive, as it may very well be the opposite.

Secondly, it may be worthwhile asking what the point of submit+ is.  
As I understand it, submit+ is there to limit the effective scope of  
the damage caused by the leak of such a URL. It's not to limit the  
scope of where it's used legitimately, because all legitimate usage  
is, by definition, okay.

But if a URI is leaked, the intention here is to make it more  
difficult for an attacker. So, if an attacker gets hold of a submit+  
URI, said attacker must also have a compromised trusted submission  
server. By extending the scope of submit+ to include other trusted  
servers, the attack surface is increased, and therefore the protocol  
as a whole is weakened.

Hence, reusing the submit+ prefix in other circumstances appears to  
me to be a marginal simplification for IMAP client and server  
implementors, at the expense of security, which is an argument I find  
very difficult to justify.

Dave.
-- 
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - 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://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade


From lemonade-bounces@ietf.org  Tue Oct 14 03:59:51 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 376DF3A6889;
	Tue, 14 Oct 2008 03:59:51 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1EA193A6889
	for <lemonade@core3.amsl.com>; Tue, 14 Oct 2008 03:59:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.11
X-Spam-Level: 
X-Spam-Status: No, score=-101.11 tagged_above=-999 required=5
	tests=[BAYES_05=-1.11, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id dbybrV+i0jt2 for <lemonade@core3.amsl.com>;
	Tue, 14 Oct 2008 03:59:49 -0700 (PDT)
Received: from blu0-omc4-s30.blu0.hotmail.com (blu0-omc4-s30.blu0.hotmail.com
	[65.55.111.169])
	by core3.amsl.com (Postfix) with ESMTP id 477F43A67F8
	for <lemonade@ietf.org>; Tue, 14 Oct 2008 03:59:49 -0700 (PDT)
Received: from BLU126-W37 ([65.55.111.136]) by blu0-omc4-s30.blu0.hotmail.com
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 14 Oct 2008 03:59:33 -0700
Message-ID: <BLU126-W37BB2E1C2369370899BA42B8310@phx.gbl>
X-Originating-IP: [72.254.136.190]
From: Mark Crispin <markrcrispin@live.com>
To: Dave Cridland <dave@cridland.net>, Enhancements to Internet email to
	support diverse service enivronments <lemonade@ietf.org>
Date: Tue, 14 Oct 2008 03:59:32 -0700
Importance: Normal
In-Reply-To: <7729.1223902415.288805@peirce.dave.cridland.net>
References: <67980E1E-10BD-419D-9989-2FA1F176C022@noware.co.uk>
	<13073304-D8ED-443D-8712-0EAD560F993A@standardstrack.com>
	<E2vzVloFHx1bdtPVpD7xHQ.md5@lochnagar.oryx.com>
	<4D9EBFB3-7FBF-407B-9239-58475DFAECA0@noware.co.uk>
	<tNasjzU+8A9iOtNviybCCw.md5@lochnagar.oryx.com>
	<144F118B-9A41-405E-9EB9-18F3FB60405B@noware.co.uk>
	<E989572A-EF04-4930-A776-33F043FE82E4@standardstrack.com>
	<EE9C5353-63ED-4D6A-8A72-BBFCCC619115@noware.co.uk>
	<017628E4-F698-4FE4-A3B7-8BB8AF81C651@standardstrack.com> 
	<7729.1223902415.288805@peirce.dave.cridland.net>
MIME-Version: 1.0
X-OriginalArrivalTime: 14 Oct 2008 10:59:33.0083 (UTC)
	FILETIME=[F06A42B0:01C92DEB]
Cc: Alexey Melnikov <alexey.melnikov@isode.com>
Subject: Re: [lemonade] "submit+" versus "stream+"
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org


> Hence, reusing the submit+ prefix in other circumstances appears to  
> me to be a marginal simplification for IMAP client and server  
> implementors, at the expense of security, which is an argument I find  
> very difficult to justify.

I consider this to be a compelling argument.

_________________________________________________________________
Stay up to date on your PC, the Web, and your mobile phone with Windows Live.
http://clk.atdmt.com/MRT/go/msnnkwxp1020093185mrt/direct/01/
_______________________________________________
lemonade mailing list
lemonade@ietf.org
https://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade


From lemonade-bounces@ietf.org  Wed Oct 15 17:26:51 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AD00828C0ED;
	Wed, 15 Oct 2008 17:26:51 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6CA993A67CF
	for <lemonade@core3.amsl.com>; Wed, 15 Oct 2008 17:26:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.556
X-Spam-Level: 
X-Spam-Status: No, score=-2.556 tagged_above=-999 required=5 tests=[AWL=0.043, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id TTssYDW3V5BZ for <lemonade@core3.amsl.com>;
	Wed, 15 Oct 2008 17:26:49 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19b.inmotionhosting.com
	[66.117.3.189]) by core3.amsl.com (Postfix) with ESMTP id A210528C0E1
	for <lemonade@ietf.org>; Wed, 15 Oct 2008 17:26:49 -0700 (PDT)
Received: from [75.68.119.237] (port=62949 helo=[192.168.15.100])
	by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.68) (envelope-from <eburger@standardstrack.com>)
	id 1KqGiI-0001Wy-TR; Wed, 15 Oct 2008 17:27:39 -0700
Message-Id: <E5D5ECC0-BDAD-4720-9478-4E6C1601EE03@standardstrack.com>
From: Eric Burger <eburger@standardstrack.com>
To: Dave Cridland <dave@cridland.net>,
 Mark Crispin <MRC@Lingling.Panda.COM>
In-Reply-To: <BLU126-W37BB2E1C2369370899BA42B8310@phx.gbl>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 15 Oct 2008 20:27:43 -0400
References: <67980E1E-10BD-419D-9989-2FA1F176C022@noware.co.uk>
	<13073304-D8ED-443D-8712-0EAD560F993A@standardstrack.com>
	<E2vzVloFHx1bdtPVpD7xHQ.md5@lochnagar.oryx.com>
	<4D9EBFB3-7FBF-407B-9239-58475DFAECA0@noware.co.uk>
	<tNasjzU+8A9iOtNviybCCw.md5@lochnagar.oryx.com>
	<144F118B-9A41-405E-9EB9-18F3FB60405B@noware.co.uk>
	<E989572A-EF04-4930-A776-33F043FE82E4@standardstrack.com>
	<EE9C5353-63ED-4D6A-8A72-BBFCCC619115@noware.co.uk>
	<017628E4-F698-4FE4-A3B7-8BB8AF81C651@standardstrack.com>
	<7729.1223902415.288805@peirce.dave.cridland.net>
	<BLU126-W37BB2E1C2369370899BA42B8310@phx.gbl>
X-Mailer: Apple Mail (2.929.2)
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: Enhancements to Internet email to support diverse service enivronments
	<lemonade@ietf.org>
Subject: Re: [lemonade] "submit+" versus "stream+"
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1419845859=="
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org


--===============1419845859==
Content-Type: multipart/signed; boundary=Apple-Mail-93-996528282; micalg=sha1; protocol="application/pkcs7-signature"


--Apple-Mail-93-996528282
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

I would consider it to be compelling, if one could argue how submit+  
is different from stream+ in practice.

If people will provision IMAP servers with separate ACL's, I would buy  
it. However, I don't see it in practice.

This one is certainly in "it's the will of the work group."

<chair hat on>
So far, it's 3 votes for submit+ only, and 4 for submit+ and stream+.  
In my book the 4 votes for having bunches of ACL's counts more heavily  
than the 3 votes, because my vote does not count as I'm not an  
implementor.

Do be aware that if we do stream+, we would do a stand-alone document  
for stream+ (standards track)  and a separate document for how to use  
it in the context of streaming voice and video (informational). A  
separate issue is whether we would need to recharter. I do not think  
we do, as to me stream+ would be an IMAP (URLAUTH) extension in  
support of handling streaming multimedia content, which is deliverable  
#1.

I would offer if we go the route of multiple prefixes that we spend  
time thinking about whether submit+ and stream+ will be the only  
prefixes. To me, this mechanism is opening the door for lots and lots  
of access "reasons", in which case we should set up an IANA registry  
for future prefixes (reason codes).



On Oct 14, 2008, at 6:59 AM, Mark Crispin wrote:
> Quoting Dave Cridland:
>> Hence, reusing the submit+ prefix in other circumstances appears to
>> me to be a marginal simplification for IMAP client and server
>> implementors, at the expense of security, which is an argument I find
>> very difficult to justify.
>
> I consider this to be a compelling argument.

--Apple-Mail-93-996528282
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGPTCCBjkw
ggUhoAMCAQICEC+VK1RLWxrF8KJZDR9k8p8wDQYJKoZIhvcNAQEFBQAwga4xCzAJBgNVBAYTAlVT
MQswCQYDVQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VS
VFJVU1QgTmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQD
Ey1VVE4tVVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwwHhcNMDgwODEz
MDAwMDAwWhcNMDkwODEzMjM1OTU5WjCB4TE1MDMGA1UECxMsQ29tb2RvIFRydXN0IE5ldHdvcmsg
LSBQRVJTT05BIE5PVCBWQUxJREFURUQxRjBEBgNVBAsTPVRlcm1zIGFuZCBDb25kaXRpb25zIG9m
IHVzZTogaHR0cDovL3d3dy5jb21vZG8ubmV0L3JlcG9zaXRvcnkxHzAdBgNVBAsTFihjKTIwMDMg
Q29tb2RvIExpbWl0ZWQxFDASBgNVBAMTC0VyaWMgQnVyZ2VyMSkwJwYJKoZIhvcNAQkBFhplYnVy
Z2VyQHN0YW5kYXJkc3RyYWNrLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMTF
RRoA4LgOACMFph0aomRC/UpqoA5C/d6DUTOvTMrYSEqkjwnU4zxDtBcHlcB4AxKAov00MYsUvEU4
loz7BHjfDjv76AIkcwu33VYQbzGmarVnyaXsVb6f/cyRL3fPT0VOVO2tQAEEgwg//CX0jN8Kn2jH
uXD/HEvko7cmpL3Pwevf3+DwB61v7ca79PpEZfn/WhaqRKA4uVNPj/JbieeaLo2v/0RJzrEElZK0
pHCqxiD3mQ8ossPkA9fUCSxLlbdMcPU3be5x8vt8Q8mYTXF5Z3d9RZmYrmNkvTQtdzVpfYWr/hgV
Xqm9tByOOAR+hoN3FKbubR/OrAHL9yDAd4sCAwEAAaOCAhwwggIYMB8GA1UdIwQYMBaAFImCZ33E
nSZwAEu0UEh83j2uBG59MB0GA1UdDgQWBBRDWgutb7b8R/L7G3Y3D+molAA3VzAOBgNVHQ8BAf8E
BAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggrBgEFBQcDBAYLKwYBBAGyMQEDBQIwEQYJ
YIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQEBMCswKQYIKwYBBQUHAgEW
HWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMIGlBgNVHR8EgZ0wgZowTKBKoEiGRmh0dHA6
Ly9jcmwuY29tb2RvY2EuY29tL1VUTi1VU0VSRmlyc3QtQ2xpZW50QXV0aGVudGljYXRpb25hbmRF
bWFpbC5jcmwwSqBIoEaGRGh0dHA6Ly9jcmwuY29tb2RvLm5ldC9VVE4tVVNFUkZpcnN0LUNsaWVu
dEF1dGhlbnRpY2F0aW9uYW5kRW1haWwuY3JsMGwGCCsGAQUFBwEBBGAwXjA2BggrBgEFBQcwAoYq
aHR0cDovL2NydC5jb21vZG9jYS5jb20vVVROQUFBQ2xpZW50Q0EuY3J0MCQGCCsGAQUFBzABhhho
dHRwOi8vb2NzcC5jb21vZG9jYS5jb20wJQYDVR0RBB4wHIEaZWJ1cmdlckBzdGFuZGFyZHN0cmFj
ay5jb20wDQYJKoZIhvcNAQEFBQADggEBAGeBR7NPCvrY3GQoIi49JOuciatY2r4st905Jw1etp6J
umFFWlaCBl11tFSclk/3S45B+lUv3SEvG4CEjUByPScprVmCqHR+y8BAQaB/CV+N1y14x3MbhJ+Z
8XDGKeUXuuyGd9w0l3/t/QPid6TRXQjQFrLPFs1IALuNpNiFMHEF/xFbMG1Z2vznR/gSPlePekoZ
TqcExIDBNZTBebpZqwAXzPpedNNOclbMLFLWDMOAozVRpkfjI0eiFsk8SF1Ho1Gb9Bx8DeG4peE2
KRVOR9FFnZZgBpFjXYRcglsMOSKCY8HgE+NGvbbqbrMoBV/BlYyxRXwfti71RL9Zs2Cq1eQxggP8
MIID+AIBATCBwzCBrjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExh
a2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8v
d3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkNH2TynzAJBgUrDgMCGgUAoIICDTAYBgkqhkiG
9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wODEwMTYwMDI3NDRaMCMGCSqGSIb3
DQEJBDEWBBQOs7RA/fhOc+RVQrJQpmaJXED7aTCB1AYJKwYBBAGCNxAEMYHGMIHDMIGuMQswCQYD
VQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVU
aGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2
MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhAv
lStUS1saxfCiWQ0fZPKfMIHWBgsqhkiG9w0BCRACCzGBxqCBwzCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVU
Ti1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkN
H2TynzANBgkqhkiG9w0BAQEFAASCAQA5b5eWJP+LSAckQFs9XmFivjsROr1ORcQlF5hFkq/UcV4J
BhXl37OCw2gEQCdwNEcA7Zc+D1eskPRdLXPTl3ePguqt5y5yI+vVgsRQsIkxym39DJFSB06m3gZP
1tmwvUBd1is1+bTzRk8g2RDci/qCNLC2olow61kitvMpyN3rcmdNI0gnfTSNsml2TRr4e4vbVpvw
KdifbMT9X+sMKZoSp4qXALCNg4ei0XZ7gCcMK6zYL0BrF8j+Z0me20OGWtwhsgbyCl7zeJq3xZfz
KOXBcjESwCnA6fPJ3mjb5KRtIZW4w4dfzDjS1XgOGEAB5RZ4wFHwgdJfMNZn5/nf3QmRAAAAAAAA

--Apple-Mail-93-996528282--

--===============1419845859==
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://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade
--===============1419845859==--


From lemonade-bounces@ietf.org  Thu Oct 16 00:55:54 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B4A9A3A6A86;
	Thu, 16 Oct 2008 00:55:54 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4C10C3A6A63
	for <lemonade@core3.amsl.com>; Thu, 16 Oct 2008 00:55:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id cRmW9bUwn0oS for <lemonade@core3.amsl.com>;
	Thu, 16 Oct 2008 00:55:52 -0700 (PDT)
Received: from kalyani.oryx.com (kalyani.oryx.com [195.30.37.30])
	by core3.amsl.com (Postfix) with ESMTP id 6041F3A6A84
	for <lemonade@ietf.org>; Thu, 16 Oct 2008 00:55:51 -0700 (PDT)
Received: from kalyani.oryx.com (localhost.oryx.com [127.0.0.1])
	by kalyani.oryx.com (Postfix) with ESMTP id A1AE64AC8C;
	Thu, 16 Oct 2008 09:56:47 +0200 (CEST)
Received: from arnt@oryx.com (client address 195.30.37.40) (HELO
	lochnagar.oryx.com) by kalyani.oryx.com (Archiveopteryx 3.1.0) with
	esmtp id 1224143807-66249-5174 (5 recipients); Thu, 16 Oct 2008
	09:56:47 +0200
Message-Id: <RXWSsIyHCaL13Hb13D3HEA.md5@lochnagar.oryx.com>
Date: Thu, 16 Oct 2008 09:55:14 +0200
From: Arnt Gulbrandsen <arnt@oryx.com>
To: lemonade@ietf.org
References: <67980E1E-10BD-419D-9989-2FA1F176C022@noware.co.uk>
	<13073304-D8ED-443D-8712-0EAD560F993A@standardstrack.com>
	<E2vzVloFHx1bdtPVpD7xHQ.md5@lochnagar.oryx.com>
	<4D9EBFB3-7FBF-407B-9239-58475DFAECA0@noware.co.uk>
	<tNasjzU+8A9iOtNviybCCw.md5@lochnagar.oryx.com>
	<144F118B-9A41-405E-9EB9-18F3FB60405B@noware.co.uk>
	<E989572A-EF04-4930-A776-33F043FE82E4@standardstrack.com>
	<EE9C5353-63ED-4D6A-8A72-BBFCCC619115@noware.co.uk>
	<017628E4-F698-4FE4-A3B7-8BB8AF81C651@standardstrack.com>
	<7729.1223902415.288805@peirce.dave.cridland.net>
	<BLU126-W37BB2E1C2369370899BA42B8310@phx.gbl>
	<E5D5ECC0-BDAD-4720-9478-4E6C1601EE03@standardstrack.com>
In-Reply-To: <E5D5ECC0-BDAD-4720-9478-4E6C1601EE03@standardstrack.com>
Cc: Mark Crispin <MRC@Lingling.Panda.COM>
Subject: Re: [lemonade] "submit+" versus "stream+"
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

Eric Burger writes:
> <chair hat on>
> So far, it's 3 votes for submit+ only, and 4 for submit+ and stream+.

Uh. Dave's missive the other day changed my mind.

Arnt
_______________________________________________
lemonade mailing list
lemonade@ietf.org
https://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade


From lemonade-bounces@ietf.org  Sun Oct 19 04:00:20 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 29A903A684D;
	Sun, 19 Oct 2008 04:00:20 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B39B63A684D
	for <lemonade@core3.amsl.com>; Sun, 19 Oct 2008 04:00:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.429
X-Spam-Level: 
X-Spam-Status: No, score=-2.429 tagged_above=-999 required=5 tests=[AWL=0.170, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id u9IZJkzwx+tk for <lemonade@core3.amsl.com>;
	Sun, 19 Oct 2008 04:00:19 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251])
	by core3.amsl.com (Postfix) with ESMTP id A746B3A681C
	for <lemonade@ietf.org>; Sun, 19 Oct 2008 04:00:18 -0700 (PDT)
Received: from [92.40.217.73] (92.40.217.73.sub.mbb.three.co.uk
	[92.40.217.73]) 
	by rufus.isode.com (submission channel) via TCP with ESMTPA 
	id <SPsThQBpDDXJ@rufus.isode.com>; Sun, 19 Oct 2008 12:01:26 +0100
Message-ID: <48FB137B.5000906@isode.com>
Date: Sun, 19 Oct 2008 12:01:15 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
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: Timo Sirainen <tss@iki.fi>
References: <1223809356.27703.233.camel@hurina>
In-Reply-To: <1223809356.27703.233.camel@hurina>
MIME-Version: 1.0
Cc: lemonade@ietf.org
Subject: Re: [lemonade] QRESYNC again
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

Timo Sirainen wrote:

>I think we decided two things when QRESYNC is enabled:
>
>1) FETCH replies will always contain UID
>2) CLOSE doesn't send HIGHESTMODSEQ and it's recommended against using
>it at all.
>
>But I'm not really sure if anything was decided about the 3rd issue
>where:
>
>C1: a EXPUNGE
>S1: * VANISHED 1234
>S1: a ok [highestmodseq 2]
>
>C2: b STORE 1 -FLAGS \Seen
>S2: * 1 fetch (flags () modseq 3)
>S2: b ok
>[[Client 2 disconnects]]
>
>Client 2 loses the VANISHED reply. My idea was that server would be able
>to detect this and send just before the "b ok":
>
>* OK [HIGHESTMODSEQ 1]
>
>Which would tell the client that it doesn't know all the modseqs yet.
>
While I originally had some reservations about this solution, it looks 
sensible to me now.


_______________________________________________
lemonade mailing list
lemonade@ietf.org
https://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade


From lemonade-bounces@ietf.org  Sun Oct 19 13:08:14 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 48C7B3A6A95;
	Sun, 19 Oct 2008 13:08:14 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 487623A6A95
	for <lemonade@core3.amsl.com>; Sun, 19 Oct 2008 13:08:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[AWL=0.164, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id PvIYxsH3O+qR for <lemonade@core3.amsl.com>;
	Sun, 19 Oct 2008 13:08:12 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251])
	by core3.amsl.com (Postfix) with ESMTP id 2CCC13A680F
	for <lemonade@ietf.org>; Sun, 19 Oct 2008 13:08:12 -0700 (PDT)
Received: from [92.40.27.147] (92.40.27.147.sub.mbb.three.co.uk
	[92.40.27.147]) 
	by rufus.isode.com (submission channel) via TCP with ESMTPA 
	id <SPuT7QBpDFt7@rufus.isode.com>; Sun, 19 Oct 2008 21:09:19 +0100
Message-ID: <48FB93D8.4030501@isode.com>
Date: Sun, 19 Oct 2008 21:08:56 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
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: Timo Sirainen <tss@iki.fi>
References: <1223809356.27703.233.camel@hurina> <48FB137B.5000906@isode.com>
In-Reply-To: <48FB137B.5000906@isode.com>
MIME-Version: 1.0
Cc: Lemonade WG <lemonade@ietf.org>
Subject: Re: [lemonade] QRESYNC again
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

Hi Timo,
I've started updating my copy of the QRESYNCbis document.

Alexey Melnikov wrote:

> Timo Sirainen wrote:
>
>> I think we decided two things when QRESYNC is enabled:
>> 1) FETCH replies will always contain UID
>
I've just updated my copy by adding the following text:

    Once a "CONDSTORE enabling command" is issued by the client,
    the server MUST automatically include both UID and mod-sequence data
    in all subsequent untagged FETCH responses (until the connection is 
closed),
    whether they were caused by a regular STORE, a STORE with UNCHANGEDSINCE
    modifier, or an external agent.

This is similar to the text in the CONDSTORE RFC.

>> 2) CLOSE doesn't send HIGHESTMODSEQ
>
I've added the following text to address that:

    The server MUST NOT send the updated per-mailbox modification sequence
    using the HIGHESTMODSEQ response code (defined in [CONDSTORE]
    in the tagged OK response, as this might cause loss of synchronization
    on the client.

>> and it's recommended against using it
>
Can you elaborate on what do you mean by "it" here?

>> at all.
>

_______________________________________________
lemonade mailing list
lemonade@ietf.org
https://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade


From lemonade-bounces@ietf.org  Sun Oct 19 13:26:48 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 810AD3A68E4;
	Sun, 19 Oct 2008 13:26:48 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D43593A68E4
	for <lemonade@core3.amsl.com>; Sun, 19 Oct 2008 13:26:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.274
X-Spam-Level: 
X-Spam-Status: No, score=-6.274 tagged_above=-999 required=5 tests=[AWL=0.326, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 5jBWAaUxLWRD for <lemonade@core3.amsl.com>;
	Sun, 19 Oct 2008 13:26:47 -0700 (PDT)
Received: from dovecot.org (dovecot.org [82.118.211.50])
	by core3.amsl.com (Postfix) with ESMTP id E7FBA3A67D4
	for <lemonade@ietf.org>; Sun, 19 Oct 2008 13:26:46 -0700 (PDT)
Received: from [192.168.10.200] (xdsl-177-118.nblnetworks.fi [217.30.177.118])
	by dovecot.org (Postfix) with ESMTP id 22923FA8AA9;
	Sun, 19 Oct 2008 23:27:52 +0300 (EEST)
Message-Id: <487C9C54-DEF9-41D2-A47D-DC5BD9248E3D@iki.fi>
From: Timo Sirainen <tss@iki.fi>
To: Alexey Melnikov <alexey.melnikov@isode.com>
In-Reply-To: <48FB93D8.4030501@isode.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sun, 19 Oct 2008 23:27:48 +0300
References: <1223809356.27703.233.camel@hurina> <48FB137B.5000906@isode.com>
	<48FB93D8.4030501@isode.com>
X-Pgp-Agent: GPGMail d51 (Leopard)
X-Mailer: Apple Mail (2.929.2)
Cc: Lemonade WG <lemonade@ietf.org>
Subject: Re: [lemonade] QRESYNC again
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2080112159=="
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============2080112159==
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-17--819751174"
Content-Transfer-Encoding: 7bit

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--Apple-Mail-17--819751174
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit

On Oct 19, 2008, at 11:08 PM, Alexey Melnikov wrote:

> I've just updated my copy by adding the following text:
>
>   Once a "CONDSTORE enabling command" is issued by the client,
>   the server MUST automatically include both UID and mod-sequence data
>   in all subsequent untagged FETCH responses (until the connection  
> is closed),
>   whether they were caused by a regular STORE, a STORE with  
> UNCHANGEDSINCE
>   modifier, or an external agent.

What about FETCH command without UID parameter?

>>> 2) CLOSE doesn't send HIGHESTMODSEQ
>>
> I've added the following text to address that:
>
>   The server MUST NOT send the updated per-mailbox modification  
> sequence
>   using the HIGHESTMODSEQ response code (defined in [CONDSTORE]
>   in the tagged OK response, as this might cause loss of  
> synchronization
>   on the client.
>
>>> and it's recommended against using it
>>
> Can you elaborate on what do you mean by "it" here?
>
>>> at all.

I guess I was thinking something like "Since the client probably cares  
about knowing the latest mailbox modseq state, it should use EXPUNGE +  
SELECT/UNSELECT/LOGOUT instead of CLOSE command."


--Apple-Mail-17--819751174
content-type: application/pgp-signature; x-mac-type=70674453;
	name=PGP.sig
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
content-transfer-encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkj7mEQACgkQyUhSUUBVisldLACgnN2sOXkdznzoEAbyz6Gd5Kgn
Gu8AnA8a8kN0XfIizvcJYgTOoAcAlMrK
=mqr5
-----END PGP SIGNATURE-----

--Apple-Mail-17--819751174--

--===============2080112159==
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://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade
--===============2080112159==--


From lemonade-bounces@ietf.org  Sun Oct 19 13:35:47 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 28D933A6A95;
	Sun, 19 Oct 2008 13:35:47 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 892483A6AA5
	for <lemonade@core3.amsl.com>; Sun, 19 Oct 2008 13:35:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.455
X-Spam-Level: 
X-Spam-Status: No, score=-2.455 tagged_above=-999 required=5 tests=[AWL=0.144, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id SpFsF9p1WOG9 for <lemonade@core3.amsl.com>;
	Sun, 19 Oct 2008 13:35:44 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251])
	by core3.amsl.com (Postfix) with ESMTP id 868DD3A6864
	for <lemonade@ietf.org>; Sun, 19 Oct 2008 13:35:44 -0700 (PDT)
Received: from [92.40.27.147] (92.40.27.147.sub.mbb.three.co.uk
	[92.40.27.147]) 
	by rufus.isode.com (submission channel) via TCP with ESMTPA 
	id <SPuaZABpDIFM@rufus.isode.com>; Sun, 19 Oct 2008 21:36:53 +0100
Message-ID: <48FB9A54.4020408@isode.com>
Date: Sun, 19 Oct 2008 21:36:36 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
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: Timo Sirainen <tss@iki.fi>
References: <1223809356.27703.233.camel@hurina> <48FB137B.5000906@isode.com>
	<48FB93D8.4030501@isode.com>
	<487C9C54-DEF9-41D2-A47D-DC5BD9248E3D@iki.fi>
In-Reply-To: <487C9C54-DEF9-41D2-A47D-DC5BD9248E3D@iki.fi>
MIME-Version: 1.0
Cc: Lemonade WG <lemonade@ietf.org>
Subject: Re: [lemonade] QRESYNC again
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

Timo Sirainen wrote:

> On Oct 19, 2008, at 11:08 PM, Alexey Melnikov wrote:
>
>> I've just updated my copy by adding the following text:
>>
>>   Once a "CONDSTORE enabling command" is issued by the client,
>>   the server MUST automatically include both UID and mod-sequence data
>>   in all subsequent untagged FETCH responses (until the connection  
>> is closed),
>>   whether they were caused by a regular STORE, a STORE with  
>> UNCHANGEDSINCE
>>   modifier, or an external agent.
>
> What about FETCH command without UID parameter?

Ok, I will add this to the list.

_______________________________________________
lemonade mailing list
lemonade@ietf.org
https://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade


From lemonade-bounces@ietf.org  Sun Oct 19 13:37:38 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4D9AD3A6A95;
	Sun, 19 Oct 2008 13:37:38 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A8D743A6A95
	for <lemonade@core3.amsl.com>; Sun, 19 Oct 2008 13:37:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.328
X-Spam-Level: 
X-Spam-Status: No, score=-6.328 tagged_above=-999 required=5 tests=[AWL=0.271, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id o2zbwSgmfgvP for <lemonade@core3.amsl.com>;
	Sun, 19 Oct 2008 13:37:36 -0700 (PDT)
Received: from dovecot.org (dovecot.org [82.118.211.50])
	by core3.amsl.com (Postfix) with ESMTP id D2FE73A68E4
	for <lemonade@ietf.org>; Sun, 19 Oct 2008 13:37:35 -0700 (PDT)
Received: from [192.168.10.200] (xdsl-177-118.nblnetworks.fi [217.30.177.118])
	by dovecot.org (Postfix) with ESMTP id 5580316471FE;
	Sun, 19 Oct 2008 23:38:45 +0300 (EEST)
Message-Id: <14C8970C-7E09-462A-99F2-316DEB4DFBC5@iki.fi>
From: Timo Sirainen <tss@iki.fi>
To: Alexey Melnikov <alexey.melnikov@isode.com>
In-Reply-To: <48FB9A54.4020408@isode.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sun, 19 Oct 2008 23:38:44 +0300
References: <1223809356.27703.233.camel@hurina> <48FB137B.5000906@isode.com>
	<48FB93D8.4030501@isode.com>
	<487C9C54-DEF9-41D2-A47D-DC5BD9248E3D@iki.fi>
	<48FB9A54.4020408@isode.com>
X-Pgp-Agent: GPGMail d51 (Leopard)
X-Mailer: Apple Mail (2.929.2)
Cc: Lemonade WG <lemonade@ietf.org>
Subject: Re: [lemonade] QRESYNC again
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0438951857=="
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0438951857==
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-18--819094593"
Content-Transfer-Encoding: 7bit

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--Apple-Mail-18--819094593
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit

On Oct 19, 2008, at 11:36 PM, Alexey Melnikov wrote:

> Timo Sirainen wrote:
>
>> On Oct 19, 2008, at 11:08 PM, Alexey Melnikov wrote:
>>
>>> I've just updated my copy by adding the following text:
>>>
>>>  Once a "CONDSTORE enabling command" is issued by the client,
>>>  the server MUST automatically include both UID and mod-sequence  
>>> data
>>>  in all subsequent untagged FETCH responses (until the connection   
>>> is closed),
>>>  whether they were caused by a regular STORE, a STORE with   
>>> UNCHANGEDSINCE
>>>  modifier, or an external agent.
>>
>> What about FETCH command without UID parameter?
>
> Ok, I will add this to the list.

I was rather thinking that maybe that shouldn't contain the UID since  
if client wanted it it would have used the UID parameter. But I don't  
really care that much :)


--Apple-Mail-18--819094593
content-type: application/pgp-signature; x-mac-type=70674453;
	name=PGP.sig
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
content-transfer-encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkj7mtQACgkQyUhSUUBVislBpQCdHzGMwQis6sNAzOyTWivKcGDb
BnwAoJv5IjjFRDYY4U6P21Pc0MT9t03M
=ClCK
-----END PGP SIGNATURE-----

--Apple-Mail-18--819094593--

--===============0438951857==
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://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade
--===============0438951857==--


From lemonade-bounces@ietf.org  Sun Oct 19 13:58:50 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0D92F3A6AB5;
	Sun, 19 Oct 2008 13:58:50 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DCD073A67AB
	for <lemonade@core3.amsl.com>; Sun, 19 Oct 2008 13:58:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.471
X-Spam-Level: 
X-Spam-Status: No, score=-2.471 tagged_above=-999 required=5 tests=[AWL=0.128, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id H+WC6ai4gWfg for <lemonade@core3.amsl.com>;
	Sun, 19 Oct 2008 13:58:48 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251])
	by core3.amsl.com (Postfix) with ESMTP id D42ED3A6AB5
	for <lemonade@ietf.org>; Sun, 19 Oct 2008 13:58:47 -0700 (PDT)
Received: from [92.40.27.147] (92.40.27.147.sub.mbb.three.co.uk
	[92.40.27.147]) 
	by rufus.isode.com (submission channel) via TCP with ESMTPA 
	id <SPufxgBpDEnv@rufus.isode.com>; Sun, 19 Oct 2008 21:59:55 +0100
Message-ID: <48FB9FB4.7010106@isode.com>
Date: Sun, 19 Oct 2008 21:59:32 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
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: Timo Sirainen <tss@iki.fi>
References: <1223809356.27703.233.camel@hurina> <48FB137B.5000906@isode.com>
	<48FB93D8.4030501@isode.com>
	<487C9C54-DEF9-41D2-A47D-DC5BD9248E3D@iki.fi>
	<48FB9A54.4020408@isode.com>
	<14C8970C-7E09-462A-99F2-316DEB4DFBC5@iki.fi>
In-Reply-To: <14C8970C-7E09-462A-99F2-316DEB4DFBC5@iki.fi>
MIME-Version: 1.0
Cc: Lemonade WG <lemonade@ietf.org>
Subject: Re: [lemonade] QRESYNC again
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

Timo Sirainen wrote:

> On Oct 19, 2008, at 11:36 PM, Alexey Melnikov wrote:
>
>> Timo Sirainen wrote:
>>
>>> On Oct 19, 2008, at 11:08 PM, Alexey Melnikov wrote:
>>>
>>>> I've just updated my copy by adding the following text:
>>>>
>>>>  Once a "CONDSTORE enabling command" is issued by the client,
>>>>  the server MUST automatically include both UID and mod-sequence  data
>>>>  in all subsequent untagged FETCH responses (until the connection   
>>>> is closed),
>>>>  whether they were caused by a regular STORE, a STORE with   
>>>> UNCHANGEDSINCE
>>>>  modifier, or an external agent.
>>>
>>> What about FETCH command without UID parameter?
>>
>> Ok, I will add this to the list.
>
> I was rather thinking that maybe that shouldn't contain the UID since  
> if client wanted it it would have used the UID parameter. But I don't  
> really care that much :)

Why did you mention FETCH then, as it was clearly NOT in the list above :-)?

I can go either way with FETCH, I don't really care.

_______________________________________________
lemonade mailing list
lemonade@ietf.org
https://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade


From lemonade-bounces@ietf.org  Sun Oct 19 14:02:28 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4EB6A3A6ABB;
	Sun, 19 Oct 2008 14:02:28 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 73AEB3A6ABE
	for <lemonade@core3.amsl.com>; Sun, 19 Oct 2008 14:02:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.367
X-Spam-Level: 
X-Spam-Status: No, score=-6.367 tagged_above=-999 required=5 tests=[AWL=0.232, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id gQ8bY2W8l9HE for <lemonade@core3.amsl.com>;
	Sun, 19 Oct 2008 14:02:26 -0700 (PDT)
Received: from dovecot.org (dovecot.org [82.118.211.50])
	by core3.amsl.com (Postfix) with ESMTP id 5D54A3A6917
	for <lemonade@ietf.org>; Sun, 19 Oct 2008 14:02:26 -0700 (PDT)
Received: from [192.168.10.200] (xdsl-177-118.nblnetworks.fi [217.30.177.118])
	by dovecot.org (Postfix) with ESMTP id AF7C316473AC;
	Mon, 20 Oct 2008 00:03:33 +0300 (EEST)
Message-Id: <7AC779D8-0A89-4E84-82B7-CD9AD97D439C@iki.fi>
From: Timo Sirainen <tss@iki.fi>
To: Alexey Melnikov <alexey.melnikov@isode.com>
In-Reply-To: <48FB9FB4.7010106@isode.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 20 Oct 2008 00:03:33 +0300
References: <1223809356.27703.233.camel@hurina> <48FB137B.5000906@isode.com>
	<48FB93D8.4030501@isode.com>
	<487C9C54-DEF9-41D2-A47D-DC5BD9248E3D@iki.fi>
	<48FB9A54.4020408@isode.com>
	<14C8970C-7E09-462A-99F2-316DEB4DFBC5@iki.fi>
	<48FB9FB4.7010106@isode.com>
X-Pgp-Agent: GPGMail d51 (Leopard)
X-Mailer: Apple Mail (2.929.2)
Cc: Lemonade WG <lemonade@ietf.org>
Subject: Re: [lemonade] QRESYNC again
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0928316216=="
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0928316216==
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-19--817606184"
Content-Transfer-Encoding: 7bit

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--Apple-Mail-19--817606184
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit

On Oct 19, 2008, at 11:59 PM, Alexey Melnikov wrote:

> Timo Sirainen wrote:
>
>> On Oct 19, 2008, at 11:36 PM, Alexey Melnikov wrote:
>>
>>> Timo Sirainen wrote:
>>>
>>>> On Oct 19, 2008, at 11:08 PM, Alexey Melnikov wrote:
>>>>
>>>>> I've just updated my copy by adding the following text:
>>>>>
>>>>> Once a "CONDSTORE enabling command" is issued by the client,
>>>>> the server MUST automatically include both UID and mod-sequence   
>>>>> data
>>>>> in all subsequent untagged FETCH responses (until the  
>>>>> connection   is closed),
>>>>> whether they were caused by a regular STORE, a STORE with    
>>>>> UNCHANGEDSINCE
>>>>> modifier, or an external agent.
>>>>
>>>> What about FETCH command without UID parameter?
>>>
>>> Ok, I will add this to the list.
>>
>> I was rather thinking that maybe that shouldn't contain the UID  
>> since  if client wanted it it would have used the UID parameter.  
>> But I don't  really care that much :)
>
> Why did you mention FETCH then, as it was clearly NOT in the list  
> above :-)?
>
> I can go either way with FETCH, I don't really care.


Because it says "all untagged FETCH responses", and I think that also  
means the FETCH responses to FETCH commands even though it's not  
explicitly in the following list (they seem like examples rather than  
a definitive list).

--Apple-Mail-19--817606184
content-type: application/pgp-signature; x-mac-type=70674453;
	name=PGP.sig
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
content-transfer-encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkj7oKUACgkQyUhSUUBVislUfQCgptnyGPmteuP5ic8mIxBb2678
yBQAn2yXRmkbsj1pPcYNhRGHN8gNwHUU
=eKcc
-----END PGP SIGNATURE-----

--Apple-Mail-19--817606184--

--===============0928316216==
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://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade
--===============0928316216==--


From lemonade-bounces@ietf.org  Sun Oct 19 14:11:43 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9E1E73A68BB;
	Sun, 19 Oct 2008 14:11:43 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 659093A67AB
	for <lemonade@core3.amsl.com>; Sun, 19 Oct 2008 14:11:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.561
X-Spam-Level: 
X-Spam-Status: No, score=-2.561 tagged_above=-999 required=5 tests=[AWL=0.038, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id gp-dq8dxM0If for <lemonade@core3.amsl.com>;
	Sun, 19 Oct 2008 14:11:41 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251])
	by core3.amsl.com (Postfix) with ESMTP id A5E983A68BB
	for <lemonade@ietf.org>; Sun, 19 Oct 2008 14:11:40 -0700 (PDT)
Received: from [172.16.2.156] (shiny.isode.com [62.3.217.250]) 
	by rufus.isode.com (submission channel) via TCP with ESMTPA 
	id <SPuiuQBpDFI2@rufus.isode.com>; Sun, 19 Oct 2008 22:12:45 +0100
Message-ID: <48FBA288.3010309@isode.com>
Date: Sun, 19 Oct 2008 22:11:36 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
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: Timo Sirainen <tss@iki.fi>
References: <1223809356.27703.233.camel@hurina> <48FB137B.5000906@isode.com>
	<48FB93D8.4030501@isode.com>
	<487C9C54-DEF9-41D2-A47D-DC5BD9248E3D@iki.fi>
	<48FB9A54.4020408@isode.com>
	<14C8970C-7E09-462A-99F2-316DEB4DFBC5@iki.fi>
	<48FB9FB4.7010106@isode.com>
	<7AC779D8-0A89-4E84-82B7-CD9AD97D439C@iki.fi>
In-Reply-To: <7AC779D8-0A89-4E84-82B7-CD9AD97D439C@iki.fi>
MIME-Version: 1.0
Cc: Lemonade WG <lemonade@ietf.org>
Subject: Re: [lemonade] QRESYNC again
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

Timo Sirainen wrote:

> On Oct 19, 2008, at 11:59 PM, Alexey Melnikov wrote:
>
>> Timo Sirainen wrote:
>>
>>> On Oct 19, 2008, at 11:36 PM, Alexey Melnikov wrote:
>>>
>>>> Timo Sirainen wrote:
>>>
 [...]

>>>>> What about FETCH command without UID parameter?
>>>>
>>>> Ok, I will add this to the list.
>>>
>>> I was rather thinking that maybe that shouldn't contain the UID  
>>> since  if client wanted it it would have used the UID parameter.  
>>> But I don't  really care that much :)
>>
>> Why did you mention FETCH then, as it was clearly NOT in the list  
>> above :-)?
>>
>> I can go either way with FETCH, I don't really care.
>
> Because it says "all untagged FETCH responses", and I think that also  
> means the FETCH responses to FETCH commands even though it's not  
> explicitly in the following list (they seem like examples rather than  
> a definitive list).

Ok, how about the following text:

    Once a "CONDSTORE enabling command" is issued by the client,
    the server MUST automatically include both UID and mod-sequence data
    in all subsequent untagged FETCH responses (until the connection is 
closed),
    whether they were caused by a regular STORE/UID STORE, a STORE/UID STORE
    with UNCHANGEDSINCE modifier, or an external agent.
    Note that this rule doesn't affect untagged FETCH responses caused 
by a FETCH
    command that doesn't include UID and/or MODSEQ FETCH data item, or 
UID FETCH
    without the MODSEQ FETCH data item.

_______________________________________________
lemonade mailing list
lemonade@ietf.org
https://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade


From lemonade-bounces@ietf.org  Sun Oct 19 14:25:44 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2E5723A6A28;
	Sun, 19 Oct 2008 14:25:44 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 391193A68ED
	for <lemonade@core3.amsl.com>; Sun, 19 Oct 2008 14:25:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.396
X-Spam-Level: 
X-Spam-Status: No, score=-6.396 tagged_above=-999 required=5 tests=[AWL=0.203, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id u5m2DEkRQaFx for <lemonade@core3.amsl.com>;
	Sun, 19 Oct 2008 14:25:42 -0700 (PDT)
Received: from dovecot.org (dovecot.org [82.118.211.50])
	by core3.amsl.com (Postfix) with ESMTP id 3EBB73A6A28
	for <lemonade@ietf.org>; Sun, 19 Oct 2008 14:25:42 -0700 (PDT)
Received: from [192.168.10.200] (xdsl-177-118.nblnetworks.fi [217.30.177.118])
	by dovecot.org (Postfix) with ESMTP id 6A60916473A9;
	Mon, 20 Oct 2008 00:26:31 +0300 (EEST)
Message-Id: <3E243744-6F24-4D6C-B851-D8716C2A90B7@iki.fi>
From: Timo Sirainen <tss@iki.fi>
To: Alexey Melnikov <alexey.melnikov@isode.com>
In-Reply-To: <48FBA288.3010309@isode.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 20 Oct 2008 00:26:30 +0300
References: <1223809356.27703.233.camel@hurina> <48FB137B.5000906@isode.com>
	<48FB93D8.4030501@isode.com>
	<487C9C54-DEF9-41D2-A47D-DC5BD9248E3D@iki.fi>
	<48FB9A54.4020408@isode.com>
	<14C8970C-7E09-462A-99F2-316DEB4DFBC5@iki.fi>
	<48FB9FB4.7010106@isode.com>
	<7AC779D8-0A89-4E84-82B7-CD9AD97D439C@iki.fi>
	<48FBA288.3010309@isode.com>
X-Pgp-Agent: GPGMail d51 (Leopard)
X-Mailer: Apple Mail (2.929.2)
Cc: Lemonade WG <lemonade@ietf.org>
Subject: Re: [lemonade] QRESYNC again
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0278111695=="
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0278111695==
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-20--816228623"
Content-Transfer-Encoding: 7bit

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--Apple-Mail-20--816228623
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit

On Oct 20, 2008, at 12:11 AM, Alexey Melnikov wrote:

>   Once a "CONDSTORE enabling command" is issued by the client,
>   the server MUST automatically include both UID and mod-sequence data
>   in all subsequent untagged FETCH responses (until the connection  
> is closed),
>   whether they were caused by a regular STORE/UID STORE, a STORE/UID  
> STORE
>   with UNCHANGEDSINCE modifier, or an external agent.
>   Note that this rule doesn't affect untagged FETCH responses caused  
> by a FETCH
>   command that doesn't include UID and/or MODSEQ FETCH data item, or  
> UID FETCH
>   without the MODSEQ FETCH data item.

That looks good to me.


--Apple-Mail-20--816228623
content-type: application/pgp-signature; x-mac-type=70674453;
	name=PGP.sig
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
content-transfer-encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkj7pgYACgkQyUhSUUBVisk/QgCfdimNsvGmXN3Oxu2pqACXFV/J
7Z0An3uTBC6gFM8KbBFGdYlljB1Z3MXI
=AZBh
-----END PGP SIGNATURE-----

--Apple-Mail-20--816228623--

--===============0278111695==
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://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade
--===============0278111695==--


From lemonade-bounces@ietf.org  Sun Oct 19 14:45:03 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3517428C0EA;
	Sun, 19 Oct 2008 14:45:03 -0700 (PDT)
X-Original-To: lemonade@ietf.org
Delivered-To: lemonade@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 08F3E3A6AC1; Sun, 19 Oct 2008 14:45:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081019214502.08F3E3A6AC1@core3.amsl.com>
Date: Sun, 19 Oct 2008 14:45:02 -0700 (PDT)
Cc: lemonade@ietf.org
Subject: [lemonade] I-D Action:draft-ietf-lemonade-5162bis-00.txt
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
Sender: lemonade-bounces@ietf.org
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           : IMAP4 Extensions for Quick Mailbox Resynchronization
	Author(s)       : A. Melnikov, et al.
	Filename        : draft-ietf-lemonade-5162bis-00.txt
	Pages           : 25
	Date            : 2008-10-19

This document defines an IMAP4 extension, which gives an IMAP client
the ability to quickly resynchronize any previously opened mailbox as
part of the SELECT command, without the need for server-side state or
additional client round-trips.  This extension also introduces a new
response that allows for a more compact representation of a list of
expunged messages (and always includes the Unique Identifiers (UIDs)
expunged).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-lemonade-5162bis-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-ietf-lemonade-5162bis-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-10-19143258.I-D@ietf.org>


--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://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade
--NextPart--


From lemonade-bounces@ietf.org  Mon Oct 20 06:14:09 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 60D293A6A2F;
	Mon, 20 Oct 2008 06:14:09 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2F6D53A69F9
	for <lemonade@core3.amsl.com>; Mon, 20 Oct 2008 06:14:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RZgNxn-UJ8v8 for <lemonade@core3.amsl.com>;
	Mon, 20 Oct 2008 06:14:07 -0700 (PDT)
Received: from ncookx.randomflow.net (ncookx.randomflow.net [78.129.143.222])
	by core3.amsl.com (Postfix) with ESMTP id 333013A68DA
	for <lemonade@ietf.org>; Mon, 20 Oct 2008 06:14:06 -0700 (PDT)
Authentication-Results: ncookx smtp.user=ncook; auth=pass (LOGIN)
X-Cloudmark-Analysis: v=1.0 c=1 a=5zNiokQ0KmmPw4Fxb74A:9
	a=-rUB7r8cAq1y-yrzzpMA:7 a=YMQmskABSz0YKMpXjh2qQZXGVOgA:4
	a=-ZQhYGXY2L8A:10
X-Cloudmark-SWS: 
X-Cloudmark-SRS: 
Received: from [72.5.239.5] ([72.5.239.5:62533] helo=[172.22.1.157])
	by ncookx (envelope-from <neil.cook@noware.co.uk>)
	(ecelerity 2.2.2.29 r(23143M)) with ESMTPA
	id 70/00-23812-FC18CF84; Mon, 20 Oct 2008 09:04:16 -0400
Message-Id: <6BDEE540-9790-4E3C-B5CD-29FA7073CC5F@noware.co.uk>
From: Neil Cook <neil.cook@noware.co.uk>
To: "lemonade@ietf.org service enivronments" <lemonade@ietf.org>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Mon, 20 Oct 2008 14:15:11 +0100
X-Mailer: Apple Mail (2.919.2)
Subject: [lemonade] New stream+ prefix for streaming
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

Folks,

It appears we have a rough consensus on using a new "stream+" prefix  
to handle the streaming use case - the general feeling being that  
using separate prefixes helps reduce the attack surface for particular  
prefix types.

Bearing in mind that this will require a new draft, and that new  
prefixes may well be required in the future, I propose the following:

1) I will modify the streaming draft to use a new "stream+" prefix

2) I will create a new (standard track) draft that describes the stream 
+ prefix, as well as an IANA mechanism to define new ones.

Please reply if you object to this proposal,

Neil

_______________________________________________
lemonade mailing list
lemonade@ietf.org
https://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade


From lemonade-bounces@ietf.org  Thu Oct 23 14:59:32 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9398028C16E;
	Thu, 23 Oct 2008 14:59:32 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C523F28C144;
	Thu, 23 Oct 2008 14:59:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.416
X-Spam-Level: 
X-Spam-Status: No, score=-17.416 tagged_above=-999 required=5
	tests=[AWL=0.183, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id VsoauMqxREDG; Thu, 23 Oct 2008 14:59:29 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207])
	by core3.amsl.com (Postfix) with ESMTP id ECB1828C13A;
	Thu, 23 Oct 2008 14:59:28 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70)
	id EDD4816A84E; Thu, 23 Oct 2008 15:00:46 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20081023220046.EDD4816A84E@bosco.isi.edu>
Date: Thu, 23 Oct 2008 15:00:46 -0700 (PDT)
Cc: lemonade@ietf.org, rfc-editor@rfc-editor.org
Subject: [lemonade] BCP 143,
	RFC 5383 on Deployment Considerations for Lemonade-Compliant Mobile
	Email
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>,
	<mailto:lemonade-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org


A new Request for Comments is now available in online RFC libraries.

        BCP 143        
        RFC 5383

        Title:      Deployment Considerations for Lemonade-Compliant
                    Mobile Email 
        Author:     R. Gellens
        Status:     Best Current Practice
        Date:       October 2008
        Mailbox:    randy@qualcomm.com
        Pages:      12
        Characters: 28290
        See Also:   BCP0143

        I-D Tag:    draft-ietf-lemonade-deployments-09.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5383.txt

This document discusses deployment issues and describes requirements
for successful deployment of mobile email that are implicit in the
IETF lemonade documents.  This document specifies an Internet Best Current 
Practices for the Internet Community, and requests discussion and
suggestions for improvements.

This document is a product of the Enhancements to Internet email to support diverse service environments Working Group of the IETF.


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute


_______________________________________________
lemonade mailing list
lemonade@ietf.org
https://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade


