From lemonade-bounces@ietf.org  Fri May  2 17:18:11 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 core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 238963A6C32;
	Fri,  2 May 2008 17:18:11 -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 3C79B3A6C32
	for <lemonade@core3.amsl.com>; Fri,  2 May 2008 17:18:09 -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 l9kJgVUSjGUg for <lemonade@core3.amsl.com>;
	Fri,  2 May 2008 17:18:08 -0700 (PDT)
Received: from dovecot.org (dovecot.org [82.118.211.50])
	by core3.amsl.com (Postfix) with ESMTP id 62D8A3A6C17
	for <lemonade@ietf.org>; Fri,  2 May 2008 17:18:08 -0700 (PDT)
Received: from [192.168.10.2] (82-203-162-146.dsl.gohome.fi [82.203.162.146])
	by dovecot.org (Postfix) with ESMTP id 5893D16471E7
	for <lemonade@ietf.org>; Sat,  3 May 2008 03:17:36 +0300 (EEST)
From: Timo Sirainen <tss@iki.fi>
To: lemonade@ietf.org
Date: Sat, 03 May 2008 03:17:36 +0300
Message-Id: <1209773856.9518.31.camel@hurina>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.1 
Subject: [lemonade] Another QRESYNC race condition
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-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="===============1815520222=="
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org


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


--=-/AiNJ4l7SVTnsTR9g4Ue
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

> After completing a full synchronization, the client MUST also take
>    note of any unsolicited MODSEQ FETCH data items received from the
>    server.  Whenever the client receives a tagged response to a command,
>    it calculates the highest value among all MODSEQ FETCH data items
>    received since the last tagged response.  If this value is bigger
>    than the client's copy of the HIGHESTMODSEQ value, then the client
>    MUST use this value as its new HIGHESTMODSEQ value.

Problem:

C1: a store 1 +flags \seen
S1: * 1 FETCH (FLAGS (\Seen) MODSEQ (1))
S1: a OK

C2: b expunge
S2: * VANISHED 1234
S2: b OK [HIGHESTMODSEQ 2]

C1: c store 1 -flags \seen
=EF=BB=BFS1: * 1 FETCH (FLAGS () MODSEQ (3))
S1: c OK

If C1 disconnects here, the next resync won't show that UID 1234 was
expunged, because it uses 3 as the last seen HIGHESTMODSEQ.

Are there any solutions? The only real one that I can see is that a
client shouldn't update HIGHESTMODSEQ immediately after SEARCH, STORE,
FETCH, SORT and THREAD command replies, but should remember it until a
future "expunge-invoking" command finishes. After then the client can
update the HIGHESTMODSEQ with the previous value (or new one if there
had been more changes).

This also requires that the server MUST send pending EXPUNGE/VANISHED
replies on such expunge-invoking commands. Those commands would probably
be: NOOP, CHECK, UID <anything>, APPEND, IDLE, UNSELECT and obviously
CLOSE and EXPUNGE.


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

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

iD8DBQBIG68gyUhSUUBViskRAlC4AJ9GTmAPMZw0eViCFMsuXbH3XymXkACeN5yJ
1bB/+vOpMWtg9hfUMaWBXsE=
=hwE6
-----END PGP SIGNATURE-----

--=-/AiNJ4l7SVTnsTR9g4Ue--


--===============1815520222==
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
--===============1815520222==--



From lemonade-bounces@ietf.org  Fri May  2 20:03:00 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 core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B05AE28C0F0;
	Fri,  2 May 2008 20:03:00 -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 7480C28C0F0
	for <lemonade@core3.amsl.com>; Fri,  2 May 2008 20:02:59 -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 rBs3PP1OzX9k for <lemonade@core3.amsl.com>;
	Fri,  2 May 2008 20:02:58 -0700 (PDT)
Received: from dovecot.org (dovecot.org [82.118.211.50])
	by core3.amsl.com (Postfix) with ESMTP id 8797A28C0D7
	for <lemonade@ietf.org>; Fri,  2 May 2008 20:02:58 -0700 (PDT)
Received: from [192.168.10.200] (82-203-162-146.dsl.gohome.fi [82.203.162.146])
	by dovecot.org (Postfix) with ESMTP id 8065416471E7
	for <lemonade@ietf.org>; Sat,  3 May 2008 06:02:29 +0300 (EEST)
Message-Id: <1D0DAE42-E047-47A8-960B-0109F1423083@iki.fi>
From: Timo Sirainen <tss@iki.fi>
To: lemonade@ietf.org
In-Reply-To: <1209773856.9518.31.camel@hurina>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Sat, 3 May 2008 06:02:24 +0300
References: <1209773856.9518.31.camel@hurina>
X-Pgp-Agent: GPGMail d51 (Leopard)
X-Mailer: Apple Mail (2.919.2)
Subject: Re: [lemonade] Another QRESYNC race condition
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-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="===============0295562512=="
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

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

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

On May 3, 2008, at 3:17 AM, Timo Sirainen wrote:

> This also requires that the server MUST send pending EXPUNGE/VANISHED
> replies on such expunge-invoking commands. Those commands would  
> probably
> be: NOOP, CHECK, UID <anything>, APPEND, IDLE, UNSELECT and obviously
> CLOSE and EXPUNGE.


(UID <anything> could be replaced with only UID STORE, but the rest of  
them would be required.)

Perhaps a cleaner alternative: Never update HIGHESTMODSEQ from FETCH  
MODSEQs, instead make the server return changed [HIGHESTMODSEQ n] on  
either the FETCH/STORE/etc. tagged command reply, or in some future  
tagged command reply, but only when all the pending changes up to that  
modseq have been sent to the client.


--Apple-Mail-6--451689104
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)

iEYEARECAAYFAkgb1cAACgkQyUhSUUBVislEwwCfdiRVQk+QXayJ05jxRW6cMzl1
yrAAn2fWL4wx7G9dajI4pTxzfJN104Le
=WElP
-----END PGP SIGNATURE-----

--Apple-Mail-6--451689104--

--===============0295562512==
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
--===============0295562512==--


From lemonade-bounces@ietf.org  Sun May  4 09:24:13 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 core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 83EB428C2FB;
	Sun,  4 May 2008 09:24:13 -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 BFB8E3A6906;
	Fri,  2 May 2008 12:02:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.016
X-Spam-Level: 
X-Spam-Status: No, score=-6.016 tagged_above=-999 required=5 tests=[AWL=0.583, 
	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 KgtrO7TiTNTC; Fri,  2 May 2008 12:02:36 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20])
	by core3.amsl.com (Postfix) with ESMTP id 06C3E3A6E59;
	Fri,  2 May 2008 12:02:08 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com
	[10.254.111.54])
	by mexforward.lss.emc.com (Switch-3.2.5/Switch-3.1.7) with ESMTP id
	m42J25MU009987
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 2 May 2008 15:02:05 -0400 (EDT)
Received: from mailhub.lss.emc.com (nagas.lss.emc.com [10.254.144.11]) by
	hop04-l1d11-si01.isus.emc.com (Tablus Interceptor);
	Fri, 2 May 2008 15:02:03 -0400
Received: from corpussmtp3.corp.emc.com (corpussmtp3.corp.emc.com
	[10.254.64.53])
	by mailhub.lss.emc.com (Switch-3.2.5/Switch-3.1.7) with ESMTP id
	m42J20Ia011198; Fri, 2 May 2008 15:02:03 -0400 (EDT)
From: Black_David@emc.com
Received: from CORPUSMX20A.corp.emc.com ([128.221.62.11]) by
	corpussmtp3.corp.emc.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 2 May 2008 15:01:51 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 2 May 2008 15:01:50 -0400
Message-ID: <8CC6CEAB44F131478D3A7B429ECACD91016F6113@CORPUSMX20A.corp.emc.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Gen-ART review of draft-ietf-lemonade-convert-18.txt
Thread-Index: AcietuD6zRiwq9zOTSK6y1+D8tbCgQNzwh6w
To: <'Alexey.Melnikov@isode.com'>, <'peter.coates@Sun.COM'>,
	<'gen-art@ietf.org'>, <'ietf@ietf.org'>, <'lemonade@ietf.org'>
X-OriginalArrivalTime: 02 May 2008 19:01:51.0416 (UTC)
	FILETIME=[FAD8B380:01C8AC86]
X-Tablus-Inspected: yes
X-Tablus-Classifications: public
X-Tablus-Action: allow
X-Mailman-Approved-At: Sun, 04 May 2008 09:24:12 -0700
Cc: 'chris.newman@sun.com', Black_David@emc.com, gparsons@nortel.com
Subject: [lemonade] FW: Gen-ART review of draft-ietf-lemonade-convert-18.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-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

I have been selected as the General Area Review Team (Gen-ART) 
reviewer for this draft (for background on Gen-ART, please see 
http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-ietf-lemonade-convert-18.txt
Reviewer: David L. Black
Review Date: 1 May 2008
IESG Telechat date: 08 May 2008

Summary: 
This draft is ready for publication as a Proposed Standard RFC.

Comments:
This is a generally well-written draft on the CONVERT
extension to IMAP.

All of the minor comments in the Gen-ART review of the -17
version have been addressed in the -18 version.

Many thanks to the authors,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953             FAX: +1 (508) 293-7786
black_david@emc.com        Mobile: +1 (978) 394-7754
----------------------------------------------------
_______________________________________________
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 May  7 03:58: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 core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 664703A7104;
	Wed,  7 May 2008 03:58: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 9277C3A69D7
	for <lemonade@core3.amsl.com>; Wed,  7 May 2008 03:58:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.607
X-Spam-Level: 
X-Spam-Status: No, score=-1.607 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, DATE_IN_PAST_12_24=0.992]
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 cHWEqoCJA9N3 for <lemonade@core3.amsl.com>;
	Wed,  7 May 2008 03:58:44 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251])
	by core3.amsl.com (Postfix) with ESMTP id A766E3A6A13
	for <lemonade@ietf.org>; Wed,  7 May 2008 03:58:43 -0700 (PDT)
Received: from [192.168.0.11] ((unknown) [62.3.217.253]) 
	by rufus.isode.com (submission channel) via TCP with ESMTPA 
	id <SCGLXwA4EcIr@rufus.isode.com>; Wed, 7 May 2008 11:58:40 +0100
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <48206629.5020305@isode.com>
Date: Tue, 06 May 2008 15:07:37 +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: Randall Gellens <randy@qualcomm.com>
References: <C433D1E5.1AB12%eburger@bea.com>
In-Reply-To: <C433D1E5.1AB12%eburger@bea.com>
MIME-Version: 1.0
Cc: lemonade@ietf.org
Subject: Re: [lemonade] WGLC Notifications
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-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

Eric Burger wrote:

>Work Group Last Call for Lemonade Notifications Architecture,
>http://tools.ietf.org/html/draft-ietf-lemonade-notifications-08
>starts now and ends 5 May 2008.
>
The draft is in much better shape now.

Some comments below:

>     *    NF and DF:  When internal to the mail store, these are
>     typically implemented using Sieve and hence a Sieve management
>     protocol is used for client modifications.  See [IMAP-SIEVE] and
>     [MANAGE-SIEVE] for more information.  When the NF is within a
>     notification server, it is out of scope of Lemonade.

I don't think [IMAP-SIEVE] is relevant in case of NF or DF.
Unless NF is invoked on message flag changes, etc.

>     Note that when implementing DF using Sieve, the 'enotify'
>     [SIEVE-NOTIFY] and 'variables' [SIEVE-VARIABLES] Sieve extensions
>     are needed.

If NF is generating notifications on mail delivery, than 'enotify' + 
'variables' is also needed there.
If NF is generating notifications both on mail delivery and IMAP events, 
then 'enotify' + 'variables' are *only* needed in NF.

> 4.  Push Email
>     
>     A good user experience of "push email" requires that when
>     "interesting" events occur in the mail store, the client is informed
>     so that it can connect and resynchronize.  The Lemonade Profile
>     [LEMONADE-PROFILE] contains more information, especially in Section
>     4.1.2.

I can't find section 4.1.2 in draft-ietf-lemonade-profile-bis-08.txt.
/*
*/

_______________________________________________
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 May 11 07:46:22 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 B2EEA28C190;
	Sun, 11 May 2008 07:46:22 -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 95E3028C190
	for <lemonade@core3.amsl.com>; Sun, 11 May 2008 07:46:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.74
X-Spam-Level: 
X-Spam-Status: No, score=-0.74 tagged_above=-999 required=5
	tests=[BAYES_20=-0.74]
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 Mr5nnwgxYRlP for <lemonade@core3.amsl.com>;
	Sun, 11 May 2008 07:46:21 -0700 (PDT)
Received: from smtp101-mob.biz.mail.re2.yahoo.com
	(smtp101-mob.biz.mail.re2.yahoo.com [206.190.36.116])
	by core3.amsl.com (Postfix) with SMTP id 3921928C18D
	for <lemonade@ietf.org>; Sun, 11 May 2008 07:46:21 -0700 (PDT)
Received: (qmail 59409 invoked from network); 11 May 2008 14:39:07 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:X-rim-org-msg-ref-id:Return-Receipt-To:Message-ID:Reply-To:X-Priority:Sensitivity:Importance:To:Subject:From:Date:Content-Type:MIME-Version;
	b=zko2uky7Ta9OZoxF+6ptkzFZwgpxxDS104wO16fB73E7WWOHu/woUaw7aInR/WOGOZhQ6lMLGj6OLcuW8MVYbd69bCfv1c+5oaNFKSHbZ6XFs10dOKcQO70kv2WaMIMZJlpx4N08U9Np6pXjovGMPoQSD0fvCYbSXx5DYE7YaY8=
	; 
Received: from unknown (HELO bda381.bisx.prod.on.blackberry)
	(awe3bz@206.53.151.174 with xymcookie)
	by smtp101-mob.biz.mail.re2.yahoo.com with SMTP;
	11 May 2008 14:39:06 -0000
X-YMail-OSG: kSuCdpcVM1lKviIXZ0OvOVQbeC_qzESeXM084_Mt1GhCtb8IfNnbKhVMYyuH9JUpw7GdxmPxFEAHCaqn6Ne.cSDnd4S0VIt58G5nfxJCQ6DhD6Imvw.2Z3g0JGcc3KSXBQ--
X-Yahoo-Newman-Property: ymail-3
X-rim-org-msg-ref-id: 1371086714
Message-ID: <1371086714-1210516745-cardhu_decombobulator_blackberry.rim.net-609866642-@bxe033.bisx.prod.on.blackberry>
X-Priority: Normal
Sensitivity: Normal
Importance: Normal
To: lemonade@ietf.org,speechsc@ietf.org,mediactrl@ietf.org
From: ewburger@yahoo.com
Date: Sun, 11 May 2008 14:39:03 +0000
MIME-Version: 1.0
Subject: [lemonade] My Whereabouts
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ewburger@yahoo.com
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

Some of you may have noticed my BEA out-of-office message or Plaxo update. Last Friday was my last day with BEA. I happily took the package.

I will be spending the next two months focusing on getting speechsc and lemonade finished, focusing on the SIP Forum, and having fun.

My BEA account has gone away. Please use my StandardsTrack, SIP Forum, or MIT addresses for standards, work, or personal correspondence, respectively. I should have my mobile number ported soon, so that will not change. 
If you subscribe to Plaxo, do not panic (or prematurely rejoice): I am not moving to Stockholm. That is just the office address of the SIP Forum.

Thanks, and get back to work :-)

--
- Eric 

P.S. Please do not respond to this message on-list. Thanks.
Sent from my Verizon Wireless BlackBerry

_______________________________________________
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  Mon May 12 11:30: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 1DE883A6B7A;
	Mon, 12 May 2008 11:30:04 -0700 (PDT)
X-Original-To: lemonade@ietf.org
Delivered-To: lemonade@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id E32433A6822; Mon, 12 May 2008 11:30: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: <20080512183001.E32433A6822@core3.amsl.com>
Date: Mon, 12 May 2008 11:30:01 -0700 (PDT)
Cc: lemonade@ietf.org
Subject: [lemonade] I-D Action:draft-ietf-lemonade-convert-19.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           : IMAP CONVERT extension
	Author(s)       : A. Melnikov, P. Coates
	Filename        : draft-ietf-lemonade-convert-19.txt
	Pages           : 30
	Date            : 2008-05-12

CONVERT defines extensions to IMAP allowing clients to request
adaptation and/or transcoding of attachments.  Clients can specify
the conversion details or allow servers to decide based on knowledge
of client capabilities, on user or administrator preferences or its
settings.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-lemonade-convert-19.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-convert-19.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-05-12112153.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  Tue May 13 14:54: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 10D8B3A6968;
	Tue, 13 May 2008 14:54: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 74A5B3A6962
	for <lemonade@core3.amsl.com>; Tue, 13 May 2008 14:54:11 -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 khirXcfvF+w3 for <lemonade@core3.amsl.com>;
	Tue, 13 May 2008 14:54:10 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19b.inmotionhosting.com
	[66.117.3.189]) by core3.amsl.com (Postfix) with ESMTP id CDEC23A6959
	for <lemonade@ietf.org>; Tue, 13 May 2008 14:54:10 -0700 (PDT)
Received: from [124.17.15.2] (port=45446 helo=[172.31.13.6])
	by gs19.inmotionhosting.com with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.68) (envelope-from <eburger@standardstrack.com>)
	id 1Jw2R0-00055R-UQ
	for lemonade@ietf.org; Tue, 13 May 2008 14:53:26 -0700
Message-Id: <6954AC12-DE98-4D41-9E42-3BE28417B556@standardstrack.com>
From: Eric Burger <eburger@standardstrack.com>
To: lemonade@ietf.org
Mime-Version: 1.0 (Apple Message framework v912)
Date: Wed, 14 May 2008 05:53:27 +0800
X-Mailer: Apple Mail (2.912)
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] Apps Area interop day
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

The Apps Area is considering having an interop day in Dublin.

Any interest for some lemonade interop?
_______________________________________________
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  Fri May 16 05:20:12 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 5BEE43A6B2E;
	Fri, 16 May 2008 05:20:12 -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 4C23E3A6B2E
	for <lemonade@core3.amsl.com>; Fri, 16 May 2008 05:20:11 -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 eObqZkfeySzs for <lemonade@core3.amsl.com>;
	Fri, 16 May 2008 05:20:10 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19b.inmotionhosting.com
	[66.117.3.189]) by core3.amsl.com (Postfix) with ESMTP id 49ED03A6785
	for <lemonade@ietf.org>; Fri, 16 May 2008 05:20:10 -0700 (PDT)
Received: from [75.68.119.237] (port=63363 helo=[192.168.15.100])
	by gs19.inmotionhosting.com with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.68) (envelope-from <eburger@standardstrack.com>)
	id 1Jwyup-0001KP-BQ; Fri, 16 May 2008 05:20:03 -0700
Message-Id: <42D8937C-4FC9-4CCE-95B1-A0219C019888@standardstrack.com>
From: Eric Burger <eburger@standardstrack.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>,
	Randall Gellens <randy@qualcomm.com>
In-Reply-To: <48206629.5020305@isode.com>
Mime-Version: 1.0 (Apple Message framework v912)
Date: Fri, 16 May 2008 08:16:51 -0400
References: <C433D1E5.1AB12%eburger@bea.com> <48206629.5020305@isode.com>
X-Mailer: Apple Mail (2.912)
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: lemonade@ietf.org
Subject: Re: [lemonade] WGLC Notifications
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

I have written up the shepherd document.  Is this OK?



inline

On May 6, 2008, at 10:07 AM, Alexey Melnikov wrote:

> Eric Burger wrote:
>
>> Work Group Last Call for Lemonade Notifications Architecture,
>> http://tools.ietf.org/html/draft-ietf-lemonade-notifications-08
>> starts now and ends 5 May 2008.
>>
> The draft is in much better shape now.
>
> Some comments below:
>
>> *    NF and DF:  When internal to the mail store, these are
>> typically implemented using Sieve and hence a Sieve management
>> protocol is used for client modifications.  See [IMAP-SIEVE] and
>> [MANAGE-SIEVE] for more information.  When the NF is within a
>> notification server, it is out of scope of Lemonade.
>
> I don't think [IMAP-SIEVE] is relevant in case of NF or DF.
> Unless NF is invoked on message flag changes, etc.

We are not saying, "you can only use Sieve."  I read this as "you can  
use Sieve."  In a purely Informational document, "typically  
implemented" has no normative meaning.

>> Note that when implementing DF using Sieve, the 'enotify'
>> [SIEVE-NOTIFY] and 'variables' [SIEVE-VARIABLES] Sieve extensions
>> are needed.
>
> If NF is generating notifications on mail delivery, than 'enotify' +
> 'variables' is also needed there.
> If NF is generating notifications both on mail delivery and IMAP  
> events,
> then 'enotify' + 'variables' are *only* needed in NF.

Do we really need to change the words here?

>> 4.  Push Email
>>
>> A good user experience of "push email" requires that when
>> "interesting" events occur in the mail store, the client is informed
>> so that it can connect and resynchronize.  The Lemonade Profile
>> [LEMONADE-PROFILE] contains more information, especially in Section
>> 4.1.2.
>
> I can't find section 4.1.2 in draft-ietf-lemonade-profile-bis-08.txt.
> /*
> */
I would offer that since profile-bis has a propensity to renumber, we  
reference by name not number.  That way, if we use IPv6 section  
headers, our application still works :-)

OLD

especially in Section 4.1.2

NEW

especially in the section "External Notifications"





Nit: When I read this, I had no idea what "it" is.  Here is my guess.

Section 5.2

OLD

notification system; it then becomes

NEW

notification system.  Thus the security relationship then becomes


_______________________________________________
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  Fri May 16 07:22: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 E591828C1CE;
	Fri, 16 May 2008 07:22: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 2E78228C1E3
	for <lemonade@core3.amsl.com>; Fri, 16 May 2008 07:22:40 -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 JvbfdbVR5Anf for <lemonade@core3.amsl.com>;
	Fri, 16 May 2008 07:22:39 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19b.inmotionhosting.com
	[66.117.3.189]) by core3.amsl.com (Postfix) with ESMTP id 4B0EF28C1CE
	for <lemonade@ietf.org>; Fri, 16 May 2008 07:22:39 -0700 (PDT)
Received: from c-75-68-119-237.hsd1.nh.comcast.net ([75.68.119.237]:63363
	helo=[192.168.15.100])
	by gs19.inmotionhosting.com with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.68) (envelope-from <eburger@standardstrack.com>)
	id 1Jwyuq-0001KP-0r
	for lemonade@ietf.org; Fri, 16 May 2008 05:20:04 -0700
Message-Id: <D047B282-36BC-4EF3-BB9F-27236B8F4B91@standardstrack.com>
From: Eric Burger <eburger@standardstrack.com>
To: lemonade@ietf.org
In-Reply-To: <C433D1C4.1AB0E%eburger@bea.com>
Mime-Version: 1.0 (Apple Message framework v912)
Date: Fri, 16 May 2008 08:16:54 -0400
References: <C433D1C4.1AB0E%eburger@bea.com>
X-Mailer: Apple Mail (2.912)
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] Second WGLC: BINARY
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

Second Last Call closed.

On Apr 22, 2008, at 5:32 PM, Eric Burger wrote:

> Although this is a short document, only 6 pages of text, it did grow  
> by two
> pages and the ABNF was revamped and the example was corrected.  Thus  
> we are
> holding a second call for final comments.
>
> The period for getting your comments in expires 2 May 2008.
>
> http://tools.ietf.org/html/draft-cridland-urlfetch-binary-02
>
>
> Notice:  This email message, together with any attachments, may  
> contain information  of  BEA Systems,  Inc.,  its subsidiaries  and   
> affiliated entities,  that may be confidential,  proprietary,   
> copyrighted  and/or legally privileged, and is intended solely for  
> the use of the individual or entity named in this message. If you  
> are not the intended recipient, and have received this message in  
> error, please immediately return this by email and then delete it.
> _______________________________________________
> lemonade mailing list
> lemonade@ietf.org
> https://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  Fri May 16 07:22: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 196F028C1F4;
	Fri, 16 May 2008 07:22: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 BA9543A6993
	for <lemonade@core3.amsl.com>; Fri, 16 May 2008 07:22:41 -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 kanvh2q28jmQ for <lemonade@core3.amsl.com>;
	Fri, 16 May 2008 07:22:40 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19b.inmotionhosting.com
	[66.117.3.189]) by core3.amsl.com (Postfix) with ESMTP id D1A0128C1CE
	for <lemonade@ietf.org>; Fri, 16 May 2008 07:22:40 -0700 (PDT)
Received: from c-75-68-119-237.hsd1.nh.comcast.net ([75.68.119.237]:63363
	helo=[192.168.15.100])
	by gs19.inmotionhosting.com with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.68) (envelope-from <eburger@standardstrack.com>)
	id 1Jwyuq-0001KP-GB
	for lemonade@ietf.org; Fri, 16 May 2008 05:20:04 -0700
Message-Id: <8B9B8F32-8DEF-40B9-992E-9337FB7AE344@standardstrack.com>
From: Eric Burger <eburger@standardstrack.com>
To: lemonade@ietf.org
In-Reply-To: <C433D277.1AB18%eburger@bea.com>
Mime-Version: 1.0 (Apple Message framework v912)
X-Priority: 2
Date: Fri, 16 May 2008 08:16:58 -0400
References: <C433D277.1AB18%eburger@bea.com>
X-Mailer: Apple Mail (2.912)
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] WGLC NOTIFY
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

DUDES!!!

I still have not received ANY last call comments.  Please at least  
give us some +1's.


On Apr 22, 2008, at 5:35 PM, Eric Burger wrote:

> OK, I may have been joking: there were absolutely NO last call  
> comments.
>
> If NOTIFY is so beautiful that you couldn't even hit +1, go ahead,  
> feel
> good, and +1 me.
>
> Thanks.
>
>
> On 4/22/08 5:10 PM, "Eric Burger" <eburger@bea.com> wrote:
>
>> WGLC is closed.
>>
>>
>> On 3/31/08 10:01 AM, "Eric Burger" <eburger@bea.com> wrote:
>>
>>> IMAP NOTIFY is ready for Work Group Last Call.
>>>
>>> There has already been one comment that Alexey said he will put in  
>>> the
>>> final version.  Anything else anyone wants to see?
>>>
>>> <http://www.ietf.org/internet-drafts/draft-ietf-lemonade-imap-notify-05 
>>> .
>>> txt>
>>>
>>> WGLC closes 11 April 2008.
>>>
>>> Notice:  This email message, together with any attachments, may  
>>> contain
>>> information  of  BEA Systems,  Inc.,  its subsidiaries  and   
>>> affiliated
>>> entities,  that may be confidential,  proprietary,  copyrighted   
>>> and/or
>>> legally privileged, and is intended solely for the use of the  
>>> individual or
>>> entity named in this message. If you are not the intended  
>>> recipient, and have
>>> received this message in error, please immediately return this by  
>>> email and
>>> then delete it.
>>> _______________________________________________
>>> lemonade mailing list
>>> lemonade@ietf.org
>>> https://www.ietf.org/mailman/listinfo/lemonade
>>> Supplemental Web Site:
>>> http://www.standardstrack.com/ietf/lemonade
>>
>>
>> Notice:  This email message, together with any attachments, may  
>> contain
>> information  of  BEA Systems,  Inc.,  its subsidiaries  and   
>> affiliated
>> entities,  that may be confidential,  proprietary,  copyrighted   
>> and/or
>> legally privileged, and is intended solely for the use of the  
>> individual or
>> entity named in this message. If you are not the intended  
>> recipient, and have
>> received this message in error, please immediately return this by  
>> email and
>> then delete it.
>> _______________________________________________
>> lemonade mailing list
>> lemonade@ietf.org
>> https://www.ietf.org/mailman/listinfo/lemonade
>> Supplemental Web Site:
>> http://www.standardstrack.com/ietf/lemonade
>
>
> Notice:  This email message, together with any attachments, may  
> contain information  of  BEA Systems,  Inc.,  its subsidiaries  and   
> affiliated entities,  that may be confidential,  proprietary,   
> copyrighted  and/or legally privileged, and is intended solely for  
> the use of the individual or entity named in this message. If you  
> are not the intended recipient, and have received this message in  
> error, please immediately return this by email and then delete it.
> _______________________________________________
> lemonade mailing list
> lemonade@ietf.org
> https://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  Fri May 16 08:10: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 9594428C1EE;
	Fri, 16 May 2008 08:10: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 E112128C1FA
	for <lemonade@core3.amsl.com>; Fri, 16 May 2008 08:10: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=[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 3N2eQRVQg9mq for <lemonade@core3.amsl.com>;
	Fri, 16 May 2008 08:10:51 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19b.inmotionhosting.com
	[66.117.3.189]) by core3.amsl.com (Postfix) with ESMTP id 84AB728C188
	for <lemonade@ietf.org>; Fri, 16 May 2008 08:10:51 -0700 (PDT)
Received: from c-75-68-119-237.hsd1.nh.comcast.net ([75.68.119.237]:63363
	helo=[192.168.15.100])
	by gs19.inmotionhosting.com with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.68) (envelope-from <eburger@standardstrack.com>)
	id 1Jwyus-0001KP-M6; Fri, 16 May 2008 05:20:06 -0700
Message-Id: <77A6536B-8D2A-4E0F-9B03-BA0F8095024F@standardstrack.com>
From: Eric Burger <eburger@standardstrack.com>
To: Neil Cook <neil.cook@noware.co.uk>,
	Alexey Melnikov <alexey.melnikov@isode.com>
In-Reply-To: <CAA0228D-F251-4AA5-8AAA-EE41CB125C6B@noware.co.uk>
Mime-Version: 1.0 (Apple Message framework v912)
Date: Fri, 16 May 2008 08:17:19 -0400
References: <20080423220548.CB3533A6B54@core3.amsl.com>
	<AE908103-7787-4122-8B5D-8F161D8B07E7@noware.co.uk>
	<48106D68.40709@isode.com>
	<CAA0228D-F251-4AA5-8AAA-EE41CB125C6B@noware.co.uk>
X-Mailer: Apple Mail (2.912)
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: lemonade@ietf.org
Subject: Re: [lemonade] New Version Notification for
	draft-ietf-lemonade-streaming-05
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

I was writing up the shepherd document for this draft, and I realized  
this conversation was off-list.  Most of the comments are purely  
editorial.  However, I would like work group consensus on the Section  
2.7 issue.

I would offer that as an Informational document, we change the  
sentence.  My opinion, CHAIR HAT OFF and AS A PARTICIPANT, is there is  
no requirement for a MUST here.  RFC 4240 does what it does.
OLD
If the IMAP server does not advertise
URLAUTH=BINARY in its capability string, then the media server SHOULD
return a suitable error code to the client.
NEW
If the IMAP server does not advertise
URLAUTH=BINARY in its capability string, then the media server
returns a suitable SIP error code to the client.


On the editorial front, there is a problem.  IMAP lines easily fold,  
and it is easy to determine from the C: and S: what is a line.  SIP  
lines do NOT fold on C: and S: boundaries.  Specifically, the SDP and  
MSCML examples must not fold.  Thus, something must change.  I would  
offer the following text in the Conventions section:

In IMAP examples, "C:" and "S:" indicate lines sent by the client and
server respectively.  If a single "C:" or "S:" label applies to
multiple lines, then the line breaks between those lines are for
editorial clarity only and are not part of the actual protocol
exchange.

In SIP examples, "C:" and "S:" indicate messages sent by the client and
server respectively.  For SIP examples, this document explicitly
indicates line folding by using a backslash (\) at the end of the
line.  Line breaks in a C: or S: block do not fold and are part of
the protocol.





On Apr 24, 2008, at 7:37 AM, Neil Cook wrote:

> Alexey,
>
> thanks for reviewing the draft, comments inline:
>
> Neil
>
> On 24 Apr 2008, at 12:22, Alexey Melnikov wrote:
>
> > Neil Cook wrote:
> >
> >> 2.5.  Media Negotiation and Transcoding
> >>
> > [...]
> >
> >>   Example SIP INVITE and SDP Media Negotiation
> >>
> >>   C: INVITE sip:annc@ms2.example.com; \
> >>   play=imap://joe@example.com/INBOX/;uid=24356/;section=1.2;\
> >>   expire=2006-12-19T16:39:\57-08:00;urlauth=anonymous:\
> >>   internal:238234982398239898a9898998798b987s87920; \
> >>   content-type=video/mpeg; \
> >>
> > Are all these '\' needed?
> >
>
> Well the SIP INVITE should all be on a single line, so the '\'
> characters are there to show that.
>
> > In section 2.7:
> >
> > You've changed the following text:
> >
> >>   A successful URLFETCH command will return the message part
> >> containing
> >>   the media to be streamed.  If the URLFETCH was unsuccessful,
> >> then the
> >>   media server MUST return a response code of 404 to the client
> >>   with an appropriate reason code.
> >>
> > to:
> >
> >>   A successful URLFETCH command will return the message part
> >> containing
> >>   the media to be streamed.  If the URLFETCH was unsuccessful,
> >> then the
> >>   media server SHOULD return an appropriate error code to the  
> client
> >>   with an appropriate reason code.
> >>
> > I think the new SHOULD is wrong, are there any cases when the media
> > server would not want to dislose URLFETCH failure to the client? I
> > think what you were trying to say is that the media server MUST
> > return an error code and it SHOULD be 404.
> >
>
> Well I've gone back and forwards on this one.
>
> I actually don't want to mandate the error code that the media server
> returns to the client, I think the media server should return
> whatever error code is appropriate in the circumstance.
>
> As far as mandating whether the media server MUST return an error
> code, well that is implicit in the SIP standard (since returning a
> 200 (OK) response indicates that the media server is ready to stream
> some content, which it clearly isn't), so I wanted to avoid repeating
> that.
>
> What I wanted to stress here was simply that the media server SHOULD
> return an error code that is *appropriate* to the failure (e.g. if
> it's a transient failure, return a transient error code, but if it
> will never work, return a permanent error).
>
> >>   Examples:
> >>
> >>   C: a001 LOGIN anonymous null
> >>   S: a001 OK LOGIN completed.
> >>   C: a002 URLFETCH (
> >>   "imap://joe@example.com/INBOX/;uid=24356/;section=1.2;
> >>   expire=2006-12-19T16:39:57-08:00;urlauth=anonymous:
> >>   internal:238234982398239898a9898998798b987s87920"  
> BODYPARTSTRUCTURE
> >>   BINARY )
> >>
> > Please delete the extra space before the closing ')'
> >
> Oops
>
> >>   S: * URLFETCH "imap://joe@example.com/INBOX/;uid=24356/;
> >>   section=1.2;expire=2006-12-19T16:39:57-08:00;urlauth=anonymous:
> >>   internal:238234982398239898a9898998798b987s87920"
> >>   (BODYPARTSTRUCTURE ("VIDEO" "MPEG" () NIL NIL "BINARY" 655350 ))
> >>   (BINARY ~{655350}
> >>   S: [ ~655350 octets of binary data, containing NUL octets ])
> >>   S: a002 OK URLFETCH completed.
> >>   C: a003 LOGOUT
> >>   S: a003 OK LOGOUT completed.
> >>
> >
> >
>
>

_______________________________________________
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  Fri May 16 08:19: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 8CD0428C21D;
	Fri, 16 May 2008 08:19:55 -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 322B828C20B
	for <lemonade@core3.amsl.com>; Fri, 16 May 2008 08:19:53 -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 rVTeQwSnWBwE for <lemonade@core3.amsl.com>;
	Fri, 16 May 2008 08:19:51 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19b.inmotionhosting.com
	[66.117.3.189]) by core3.amsl.com (Postfix) with ESMTP id 7235528C188
	for <lemonade@ietf.org>; Fri, 16 May 2008 08:18:53 -0700 (PDT)
Received: from c-75-68-119-237.hsd1.nh.comcast.net ([75.68.119.237]:63363
	helo=[192.168.15.100])
	by gs19.inmotionhosting.com with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.68) (envelope-from <eburger@standardstrack.com>)
	id 1Jwyuu-0001KP-FP; Fri, 16 May 2008 05:20:08 -0700
Message-Id: <041242CE-3F97-44E8-B7A0-FCB76B4CA609@standardstrack.com>
From: Eric Burger <eburger@standardstrack.com>
To: Neil Cook <neil.cook@noware.co.uk>,
	Alexey Melnikov <alexey.melnikov@isode.com>
In-Reply-To: <CAA0228D-F251-4AA5-8AAA-EE41CB125C6B@noware.co.uk>
Mime-Version: 1.0 (Apple Message framework v912)
Date: Fri, 16 May 2008 08:18:02 -0400
References: <20080423220548.CB3533A6B54@core3.amsl.com>
	<AE908103-7787-4122-8B5D-8F161D8B07E7@noware.co.uk>
	<48106D68.40709@isode.com>
	<CAA0228D-F251-4AA5-8AAA-EE41CB125C6B@noware.co.uk>
X-Mailer: Apple Mail (2.912)
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: lemonade@ietf.org
Subject: Re: [lemonade] New Version Notification for
	draft-ietf-lemonade-streaming-05
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

I was writing up the shepherd document for this draft, and I realized  
this conversation was off-list.  Most of the comments are purely  
editorial.  However, I would like work group consensus on the Section  
2.7 issue.

I would offer that as an Informational document, we change the  
sentence.  My opinion, CHAIR HAT OFF and AS A PARTICIPANT, is there is  
no requirement for a MUST here.  RFC 4240 does what it does.
OLD
If the IMAP server does not advertise
URLAUTH=BINARY in its capability string, then the media server SHOULD
return a suitable error code to the client.
NEW
If the IMAP server does not advertise
URLAUTH=BINARY in its capability string, then the media server
returns a suitable SIP error code to the client.


On the editorial front, there is a problem.  IMAP lines easily fold,  
and it is easy to determine from the C: and S: what is a line.  SIP  
lines do NOT fold on C: and S: boundaries.  Specifically, the SDP and  
MSCML examples must not fold.  Thus, something must change.  I would  
offer the following text in the Conventions section:

  In IMAP examples, "C:" and "S:" indicate lines sent by the client and
  server respectively.  If a single "C:" or "S:" label applies to
  multiple lines, then the line breaks between those lines are for
  editorial clarity only and are not part of the actual protocol
  exchange.

  In SIP examples, "C:" and "S:" indicate messages sent by the client  
and
  server respectively.  For SIP examples, this document explicitly
  indicates line folding by using a backslash (\) at the end of the
  line.  Line breaks in a C: or S: block do not fold and are part of
  the protocol.





On Apr 24, 2008, at 7:37 AM, Neil Cook wrote:

> Alexey,
>
> thanks for reviewing the draft, comments inline:
>
> Neil
>
> On 24 Apr 2008, at 12:22, Alexey Melnikov wrote:
>
> > Neil Cook wrote:
> >
> >> 2.5.  Media Negotiation and Transcoding
> >>
> > [...]
> >
> >>   Example SIP INVITE and SDP Media Negotiation
> >>
> >>   C: INVITE sip:annc@ms2.example.com; \
> >>   play=imap://joe@example.com/INBOX/;uid=24356/;section=1.2;\
> >>   expire=2006-12-19T16:39:\57-08:00;urlauth=anonymous:\
> >>   internal:238234982398239898a9898998798b987s87920; \
> >>   content-type=video/mpeg; \
> >>
> > Are all these '\' needed?
> >
>
> Well the SIP INVITE should all be on a single line, so the '\'
> characters are there to show that.
>
> > In section 2.7:
> >
> > You've changed the following text:
> >
> >>   A successful URLFETCH command will return the message part
> >> containing
> >>   the media to be streamed.  If the URLFETCH was unsuccessful,
> >> then the
> >>   media server MUST return a response code of 404 to the client
> >>   with an appropriate reason code.
> >>
> > to:
> >
> >>   A successful URLFETCH command will return the message part
> >> containing
> >>   the media to be streamed.  If the URLFETCH was unsuccessful,
> >> then the
> >>   media server SHOULD return an appropriate error code to the  
> client
> >>   with an appropriate reason code.
> >>
> > I think the new SHOULD is wrong, are there any cases when the media
> > server would not want to dislose URLFETCH failure to the client? I
> > think what you were trying to say is that the media server MUST
> > return an error code and it SHOULD be 404.
> >
>
> Well I've gone back and forwards on this one.
>
> I actually don't want to mandate the error code that the media server
> returns to the client, I think the media server should return
> whatever error code is appropriate in the circumstance.
>
> As far as mandating whether the media server MUST return an error
> code, well that is implicit in the SIP standard (since returning a
> 200 (OK) response indicates that the media server is ready to stream
> some content, which it clearly isn't), so I wanted to avoid repeating
> that.
>
> What I wanted to stress here was simply that the media server SHOULD
> return an error code that is *appropriate* to the failure (e.g. if
> it's a transient failure, return a transient error code, but if it
> will never work, return a permanent error).
>
> >>   Examples:
> >>
> >>   C: a001 LOGIN anonymous null
> >>   S: a001 OK LOGIN completed.
> >>   C: a002 URLFETCH (
> >>   "imap://joe@example.com/INBOX/;uid=24356/;section=1.2;
> >>   expire=2006-12-19T16:39:57-08:00;urlauth=anonymous:
> >>   internal:238234982398239898a9898998798b987s87920"  
> BODYPARTSTRUCTURE
> >>   BINARY )
> >>
> > Please delete the extra space before the closing ')'
> >
> Oops
>
> >>   S: * URLFETCH "imap://joe@example.com/INBOX/;uid=24356/;
> >>   section=1.2;expire=2006-12-19T16:39:57-08:00;urlauth=anonymous:
> >>   internal:238234982398239898a9898998798b987s87920"
> >>   (BODYPARTSTRUCTURE ("VIDEO" "MPEG" () NIL NIL "BINARY" 655350 ))
> >>   (BINARY ~{655350}
> >>   S: [ ~655350 octets of binary data, containing NUL octets ])
> >>   S: a002 OK URLFETCH completed.
> >>   C: a003 LOGOUT
> >>   S: a003 OK LOGOUT completed.
> >>
> >
> >
>
>

_______________________________________________
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  Fri May 16 08:23:29 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 4BA2B3A6B06;
	Fri, 16 May 2008 08:23:29 -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 4DDD83A68AC
	for <lemonade@core3.amsl.com>; Fri, 16 May 2008 08:23:27 -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 UozyrckH750c for <lemonade@core3.amsl.com>;
	Fri, 16 May 2008 08:23:26 -0700 (PDT)
Received: from dovecot.org (dovecot.org [82.118.211.50])
	by core3.amsl.com (Postfix) with ESMTP id CC57C3A6B30
	for <lemonade@ietf.org>; Fri, 16 May 2008 08:23:25 -0700 (PDT)
Received: from [192.168.10.2] (82-203-162-146.dsl.gohome.fi [82.203.162.146])
	by dovecot.org (Postfix) with ESMTP id 0BCFA16471EF
	for <lemonade@ietf.org>; Fri, 16 May 2008 18:22:47 +0300 (EEST)
From: Timo Sirainen <tss@iki.fi>
To: lemonade <lemonade@ietf.org>
In-Reply-To: <8B9B8F32-8DEF-40B9-992E-9337FB7AE344@standardstrack.com>
X-Smtp-Server: dovecot.org:timo.sirainen
X-Priority: 2
References: <C433D277.1AB18%eburger@bea.com>
	<8B9B8F32-8DEF-40B9-992E-9337FB7AE344@standardstrack.com>
X-Pgp-Agent: GPGMail d51 (Leopard)
X-Priority: 1
Date: Fri, 16 May 2008 18:22:46 +0300
Message-Id: <1210951366.9518.654.camel@hurina>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.1 
Subject: Re: [lemonade] WGLC NOTIFY
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="===============1897789124=="
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org


--===============1897789124==
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-/i+q/VIGyE8pMvRgd5Sh"


--=-/i+q/VIGyE8pMvRgd5Sh
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

(Resend, accidentally used Reply instead of Reply-to-all for first send)

On May 16, 2008, at 3:16 PM, Eric Burger wrote:
=EF=BB=BF
> DUDES!!!
>=20
> I still have not received ANY last call comments.  Please at least
> give us some +1's.

I was too busy to give comments on time, but here are some now anyway:
=EF=BB=BF
> If FlagChange event is specified, MessageNew and MessageExpunge MUST
> also be specified by the client.

I assume this is because otherwise it's difficult for server. So =20
shouldn't this be "If FlagChange or AnnotationChange event is .." to =20
make it easier also for servers supporting annotations? Or are =20
annotations handled somehow differently from flags? (I haven't =20
implemented annotations or read the spec for a while)

Kind of a conflict:
=EF=BB=BF
> If either AnnotationChange or FlagChange are included and the server =20
> also supports CONDSTORE [RFC4551] and/or QRESYNC [QRESYNC] =20
> extension, the STATUS response MUST contain UIDVALIDITY and =20
> HIGHESTMODSEQ.

vs.
=EF=BB=BF
> If the change happens in another mailbox, then the response depends =20
> on whether CONDSTORE [RFC4551] and/or QRESYNC [QRESYNC] is being =20
> used. If so, the server sends a STATUS (HIGHESTMODSEQ) response.

So is UIDVALIDITY required to be sent or not?
=EF=BB=BF
> Note that for different event types different <event-group>s can =20
> apply to the same mailbox. .. SubscriptionChange event will also be =20
> reported for INBOX due to the second <event-group>.
> C: a notify set (mailboxes INBOX (Messagenew messageExpunge)) =20
> (personal (SubscriptionChange))

Is SubscriptionChange somehow more special than other events then, =20
because the next example shows:
=EF=BB=BF
> In this example, the client asks for FlagChange events for all =20
> personal mailboxes except the selected mailbox:
> C: a notify set (selected (Messagenew (uid flags) messageExpunge)) =20
> (personal (MessageNew FlagChange MessageExpunge))

I suppose the intent is to separate message-events, mailbox-events and =20
user-events into their own overridable groups? If so, I think it =20
should say that.

Also I find FlagChange for non-selected mailboxes to be a bit =20
pointless currently. A FlagModseqChange would better describe what it =20
currently sends to clients. But maybe using different names for =20
selected and non-selected event groups would be a bit too complex. =20
Anyway the point is that I think this should work well in future when =20
it's integrated with STATUS-COUNTERS so that a client can ask for all =20
flag changes on selected mailbox and also have server reply with flag =20
counters on non-selected mailboxes.

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

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

iD8DBQBILabGyUhSUUBViskRAimyAJ4tYCgqg2nLwkg5rnFnSKmoblMTdQCgmQ09
ntP5BhRqiAqkVBo4/7uMc3A=
=Mnd/
-----END PGP SIGNATURE-----

--=-/i+q/VIGyE8pMvRgd5Sh--


--===============1897789124==
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
--===============1897789124==--



From lemonade-bounces@ietf.org  Fri May 16 15:05:30 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 EFF3E3A6B66;
	Fri, 16 May 2008 15:05:29 -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 9A4E83A6B5D
	for <lemonade@core3.amsl.com>; Fri, 16 May 2008 15:05:25 -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 KNEs2VwC-CuA for <lemonade@core3.amsl.com>;
	Fri, 16 May 2008 15:05:24 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19b.inmotionhosting.com
	[66.117.3.189]) by core3.amsl.com (Postfix) with ESMTP id 43F633A68A0
	for <lemonade@ietf.org>; Fri, 16 May 2008 15:05:23 -0700 (PDT)
Received: from [75.68.119.237] (port=63087 helo=[192.168.15.100])
	by gs19.inmotionhosting.com with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.68) (envelope-from <eburger@standardstrack.com>)
	id 1Jx83A-0004OB-E3
	for lemonade@ietf.org; Fri, 16 May 2008 15:05:16 -0700
Message-Id: <93730B48-1250-49B0-9BBB-A403212BF1EF@standardstrack.com>
From: Eric Burger <eburger@standardstrack.com>
To: lemonade@ietf.org
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Fri, 16 May 2008 18:05:15 -0400
X-Mailer: Apple Mail (2.919.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] WGLC Architecture
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

Work Group Last Call for the Lemonade Architecture document  
(Informational) has begun and will end 2 June 2008.  Note that at IETF  
71 (and on the list via the posting and acceptance of the minutes), we  
were planning on a 3-week WGLC.  However, that presupposed a  
concurrent WGLC of profile-bis.  Since profile-bis is not ready, we  
will use a normal two week WGLC.

The draft is at:
http://www.ietf.org/internet-drafts/draft-ietf-lemonade-architecture-02.txt
_______________________________________________
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  Fri May 16 15:15: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 81BBE3A6B66;
	Fri, 16 May 2008 15:15:04 -0700 (PDT)
X-Original-To: lemonade@ietf.org
Delivered-To: lemonade@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id DE1233A6B66; Fri, 16 May 2008 15:15: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: <20080516221501.DE1233A6B66@core3.amsl.com>
Date: Fri, 16 May 2008 15:15:01 -0700 (PDT)
Cc: lemonade@ietf.org
Subject: [lemonade] I-D Action:draft-ietf-lemonade-architecture-02.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           : LEMONADE Architecture - Supporting OMA Mobile Email (MEM) using Internet Mail
	Author(s)       : E. Burger, G. Parsons
	Filename        : draft-ietf-lemonade-architecture-02.txt
	Pages           : 15
	Date            : 2008-05-16

This document specifies the architecture for mobile email, as
described by the OMA, using Internet Mail protocols.  This
architecture is the basis of the work of the LEMONADE WG and is a
guideline for the LEMONADE Profile.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-lemonade-architecture-02.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-architecture-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-05-16150243.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 May 19 00:21: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 50D7028C5F2;
	Mon, 19 May 2008 00:21:40 -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 85EED28C352
	for <lemonade@core3.amsl.com>; Mon, 19 May 2008 00:21:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.961
X-Spam-Level: *
X-Spam-Status: No, score=1.961 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, RCVD_IN_BL_SPAMCOP_NET=1.96]
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 BYSdFjQEN7Jz for <lemonade@core3.amsl.com>;
	Mon, 19 May 2008 00:21:37 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251])
	by core3.amsl.com (Postfix) with ESMTP id 7F95C28C5F0
	for <lemonade@ietf.org>; Mon, 19 May 2008 00:21:37 -0700 (PDT)
Received: from [192.168.0.11] (atomnet2.ttr.ru [195.245.249.86]) 
	by rufus.isode.com (submission channel) via TCP with ESMTPA 
	id <SDEqgAA4ERH4@rufus.isode.com>; Mon, 19 May 2008 08:21:36 +0100
Message-ID: <48312AB4.6090009@isode.com>
Date: Mon, 19 May 2008 11:22:28 +0400
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
To: Eric Burger <eburger@standardstrack.com>
References: <20080423220548.CB3533A6B54@core3.amsl.com>
	<AE908103-7787-4122-8B5D-8F161D8B07E7@noware.co.uk>
	<48106D68.40709@isode.com>
	<CAA0228D-F251-4AA5-8AAA-EE41CB125C6B@noware.co.uk>
	<77A6536B-8D2A-4E0F-9B03-BA0F8095024F@standardstrack.com>
In-Reply-To: <77A6536B-8D2A-4E0F-9B03-BA0F8095024F@standardstrack.com>
MIME-Version: 1.0
Cc: lemonade@ietf.org
Subject: Re: [lemonade] New Version Notification for
 draft-ietf-lemonade-streaming-05
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

Eric Burger wrote:
> I was writing up the shepherd document for this draft, and I realized 
> this conversation was off-list.  Most of the comments are purely 
> editorial.  However, I would like work group consensus on the Section 
> 2.7 issue.
>
> I would offer that as an Informational document, we change the 
> sentence.  My opinion, CHAIR HAT OFF and AS A PARTICIPANT, is there is 
> no requirement for a MUST here.  RFC 4240 does what it does.
> OLD
> If the IMAP server does not advertise
> URLAUTH=BINARY in its capability string, then the media server SHOULD
> return a suitable error code to the client.
> NEW
> If the IMAP server does not advertise
> URLAUTH=BINARY in its capability string, then the media server
> returns a suitable SIP error code to the client.
I think your suggested text is better.

_______________________________________________
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  Mon May 19 00:26: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 EFA6C28C5F6;
	Mon, 19 May 2008 00:26: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 44C8F28C5F9
	for <lemonade@core3.amsl.com>; Mon, 19 May 2008 00:26:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.961
X-Spam-Level: *
X-Spam-Status: No, score=1.961 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, RCVD_IN_BL_SPAMCOP_NET=1.96]
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 UJK4ARB+1EeY for <lemonade@core3.amsl.com>;
	Mon, 19 May 2008 00:26:41 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251])
	by core3.amsl.com (Postfix) with ESMTP id 8AAF828C352
	for <lemonade@ietf.org>; Mon, 19 May 2008 00:26:41 -0700 (PDT)
Received: from [192.168.0.11] (atomnet2.ttr.ru [195.245.249.86]) 
	by rufus.isode.com (submission channel) via TCP with ESMTPA 
	id <SDErsAA4EUEk@rufus.isode.com>; Mon, 19 May 2008 08:26:41 +0100
Message-ID: <48312BE4.5080502@isode.com>
Date: Mon, 19 May 2008 11:27:32 +0400
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
To: Eric Burger <eburger@standardstrack.com>
References: <C433D1E5.1AB12%eburger@bea.com> <48206629.5020305@isode.com>
	<42D8937C-4FC9-4CCE-95B1-A0219C019888@standardstrack.com>
In-Reply-To: <42D8937C-4FC9-4CCE-95B1-A0219C019888@standardstrack.com>
MIME-Version: 1.0
Cc: Randall Gellens <randy@qualcomm.com>, lemonade@ietf.org
Subject: Re: [lemonade] WGLC Notifications
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

Eric Burger wrote:
> I have written up the shepherd document.  Is this OK?
>
>
>
> inline
>   
See below.
> On May 6, 2008, at 10:07 AM, Alexey Melnikov wrote:
>   
>> Eric Burger wrote:
>>     
>>> Work Group Last Call for Lemonade Notifications Architecture,
>>> http://tools.ietf.org/html/draft-ietf-lemonade-notifications-08
>>> starts now and ends 5 May 2008.
>>>       
>> The draft is in much better shape now.
>>
>> Some comments below:
>>     
>>> *    NF and DF:  When internal to the mail store, these are
>>> typically implemented using Sieve and hence a Sieve management
>>> protocol is used for client modifications.  See [IMAP-SIEVE] and
>>> [MANAGE-SIEVE] for more information.  When the NF is within a
>>> notification server, it is out of scope of Lemonade.
>>>       
>> I don't think [IMAP-SIEVE] is relevant in case of NF or DF.
>> Unless NF is invoked on message flag changes, etc.
>>     
> We are not saying, "you can only use Sieve."  I read this as "you can  
> use Sieve."  In a purely Informational document, "typically  
> implemented" has no normative meaning.
>   
You've missed my point. I was trying to say that the sentence:
  See [IMAP-SIEVE] and [MANAGE-SIEVE] for more information.

Should read:
 See [MANAGE-SIEVE] for more information.

As [IMAP-SIEVE] has nothing to do with NF or DF (I think. I would like Randy to clarify the intent of the text)

>>> Note that when implementing DF using Sieve, the 'enotify'
>>> [SIEVE-NOTIFY] and 'variables' [SIEVE-VARIABLES] Sieve extensions
>>> are needed.
>>>       
>> If NF is generating notifications on mail delivery, than 'enotify' +
>> 'variables' is also needed there.
>> If NF is generating notifications both on mail delivery and IMAP  
>> events,
>> then 'enotify' + 'variables' are *only* needed in NF.
>>     
> Do we really need to change the words here?
>   
Yes, I want the proposed architecture to be clear.
>>> 4.  Push Email
>>>
>>> A good user experience of "push email" requires that when
>>> "interesting" events occur in the mail store, the client is informed
>>> so that it can connect and resynchronize.  The Lemonade Profile
>>> [LEMONADE-PROFILE] contains more information, especially in Section
>>> 4.1.2.
>>>       
>> I can't find section 4.1.2 in draft-ietf-lemonade-profile-bis-08.txt.
>>     
> I would offer that since profile-bis has a propensity to renumber, we  
> reference by name not number.  That way, if we use IPv6 section  
> headers, our application still works :-)
>
> OLD
>
> especially in Section 4.1.2
>
> NEW
>
> especially in the section "External Notifications"
>   
Fine with me.
> Nit: When I read this, I had no idea what "it" is.  Here is my guess.
>
> Section 5.2
>
> OLD
>
> notification system; it then becomes
>
> NEW
>
> notification system.  Thus the security relationship then becomes
>   


_______________________________________________
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  Mon May 19 00:42:46 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 739393A6AC7;
	Mon, 19 May 2008 00:42:46 -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 96DB43A69E5
	for <lemonade@core3.amsl.com>; Mon, 19 May 2008 00:42:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.961
X-Spam-Level: *
X-Spam-Status: No, score=1.961 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, RCVD_IN_BL_SPAMCOP_NET=1.96]
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 gI-KRvA5MPDo for <lemonade@core3.amsl.com>;
	Mon, 19 May 2008 00:42:44 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251])
	by core3.amsl.com (Postfix) with ESMTP id 640463A6AE6
	for <lemonade@ietf.org>; Mon, 19 May 2008 00:42:03 -0700 (PDT)
Received: from [192.168.0.11] (atomnet2.ttr.ru [195.245.249.86]) 
	by rufus.isode.com (submission channel) via TCP with ESMTPA 
	id <SDEvSQA4ESrj@rufus.isode.com>; Mon, 19 May 2008 08:42:03 +0100
Message-ID: <48312F7D.8090103@isode.com>
Date: Mon, 19 May 2008 11:42:53 +0400
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
To: Timo Sirainen <tss@iki.fi>
References: <C433D277.1AB18%eburger@bea.com>
	<8B9B8F32-8DEF-40B9-992E-9337FB7AE344@standardstrack.com>
	<1210951366.9518.654.camel@hurina>
In-Reply-To: <1210951366.9518.654.camel@hurina>
MIME-Version: 1.0
Cc: lemonade <lemonade@ietf.org>
Subject: Re: [lemonade] WGLC NOTIFY
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="utf-8"
Content-Transfer-Encoding: base64
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

VGltbyBTaXJhaW5lbiB3cm90ZToKPiAoUmVzZW5kLCBhY2NpZGVudGFsbHkgdXNlZCBSZXBseSBp
bnN0ZWFkIG9mIFJlcGx5LXRvLWFsbCBmb3IgZmlyc3Qgc2VuZCkKPiAgIApIaSBUaW1vLApUaGFu
ayB5b3UgZm9yIHlvdXIgcmV2aWV3Lgo+IE9uIE1heSAxNiwgMjAwOCwgYXQgMzoxNiBQTSwgRXJp
YyBCdXJnZXIgd3JvdGU6Cj4gICAKPj4gRFVERVMhISEKPj4KPj4gSSBzdGlsbCBoYXZlIG5vdCBy
ZWNlaXZlZCBBTlkgbGFzdCBjYWxsIGNvbW1lbnRzLiAgUGxlYXNlIGF0IGxlYXN0Cj4+IGdpdmUg
dXMgc29tZSArMSdzLgo+PiAgICAgCj4gSSB3YXMgdG9vIGJ1c3kgdG8gZ2l2ZSBjb21tZW50cyBv
biB0aW1lLCBidXQgaGVyZSBhcmUgc29tZSBub3cgYW55d2F5Ogo+ICAgCj4+IElmIEZsYWdDaGFu
Z2UgZXZlbnQgaXMgc3BlY2lmaWVkLCBNZXNzYWdlTmV3IGFuZCBNZXNzYWdlRXhwdW5nZSBNVVNU
Cj4+IGFsc28gYmUgc3BlY2lmaWVkIGJ5IHRoZSBjbGllbnQuCj4+ICAgICAKPiBJIGFzc3VtZSB0
aGlzIGlzIGJlY2F1c2Ugb3RoZXJ3aXNlIGl0J3MgZGlmZmljdWx0IGZvciBzZXJ2ZXIuClllcy4g
UGV0ZXIgQ29hdGVzIGhhcyByZXF1ZXN0ZWQgdGhpcy4KPiBTbyBzaG91bGRuJ3QgdGhpcyBiZSAi
SWYgRmxhZ0NoYW5nZSBvciBBbm5vdGF0aW9uQ2hhbmdlIGV2ZW50IGlzIC4uIiB0byAgCj4gbWFr
ZSBpdCBlYXNpZXIgYWxzbyBmb3Igc2VydmVycyBzdXBwb3J0aW5nIGFubm90YXRpb25zPyBPciBh
cmUgIAo+IGFubm90YXRpb25zIGhhbmRsZWQgc29tZWhvdyBkaWZmZXJlbnRseSBmcm9tIGZsYWdz
PyAoSSBoYXZlbid0ICAKPiBpbXBsZW1lbnRlZCBhbm5vdGF0aW9ucyBvciByZWFkIHRoZSBzcGVj
IGZvciBhIHdoaWxlKQo+ICAgCkFncmVlZC4KPiBLaW5kIG9mIGEgY29uZmxpY3Q6Cj4g77u/Cj4g
ICAKPj4gSWYgZWl0aGVyIEFubm90YXRpb25DaGFuZ2Ugb3IgRmxhZ0NoYW5nZSBhcmUgaW5jbHVk
ZWQgYW5kIHRoZSBzZXJ2ZXIgIAo+PiBhbHNvIHN1cHBvcnRzIENPTkRTVE9SRSBbUkZDNDU1MV0g
YW5kL29yIFFSRVNZTkMgW1FSRVNZTkNdICAKPj4gZXh0ZW5zaW9uLCB0aGUgU1RBVFVTIHJlc3Bv
bnNlIE1VU1QgY29udGFpbiBVSURWQUxJRElUWSBhbmQgIAo+PiBISUdIRVNUTU9EU0VRLgo+PiAg
ICAgCj4KPiB2cy4KPiDvu78KPiAgIAo+PiBJZiB0aGUgY2hhbmdlIGhhcHBlbnMgaW4gYW5vdGhl
ciBtYWlsYm94LCB0aGVuIHRoZSByZXNwb25zZSBkZXBlbmRzICAKPj4gb24gd2hldGhlciBDT05E
U1RPUkUgW1JGQzQ1NTFdIGFuZC9vciBRUkVTWU5DIFtRUkVTWU5DXSBpcyBiZWluZyAgCj4+IHVz
ZWQuIElmIHNvLCB0aGUgc2VydmVyIHNlbmRzIGEgU1RBVFVTIChISUdIRVNUTU9EU0VRKSByZXNw
b25zZS4KPj4gICAgIAo+Cj4gU28gaXMgVUlEVkFMSURJVFkgcmVxdWlyZWQgdG8gYmUgc2VudCBv
ciBub3Q/Cj4gICAKSXQgaXMgcmVxdWlyZWQsIGFzIHdpdGhvdXQgVUlEVkFMSURJVFkgSElHSEVT
VE1PRFNFUSBpcyBtZWFuaW5nbGVzcy4KSSB3aWxsIGZpeCB0aGUgZG9jdW1lbnQuCj4+IE5vdGUg
dGhhdCBmb3IgZGlmZmVyZW50IGV2ZW50IHR5cGVzIGRpZmZlcmVudCA8ZXZlbnQtZ3JvdXA+cyBj
YW4gIAo+PiBhcHBseSB0byB0aGUgc2FtZSBtYWlsYm94LiAuLiBTdWJzY3JpcHRpb25DaGFuZ2Ug
ZXZlbnQgd2lsbCBhbHNvIGJlICAKPj4gcmVwb3J0ZWQgZm9yIElOQk9YIGR1ZSB0byB0aGUgc2Vj
b25kIDxldmVudC1ncm91cD4uCj4+IEM6IGEgbm90aWZ5IHNldCAobWFpbGJveGVzIElOQk9YIChN
ZXNzYWdlbmV3IG1lc3NhZ2VFeHB1bmdlKSkgIAo+PiAocGVyc29uYWwgKFN1YnNjcmlwdGlvbkNo
YW5nZSkpCj4+ICAgICAKPiBJcyBTdWJzY3JpcHRpb25DaGFuZ2Ugc29tZWhvdyBtb3JlIHNwZWNp
YWwgdGhhbiBvdGhlciBldmVudHMgdGhlbiwgIAo+IGJlY2F1c2UgdGhlIG5leHQgZXhhbXBsZSBz
aG93czoKTm8sIGl0IGlzIG5vdC4gSSBqdXN0IHdhbnRlZCB0byBpbmNsdWRlIGluIG9uZSBleGFt
cGxlIGFuIGV2ZW50IHRoYXQgd2FzIApub3QgYSBtZXNzYWdlIHNwZWNpZmljIGV2ZW50Lgo+PiBJ
biB0aGlzIGV4YW1wbGUsIHRoZSBjbGllbnQgYXNrcyBmb3IgRmxhZ0NoYW5nZSBldmVudHMgZm9y
IGFsbCAgCj4+IHBlcnNvbmFsIG1haWxib3hlcyBleGNlcHQgdGhlIHNlbGVjdGVkIG1haWxib3g6
Cj4+IEM6IGEgbm90aWZ5IHNldCAoc2VsZWN0ZWQgKE1lc3NhZ2VuZXcgKHVpZCBmbGFncykgbWVz
c2FnZUV4cHVuZ2UpKSAgCj4+IChwZXJzb25hbCAoTWVzc2FnZU5ldyBGbGFnQ2hhbmdlIE1lc3Nh
Z2VFeHB1bmdlKSkKPj4gICAgIAo+IEkgc3VwcG9zZSB0aGUgaW50ZW50IGlzIHRvIHNlcGFyYXRl
IG1lc3NhZ2UtZXZlbnRzLCBtYWlsYm94LWV2ZW50cyBhbmQgIAo+IHVzZXItZXZlbnRzIGludG8g
dGhlaXIgb3duIG92ZXJyaWRhYmxlIGdyb3Vwcz8KQ2FuIHlvdSBjbGFyaWZ5IHdoYXQgaXMgeW91
ciBkZWZpbml0aW9uIG9mICJvdmVycmlkYWJsZSI/Cj4gSWYgc28sIEkgdGhpbmsgaXQgIAo+IHNo
b3VsZCBzYXkgdGhhdC4KPgo+IEFsc28gSSBmaW5kIEZsYWdDaGFuZ2UgZm9yIG5vbi1zZWxlY3Rl
ZCBtYWlsYm94ZXMgdG8gYmUgYSBiaXQgIAo+IHBvaW50bGVzcyBjdXJyZW50bHkuClllcy4KPiBB
IEZsYWdNb2RzZXFDaGFuZ2Ugd291bGQgYmV0dGVyIGRlc2NyaWJlIHdoYXQgaXQgIAo+IGN1cnJl
bnRseSBzZW5kcyB0byBjbGllbnRzLiBCdXQgbWF5YmUgdXNpbmcgZGlmZmVyZW50IG5hbWVzIGZv
ciAgCj4gc2VsZWN0ZWQgYW5kIG5vbi1zZWxlY3RlZCBldmVudCBncm91cHMgd291bGQgYmUgYSBi
aXQgdG9vIGNvbXBsZXguCj4gICAKRXhhY3RseS4KPiBBbnl3YXkgdGhlIHBvaW50IGlzIHRoYXQg
SSB0aGluayB0aGlzIHNob3VsZCB3b3JrIHdlbGwgaW4gZnV0dXJlIHdoZW4gIAo+IGl0J3MgaW50
ZWdyYXRlZCB3aXRoIFNUQVRVUy1DT1VOVEVSUyBzbyB0aGF0IGEgY2xpZW50IGNhbiBhc2sgZm9y
IGFsbCAgCj4gZmxhZyBjaGFuZ2VzIG9uIHNlbGVjdGVkIG1haWxib3ggYW5kIGFsc28gaGF2ZSBz
ZXJ2ZXIgcmVwbHkgd2l0aCBmbGFnICAKPiBjb3VudGVycyBvbiBub24tc2VsZWN0ZWQgbWFpbGJv
eGVzLgpZZXMuCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
XwpsZW1vbmFkZSBtYWlsaW5nIGxpc3QKbGVtb25hZGVAaWV0Zi5vcmcKaHR0cHM6Ly93d3cuaWV0
Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9sZW1vbmFkZQpTdXBwbGVtZW50YWwgV2ViIFNpdGU6Cmh0
dHA6Ly93d3cuc3RhbmRhcmRzdHJhY2suY29tL2lldGYvbGVtb25hZGU=


From lemonade-bounces@ietf.org  Mon May 19 03:02: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 B685A3A68EF;
	Mon, 19 May 2008 03:02: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 8B13A3A6E2C
	for <lemonade@core3.amsl.com>; Mon, 19 May 2008 03:02:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.603
X-Spam-Level: 
X-Spam-Status: No, score=-2.603 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, MIME_QP_LONG_LINE=1.396, 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 qg2RA2LFW2AM for <lemonade@core3.amsl.com>;
	Mon, 19 May 2008 03:02:45 -0700 (PDT)
Received: from dovecot.org (dovecot.org [82.118.211.50])
	by core3.amsl.com (Postfix) with ESMTP id 51FD83A6E31
	for <lemonade@ietf.org>; Mon, 19 May 2008 03:02:19 -0700 (PDT)
Received: from [192.168.10.2] (82-203-162-146.dsl.gohome.fi [82.203.162.146])
	by dovecot.org (Postfix) with ESMTP id 7AEAC16471E4;
	Mon, 19 May 2008 13:01:45 +0300 (EEST)
From: Timo Sirainen <tss@iki.fi>
To: Alexey Melnikov <alexey.melnikov@isode.com>
In-Reply-To: <48312F7D.8090103@isode.com>
References: <C433D277.1AB18%eburger@bea.com>
	<8B9B8F32-8DEF-40B9-992E-9337FB7AE344@standardstrack.com>
	<1210951366.9518.654.camel@hurina>  <48312F7D.8090103@isode.com>
Date: Mon, 19 May 2008 13:01:44 +0300
Message-Id: <1211191304.9518.755.camel@hurina>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.1 
Cc: lemonade <lemonade@ietf.org>
Subject: Re: [lemonade] WGLC NOTIFY
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="===============1506769862=="
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org


--===============1506769862==
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-41ZqGkqL1Jw7byshlROy"


--=-41ZqGkqL1Jw7byshlROy
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Mon, 2008-05-19 at 11:42 +0400, Alexey Melnikov wrote:
> >> Note that for different event types different <event-group>s can =20
> >> apply to the same mailbox. .. SubscriptionChange event will also be =20
> >> reported for INBOX due to the second <event-group>.
> >> C: a notify set (mailboxes INBOX (Messagenew messageExpunge)) =20
> >> (personal (SubscriptionChange))
> >>    =20
> > Is SubscriptionChange somehow more special than other events then, =20
> > because the next example shows:
> No, it is not. I just wanted to include in one example an event that was=20
> not a message specific event.
> >> In this example, the client asks for FlagChange events for all =20
> >> personal mailboxes except the selected mailbox:
> >> C: a notify set (selected (Messagenew (uid flags) messageExpunge)) =20
> >> (personal (MessageNew FlagChange MessageExpunge))
> >>    =20
> > I suppose the intent is to separate message-events, mailbox-events and =
=20
> > user-events into their own overridable groups?
> Can you clarify what is your definition of "overridable"?

Being able to drop an event. If you look at the examples and their
descriptions:

> SubscriptionChange event
> will also be reported for INBOX due to the second <event-group>.
>=20
>         C: a notify set (mailboxes INBOX (Messagenew messageExpunge))
>            (personal (SubscriptionChange))

This means the result is a union of "mailboxes INBOX" events and
"personal" events, because they both match INBOX.

The next example however shows:

> In this example, the client asks for FlagChange events for all
> personal mailboxes except the selected mailbox:
>         C: a notify set (selected (Messagenew (uid flags)
>            messageExpunge)) (personal (MessageNew FlagChange
>            MessageExpunge))

Using the previous logic I would have thought that the result is again a
union of "selected" and "personal" events, resulting flag changes being
returned again. Unless "selected" is treated specially? So given two
more simplified examples:

a notify set (selected (MessageNew MessageExpunge)) (personal
(SubscriptionChange))

=EF=BB=BFb notify set (selected (MessageNew MessageExpunge)) (personal
(MessageNew MessageExpunge FlagChange))

If a) returns SubscriptionChange, does b) return FlagChanges or not, and
using what logic?


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

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

iD8DBQBIMVAIyUhSUUBViskRAp+uAJsFWxuitJXv0Lw8jDiEE3KVdlY2QwCfUtXu
I42dF4rYYH2Z/8lJEENmelI=
=IDJh
-----END PGP SIGNATURE-----

--=-41ZqGkqL1Jw7byshlROy--


--===============1506769862==
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
--===============1506769862==--



From lemonade-bounces@ietf.org  Tue May 20 07:30: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 C7DD728CA22;
	Tue, 20 May 2008 07:30: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 524DE28CA18; Tue, 20 May 2008 07:30: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: <20080520143001.524DE28CA18@core3.amsl.com>
Date: Tue, 20 May 2008 07:30:01 -0700 (PDT)
Cc: lemonade@ietf.org
Subject: [lemonade] I-D Action:draft-ietf-lemonade-convert-20.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           : IMAP CONVERT extension
	Author(s)       : A. Melnikov, P. Coates
	Filename        : draft-ietf-lemonade-convert-20.txt
	Pages           : 30
	Date            : 2008-05-20

CONVERT defines extensions to IMAP allowing clients to request
adaptation and/or transcoding of attachments.  Clients can specify
the conversion details or allow servers to decide based on knowledge
of client capabilities, on user or administrator preferences or its
settings.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-lemonade-convert-20.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-convert-20.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-05-20072904.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  Thu May 22 12:56:36 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 21BB03A6B0E;
	Thu, 22 May 2008 12:56:36 -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 D85563A6B0E
	for <lemonade@core3.amsl.com>; Thu, 22 May 2008 12:55:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.455
X-Spam-Level: 
X-Spam-Status: No, score=-0.455 tagged_above=-999 required=5 tests=[AWL=0.184, 
	BAYES_00=-2.599, RCVD_IN_BL_SPAMCOP_NET=1.96]
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 zj93JAXsBDSx for <lemonade@core3.amsl.com>;
	Thu, 22 May 2008 12:55:38 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251])
	by core3.amsl.com (Postfix) with ESMTP id AA47F3A63EC
	for <lemonade@ietf.org>; Thu, 22 May 2008 12:55:37 -0700 (PDT)
Received: from [192.168.0.11] (atomnet2.ttr.ru [195.245.249.86]) 
	by rufus.isode.com (submission channel) via TCP with ESMTPA 
	id <SDXPuAA4EWPf@rufus.isode.com>; Thu, 22 May 2008 20:55:36 +0100
Message-ID: <4835D000.4080808@isode.com>
Date: Thu, 22 May 2008 23:56:48 +0400
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
To: Timo Sirainen <tss@iki.fi>
References: <C433D277.1AB18%eburger@bea.com>
	<8B9B8F32-8DEF-40B9-992E-9337FB7AE344@standardstrack.com>
	<1210951366.9518.654.camel@hurina> <48312F7D.8090103@isode.com>
	<1211191304.9518.755.camel@hurina>
In-Reply-To: <1211191304.9518.755.camel@hurina>
MIME-Version: 1.0
Cc: lemonade <lemonade@ietf.org>
Subject: Re: [lemonade] WGLC NOTIFY
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

Timo Sirainen wrote:
> On Mon, 2008-05-19 at 11:42 +0400, Alexey Melnikov wrote:
>   
>>>> Note that for different event types different <event-group>s can  
>>>> apply to the same mailbox. .. SubscriptionChange event will also be  
>>>> reported for INBOX due to the second <event-group>.
>>>> C: a notify set (mailboxes INBOX (Messagenew messageExpunge))  
>>>> (personal (SubscriptionChange))
>>>>         
>>> Is SubscriptionChange somehow more special than other events then,  
>>> because the next example shows:    
>> No, it is not. I just wanted to include in one example an event that was 
>> not a message specific event.
>>     
>>>> In this example, the client asks for FlagChange events for all  
>>>> personal mailboxes except the selected mailbox:
>>>> C: a notify set (selected (Messagenew (uid flags) messageExpunge))  
>>>> (personal (MessageNew FlagChange MessageExpunge))
>>>>         
>>> I suppose the intent is to separate message-events, mailbox-events and  
>>> user-events into their own overridable groups?      
>> Can you clarify what is your definition of "overridable"?    
> Being able to drop an event.
Sorry, what do you mean by "drop an event"?
> If you look at the examples and their
> descriptions:
>   
>> SubscriptionChange event
>> will also be reported for INBOX due to the second <event-group>.
>>
>>         C: a notify set (mailboxes INBOX (Messagenew messageExpunge))
>>            (personal (SubscriptionChange))
>>     
> This means the result is a union of "mailboxes INBOX" events and
> "personal" events, because they both match INBOX.  
Correct.
> The next example however shows:  
>> In this example, the client asks for FlagChange events for all
>> personal mailboxes except the selected mailbox:
>>         C: a notify set (selected (Messagenew (uid flags)
>>            messageExpunge)) (personal (MessageNew FlagChange
>>            MessageExpunge))
>>     
> Using the previous logic I would have thought that the result is again a
> union of "selected" and "personal" events, resulting flag changes being
> returned again. Unless "selected" is treated specially?
"Selected" is indeed treated specially, as per the following text in
section 3.1:

The NOTIFY SET command can request notifications of changes to the
selected mailbox, whatever it may be at the time the notifications are
being generated. This is done by specifying the SELECTED mailbox
selector (see Section 6.1) in the NOTIFY SET command. The client can
also request notifications on other mailboxes by name or by a limited
mailbox pattern match. The notifications returned for the currently
selected mailbox will be those specified by the SELECTED mailbox
specifier, even if the selected mailbox also appears by name in the command.

So, according to this text:
> So given two more simplified examples:
>
> a notify set (selected (MessageNew MessageExpunge)) (personal
> (SubscriptionChange))
>   
This would result in MessageNew and MessageExpunge events for the
currently selected mailbox (whether it is a personal one or not) and
subscription change notifications for all personal mailboxes except for
the currently selected one (if it is a personal mailbox).

Hmm, this raises an interesting question: is the "except for the
currently selected" part in the last sentence is what we actually want?
Should "Selected"only apply to message level events?
> b notify set (selected (MessageNew MessageExpunge)) (personal
> (MessageNew MessageExpunge FlagChange))
>   
This would result in MessageNew and MessageExpunge events for the
currently selected mailbox (whether it is a personal one or not) and
MessageNew+MessageExpunge+FlagChange notifications for all personal
mailboxes except for the currently selected one (if it is a personal
mailbox).
> If a) returns SubscriptionChange, does b) return FlagChanges or not, and
> using what logic?




_______________________________________________
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  Fri May 23 06:12:26 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 9A0EF3A6B20;
	Fri, 23 May 2008 06:12:26 -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 8DD523A6AC8
	for <lemonade@core3.amsl.com>; Fri, 23 May 2008 06:12:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.486
X-Spam-Level: 
X-Spam-Status: No, score=-0.486 tagged_above=-999 required=5 tests=[AWL=0.153, 
	BAYES_00=-2.599, RCVD_IN_BL_SPAMCOP_NET=1.96]
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 WUqn6SItGdSO for <lemonade@core3.amsl.com>;
	Fri, 23 May 2008 06:12:20 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251])
	by core3.amsl.com (Postfix) with ESMTP id 9CDD23A6B20
	for <lemonade@ietf.org>; Fri, 23 May 2008 06:12:19 -0700 (PDT)
Received: from [192.168.0.11] (atomnet2.ttr.ru [195.245.249.86]) 
	by rufus.isode.com (submission channel) via TCP with ESMTPA 
	id <SDbCsQA4EXqk@rufus.isode.com>; Fri, 23 May 2008 14:12:18 +0100
Message-ID: <4836C2B5.4020502@isode.com>
Date: Fri, 23 May 2008 17:12:21 +0400
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
To: Eric Burger <eburger@standardstrack.com>
References: <93730B48-1250-49B0-9BBB-A403212BF1EF@standardstrack.com>
In-Reply-To: <93730B48-1250-49B0-9BBB-A403212BF1EF@standardstrack.com>
MIME-Version: 1.0
Cc: lemonade@ietf.org
Subject: Re: [lemonade] WGLC Architecture
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

Eric Burger wrote:
> Work Group Last Call for the Lemonade Architecture document  
> (Informational) has begun and will end 2 June 2008.  Note that at IETF  
> 71 (and on the list via the posting and acceptance of the minutes), we  
> were planning on a 3-week WGLC.  However, that presupposed a  
> concurrent WGLC of profile-bis.  Since profile-bis is not ready, we  
> will use a normal two week WGLC.
>
> The draft is at:
> http://www.ietf.org/internet-drafts/draft-ietf-lemonade-architecture-02.txt
>   
I've just reviewed the document and it looks good in general. But I have 
some comments (mostly minor):
> 2.2.1.  OMA MEM logical Architecture
 [...]
>    o  Other OMA enablers are needed to directly support the mobile email
>       enabler.  They are out of scope of IETF but they may include
>       support for:
>       *  Client provisioning and management for over the air
>          installation of the MEM client on the device, provisioning of
>          its settings and revocation, and
>       *  Messaging enablers for out-of-band notification, where out-of-
>          band notifications that are server to client event exchanges
>          not transported by the MEM protocol but via other channels.
Should this also mention charging? Charging is a part of OMA MEM 
architecture.
> 2.2.2.2.  OMA MEM deployment cases
>
>    OMA MEM identifies that each component (MEM client, MEM servers,
>    other enablers, and the email server) may be deployed in different
>    domains, possibly separated by firewalls and other network
>    intermediaries.  MEM proxies may be involved in front of firewall
>    that protects the MEM server domain.
>
>    OMA MEM targets support of configurations where:
>    o  All components are within a same domain, such as in a mobile
I think "a same domain" should be changed to either "a single domain" or 
"the same domain"?
>       operator

> 3.  IETF LEMONADE Architecture
 [...]
>    The LEMONADE profile [PROFILE] assumes:
>    o  IMAP protocol [RFC3501] including LEMONADE profile extensions
>       [PROFILE]
>    o  SUBMIT protocol [RFC4409], including LEMONADE profile extensions
>    o  LEMONADE profile compliant IMAP store connected to MTA (Mail
>       Transfer Agent) via ESMTP
My Lemonade server is not connected over ESMTP. It is connected over 
LMTP to our MTA which is connected over ESMTP to the rest of the world.
I don't think Isode's implementation is unique in this respect and I 
don't see a reason why the document should be limiting this.

I would suggest rephrasing this to say something like "LEMONADE profile 
compliant IMAP store. Email can be delivered to this store over ESMTP".
> [RFC1861]
Please change [RFC1861] ("Simple Network Paging Protocol - Version 3 
-Two-Way Enhanced") to [RFC2821]
>    o  LEMONADE profile compliant Submit server connected to MTA via
>       ESMTP
>    o  Lemonade profile message store / submit server protocols (URLAUTH,
>       BURL, CATENATE) (see lemonade Profile [PROFILE]).
This bullet just repeating something that is already mentioned above. I 
suggest deleting it.
>    o  Out-of-band server to client notifications relying on external
>       notification mechanisms (and notification protocols) that may be
>       out of scope of the LEMONADE profile.
>    o  A LEMONADE aware MUA (Mail User Agent).  While use of out-of-band
>       notification is described in the LEMONADE profile, support for the
>       underlying notifications mechanisms/protocols is out of scope of
>       the LEMONADE specifications.

> 4.  Filters and server to client notifications and LEMONADE
 [...]
>    In Figure 6, we define four categories of filters:
>    o  AF: Administrative Filters - The e-mail service provider usually
>       sets administrative filters.  The user typically does not
>       configure AF.  AF applies policies covering content filtering,
>       virus protection, spam filtering, etc.
>    o  DF: Deposit Filters - Filters that are executed on deposit of new
>       emails.  They can be defined as SIEVE filters [SIEVE].  They can
>       include vacation notices.
Please add a reference to RFC 5230 at the end of the last sentence.
>    o  VF: View Filters - Filters that define which emails are visible to
>       the MUA.  View filters can be performed via IMAP using the
>       facilities described in [NOTIFICATIONS].
>    o  NF: Notification Filters - Filters that define for what email
>       server event an out-of-band notification is sent to the client, as
>       described in [NOTIFICATIONS].
>
>    The MUA can manage the NF and DF filters using the SIEVE management
>    protocol.
Please add a reference to draft-martin-managesieve (currently 
draft-martin-managesieve-09.txt) at the end of the last sentence.

Regards,
Alexey


_______________________________________________
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 May 25 12:59: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 7CE773A6AAB;
	Sun, 25 May 2008 12:59: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 C363D3A67AA
	for <lemonade@core3.amsl.com>; Sun, 25 May 2008 12:56:14 -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 nE5tZwAOPRCS for <lemonade@core3.amsl.com>;
	Sun, 25 May 2008 12:56:14 -0700 (PDT)
Received: from dovecot.org (dovecot.org [82.118.211.50])
	by core3.amsl.com (Postfix) with ESMTP id 9AE9C3A6765
	for <lemonade@ietf.org>; Sun, 25 May 2008 12:56:13 -0700 (PDT)
Received: from [192.168.10.2] (xdsl-177-118.nblnetworks.fi [217.30.177.118])
	by dovecot.org (Postfix) with ESMTP id BED8416471E6;
	Sun, 25 May 2008 22:55:39 +0300 (EEST)
From: Timo Sirainen <tss@iki.fi>
To: Alexey Melnikov <alexey.melnikov@isode.com>
In-Reply-To: <4835D000.4080808@isode.com>
References: <C433D277.1AB18%eburger@bea.com>
	<8B9B8F32-8DEF-40B9-992E-9337FB7AE344@standardstrack.com>
	<1210951366.9518.654.camel@hurina> <48312F7D.8090103@isode.com>
	<1211191304.9518.755.camel@hurina>  <4835D000.4080808@isode.com>
Date: Sun, 25 May 2008 22:55:39 +0300
Message-Id: <1211745339.3904.166.camel@hurina>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.1 
Cc: lemonade <lemonade@ietf.org>
Subject: Re: [lemonade] WGLC NOTIFY
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="===============1974440872=="
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org


--===============1974440872==
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-uWqKDlVF9x1tx/X3PtU5"


--=-uWqKDlVF9x1tx/X3PtU5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, 2008-05-22 at 23:56 +0400, Alexey Melnikov wrote:
> > The next example however shows: =20
> >> In this example, the client asks for FlagChange events for all
> >> personal mailboxes except the selected mailbox:
> >>         C: a notify set (selected (Messagenew (uid flags)
> >>            messageExpunge)) (personal (MessageNew FlagChange
> >>            MessageExpunge))
> >>    =20
> > Using the previous logic I would have thought that the result is again =
a
> > union of "selected" and "personal" events, resulting flag changes being
> > returned again. Unless "selected" is treated specially?
> "Selected" is indeed treated specially, as per the following text in
> section 3.1:

OK, I guess this answers my question. It would be helpful if the
examples in 6. mentioned that. For example changing:

> =EF=BB=BF    In this example, the client asks for FlagChange events for a=
ll
>     personal mailboxes except the selected mailbox:
>         C: a notify set (selected (Messagenew (uid flags)
>            messageExpunge)) (personal (MessageNew FlagChange
>            MessageExpunge))

to something like:

In the next example the client asks for FlagChange events for all
personal mailboxes except the selected mailbox. This is different from
the previous example, because SELECTED overrides all other event
definitions.

> > a notify set (selected (MessageNew MessageExpunge)) (personal
> > (SubscriptionChange))
> >  =20
> This would result in MessageNew and MessageExpunge events for the
> currently selected mailbox (whether it is a personal one or not) and
> subscription change notifications for all personal mailboxes except for
> the currently selected one (if it is a personal mailbox).
>=20
> Hmm, this raises an interesting question: is the "except for the
> currently selected" part in the last sentence is what we actually want?
> Should "Selected"only apply to message level events?

I think that would be better.

One more thing I thought of:

> If IDLE (as well as this extension) is supported, while processing
>     IDLE the server MUST send the same events as instructed by the
>     client using the NOTIFY command.

Does this mean EXPUNGEs must not be sent if MessageExpunge isn't
included in NOTIFY SET? That would make it impossible to create clients
that use MSNs and want to be immediately notified of EXPUNGEs (while
IDLEing).

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

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

iD8DBQBIOcQ7yUhSUUBViskRArcgAJ0W/K3MACKVsm+hVjHCzJYme9gK/wCfVW6M
tzo6iPxAMcszA1f4aTodY5M=
=NeZM
-----END PGP SIGNATURE-----

--=-uWqKDlVF9x1tx/X3PtU5--


--===============1974440872==
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
--===============1974440872==--



From lemonade-bounces@ietf.org  Mon May 26 23:33:08 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 6FAFC3A6B3A;
	Mon, 26 May 2008 23:33:08 -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 B4FC63A6B3A
	for <lemonade@core3.amsl.com>; Mon, 26 May 2008 23:33:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.492
X-Spam-Level: 
X-Spam-Status: No, score=-0.492 tagged_above=-999 required=5 tests=[AWL=0.147, 
	BAYES_00=-2.599, RCVD_IN_BL_SPAMCOP_NET=1.96]
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 1agoebTq5Og9 for <lemonade@core3.amsl.com>;
	Mon, 26 May 2008 23:33:06 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251])
	by core3.amsl.com (Postfix) with ESMTP id 86F2E3A688F
	for <lemonade@ietf.org>; Mon, 26 May 2008 23:33:05 -0700 (PDT)
Received: from [192.168.0.11] (atomnet2.ttr.ru [195.245.249.86]) 
	by rufus.isode.com (submission channel) via TCP with ESMTPA 
	id <SDurJAA4EZdm@rufus.isode.com>; Tue, 27 May 2008 07:33:09 +0100
Message-ID: <483BAB35.2080806@isode.com>
Date: Tue, 27 May 2008 10:33:25 +0400
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
To: Timo Sirainen <tss@iki.fi>
References: <C433D277.1AB18%eburger@bea.com>
	<8B9B8F32-8DEF-40B9-992E-9337FB7AE344@standardstrack.com>
	<1210951366.9518.654.camel@hurina> <48312F7D.8090103@isode.com>
	<1211191304.9518.755.camel@hurina> <4835D000.4080808@isode.com>
	<1211745339.3904.166.camel@hurina>
In-Reply-To: <1211745339.3904.166.camel@hurina>
MIME-Version: 1.0
Cc: lemonade <lemonade@ietf.org>
Subject: Re: [lemonade] WGLC NOTIFY
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

Timo Sirainen wrote:
> One more thing I thought of:
>> If IDLE (as well as this extension) is supported, while processing
>>     IDLE the server MUST send the same events as instructed by the
>>     client using the NOTIFY command.
>>     
> Does this mean EXPUNGEs must not be sent if MessageExpunge isn't
> included in NOTIFY SET?
Correct.
> That would make it impossible to create clients
> that use MSNs and want to be immediately notified of EXPUNGEs (while
> IDLEing).
>   
Correct. The client can either chose not to use NOTIFY at all (in which 
case it will get expunges with MSNs), or it can chose to specify both 
MessageNew & MessageExpunge (they are tied together as per section 5), 
in which case it will get back UIDs.

It is possible that some servers that support IDLE don't send 
MessageExpunge events while idling, but I haven't seen any such server. 
We could mandate that all servers advertising the NOTIFY capability send 
MessageExpunge during IDLE if NOTIFY wasn't issued on the connection?!


_______________________________________________
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 May 27 00:13:33 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 E1EC63A68C2;
	Tue, 27 May 2008 00:13:33 -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 D584C3A67FE
	for <lemonade@core3.amsl.com>; Tue, 27 May 2008 00:13:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.193
X-Spam-Level: 
X-Spam-Status: No, score=0.193 tagged_above=-999 required=5 tests=[AWL=-0.564, 
	BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396,
	RCVD_IN_BL_SPAMCOP_NET=1.96]
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 0wt7iJYjDMtm for <lemonade@core3.amsl.com>;
	Tue, 27 May 2008 00:13:32 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251])
	by core3.amsl.com (Postfix) with ESMTP id A7F753A6912
	for <lemonade@ietf.org>; Tue, 27 May 2008 00:13:22 -0700 (PDT)
Received: from [192.168.0.11] (atomnet2.ttr.ru [195.245.249.86]) 
	by rufus.isode.com (submission channel) via TCP with ESMTPA 
	id <SDu0lgA4EUHf@rufus.isode.com>; Tue, 27 May 2008 08:13:26 +0100
Message-ID: <483BB4A0.2090403@isode.com>
Date: Tue, 27 May 2008 11:13:36 +0400
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
To: lemonade <lemonade@ietf.org>
References: <C433D277.1AB18%eburger@bea.com>
	<8B9B8F32-8DEF-40B9-992E-9337FB7AE344@standardstrack.com>
	<1210951366.9518.654.camel@hurina> <48312F7D.8090103@isode.com>
	<1211191304.9518.755.camel@hurina> <4835D000.4080808@isode.com>
	<1211745339.3904.166.camel@hurina>
In-Reply-To: <1211745339.3904.166.camel@hurina>
MIME-Version: 1.0
Subject: [lemonade] Poll: Scope of SELECTED in IMAP NOTIFY
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="utf-8"
Content-Transfer-Encoding: base64
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

VGltbyBTaXJhaW5lbiB3cm90ZToKPiBPbiBUaHUsIDIwMDgtMDUtMjIgYXQgMjM6NTYgKzA0MDAs
IEFsZXhleSBNZWxuaWtvdiB3cm90ZToKPiAgIAo+Pj4gVGhlIG5leHQgZXhhbXBsZSBob3dldmVy
IHNob3dzOiAgCj4+PiAgICAgICAKPj4+PiBJbiB0aGlzIGV4YW1wbGUsIHRoZSBjbGllbnQgYXNr
cyBmb3IgRmxhZ0NoYW5nZSBldmVudHMgZm9yIGFsbAo+Pj4+IHBlcnNvbmFsIG1haWxib3hlcyBl
eGNlcHQgdGhlIHNlbGVjdGVkIG1haWxib3g6Cj4+Pj4gICAgICAgICBDOiBhIG5vdGlmeSBzZXQg
KHNlbGVjdGVkIChNZXNzYWdlbmV3ICh1aWQgZmxhZ3MpCj4+Pj4gICAgICAgICAgICBtZXNzYWdl
RXhwdW5nZSkpIChwZXJzb25hbCAoTWVzc2FnZU5ldyBGbGFnQ2hhbmdlCj4+Pj4gICAgICAgICAg
ICBNZXNzYWdlRXhwdW5nZSkpICAgIAo+Pj4+ICAgICAgICAgCj4+PiBVc2luZyB0aGUgcHJldmlv
dXMgbG9naWMgSSB3b3VsZCBoYXZlIHRob3VnaHQgdGhhdCB0aGUgcmVzdWx0IGlzIGFnYWluIGEK
Pj4+IHVuaW9uIG9mICJzZWxlY3RlZCIgYW5kICJwZXJzb25hbCIgZXZlbnRzLCByZXN1bHRpbmcg
ZmxhZyBjaGFuZ2VzIGJlaW5nCj4+PiByZXR1cm5lZCBhZ2Fpbi4gVW5sZXNzICJzZWxlY3RlZCIg
aXMgdHJlYXRlZCBzcGVjaWFsbHk/Cj4+PiAgICAgICAKPj4gIlNlbGVjdGVkIiBpcyBpbmRlZWQg
dHJlYXRlZCBzcGVjaWFsbHksIGFzIHBlciB0aGUgZm9sbG93aW5nIHRleHQgaW4KPj4gc2VjdGlv
biAzLjE6Cj4+ICAgICAKPiBPSywgSSBndWVzcyB0aGlzIGFuc3dlcnMgbXkgcXVlc3Rpb24uIEl0
IHdvdWxkIGJlIGhlbHBmdWwgaWYgdGhlCj4gZXhhbXBsZXMgaW4gNi4gbWVudGlvbmVkIHRoYXQu
IEZvciBleGFtcGxlIGNoYW5naW5nOgo+ICAgCj4+IO+7vyAgICBJbiB0aGlzIGV4YW1wbGUsIHRo
ZSBjbGllbnQgYXNrcyBmb3IgRmxhZ0NoYW5nZSBldmVudHMgZm9yIGFsbAo+PiAgICAgcGVyc29u
YWwgbWFpbGJveGVzIGV4Y2VwdCB0aGUgc2VsZWN0ZWQgbWFpbGJveDoKPj4gICAgICAgICBDOiBh
IG5vdGlmeSBzZXQgKHNlbGVjdGVkIChNZXNzYWdlbmV3ICh1aWQgZmxhZ3MpCj4+ICAgICAgICAg
ICAgbWVzc2FnZUV4cHVuZ2UpKSAocGVyc29uYWwgKE1lc3NhZ2VOZXcgRmxhZ0NoYW5nZQo+PiAg
ICAgICAgICAgIE1lc3NhZ2VFeHB1bmdlKSkKPj4gICAgIAo+IHRvIHNvbWV0aGluZyBsaWtlOgo+
Cj4gSW4gdGhlIG5leHQgZXhhbXBsZSB0aGUgY2xpZW50IGFza3MgZm9yIEZsYWdDaGFuZ2UgZXZl
bnRzIGZvciBhbGwKPiBwZXJzb25hbCBtYWlsYm94ZXMgZXhjZXB0IHRoZSBzZWxlY3RlZCBtYWls
Ym94LiBUaGlzIGlzIGRpZmZlcmVudCBmcm9tCj4gdGhlIHByZXZpb3VzIGV4YW1wbGUsIGJlY2F1
c2UgU0VMRUNURUQgb3ZlcnJpZGVzIGFsbCBvdGhlciBldmVudAo+IGRlZmluaXRpb25zLgo+ICAg
CkkndmUgY2hhbmdlZCB0aGlzIGluIG15IGNvcHkuCj4+PiBhIG5vdGlmeSBzZXQgKHNlbGVjdGVk
IChNZXNzYWdlTmV3IE1lc3NhZ2VFeHB1bmdlKSkgKHBlcnNvbmFsCj4+PiAoU3Vic2NyaXB0aW9u
Q2hhbmdlKSkgIAo+Pj4gICAgICAgCj4+IFRoaXMgd291bGQgcmVzdWx0IGluIE1lc3NhZ2VOZXcg
YW5kIE1lc3NhZ2VFeHB1bmdlIGV2ZW50cyBmb3IgdGhlCj4+IGN1cnJlbnRseSBzZWxlY3RlZCBt
YWlsYm94ICh3aGV0aGVyIGl0IGlzIGEgcGVyc29uYWwgb25lIG9yIG5vdCkgYW5kCj4+IHN1YnNj
cmlwdGlvbiBjaGFuZ2Ugbm90aWZpY2F0aW9ucyBmb3IgYWxsIHBlcnNvbmFsIG1haWxib3hlcyBl
eGNlcHQgZm9yCj4+IHRoZSBjdXJyZW50bHkgc2VsZWN0ZWQgb25lIChpZiBpdCBpcyBhIHBlcnNv
bmFsIG1haWxib3gpLgo+Pgo+PiBIbW0sIHRoaXMgcmFpc2VzIGFuIGludGVyZXN0aW5nIHF1ZXN0
aW9uOiBpcyB0aGUgImV4Y2VwdCBmb3IgdGhlCj4+IGN1cnJlbnRseSBzZWxlY3RlZCIgcGFydCBp
biB0aGUgbGFzdCBzZW50ZW5jZSBpcyB3aGF0IHdlIGFjdHVhbGx5IHdhbnQ/Cj4+IFNob3VsZCAi
U2VsZWN0ZWQib25seSBhcHBseSB0byBtZXNzYWdlIGxldmVsIGV2ZW50cz8KPj4gICAgIAo+IEkg
dGhpbmsgdGhhdCB3b3VsZCBiZSBiZXR0ZXIuCj4gICAKSSB0aGluayB0aGlzIGNoYW5nZSB3b3Vs
ZCBuZWVkIHdpZGVyIHN1cHBvcnQgZnJvbSB0aGUgV0csIHRoYXQgaXMgd2h5IApJJ3ZlIGNoYW5n
ZWQgdGhlIHN1YmplY3Qgb2YgdGhpcyBtZXNzYWdlLgoKU3BlYWtpbmcgcGVyc29uYWxseSwgSSBh
bSBpbiBmYXZvciBvZiB0aGlzIGNoYW5nZSwgYmVjYXVzZSBiZWhhdmlvdXIgb2YgClNFTEVDVEVE
IG1pZ2h0IGJlIGEgYml0IHN1cnByaXNpbmcuCgpJIHdvdWxkIGxpa2UgdG8gaGVhciB3aGF0IG90
aGVyIHBlb3BsZSB0aGluayBhYm91dCB0aGlzLCBpbiBwYXJ0aWN1bGFyIEkgCndvdWxkIGxpa2Ug
dG8gaGVhciBvcGluaW9ucyBmcm9tIFBldGVyIENvYXRlcyBhbmQgQXJudC4KCgpfX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpsZW1vbmFkZSBtYWlsaW5nIGxp
c3QKbGVtb25hZGVAaWV0Zi5vcmcKaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m
by9sZW1vbmFkZQpTdXBwbGVtZW50YWwgV2ViIFNpdGU6Cmh0dHA6Ly93d3cuc3RhbmRhcmRzdHJh
Y2suY29tL2lldGYvbGVtb25hZGU=


From lemonade-bounces@ietf.org  Tue May 27 03:31: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 5C22A3A697D;
	Tue, 27 May 2008 03:31: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 B6C2128C226
	for <lemonade@core3.amsl.com>; Tue, 27 May 2008 03:31: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 RcZS9f7NGzw2 for <lemonade@core3.amsl.com>;
	Tue, 27 May 2008 03:31:44 -0700 (PDT)
Received: from dovecot.org (dovecot.org [82.118.211.50])
	by core3.amsl.com (Postfix) with ESMTP id 2C2713A6887
	for <lemonade@ietf.org>; Tue, 27 May 2008 03:30: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 5438A16471F2;
	Tue, 27 May 2008 13:30:19 +0300 (EEST)
Message-Id: <1B7D968F-7A77-40FC-AFD6-ADF3C2826822@iki.fi>
From: Timo Sirainen <tss@iki.fi>
To: Alexey Melnikov <alexey.melnikov@isode.com>
In-Reply-To: <483BAB35.2080806@isode.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 27 May 2008 13:30:14 +0300
References: <C433D277.1AB18%eburger@bea.com>
	<8B9B8F32-8DEF-40B9-992E-9337FB7AE344@standardstrack.com>
	<1210951366.9518.654.camel@hurina> <48312F7D.8090103@isode.com>
	<1211191304.9518.755.camel@hurina> <4835D000.4080808@isode.com>
	<1211745339.3904.166.camel@hurina> <483BAB35.2080806@isode.com>
X-Pgp-Agent: GPGMail d51 (Leopard)
X-Mailer: Apple Mail (2.919.2)
Cc: lemonade <lemonade@ietf.org>
Subject: Re: [lemonade] WGLC NOTIFY
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="===============0261174554=="
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

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

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

On May 27, 2008, at 9:33 AM, Alexey Melnikov wrote:

> Timo Sirainen wrote:
>> One more thing I thought of:
>>> If IDLE (as well as this extension) is supported, while processing
>>>    IDLE the server MUST send the same events as instructed by the
>>>    client using the NOTIFY command.
>>>
>> Does this mean EXPUNGEs must not be sent if MessageExpunge isn't
>> included in NOTIFY SET?
> Correct.
>> That would make it impossible to create clients
>> that use MSNs and want to be immediately notified of EXPUNGEs (while
>> IDLEing).
>>
> Correct. The client can either chose not to use NOTIFY at all (in  
> which
> case it will get expunges with MSNs), or it can chose to specify both
> MessageNew & MessageExpunge (they are tied together as per section 5),
> in which case it will get back UIDs.

"get back UIDs"? Do you mean VANISHED? Doesn't that depend on the  
server if it or EXPUNGE is sent?

What happens if NOTIFY SET is used, but SELECTED isn't specified? I  
can't seem to find this from the draft. I'm guessing it'll use the  
defaults? Or does it use the first other matching rule?

Anyway I think this is too restrictive if using NOTIFY basically  
requires the client to drop using MSNs. Some use cases for clients  
which want to keep using MSNs and IDLE:

1. Client just wants to use NOTIFY to see changes in other mailboxes,  
so it specifies NOTIFY SET (personal (messagenew messageexpunge)).

2. Client wants to use NOTIFY to ignore annotation changes, so it uses  
NOTIFY SET (selected (FlagChange)). EXISTS and EXPUNGEs are still sent  
in command replies, but not during IDLE?

3. Client wants to get pushed information about new messages' contents  
(MessageNew (uid ..)), but it still wants to keep using MSNs. Since  
MessageNew and MessageExpunge must specified together, this is  
impossible.

Is there even any other reason for client to even run IDLE unless it  
wants to keep using MSNs + see EXPUNGEs immediately? I think IDLE  
could be specified as sending EXPUNGEs immediately regardless of  
whether MessagExpunge has been specified.

3. is also problematic. Is it really necessary to give MessageExpunge  
if MessageNew is given? The (well-behaving) servers already have to  
handle the case when a message is expunged and a new message arrives  
during FETCH/STORE/SEARCH command. The client is notified about the  
new message but not about the expunge.

> It is possible that some servers that support IDLE don't send
> MessageExpunge events while idling, but I haven't seen any such  
> server.
> We could mandate that all servers advertising the NOTIFY capability  
> send
> MessageExpunge during IDLE if NOTIFY wasn't issued on the connection?!

I don't think that really matters since well-behaving servers already  
do that. I'm more concerned that well-behaving servers aren't allowed  
to do that when NOTIFY is used..

--Apple-Mail-2--498703341
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)

iEYEARECAAYFAkg74rYACgkQyUhSUUBViskOSgCfaVkHgrXAOn19eulw8twNr9yt
wo8AmgK78oKM3nyBpKmvvJoMGTvgSpjH
=unGY
-----END PGP SIGNATURE-----

--Apple-Mail-2--498703341--

--===============0261174554==
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
--===============0261174554==--


From lemonade-bounces@ietf.org  Thu May 29 11:36:52 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 EFAC63A6D32;
	Thu, 29 May 2008 11:36:52 -0700 (PDT)
X-Original-To: lemonade@ietf.org
Delivered-To: lemonade@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30)
	id AF9A63A6D24; Thu, 29 May 2008 11:36:50 -0700 (PDT)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <20080529183650.AF9A63A6D24@core3.amsl.com>
Date: Thu, 29 May 2008 11:36:50 -0700 (PDT)
Cc: lemonade mailing list <lemonade@ietf.org>,
	lemonade chair <lemonade-chairs@tools.ietf.org>,
	Internet Architecture Board <iab@iab.org>,
	RFC Editor <rfc-editor@rfc-editor.org>
Subject: [lemonade] Protocol Action: 'IMAP CONVERT extension' to Proposed
 Standard
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

The IESG has approved the following document:

- 'IMAP CONVERT extension '
   <draft-ietf-lemonade-convert-20.txt> as a Proposed Standard

This document is the product of the Enhancements to Internet email to 
Support Diverse Service Environments Working Group. 

The IESG contact persons are Chris Newman and Lisa Dusseault.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-lemonade-convert-20.txt

Technical Summary

   CONVERT defines extensions to IMAP allowing clients to request
   adaptation and/or transcoding of attachments.  Clients can specify
   the conversion details or allow servers to decide based on knowledge
   of client capabilities, on user or administrator preferences or its
   settings.

Working Group Summary

   The document went through two WGLC, the first one resulted in
   a major document rewrite.

   After the second WGLC it became clear that there was no consensus
   on proposed conversion discovery mechanisms. The editors formally
   polled the WG in order to figure out if any particular approach
   was preferred. Results of the poll indicated rough consensus in
   favor of conversion discovery mechanism using the CONVERSIONS
   command and AVAILABLECONVERSIONS CONVERT data item.

Document Quality

   There is at least 1 existing server implementation and at
   least 3 other server implementations are planned. At least
   2 client implementers are interested in implementing the
   specification.

   At least 6 people have reviewed the document. Posted comments
   were addressed in the latest revision.

Personnel

   Eric Burger is the Document Shepherd.  Chris Newman is the
   Responsible Area Director.

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


