Re: [Gen-art] [EAI] Gen-ART review of draft-ietf-eai-imap-utf8-07

<Black_David@emc.com> Tue, 08 September 2009 02:18 UTC

Return-Path: <Black_David@emc.com>
X-Original-To: gen-art@core3.amsl.com
Delivered-To: gen-art@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2E3173A68FF; Mon, 7 Sep 2009 19:18:51 -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 1fCaSyYZNbXv; Mon, 7 Sep 2009 19:18:50 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by core3.amsl.com (Postfix) with ESMTP id 5C3EE3A6778; Mon, 7 Sep 2009 19:18:50 -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.3.2/Switch-3.1.7) with ESMTP id n882JIll024042 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Sep 2009 22:19:18 -0400
Received: from mailhub.lss.emc.com (nagas.lss.emc.com [10.254.144.15]) by hop04-l1d11-si01.isus.emc.com (Tablus Interceptor); Mon, 7 Sep 2009 22:19:10 -0400
Received: from corpussmtp2.corp.emc.com (corpussmtp2.corp.emc.com [128.221.166.45]) by mailhub.lss.emc.com (Switch-3.3.2mp/Switch-3.3.2mp) with ESMTP id n882J9pa014377; Mon, 7 Sep 2009 22:19:10 -0400
Received: from CORPUSMX80A.corp.emc.com ([10.254.89.202]) by corpussmtp2.corp.emc.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 7 Sep 2009 22:19:09 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 07 Sep 2009 22:19:08 -0400
Message-ID: <9FA859626025B64FBC2AF149D97C944A03B1C902@CORPUSMX80A.corp.emc.com>
In-Reply-To: <4AA4D99F.5060802@isode.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Gen-art] [EAI] Gen-ART review of draft-ietf-eai-imap-utf8-07
Thread-Index: AcovohPEwoHXyMtFR2+k1JL62Q5L6AAiAVIg
References: <9FA859626025B64FBC2AF149D97C944A03A3059B@CORPUSMX80A.corp.emc.com><4A9D93D7.8010709@isode.com><9FA859626025B64FBC2AF149D97C944A03B1C08E@CORPUSMX80A.corp.emc.com><4AA3E259.5060804@isode.com> <4AA3FA5A.8030000@alvestrand.no><379713518D25EEBB9E890E6B@[192.168.1.110]> <4AA4D99F.5060802@isode.com>
From: Black_David@emc.com
To: alexey.melnikov@isode.com, klensin@jck.com
X-OriginalArrivalTime: 08 Sep 2009 02:19:09.0494 (UTC) FILETIME=[BF9C6D60:01CA302A]
X-EMM-EM: Active
Cc: presnick@qualcomm.com, gen-art@ietf.org, ima@ietf.org, Black_David@emc.com
Subject: Re: [Gen-art] [EAI] Gen-ART review of draft-ietf-eai-imap-utf8-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Sep 2009 02:18:51 -0000

> John C Klensin wrote:
> 
> > --On Sunday, September 06, 2009 8:07 PM +0200 Harald Tveit 
> Alvestrand 
> > <harald@alvestrand.no> wrote:
> >
> >> It makes quite a lot of sense to me that if an IMAP server
> >> supports a specific charset in some other context (such as
> >> IMAP SEARCH and friends), it should be consistent about
> >> supporting the same charset in UTF8 too.
> >>
> >> Inconsistency here would be unreasonable for the user - and by
> >> pointing to that, we have "reduced to a previously unsolved
> >> problem".
> >>
> >> Suggested language:
> >>
> >> If the server supports other charsets in IMAP SEARCH or IMAP
> >> CONVERT (add references to taste), it SHOULD also support
> >> those charsets in this conversion.
> >
> > Wfm
> 
> Ok, I've added this as an RFC Editor note.

Also works for me.  Thanks for working through the details,
--David