Re: [Extra] IMAP4rev2, SEARCH CHARSET

Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Thu, 07 November 2019 10:49 UTC

Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: extra@ietfa.amsl.com
Delivered-To: extra@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94F051200B2 for <extra@ietfa.amsl.com>; Thu, 7 Nov 2019 02:49:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gulbrandsen.priv.no
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 GB3S4EPzWLch for <extra@ietfa.amsl.com>; Thu, 7 Nov 2019 02:49:04 -0800 (PST)
Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [IPv6:2a01:4f8:191:91a8::3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20E7B120073 for <extra@ietf.org>; Thu, 7 Nov 2019 02:49:04 -0800 (PST)
Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [IPv6:2a01:4f8:191:91a8::3]) by stabil.gulbrandsen.priv.no (Postfix) with ESMTP id 5E471C001E; Thu, 7 Nov 2019 10:52:47 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1573123967; bh=1jzVaXsBXOOyfVkEtNEobQ2JX4NyaqVq6n2zy7jAJiY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=aEY2W1ovV3CJ4Uw7KD1NkI4dv+jDDxRPYHZWQX1DLpq3OT3OQxS+I/vmSQzHMsKdO j5Csl8gyHeSMQq676v6qCheZCm8yaaK/dRHEsW9RXcZ7n8WLvETX/hn8n1i+lLiwwi /Ix10ChhC5OsdIRF8OvnjxU8zVuyMvBhSFvd7BAc=
Received: from arnt@gulbrandsen.priv.no by stabil.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1573123966-28749-28747/9/4; Thu, 7 Nov 2019 10:52:46 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: extra@ietf.org
Date: Thu, 7 Nov 2019 11:49:00 +0100
Mime-Version: 1.0
Message-Id: <2b7ebdb2-7895-432f-8da9-8c6b95e315fb@gulbrandsen.priv.no>
In-Reply-To: <eb04c57f-682c-430c-b644-458fb704c48d@gulbrandsen.priv.no>
References: <eb04c57f-682c-430c-b644-458fb704c48d@gulbrandsen.priv.no>
User-Agent: Trojita/0.7; Qt/5.7.1; xcb; Linux; Devuan GNU/Linux 2.1 (ascii)
Content-Type: text/plain; charset=utf-8; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/DCwTg6YVzxbkZzWqS_FdxNlpDF0>
Subject: Re: [Extra] IMAP4rev2, SEARCH CHARSET
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Email mailstore and eXtensions To Revise or Amend <extra.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/extra>, <mailto:extra-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/extra/>
List-Post: <mailto:extra@ietf.org>
List-Help: <mailto:extra-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/extra>, <mailto:extra-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Nov 2019 10:49:05 -0000

I wrote:
> My question is: Obsolete CHARSET and say clients MUST NOT use 
> it, or obsolete it and say that servers MUST support CHARSET 
> UTF-8 and MAY support others?

I had a coffee. My own preference is the latter.

"Servers MUST support CHARSET UTF-8 and MAY support other encodings. 
Clients SHOULD NOT use other encodings. Note that UTF-8 is also the 
default, so selecting CHARSET UTF-8 is redundant. It is permitted for 
improved compatibility with existing IMAP4rev1 clients".

Arnt