Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joseph Yee <jyee@afilias.info>
In-Reply-To: <4EDFCC55.6000000@isode.com>
Date: Tue, 20 Dec 2011 00:22:21 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <A17A1350-E2AC-4BE5-A9AF-038E8540FD78@afilias.info>
References: <CALaySJLZaQH0Pcys561UhU6jTdEnqpAFrnMcY6oeV1SpPD-aRg@mail.gmail.com>
 <4EDFCC55.6000000@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Cc: Barry Leiba <barryleiba@computer.org>, ima@ietf.org
Subject: Re: [EAI] UTF=x IMAP capabilities
Precedence: list

On 2011-12-07, at 3:28 PM, Alexey Melnikov wrote:

> Hi Barry,
>=20
> On 15/11/2011 13:13, Barry Leiba wrote:
> [...]
>> That leaves UTF8=3DONLY, which is reasonable to leave.  And so we =
have
>> three cases:
>>=20
>> 1.  No EAI support (no UTF8=3Dx capabilities listed).
>>=20
>> 2.  EAI support, but also support of non-UTF8 versions (UTF8=3DACCEPT).=

>>=20
>> 3.  EAI support, and it's all there is (UTF8=3DONLY).
>>=20
>> So I suggest that we just spell it out that way, and make UTF8=3DACCEPT=

>> and UTF8=3DONLY be mutually exclusive: there can be one, the other, =
or
>> neither, but never both.
> I don't think the latest -02 talks about the capabilities being =
mutually exclusive. But I think the rest of your proposal was =
implemented in -02.

as individual
+1 for spelling out the mutual exclusive between UTF8=3DACCEPT and =
UTF8=3DONLY

Joseph

>=20
> _______________________________________________
> IMA mailing list
> IMA@ietf.org
> https://www.ietf.org/mailman/listinfo/ima