From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from albireo.enyo.de (albireo.enyo.de [37.24.231.21]) by sourceware.org (Postfix) with ESMTPS id 03E8C3858D38 for ; Thu, 20 Aug 2020 08:03:31 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 03E8C3858D38 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=deneb.enyo.de Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=fw@deneb.enyo.de Received: from [172.17.203.2] (helo=deneb.enyo.de) by albireo.enyo.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1k8fXl-0004IC-TS; Thu, 20 Aug 2020 08:03:29 +0000 Received: from fw by deneb.enyo.de with local (Exim 4.92) (envelope-from ) id 1k8fXl-0002Jq-Qa; Thu, 20 Aug 2020 10:03:29 +0200 From: Florian Weimer To: Max Gautier via Libc-alpha Cc: Max Gautier Subject: Re: [PATCH 0/5] iconv: module for MODIFIED-UTF-7 References: <20200819230702.229822-1-mg@max.gautier.name> Date: Thu, 20 Aug 2020 10:03:29 +0200 In-Reply-To: <20200819230702.229822-1-mg@max.gautier.name> (Max Gautier via Libc-alpha's message of "Thu, 20 Aug 2020 01:06:57 +0200") Message-ID: <87y2m9agmm.fsf@mid.deneb.enyo.de> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Status: No, score=-6.2 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_NUMSUBJECT, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Aug 2020 08:03:32 -0000 * Max Gautier via Libc-alpha: > I am unaware of an official name for the encoding, so I used > "MODIFIED-UTF-7". There might be better choices, if someone has insights > on that. Let's try to get it added to the IANA registry? It's odd that a charset defined in an RFC is not already contained in it. The contact information for the registry seems to have atrophied a bit. I will try to figure out the current process. Historically, it's been Expert Review, so we shouldn't have to write an RFC for this.