Re: [EAI] Comments on draft-ietf-eai-imap-utf8-07
Joseph Yee <joseph.yee@gmail.com> Thu, 10 September 2009 21:30 UTC
Return-Path: <joseph.yee@gmail.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 B941A28C0DB for <ima@core3.amsl.com>; Thu, 10 Sep 2009 14:30:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 yPhhAFZw0pEk for <ima@core3.amsl.com>; Thu, 10 Sep 2009 14:30:40 -0700 (PDT)
Received: from mail-bw0-f219.google.com (mail-bw0-f219.google.com [209.85.218.219]) by core3.amsl.com (Postfix) with ESMTP id 32B873A67AA for <ima@ietf.org>; Thu, 10 Sep 2009 14:30:39 -0700 (PDT)
Received: by bwz19 with SMTP id 19so417197bwz.37 for <ima@ietf.org>; Thu, 10 Sep 2009 14:31:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:in-reply-to:x-mailer :subject:references:message-id:content-type :content-transfer-encoding:mime-version:date:cc; bh=g3vUquRLbcMVitL/vU5jvHSk2aiXEgj2kESdyqIZgNY=; b=Gnt4LoXUQxY/xQaDKTWXa6eq7KG8XX/r8p03CAykrxYJBKfk0lE2KJM88BxK078E6Y bmqE0oOUeqAgeSWzaUQGMNE83jb1E31qC22qTUhHLCOlq5r2BMw0AXaZfFuvqvShZQKB r/i8dbfGRkc13jEAMsfR3Zus9tzvsCGvwAulw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:in-reply-to:x-mailer:subject:references:message-id :content-type:content-transfer-encoding:mime-version:date:cc; b=rMqBbXQgT7rDs5BiE9ybili4ykjLynHevuWnpcyY+7N1Sw0pitV4C3biBT+EYwDvHN COLd4P6CPTz8u6Hbv07P7+nezb/bZYdGCEpwN6KqlLMn9BklI3ll9FP3f3lE3ARbvI1m Evjo1+ta0Giv11L6+iqQlNT7XnKYj39AbK7PI=
Received: by 10.204.32.204 with SMTP id e12mr1352800bkd.51.1252618272196; Thu, 10 Sep 2009 14:31:12 -0700 (PDT)
Received: from ?10.127.8.37? ([24.114.234.28]) by mx.google.com with ESMTPS id 19sm3500810fkr.43.2009.09.10.14.31.08 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 10 Sep 2009 14:31:11 -0700 (PDT)
From: Joseph Yee <joseph.yee@gmail.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
In-Reply-To: <4AA96B90.7070007@isode.com>
X-Mailer: iPhone Mail (7A400)
References: <6.2.5.6.2.20090830222724.034fdb30@elandnews.com> <6c9fcc2a0909010725m9f1a4c2x159fb13d05df5f91@mail.gmail.com> <4A9D9878.7010302@isode.com> <p06250105c6c5c5428ce9@172.16.1.8> <6c9fcc2a0909031518v3e826ff2je1b622a6acfdd59a@mail.gmail.com> <4AA96B90.7070007@isode.com>
Message-Id: <D461D9E1-9EB5-4756-97E1-4B8911583AB6@gmail.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (iPhone Mail 7A400)
Date: Thu, 10 Sep 2009 17:30:51 -0400
Cc: Pete Resnick <presnick@qualcomm.com>, "barryleiba@computer.org" <barryleiba@computer.org>, 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: Thu, 10 Sep 2009 21:30:41 -0000
Inline On 2009-09-10, at 5:11 PM, Alexey Melnikov <alexey.melnikov@isode.com> wrote: > Barry Leiba wrote: > >> Hi, Pete. >> > Hi Barry, > >>>> OLD >>>> The UTF8=ONLY capability implies the UTF8 base capability, the >>>> UTF8=ALL capability and the UTF8=APPEND capability. A server which >>>> advertises UTF8=ONLY need not advertise the three implicit >>>> capabilities. >>>> >>>> Oy. This makes parsing the capability string complicated, and >>>> should >>>> be earlier in the document. It'd be good to make this clear at the >>>> beginning, when the UTF8 capability is first mentioned. >>> I'm not sure what you want here. Something in the "UTF8" section >>> that says, >>> "See below"? Left as is for now. Fix in an RFC Editor Note if need >>> be. >> When one starts reading the document, one gets to this: >> >> --------------------------------------------- >> 3. UTF8 IMAP Capability >> >> The basic "UTF8" capability indicates the server supports UTF-8 >> quoted strings, the "UTF8" parameter to SELECT and EXAMINE, and >> UTF-8 >> responses from the LIST and LSUB commands. >> --------------------------------------------- >> >> It's only later, when one gets to section 7, which I quote above, >> that >> one finds that it's not sufficient to look for "UTF8": one also has >> to >> look for "UTF8=ONLY". And we don't say that UTF8=ALL, UTF8=APPEND, >> or >> UTF8=USER imply the base UTF8. So if UTF8=ONLY is special, I think >> we >> need to say that right up there at the start of section 3, so it's >> clear. Or else we say that the presence of *any* "UTF8=" capability >> implies the base UTF8, and say *that* in section 3, so it's clear >> right up front as to what capability string(s) need to be checked >> for. >> >> D'you see what I'm getting at? >> > (As the responsible AD) After rereading various pieces of the > document, I agree this is not clear. > > > (As a WG participant) Here is my understanding how things should work: > > UTF8=USER is useful by itself, so I think it should be independent > of all other UTF8* capabilities. For example it should be possible > to only support UTF8=USER (non EAI IMAP server, but which accepts > UTF-8 usernames/passwords), or support all other EAI functions, > without supporting UTF-8 username/password (e.g. a legacy > authentication database). I agree with the second part and that's my understanding of the doc. Not sure of the first part. Allowing UTF8 login/password but not UTF8- IMAP capable? I don't think we need special capa for it, it can be done today... > > I think UTF8=APPEND should be independent of other UTF8* > capabilities. Allowing for EAI APPEND might require quite a bit of > extra work. I personally think it can imply UTF8 but not any other UTF8-*. Not sure if you mean the same from UTF8* > > Both UTF8=ALL and UTF8=ONLY are related to UTF8 capability. We can > either define them as implying UTF8, or say that if one of them is > advertised, then UTF8 MUST also be advertised. Moreover, I think > UTF8=ONLY implies UTF8=ALL. > One can also argue that UTF8=ONLY implies UTF8=APPEND. I would be Ok > either way, but one way or another this needs to be stated explicitly. Section 7 of the doc makes it clear that UTF8-ONLY implies both ALL and APPEND. I have not fully read -08 yet, is it not there anymore? Thanks Joseph > > Comments? > > _______________________________________________ > IMA mailing list > IMA@ietf.org > https://www.ietf.org/mailman/listinfo/ima
- [EAI] Comments on draft-ietf-eai-imap-utf8-07 SM
- Re: [EAI] Comments on draft-ietf-eai-imap-utf8-07 Barry Leiba
- Re: [EAI] Comments on draft-ietf-eai-imap-utf8-07 Alexey Melnikov
- Re: [EAI] Comments on draft-ietf-eai-imap-utf8-07 Alexey Melnikov
- Re: [EAI] Comments on draft-ietf-eai-imap-utf8-07 Pete Resnick
- Re: [EAI] Comments on draft-ietf-eai-imap-utf8-07 Pete Resnick
- Re: [EAI] Comments on draft-ietf-eai-imap-utf8-07 Barry Leiba
- Re: [EAI] Comments on draft-ietf-eai-imap-utf8-07 Joseph Yee
- Re: [EAI] Comments on draft-ietf-eai-imap-utf8-07 Alexey Melnikov
- Re: [EAI] Comments on draft-ietf-eai-imap-utf8-07 Alexey Melnikov
- Re: [EAI] Comments on draft-ietf-eai-imap-utf8-07 Joseph Yee
- Re: [EAI] Comments on draft-ietf-eai-imap-utf8-07 Joseph Yee
- Re: [EAI] Comments on draft-ietf-eai-imap-utf8-07 Alexey Melnikov
- Re: [EAI] Comments on draft-ietf-eai-imap-utf8-07 Barry Leiba
- Re: [EAI] Comments on draft-ietf-eai-imap-utf8-07 John C Klensin
- Re: [EAI] Comments on draft-ietf-eai-imap-utf8-07 Alexey Melnikov
- [EAI] [Fwd: Re: [Fwd: Re: Comments on draft-ietf-… Alexey Melnikov
- Re: [EAI] Comments on draft-ietf-eai-imap-utf8-07 Joseph Yee
- Re: [EAI] Comments on draft-ietf-eai-imap-utf8-07 Harald Alvestrand
- Re: [EAI] Comments on draft-ietf-eai-imap-utf8-07 Barry Leiba
- Re: [EAI] Comments on draft-ietf-eai-imap-utf8-07 Pete Resnick
- Re: [EAI] Comments on draft-ietf-eai-imap-utf8-07 Joseph Yee
- Re: [EAI] Comments on draft-ietf-eai-imap-utf8-07 Alexey Melnikov
- Re: [EAI] Comments on draft-ietf-eai-imap-utf8-07 Harald Alvestrand