[apps-discuss] AppsDir review of draft-ietf-eai-5738bis-03
Aaron Stone <aaron@serendipity.cx> Mon, 14 May 2012 13:37 UTC
Return-Path: <aaron@serendipity.cx>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7F3021F8541 for <apps-discuss@ietfa.amsl.com>; Mon, 14 May 2012 06:37:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.643
X-Spam-Level:
X-Spam-Status: No, score=-101.643 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, IP_NOT_FRIENDLY=0.334, 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 ytRjExydYTKV for <apps-discuss@ietfa.amsl.com>; Mon, 14 May 2012 06:37:47 -0700 (PDT)
Received: from slice.serendipity.cx (slice.serendipity.cx [67.23.2.90]) by ietfa.amsl.com (Postfix) with ESMTP id 7093621F8512 for <apps-discuss@ietf.org>; Mon, 14 May 2012 06:37:47 -0700 (PDT)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by slice.serendipity.cx (Postfix) with ESMTPSA id 7F1863017F for <apps-discuss@ietf.org>; Mon, 14 May 2012 06:37:02 -0700 (PDT)
Received: by wgbdr13 with SMTP id dr13so3376994wgb.13 for <apps-discuss@ietf.org>; Mon, 14 May 2012 06:37:39 -0700 (PDT)
Received: by 10.180.107.100 with SMTP id hb4mr6821497wib.22.1337002659306; Mon, 14 May 2012 06:37:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.204.9 with HTTP; Mon, 14 May 2012 06:37:19 -0700 (PDT)
From: Aaron Stone <aaron@serendipity.cx>
Date: Mon, 14 May 2012 06:37:19 -0700
Message-ID: <CAEdAYKUiduNgOv5yNsoWRADSBMYZticjXXz-8BqKW7Cd8tM-jg@mail.gmail.com>
To: apps-discuss@ietf.org, draft-ietf-eai-5738bis.all@tools.ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Subject: [apps-discuss] AppsDir review of draft-ietf-eai-5738bis-03
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 May 2012 13:37:48 -0000
I have been selected as the Applications Area Directorate reviewer for this draft (for background on appsdir, please see http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorate ). I apologize for the terrible tardiness of this review. Please resolve these comments along with any other Last Call comments you may receive. Please wait for direction from your document shepherd or AD before posting a new version of the draft. Document: draft-ietf-eai-5738bis-03 Title: IMAP Support for UTF-8 Reviewer: Aaron Stone Review Date: 5/13/2012 IETF Last Call Date: none found IESG Telechat Date: none scheduled Summary: This draft is ready for publication with only a few editorial nits. Major Issues: none Minor Issues: Section 3.2 (text that should be in 3.3, see below): The text first says that LIST without UTF8 will hide the UTF8 mailboxes, but then it says that LIST without UTF8 in the presensce of a UTF8 mailbox results in an error. Will this cause user anguish if one mailbox is upgraded to UTF-8 and now the portion of mailbox hierarchy that mailbox is in cannot be listed by non-UTF8-extension aware clients? Nits: - Section 3, last sentence: replace "imply" with "implies". - Section 3.1: What's the "appropriate internal format"? All IMAP servers that advertise the "UTF8=ACCEPT" capability SHOULD accept UTF-8 in mailbox names, and those that also support the "Mailbox International Naming Convention" described in RFC 3501, Section 5.1.3 MUST accept utf8-quoted mailbox names and convert them to the appropriate internal format. This looks like a nit, possible new last portion of text: ... MUST accept utf8-quoted mailbox names and convert them to the server's appropriate internal format as needed. - Section 3.2, second paragraph, "Servers MAY include mailboxes that can only be selected or examined..." This paragraph in the wrong section. It deals with LIST, LSUB, so I think it should be moved to 3.3. - Section 4: First sentence, the server may reject the command -- the server itself isn't failing. OLD A server that advertises "UTF8=ACCEPT" MAY fail for \NotUTF8 mailboxes with a NOT-UTF-8 response code. NEW A server that advertises "UTF8=ACCEPT" MAY fail an APPEND command for \NotUTF8 mailboxes with a NOT-UTF-8 response code. - Section 4: change "8-bit" to "8-bit character" in the last sentence. - Section 5: Expand the contraction doesn't => does not. - Section 5: Should this section state more obviously that the UTF8=USER stuff in 5738 is removed entirely? - Section 6: replace "internaltion mailbox name convention (modified UTF-7) with "Mailbox International Naming Convention" for consistency. - Section 9, Security Considerations: The first paragraph is left-over from 5738, should be removed entirely (LOGIN is no longer extended to UTF-8). Thank you, Aaron