
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l9JAHpZ9064595 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Oct 2007 03:17:51 -0700 (MST) (envelope-from owner-ietf-imapext@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l9JAHpgB064594; Fri, 19 Oct 2007 03:17:51 -0700 (MST) (envelope-from owner-ietf-imapext@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-imapext@mail.imc.org using -f
Received: from dovecot.org (dovecot.org [82.118.211.50]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l9JAHnbB064566 for <ietf-imapext@imc.org>; Fri, 19 Oct 2007 03:17:50 -0700 (MST) (envelope-from tss@iki.fi)
Received: from [192.168.10.2] (82-203-162-146.dsl.gohome.fi [82.203.162.146]) by dovecot.org (Postfix) with ESMTP id B68DEFA8A63; Fri, 19 Oct 2007 13:17:32 +0300 (EEST)
Subject: [Fwd: Re: list-extensions]
From: Timo Sirainen <tss@iki.fi>
To: Fred Batty <fredb@sun.com>
Cc: ietf-imapext@imc.org
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-RC++3iWJHmg2MfvLvXfS"
Date: Fri, 19 Oct 2007 13:17:31 +0300
Message-Id: <1192789051.25921.102.camel@hurina>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.0 
Sender: owner-ietf-imapext@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-imapext/mail-archive/>
List-ID: <ietf-imapext.imc.org>
List-Unsubscribe: <mailto:ietf-imapext-request@imc.org?body=unsubscribe>

--=-RC++3iWJHmg2MfvLvXfS
Content-Type: multipart/mixed; boundary="=-8/agslI61D74odAWo7A2"


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

This is what I ended up doing myself.


--=-8/agslI61D74odAWo7A2
Content-Disposition: inline
Content-Description: Forwarded message - Re: list-extensions
Content-Type: message/rfc822

Subject: Re: list-extensions
From: Timo Sirainen <tss@iki.fi>
To: Alexey Melnikov <alexey.melnikov@isode.com>
In-Reply-To: <1184531654.8261.167.camel@hurina>
References: <1182992741.3768.428.camel@hurina>
	 <1183066617.3768.458.camel@hurina> <1183155114.3768.551.camel@hurina>
	 <1183157680.3768.567.camel@hurina> <46895DB4.9090304@isode.com>
	 <1184276885.8261.71.camel@hurina> <469A80D8.4070003@isode.com>
	 <1184531034.8261.162.camel@hurina>  <469A8478.1090902@isode.com>
	 <1184531654.8261.167.camel@hurina>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-L6Yj1DqljkPtBIQmoVzG"
Message-Id: <1184547432.8261.188.camel@hurina>
Mime-Version: 1.0
X-Mailer: Evolution 2.10.1
Date: Mon, 16 Jul 2007 03:57:13 +0300


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

On Sun, 2007-07-15 at 23:34 +0300, Timo Sirainen wrote:
> On Mon, 2007-07-16 at 00:32 +0400, Alexey Melnikov wrote:
> > I would appreciate if you can list all the examples.

I think I'm beginning to finally understand this. :)

> C: D03 LIST (RECURSIVEMATCH SUBSCRIBED) "" "*2"
>       S: * LIST () "/" "foo2" ("CHILDINFO" ("SUBSCRIBED"))
>       S: * LIST (\Subscribed) "/" "foo2/bar2"
>       S: * LIST () "/" "baz2" ("CHILDINFO" ("SUBSCRIBED"))
>       S: * LIST (\Subscribed) "/" "baz2/bar2"
>       S: * LIST (\Subscribed) "/" "baz2/bar22"
>       S: * LIST (\Subscribed) "/" "baz2/bar222"
>       S: * LIST (\Subscribed) "/" "eps2" ("CHILDINFO" ("SUBSCRIBED"))
>       S: * LIST (\Subscribed) "/" "qux2/bar2"
>       S: D03 OK done
> "foo2" and "baz2"

"foo2" needs to be shown, because foo2/bar1 wasn't listed. But since
baz2's all children were listed, it shouldn't be shown.

Found also a typo ("collumn"):

    attribute and CHILDINFO (the first collumn describes if the parent

So, if I understood this correctly, the table could look like:

   +--------+--------------+--------------------+----------------------+
   | exists |   meets the  |  has a child that  |       returned       |
   |        |   selection  |      meets the     |     LIST-EXTENDED    |
   |        |   criteria   | selection criteria |    attributes and    |
   |        |              | (and LIST pattern) |       CHILDINFO      |
   +--------+--------------+--------------------+----------------------+
   |   no   |      no      |         no         |   no LIST response   |
   |        |              |                    |       returned       |
   |        |              |                    |                      |
   |   yes  |      no      |         no         |   no LIST response   |
   |        |              |                    |       returned       |
   |        |              |                    |                      |
   |   yes  |      no      |         no         |   no LIST response   |
   |        |              |                    |       returned       |
   |        |              |                    |                      |
   |   no   |      no      |        both        |  no LIST response    |
   |        |              |                    |       returned       |
   |        |              |                    |                      |
   |   yes  |      no      |        both        |  no LIST response    |
   |        |              |                    |       returned       |
   |        |              |                    |                      |
   |   no   |      yes     |         no         |     (\NonExistent    |
   |        |              |                    |        <attr>)       |
   |        |              |                    |                      |
   |   yes  |      yes     |         no         |       (<attr>)       |
   |        |              |                    |                      |
   |   no   |      no      |   selection-only   |   (\NonExistent) +   |
   |        |              |                    |       CHILDINFO      |
   |        |              |                    |                      |
   |   yes  |      no      |   selection-only   |    () + CHILDINFO    |
   |        |              |                    |                      |
   |   no   |      yes     |   selection/both   |     (\NonExistent    |
   |        |              |                    |  <attr>) + CHILDINFO |
   |        |              |                    |                      |
   |   yes  |      yes     |   selection/both   | (<attr>) + CHILDINFO |
   +--------+--------------+--------------------+----------------------+


--=-L6Yj1DqljkPtBIQmoVzG
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)

iD8DBQBGmsJoyUhSUUBViskRAsAoAJ9eKqnPg3L9OY2mgNBPv+m0ctF9cQCdHFje
GmLhmuZrDb+QZkA0zpzD6lg=
=CR+y
-----END PGP SIGNATURE-----

--=-L6Yj1DqljkPtBIQmoVzG--

--=-8/agslI61D74odAWo7A2--

--=-RC++3iWJHmg2MfvLvXfS
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)

iD8DBQBHGIQ7yUhSUUBViskRAnGhAKCnAvpund5NwMcv1gyweU+O8gJuIgCfej1f
19aa4NCgQochzWFusIjs5qA=
=De2L
-----END PGP SIGNATURE-----

--=-RC++3iWJHmg2MfvLvXfS--



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l9HMP8gq083053 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Oct 2007 15:25:08 -0700 (MST) (envelope-from owner-ietf-imapext@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l9HMP8F7083052; Wed, 17 Oct 2007 15:25:08 -0700 (MST) (envelope-from owner-ietf-imapext@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-imapext@mail.imc.org using -f
Received: from sca-es-mail-2.sun.com (sca-es-mail-2.Sun.COM [192.18.43.133]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l9HMOmxf083029 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for <ietf-imapext@imc.org>; Wed, 17 Oct 2007 15:25:08 -0700 (MST) (envelope-from fredb@sun.com)
Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id l9HMOlKW006147 for <ietf-imapext@imc.org>; Wed, 17 Oct 2007 15:24:47 -0700 (PDT)
Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JQ200J01QA2AI00@fe-sfbay-10.sun.com> (original mail from fredb@sun.com) for ietf-imapext@imc.org; Wed, 17 Oct 2007 15:24:47 -0700 (PDT)
Received: from [192.18.126.69] by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JQ20062QU8XOEG0@fe-sfbay-10.sun.com> for ietf-imapext@imc.org; Wed, 17 Oct 2007 15:24:33 -0700 (PDT)
Date: Wed, 17 Oct 2007 15:24:33 -0700
From: Fred Batty <fredb@sun.com>
Subject: LIST-EXTENDED and child mailboxes
To: ietf-imapext@imc.org
Message-id: <47168BA1.3070109@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, el, fr-fr, ja, en
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20060727
Sender: owner-ietf-imapext@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-imapext/mail-archive/>
List-ID: <ietf-imapext.imc.org>
List-Unsubscribe: <mailto:ietf-imapext-request@imc.org?body=unsubscribe>

Hi. I am trying to implement LIST-EXTENDED and have a problem with this
paragraph in section 3.5:

   Note: Some servers allow for mailboxes to exist without requiring
   their parent to exist.  For example, a mailbox "Customers/ABC" can
   exist while the mailbox "Customers" does not.  As CHILDINFO extended
   data item is not allowed if the RECURSIVEMATCH selection option is
   not specified, such servers SHOULD use the "\NonExistent
   \HasChildren" attribute pair to signal to the client that there is a
   descendant mailbox that matches the selection criteria.

Doesn't it force the server to do the same work as if the client had asked for
RECURSIVEMATCH, even when the client didn't specify it, thus probably doesn't
care? If so, wouldn't this be a serious problem if the selection criteria is
expensive to determine, e.g. involving annotations?


Also, I guess this is more minor but shouldn't the word 'exactly' in this
section 3.1 paragraph be replaced by 'at most':

   1.  Exactly one LIST response should be returned for each mailbox
       name which matches the canonical LIST pattern.  Server
       implementors must not assume that clients will be able to
       assemble mailbox attributes and other information returned in
       multiple LIST responses.


Fred



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l9GFZf4t024726 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Oct 2007 08:35:41 -0700 (MST) (envelope-from owner-ietf-imapext@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l9GFZfLe024725; Tue, 16 Oct 2007 08:35:41 -0700 (MST) (envelope-from owner-ietf-imapext@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-imapext@mail.imc.org using -f
Received: from mail146.messagelabs.com (mail146.messagelabs.com [216.82.245.131]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l9GFZaUv024696 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 16 Oct 2007 08:35:38 -0700 (MST) (envelope-from tony@att.com)
X-VirusChecked: Checked
X-Env-Sender: tony@att.com
X-Msg-Ref: server-11.tower-146.messagelabs.com!1192548935!20208381!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.128.149]
Received: (qmail 10710 invoked from network); 16 Oct 2007 15:35:35 -0000
Received: from sbcsmtp9.sbc.com (HELO flph024.enaf.ffdc.sbc.com) (144.160.128.149) by server-11.tower-146.messagelabs.com with AES256-SHA encrypted SMTP; 16 Oct 2007 15:35:35 -0000
Received: from enaf.ffdc.sbc.com (localhost.localdomain [127.0.0.1]) by flph024.enaf.ffdc.sbc.com (8.14.0/8.14.0) with ESMTP id l9GFZYpe004205; Tue, 16 Oct 2007 08:35:34 -0700
Received: from flph023.ffdc.sbc.com (flph023.ffdc.sbc.com [150.234.117.36]) by flph024.enaf.ffdc.sbc.com (8.14.0/8.14.0) with ESMTP id l9GFZUYf004160; Tue, 16 Oct 2007 08:35:30 -0700
Received: from ffdc.sbc.com (localhost.localdomain [127.0.0.1]) by flph023.ffdc.sbc.com (8.14.0/8.14.0) with ESMTP id l9GFZUK6010970; Tue, 16 Oct 2007 08:35:30 -0700
Received: from maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by flph023.ffdc.sbc.com (8.14.0/8.14.0) with ESMTP id l9GFZQLP010893; Tue, 16 Oct 2007 08:35:26 -0700
Received: from [135.210.128.98] (unknown[135.210.128.98](misconfigured sender)) by maillennium.att.com (mailgw1) with ESMTP id <20071016153524gw10010gsme> (Authid: tony); Tue, 16 Oct 2007 15:35:25 +0000
Message-ID: <4714DA04.5010308@att.com>
Date: Tue, 16 Oct 2007 11:34:28 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: SMTP Interest Group <ietf-smtp@imc.org>
CC: ietf-822 mailing list <ietf-822@imc.org>, LEMONADE WG mailing list <lemonade@ietf.org>, IMAP extensions mailing list <ietf-imapext@imc.org>, EAI WG mailing list <ima@ietf.org>, POP3 extensions mailing list <ietf-pop3ext@imc.org>, USEFOR WG <ietf-usefor@imc.org>
Subject: Mailing List Last Call now open for draft-klensin-rfc2821bis-05.txt
References: <E1Ihe4A-0000va-3z@stiedprstage1.ietf.org>
In-Reply-To: <E1Ihe4A-0000va-3z@stiedprstage1.ietf.org>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-imapext@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-imapext/mail-archive/>
List-ID: <ietf-imapext.imc.org>
List-Unsubscribe: <mailto:ietf-imapext-request@imc.org?body=unsubscribe>

This is a "formal" Mailing List Last Call on
draft-klensin-rfc2821bis-05.txt. The last call will last for two weeks
time, ending on October 30, 2007.

Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
> 	Title           : Simple Mail Transfer Protocol
> 	Filename        : draft-klensin-rfc2821bis-05.txt
>...
> http://www.ietf.org/internet-drafts/draft-klensin-rfc2821bis-05.txt

If you go to http://tools.ietf.org/html/draft-klensin-rfc2821bis and
click on [Diff1], you'll see a highlighted list of changes between this
and the previous version.

Major changes for this release are indicated in Appendix G.7.

   G.7.  Changes from version -04 to -05
   1.  Added registry pointers to Section 8 (issue 36).
   2.  "for" clause in Received header reduced to a single mailbox,
       since this seems to reflect list consensus (issue 37).  An
       "additional registered clauses" entry was made to allow for
       future extension (also issue 37).
   3.  Corrected some I-D references to point to now-published RFCs.

At this point, all extant issues are considered closed.

The Mailing List Last Call is now declared open.

Depending on the outcome of the Mailing List Last Call, the next step
will be to submit the document (or its revision) to the IESG for
IETF-wide Last Call.

Thanks!

	Tony Hansen
	tony@att.com



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l99Nqg41025483 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Oct 2007 16:52:42 -0700 (MST) (envelope-from owner-ietf-imapext@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l99NqgrC025482; Tue, 9 Oct 2007 16:52:42 -0700 (MST) (envelope-from owner-ietf-imapext@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-imapext@mail.imc.org using -f
Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l99NqfUI025475 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-imapext@IMC.ORG>; Tue, 9 Oct 2007 16:52:42 -0700 (MST) (envelope-from MRC@CAC.Washington.EDU)
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW07.09) with ESMTP id l99NqeCg025986 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 9 Oct 2007 16:52:40 -0700
X-Auth-Received: from Tomobiki-Cho.CAC.Washignton.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.7+UW06.06/8.13.7+UW07.09) with ESMTP id l99NqeMc010600 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 9 Oct 2007 16:52:40 -0700
Date: Tue, 9 Oct 2007 16:52:35 -0700 (Pacific Daylight Time)
From: Mark Crispin <MRC@CAC.Washington.EDU>
To: IMAP Protocol Interest List <IMAP-Protocol@U.Washington.EDU>
cc: IMAP Extensions WG <ietf-imapext@imc.org>
Subject: Modified UTF-7: justice delayed, but justice served... ;-)
Message-ID: <alpine.WNT.0.9999.0710091611520.6020@Tomobiki-Cho.CAC.Washignton.EDU>
Organization: Networks & Distributed Computing
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-PMX-Version: 5.3.3.310218, Antispam-Engine: 2.5.2.313940, Antispam-Data: 2007.10.9.163448
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CP_URI_IN_BODY 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0'
Sender: owner-ietf-imapext@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-imapext/mail-archive/>
List-ID: <ietf-imapext.imc.org>
List-Unsubscribe: <mailto:ietf-imapext-request@imc.org?body=unsubscribe>

I just spent the past several hours implementing support routines for 
Modified UTF-7, with the intention that Alpine will support multinational 
IMAP mailbox names.

I always knew that the design of Modified UTF-7 sucked.  It was certainly 
well-intentioned.  Punycode would have saved the day, but it didn't appear 
until years later.

The road to hell is paved with good intentions.

Not until today have I fully comprehended the sheer implementation 
insanity and hideous design of Modified UTF-7.  I shudder to think of all 
the people who have beaten their heads against a wall in implementing 
Modified UTF-7.

To those of you with dents in your wall: I'm sorry.  As ot today, there's 
a head-shaped dent my wall too.  You've been avenged... ;-)

This has been a learning experience for me.  I feel that we need to push 
ahead on UTF-8 mailbox names sooner rather than later.  I feel that it is 
far more important for the i18n document to make UTF-8 mailbox names 
possible than setting the language for error messages or translating 
namespaces.  The latter two are really l10n issues and belong in a 
separate IMAP-L10N document.

More specifically, I would move Section 3 of imap-i18n to a new imap-l10n, 
and upgrade the former section 5 to be a full mechanism rather than a 
discussion.  I suggest that the former section 5.1 of imap-i18n deprecate 
the LOGIN command entirely, and highlight that SASL names are Unicode.

As I suggest above, I feel that section 5.2 of imap-i18n is highly 
unsatisfactory for today and needs a real mechanism; the now-expired 
draft-ietf-eai-imap-utf8-01.txt was an option although I would prefer a 
simplified mechanism.

-- Mark --

http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l99NjYlI025002 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Oct 2007 16:45:34 -0700 (MST) (envelope-from owner-ietf-imapext@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l99NjYno025001; Tue, 9 Oct 2007 16:45:34 -0700 (MST) (envelope-from owner-ietf-imapext@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-imapext@mail.imc.org using -f
Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l99NjWjj024995 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-imapext@IMC.ORG>; Tue, 9 Oct 2007 16:45:33 -0700 (MST) (envelope-from MRC@CAC.Washington.EDU)
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.141] (may be forged)) by mxout7.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW07.09) with ESMTP id l99NjV5E021996 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <ietf-imapext@IMC.ORG>; Tue, 9 Oct 2007 16:45:32 -0700
X-Auth-Received: from Tomobiki-Cho.CAC.Washignton.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.7+UW06.06/8.13.7+UW07.09) with ESMTP id l99NjTwC004564 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <ietf-imapext@IMC.ORG>; Tue, 9 Oct 2007 16:45:31 -0700
Date: Tue, 9 Oct 2007 16:45:24 -0700 (Pacific Daylight Time)
From: Mark Crispin <MRC@CAC.Washington.EDU>
To: IMAP Extensions WG <ietf-imapext@imc.org>
Subject: error in draft-ietf-imapext-i18n-12.txt
Message-ID: <alpine.WNT.0.9999.0710091643120.5004@Tomobiki-Cho.CAC.Washignton.EDU>
Organization: Networks & Distributed Computing
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-PMX-Version: 5.3.3.310218, Antispam-Engine: 2.5.2.313940, Antispam-Data: 2007.10.9.161949
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='BODY_SIZE_500_599 0, __CP_URI_IN_BODY 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0'
Sender: owner-ietf-imapext@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-imapext/mail-archive/>
List-ID: <ietf-imapext.imc.org>
List-Unsubscribe: <mailto:ietf-imapext-request@imc.org?body=unsubscribe>

The word "presently" is used twice in this document.

The English word "presently" means "soon"/"after a short time", as in "I 
will wash the dishes presently."  The use of "presently" to mean 
"currently" (which in context seems to be the intended meaning) is 
American English slang and not accepted by all authorities.

In the name of unambiguity and good diction, please change "presently" to 
"currently" or "at present".  Thanks

-- Mark --

http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l9JAHpZ9064595 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Oct 2007 03:17:51 -0700 (MST) (envelope-from owner-ietf-imapext@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l9JAHpgB064594; Fri, 19 Oct 2007 03:17:51 -0700 (MST) (envelope-from owner-ietf-imapext@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-imapext@mail.imc.org using -f
Received: from dovecot.org (dovecot.org [82.118.211.50]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l9JAHnbB064566 for <ietf-imapext@imc.org>; Fri, 19 Oct 2007 03:17:50 -0700 (MST) (envelope-from tss@iki.fi)
Received: from [192.168.10.2] (82-203-162-146.dsl.gohome.fi [82.203.162.146]) by dovecot.org (Postfix) with ESMTP id B68DEFA8A63; Fri, 19 Oct 2007 13:17:32 +0300 (EEST)
Subject: [Fwd: Re: list-extensions]
From: Timo Sirainen <tss@iki.fi>
To: Fred Batty <fredb@sun.com>
Cc: ietf-imapext@imc.org
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-RC++3iWJHmg2MfvLvXfS"
Date: Fri, 19 Oct 2007 13:17:31 +0300
Message-Id: <1192789051.25921.102.camel@hurina>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.0 
Sender: owner-ietf-imapext@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-imapext/mail-archive/>
List-ID: <ietf-imapext.imc.org>
List-Unsubscribe: <mailto:ietf-imapext-request@imc.org?body=unsubscribe>

--=-RC++3iWJHmg2MfvLvXfS
Content-Type: multipart/mixed; boundary="=-8/agslI61D74odAWo7A2"


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

This is what I ended up doing myself.


--=-8/agslI61D74odAWo7A2
Content-Disposition: inline
Content-Description: Forwarded message - Re: list-extensions
Content-Type: message/rfc822

Subject: Re: list-extensions
From: Timo Sirainen <tss@iki.fi>
To: Alexey Melnikov <alexey.melnikov@isode.com>
In-Reply-To: <1184531654.8261.167.camel@hurina>
References: <1182992741.3768.428.camel@hurina>
	 <1183066617.3768.458.camel@hurina> <1183155114.3768.551.camel@hurina>
	 <1183157680.3768.567.camel@hurina> <46895DB4.9090304@isode.com>
	 <1184276885.8261.71.camel@hurina> <469A80D8.4070003@isode.com>
	 <1184531034.8261.162.camel@hurina>  <469A8478.1090902@isode.com>
	 <1184531654.8261.167.camel@hurina>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-L6Yj1DqljkPtBIQmoVzG"
Message-Id: <1184547432.8261.188.camel@hurina>
Mime-Version: 1.0
X-Mailer: Evolution 2.10.1
Date: Mon, 16 Jul 2007 03:57:13 +0300


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

On Sun, 2007-07-15 at 23:34 +0300, Timo Sirainen wrote:
> On Mon, 2007-07-16 at 00:32 +0400, Alexey Melnikov wrote:
> > I would appreciate if you can list all the examples.

I think I'm beginning to finally understand this. :)

> C: D03 LIST (RECURSIVEMATCH SUBSCRIBED) "" "*2"
>       S: * LIST () "/" "foo2" ("CHILDINFO" ("SUBSCRIBED"))
>       S: * LIST (\Subscribed) "/" "foo2/bar2"
>       S: * LIST () "/" "baz2" ("CHILDINFO" ("SUBSCRIBED"))
>       S: * LIST (\Subscribed) "/" "baz2/bar2"
>       S: * LIST (\Subscribed) "/" "baz2/bar22"
>       S: * LIST (\Subscribed) "/" "baz2/bar222"
>       S: * LIST (\Subscribed) "/" "eps2" ("CHILDINFO" ("SUBSCRIBED"))
>       S: * LIST (\Subscribed) "/" "qux2/bar2"
>       S: D03 OK done
> "foo2" and "baz2"

"foo2" needs to be shown, because foo2/bar1 wasn't listed. But since
baz2's all children were listed, it shouldn't be shown.

Found also a typo ("collumn"):

    attribute and CHILDINFO (the first collumn describes if the parent

So, if I understood this correctly, the table could look like:

   +--------+--------------+--------------------+----------------------+
   | exists |   meets the  |  has a child that  |       returned       |
   |        |   selection  |      meets the     |     LIST-EXTENDED    |
   |        |   criteria   | selection criteria |    attributes and    |
   |        |              | (and LIST pattern) |       CHILDINFO      |
   +--------+--------------+--------------------+----------------------+
   |   no   |      no      |         no         |   no LIST response   |
   |        |              |                    |       returned       |
   |        |              |                    |                      |
   |   yes  |      no      |         no         |   no LIST response   |
   |        |              |                    |       returned       |
   |        |              |                    |                      |
   |   yes  |      no      |         no         |   no LIST response   |
   |        |              |                    |       returned       |
   |        |              |                    |                      |
   |   no   |      no      |        both        |  no LIST response    |
   |        |              |                    |       returned       |
   |        |              |                    |                      |
   |   yes  |      no      |        both        |  no LIST response    |
   |        |              |                    |       returned       |
   |        |              |                    |                      |
   |   no   |      yes     |         no         |     (\NonExistent    |
   |        |              |                    |        <attr>)       |
   |        |              |                    |                      |
   |   yes  |      yes     |         no         |       (<attr>)       |
   |        |              |                    |                      |
   |   no   |      no      |   selection-only   |   (\NonExistent) +   |
   |        |              |                    |       CHILDINFO      |
   |        |              |                    |                      |
   |   yes  |      no      |   selection-only   |    () + CHILDINFO    |
   |        |              |                    |                      |
   |   no   |      yes     |   selection/both   |     (\NonExistent    |
   |        |              |                    |  <attr>) + CHILDINFO |
   |        |              |                    |                      |
   |   yes  |      yes     |   selection/both   | (<attr>) + CHILDINFO |
   +--------+--------------+--------------------+----------------------+


--=-L6Yj1DqljkPtBIQmoVzG
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)

iD8DBQBGmsJoyUhSUUBViskRAsAoAJ9eKqnPg3L9OY2mgNBPv+m0ctF9cQCdHFje
GmLhmuZrDb+QZkA0zpzD6lg=
=CR+y
-----END PGP SIGNATURE-----

--=-L6Yj1DqljkPtBIQmoVzG--

--=-8/agslI61D74odAWo7A2--

--=-RC++3iWJHmg2MfvLvXfS
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)

iD8DBQBHGIQ7yUhSUUBViskRAnGhAKCnAvpund5NwMcv1gyweU+O8gJuIgCfej1f
19aa4NCgQochzWFusIjs5qA=
=De2L
-----END PGP SIGNATURE-----

--=-RC++3iWJHmg2MfvLvXfS--



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l9HMP8gq083053 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Oct 2007 15:25:08 -0700 (MST) (envelope-from owner-ietf-imapext@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l9HMP8F7083052; Wed, 17 Oct 2007 15:25:08 -0700 (MST) (envelope-from owner-ietf-imapext@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-imapext@mail.imc.org using -f
Received: from sca-es-mail-2.sun.com (sca-es-mail-2.Sun.COM [192.18.43.133]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l9HMOmxf083029 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for <ietf-imapext@imc.org>; Wed, 17 Oct 2007 15:25:08 -0700 (MST) (envelope-from fredb@sun.com)
Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id l9HMOlKW006147 for <ietf-imapext@imc.org>; Wed, 17 Oct 2007 15:24:47 -0700 (PDT)
Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JQ200J01QA2AI00@fe-sfbay-10.sun.com> (original mail from fredb@sun.com) for ietf-imapext@imc.org; Wed, 17 Oct 2007 15:24:47 -0700 (PDT)
Received: from [192.18.126.69] by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JQ20062QU8XOEG0@fe-sfbay-10.sun.com> for ietf-imapext@imc.org; Wed, 17 Oct 2007 15:24:33 -0700 (PDT)
Date: Wed, 17 Oct 2007 15:24:33 -0700
From: Fred Batty <fredb@sun.com>
Subject: LIST-EXTENDED and child mailboxes
To: ietf-imapext@imc.org
Message-id: <47168BA1.3070109@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, el, fr-fr, ja, en
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20060727
Sender: owner-ietf-imapext@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-imapext/mail-archive/>
List-ID: <ietf-imapext.imc.org>
List-Unsubscribe: <mailto:ietf-imapext-request@imc.org?body=unsubscribe>

Hi. I am trying to implement LIST-EXTENDED and have a problem with this
paragraph in section 3.5:

   Note: Some servers allow for mailboxes to exist without requiring
   their parent to exist.  For example, a mailbox "Customers/ABC" can
   exist while the mailbox "Customers" does not.  As CHILDINFO extended
   data item is not allowed if the RECURSIVEMATCH selection option is
   not specified, such servers SHOULD use the "\NonExistent
   \HasChildren" attribute pair to signal to the client that there is a
   descendant mailbox that matches the selection criteria.

Doesn't it force the server to do the same work as if the client had asked for
RECURSIVEMATCH, even when the client didn't specify it, thus probably doesn't
care? If so, wouldn't this be a serious problem if the selection criteria is
expensive to determine, e.g. involving annotations?


Also, I guess this is more minor but shouldn't the word 'exactly' in this
section 3.1 paragraph be replaced by 'at most':

   1.  Exactly one LIST response should be returned for each mailbox
       name which matches the canonical LIST pattern.  Server
       implementors must not assume that clients will be able to
       assemble mailbox attributes and other information returned in
       multiple LIST responses.


Fred



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l9GFZf4t024726 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Oct 2007 08:35:41 -0700 (MST) (envelope-from owner-ietf-imapext@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l9GFZfLe024725; Tue, 16 Oct 2007 08:35:41 -0700 (MST) (envelope-from owner-ietf-imapext@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-imapext@mail.imc.org using -f
Received: from mail146.messagelabs.com (mail146.messagelabs.com [216.82.245.131]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l9GFZaUv024696 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 16 Oct 2007 08:35:38 -0700 (MST) (envelope-from tony@att.com)
X-VirusChecked: Checked
X-Env-Sender: tony@att.com
X-Msg-Ref: server-11.tower-146.messagelabs.com!1192548935!20208381!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.128.149]
Received: (qmail 10710 invoked from network); 16 Oct 2007 15:35:35 -0000
Received: from sbcsmtp9.sbc.com (HELO flph024.enaf.ffdc.sbc.com) (144.160.128.149) by server-11.tower-146.messagelabs.com with AES256-SHA encrypted SMTP; 16 Oct 2007 15:35:35 -0000
Received: from enaf.ffdc.sbc.com (localhost.localdomain [127.0.0.1]) by flph024.enaf.ffdc.sbc.com (8.14.0/8.14.0) with ESMTP id l9GFZYpe004205; Tue, 16 Oct 2007 08:35:34 -0700
Received: from flph023.ffdc.sbc.com (flph023.ffdc.sbc.com [150.234.117.36]) by flph024.enaf.ffdc.sbc.com (8.14.0/8.14.0) with ESMTP id l9GFZUYf004160; Tue, 16 Oct 2007 08:35:30 -0700
Received: from ffdc.sbc.com (localhost.localdomain [127.0.0.1]) by flph023.ffdc.sbc.com (8.14.0/8.14.0) with ESMTP id l9GFZUK6010970; Tue, 16 Oct 2007 08:35:30 -0700
Received: from maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by flph023.ffdc.sbc.com (8.14.0/8.14.0) with ESMTP id l9GFZQLP010893; Tue, 16 Oct 2007 08:35:26 -0700
Received: from [135.210.128.98] (unknown[135.210.128.98](misconfigured sender)) by maillennium.att.com (mailgw1) with ESMTP id <20071016153524gw10010gsme> (Authid: tony); Tue, 16 Oct 2007 15:35:25 +0000
Message-ID: <4714DA04.5010308@att.com>
Date: Tue, 16 Oct 2007 11:34:28 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: SMTP Interest Group <ietf-smtp@imc.org>
CC: ietf-822 mailing list <ietf-822@imc.org>, LEMONADE WG mailing list <lemonade@ietf.org>, IMAP extensions mailing list <ietf-imapext@imc.org>, EAI WG mailing list <ima@ietf.org>, POP3 extensions mailing list <ietf-pop3ext@imc.org>, USEFOR WG <ietf-usefor@imc.org>
Subject: Mailing List Last Call now open for draft-klensin-rfc2821bis-05.txt
References: <E1Ihe4A-0000va-3z@stiedprstage1.ietf.org>
In-Reply-To: <E1Ihe4A-0000va-3z@stiedprstage1.ietf.org>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-imapext@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-imapext/mail-archive/>
List-ID: <ietf-imapext.imc.org>
List-Unsubscribe: <mailto:ietf-imapext-request@imc.org?body=unsubscribe>

This is a "formal" Mailing List Last Call on
draft-klensin-rfc2821bis-05.txt. The last call will last for two weeks
time, ending on October 30, 2007.

Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
> 	Title           : Simple Mail Transfer Protocol
> 	Filename        : draft-klensin-rfc2821bis-05.txt
>...
> http://www.ietf.org/internet-drafts/draft-klensin-rfc2821bis-05.txt

If you go to http://tools.ietf.org/html/draft-klensin-rfc2821bis and
click on [Diff1], you'll see a highlighted list of changes between this
and the previous version.

Major changes for this release are indicated in Appendix G.7.

   G.7.  Changes from version -04 to -05
   1.  Added registry pointers to Section 8 (issue 36).
   2.  "for" clause in Received header reduced to a single mailbox,
       since this seems to reflect list consensus (issue 37).  An
       "additional registered clauses" entry was made to allow for
       future extension (also issue 37).
   3.  Corrected some I-D references to point to now-published RFCs.

At this point, all extant issues are considered closed.

The Mailing List Last Call is now declared open.

Depending on the outcome of the Mailing List Last Call, the next step
will be to submit the document (or its revision) to the IESG for
IETF-wide Last Call.

Thanks!

	Tony Hansen
	tony@att.com



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l99Nqg41025483 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Oct 2007 16:52:42 -0700 (MST) (envelope-from owner-ietf-imapext@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l99NqgrC025482; Tue, 9 Oct 2007 16:52:42 -0700 (MST) (envelope-from owner-ietf-imapext@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-imapext@mail.imc.org using -f
Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l99NqfUI025475 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-imapext@IMC.ORG>; Tue, 9 Oct 2007 16:52:42 -0700 (MST) (envelope-from MRC@CAC.Washington.EDU)
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW07.09) with ESMTP id l99NqeCg025986 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 9 Oct 2007 16:52:40 -0700
X-Auth-Received: from Tomobiki-Cho.CAC.Washignton.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.7+UW06.06/8.13.7+UW07.09) with ESMTP id l99NqeMc010600 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 9 Oct 2007 16:52:40 -0700
Date: Tue, 9 Oct 2007 16:52:35 -0700 (Pacific Daylight Time)
From: Mark Crispin <MRC@CAC.Washington.EDU>
To: IMAP Protocol Interest List <IMAP-Protocol@U.Washington.EDU>
cc: IMAP Extensions WG <ietf-imapext@imc.org>
Subject: Modified UTF-7: justice delayed, but justice served... ;-)
Message-ID: <alpine.WNT.0.9999.0710091611520.6020@Tomobiki-Cho.CAC.Washignton.EDU>
Organization: Networks & Distributed Computing
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-PMX-Version: 5.3.3.310218, Antispam-Engine: 2.5.2.313940, Antispam-Data: 2007.10.9.163448
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CP_URI_IN_BODY 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0'
Sender: owner-ietf-imapext@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-imapext/mail-archive/>
List-ID: <ietf-imapext.imc.org>
List-Unsubscribe: <mailto:ietf-imapext-request@imc.org?body=unsubscribe>

I just spent the past several hours implementing support routines for 
Modified UTF-7, with the intention that Alpine will support multinational 
IMAP mailbox names.

I always knew that the design of Modified UTF-7 sucked.  It was certainly 
well-intentioned.  Punycode would have saved the day, but it didn't appear 
until years later.

The road to hell is paved with good intentions.

Not until today have I fully comprehended the sheer implementation 
insanity and hideous design of Modified UTF-7.  I shudder to think of all 
the people who have beaten their heads against a wall in implementing 
Modified UTF-7.

To those of you with dents in your wall: I'm sorry.  As ot today, there's 
a head-shaped dent my wall too.  You've been avenged... ;-)

This has been a learning experience for me.  I feel that we need to push 
ahead on UTF-8 mailbox names sooner rather than later.  I feel that it is 
far more important for the i18n document to make UTF-8 mailbox names 
possible than setting the language for error messages or translating 
namespaces.  The latter two are really l10n issues and belong in a 
separate IMAP-L10N document.

More specifically, I would move Section 3 of imap-i18n to a new imap-l10n, 
and upgrade the former section 5 to be a full mechanism rather than a 
discussion.  I suggest that the former section 5.1 of imap-i18n deprecate 
the LOGIN command entirely, and highlight that SASL names are Unicode.

As I suggest above, I feel that section 5.2 of imap-i18n is highly 
unsatisfactory for today and needs a real mechanism; the now-expired 
draft-ietf-eai-imap-utf8-01.txt was an option although I would prefer a 
simplified mechanism.

-- Mark --

http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l99NjYlI025002 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Oct 2007 16:45:34 -0700 (MST) (envelope-from owner-ietf-imapext@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l99NjYno025001; Tue, 9 Oct 2007 16:45:34 -0700 (MST) (envelope-from owner-ietf-imapext@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-imapext@mail.imc.org using -f
Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l99NjWjj024995 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-imapext@IMC.ORG>; Tue, 9 Oct 2007 16:45:33 -0700 (MST) (envelope-from MRC@CAC.Washington.EDU)
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.141] (may be forged)) by mxout7.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW07.09) with ESMTP id l99NjV5E021996 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <ietf-imapext@IMC.ORG>; Tue, 9 Oct 2007 16:45:32 -0700
X-Auth-Received: from Tomobiki-Cho.CAC.Washignton.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.7+UW06.06/8.13.7+UW07.09) with ESMTP id l99NjTwC004564 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <ietf-imapext@IMC.ORG>; Tue, 9 Oct 2007 16:45:31 -0700
Date: Tue, 9 Oct 2007 16:45:24 -0700 (Pacific Daylight Time)
From: Mark Crispin <MRC@CAC.Washington.EDU>
To: IMAP Extensions WG <ietf-imapext@imc.org>
Subject: error in draft-ietf-imapext-i18n-12.txt
Message-ID: <alpine.WNT.0.9999.0710091643120.5004@Tomobiki-Cho.CAC.Washignton.EDU>
Organization: Networks & Distributed Computing
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-PMX-Version: 5.3.3.310218, Antispam-Engine: 2.5.2.313940, Antispam-Data: 2007.10.9.161949
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='BODY_SIZE_500_599 0, __CP_URI_IN_BODY 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0'
Sender: owner-ietf-imapext@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-imapext/mail-archive/>
List-ID: <ietf-imapext.imc.org>
List-Unsubscribe: <mailto:ietf-imapext-request@imc.org?body=unsubscribe>

The word "presently" is used twice in this document.

The English word "presently" means "soon"/"after a short time", as in "I 
will wash the dishes presently."  The use of "presently" to mean 
"currently" (which in context seems to be the intended meaning) is 
American English slang and not accepted by all authorities.

In the name of unambiguity and good diction, please change "presently" to 
"currently" or "at present".  Thanks

-- Mark --

http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.


