Re: [EAI] UTF=x IMAP capabilities
Alexey Melnikov <alexey.melnikov@isode.com> Wed, 07 December 2011 20:28 UTC
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DCC511E80DF for <ima@ietfa.amsl.com>; Wed, 7 Dec 2011 12:28:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.178
X-Spam-Level:
X-Spam-Status: No, score=-102.178 tagged_above=-999 required=5 tests=[AWL=-0.179, BAYES_00=-2.599, J_CHICKENPOX_31=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t0hBOADwtpNs for <ima@ietfa.amsl.com>; Wed, 7 Dec 2011 12:28:01 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id 23D1E11E80D3 for <ima@ietf.org>; Wed, 7 Dec 2011 12:28:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1323289679; d=isode.com; s=selector; i=@isode.com; bh=TnThJQPFfbdCS633i2ocPugtykfMfoQZuygNiPCNIk8=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=OAOIhxPP4uWTM7GgkEQxT3GuNuc2pzboB2OGXIIVyyw02DY+JeJTgNSeioyn3DgC6QnstQ kXDdFkWUUix6iVg7s6IRGYBGs5iUKeqqWNAG6idCgtxl+KyMVLsQpyGE0oDXg5aNzn8HfZ 6/m5C3Hp+Vau+UxGUbyWuJ2mkSjYWMg=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPSA id <Tt=MTgBaK55F@rufus.isode.com>; Wed, 7 Dec 2011 20:27:59 +0000
Message-ID: <4EDFCC55.6000000@isode.com>
Date: Wed, 07 Dec 2011 20:28:06 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
To: Barry Leiba <barryleiba@computer.org>
References: <CALaySJLZaQH0Pcys561UhU6jTdEnqpAFrnMcY6oeV1SpPD-aRg@mail.gmail.com>
In-Reply-To: <CALaySJLZaQH0Pcys561UhU6jTdEnqpAFrnMcY6oeV1SpPD-aRg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: ima@ietf.org
Subject: Re: [EAI] UTF=x IMAP capabilities
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Dec 2011 20:28:02 -0000
Hi Barry, On 15/11/2011 13:13, Barry Leiba wrote: [...] > That leaves UTF8=ONLY, which is reasonable to leave. And so we have > three cases: > > 1. No EAI support (no UTF8=x capabilities listed). > > 2. EAI support, but also support of non-UTF8 versions (UTF8=ACCEPT). > > 3. EAI support, and it's all there is (UTF8=ONLY). > > So I suggest that we just spell it out that way, and make UTF8=ACCEPT > and UTF8=ONLY 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.
- [EAI] UTF=x IMAP capabilities Barry Leiba
- Re: [EAI] UTF=x IMAP capabilities Joseph Yee
- Re: [EAI] UTF=x IMAP capabilities Alexey Melnikov
- Re: [EAI] UTF=x IMAP capabilities Tony Hansen
- Re: [EAI] UTF=x IMAP capabilities Alexey Melnikov
- Re: [EAI] UTF=x IMAP capabilities Joseph Yee