IETF Logo Mail Archive

Re: [EAI] Comments on draft-ietf-eai-imap-utf8-07

Alexey Melnikov <alexey.melnikov@isode.com> Mon, 21 September 2009 19:11 UTC

Return-Path: <lunohod.baikonur@googlemail.com>
X-Original-To: ima@core3.amsl.com
Delivered-To: ima@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3EC1F3A6AD7 for <ima@core3.amsl.com>; Mon, 21 Sep 2009 12:11:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 N7YD8ti40leK for <ima@core3.amsl.com>; Mon, 21 Sep 2009 12:11:46 -0700 (PDT)
Received: from mail-ew0-f228.google.com (mail-ew0-f228.google.com [209.85.219.228]) by core3.amsl.com (Postfix) with ESMTP id 1F9AA3A69B7 for <ima@ietf.org>; Mon, 21 Sep 2009 12:11:39 -0700 (PDT)
Received: by ewy28 with SMTP id 28so423376ewy.42 for <ima@ietf.org>; Mon, 21 Sep 2009 12:12:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=Ni8VBt291lKxaeprwB13qzZfvl5O574WOAwGjctt+Ig=; b=ajug81OJgEeHl2qsRUl7CTuN2767qvvZ+6I4JOPrqp7RdKtzYBAjwMHNJKmkWEA0Ws XMzPKayenh+8uijZA6/7hjHxIYQsfItyeyCGKKHn2vbFC/1YlqnRJofFilU/qRQAkuLW TFSF6xjQuy1x89k349B3Lo3uzCEUBovHL6/QI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=YvPa6ZYr2/HV4QjtPPXhPLP/bJRijbH5jwfKGHZ5VoRJKeTKRIbuTxtc8VnqlTALJf Sj/ZLGCgKxnpijIfScnAtDw9bVtXzBbCo0TdnbfDJ6Y7eCmg1ZTh/YVfw4D+VyV1bJQK oDjw5btFxgWtcE5/mxFbwsjb0BJ9FFhJSvS2I=
MIME-Version: 1.0
Sender: lunohod.baikonur@googlemail.com
Received: by 10.210.96.21 with SMTP id t21mr3351776ebb.4.1253560355642; Mon, 21 Sep 2009 12:12:35 -0700 (PDT)
In-Reply-To: <6c9fcc2a0909201409n472d85f1xe87526b6f86ac9c9@mail.gmail.com>
References: <6.2.5.6.2.20090830222724.034fdb30@elandnews.com> <4A9D9878.7010302@isode.com> <p06250105c6c5c5428ce9@172.16.1.8> <6c9fcc2a0909031518v3e826ff2je1b622a6acfdd59a@mail.gmail.com> <4AA96B90.7070007@isode.com> <6c9fcc2a0909101550i13d01c93tca7be5bccbf1c0b6@mail.gmail.com> <4AAA20BD.1060904@isode.com> <C814D069-77BE-4C2A-ACFE-5A5F87A20558@ca.afilias.info> <4AB67A8C.2090202@alvestrand.no> <6c9fcc2a0909201409n472d85f1xe87526b6f86ac9c9@mail.gmail.com>
Date: Mon, 21 Sep 2009 23:12:35 +0400
X-Google-Sender-Auth: 16e855feece2126d
Message-ID: <29d3c4cb0909211212s7014fcc0mf6c153ee6bc685f1@mail.gmail.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
To: barryleiba@computer.org
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: Pete Resnick <presnick@qualcomm.com>, EAI WG <ima@ietf.org>
Subject: Re: [EAI] Comments on draft-ietf-eai-imap-utf8-07
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 21 Sep 2009 19:11:47 -0000

On Mon, Sep 21, 2009 at 1:09 AM, Barry Leiba
<barryleiba.mailing.lists@gmail.com> wrote:
>> My sense of the WG is that the WG doesn't feel that being creative in how
>> IMAP options are specified is something this WG wants.
>
> Hm.  I don't read that at all, from the few responses we have.  That
> said, I'm happy to accommodate:
> I propose that we take my previous note, with all the changes
> suggested in it, but we modify the way the capabilities are specified.
>  Instead of "UTF8=x,y,z", we have "UTF8=x UTF8=y UTF8=z".  In
> particular, that means that there is no "UTF8" capability, and that is
> instead called "UTF8=ACCEPT".
>
> That should satisfy me, John, and Dave, as well as making Alexey and
> Joseph feel better.
>
> Is that cool?

Works for me.

v2.23.0 | Report a Bug | By Email