[EAI] [Errata Verified] RFC6855 (4029)

RFC Errata System <rfc-editor@rfc-editor.org> Tue, 23 February 2016 23:49 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 985821B375C; Tue, 23 Feb 2016 15:49:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.908
X-Spam-Level:
X-Spam-Status: No, score=-101.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.006, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gBkbEbIrPkx5; Tue, 23 Feb 2016 15:49:48 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5E9A1B3736; Tue, 23 Feb 2016 15:49:48 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 1BD44180005; Tue, 23 Feb 2016 15:49:16 -0800 (PST)
To: chris.newman@oracle.com, presnick@qti.qualcomm.com, chris.newman@oracle.com, shenshuo@cnnic.cn
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20160223234916.1BD44180005@rfc-editor.org>
Date: Tue, 23 Feb 2016 15:49:16 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ima/NXWV-Fl3t4XLE-KT3kLnXuGjWNU>
Cc: rfc-editor@rfc-editor.org, barryleiba@computer.org, iesg@ietf.org, ima@ietf.org
Subject: [EAI] [Errata Verified] RFC6855 (4029)
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 23 Feb 2016 23:49:50 -0000

The following errata report has been verified for RFC6855,
"IMAP Support for UTF-8". 

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6855&eid=4029

--------------------------------------
Status: Verified
Type: Technical

Reported by: Chris Newman <chris.newman@oracle.com>
Date Reported: 2014-06-27
Verified by: Barry Leiba (IESG)

Section: 3

Original Text
-------------
   Once an IMAP client has enabled UTF-8 support with the "ENABLE
   UTF8=ACCEPT" command, it MUST NOT issue a "SEARCH" command that
   contains a charset specification.  If an IMAP server receives such a
   "SEARCH" command in that situation, it SHOULD reject the command with
   a "BAD" response (due to the conflicting charset labels).


Corrected Text
--------------
   Once an IMAP client has enabled UTF-8 support with the "ENABLE
   UTF8=ACCEPT" command, it MUST NOT issue a "SEARCH" command that
   contains a charset specification. If an IMAP server receives such a
   "SEARCH" command in that situation, it SHOULD reject the command with
   a "BAD" response (due to the conflicting charset labels). This also
   applies to any IMAP command or extension that includes an optional
   charset label and associated strings in the command arguments,
   including the MULTISEARCH extension. For commands with a mandatory
   charset field, such as SORT and THREAD, servers SHOULD reject charset
   values other than UTF-8 with a “BAD” response (due to the conflicting
   charset labels).

Notes
-----
This is a straightforward extrapolation of the existing text, but a literal reading of the existing text is silent about how to deal with this situation.

--------------------------------------
RFC6855 (draft-ietf-eai-5738bis-12)
--------------------------------------
Title               : IMAP Support for UTF-8
Publication Date    : March 2013
Author(s)           : P. Resnick, Ed., C. Newman, Ed., S. Shen, Ed.
Category            : PROPOSED STANDARD
Source              : Email Address Internationalization
Area                : Applications
Stream              : IETF
Verifying Party     : IESG