[I18ndir] Time to revise RFC 2978 (charset registrations)?

John C Klensin <john-ietf@jck.com> Tue, 25 August 2020 12:06 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: i18ndir@ietfa.amsl.com
Delivered-To: i18ndir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E4C73A0C8B for <i18ndir@ietfa.amsl.com>; Tue, 25 Aug 2020 05:06:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.003
X-Spam-Level:
X-Spam-Status: No, score=0.003 tagged_above=-999 required=5 tests=[SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 55Ngk2nWjeOX for <i18ndir@ietfa.amsl.com>; Tue, 25 Aug 2020 05:06:02 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B78343A0C8F for <i18ndir@ietf.org>; Tue, 25 Aug 2020 05:06:02 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1kAXiD-000Gab-FD for i18ndir@ietf.org; Tue, 25 Aug 2020 08:06:01 -0400
Date: Tue, 25 Aug 2020 08:05:56 -0400
From: John C Klensin <john-ietf@jck.com>
To: i18ndir@ietf.org
Message-ID: <60280974B9488C6271DDB2D4@PSB>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18ndir/aFieVe7afL1cjMdMmbllmQIqmXI>
Subject: [I18ndir] Time to revise RFC 2978 (charset registrations)?
X-BeenThere: i18ndir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Internationalization Directorate <i18ndir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i18ndir/>
List-Post: <mailto:i18ndir@ietf.org>
List-Help: <mailto:i18ndir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Aug 2020 12:06:04 -0000

On the optimistic, but perhaps deluded, theory that this
directorate is still functional, perhaps we have some advice for
the ADs about what to do about this erratum and whether it is
time to revise RFC 2978 as suggested below?

See 
https://mailarchive.ietf.org/arch/msg/ietf/zYYu3xItvyCPak6dppZVIRK22PQ
and the message to which it replies,
https://mailarchive.ietf.org/arch/msg/ietf/WzwZ2fK9YqzmcKgmblmkLixOfqA
for context.

And, yes, I'll volunteer to work with Ned and Martin to get this
done (and to draft the relevant paragraph about using Unicode
(or appropriate it from elsewhere) if the conclusion is that it
would be helpful.

    john


---------- Forwarded Message ----------
Date: Tuesday, August 25, 2020 04:50 -0700
From: RFC Errata System <rfc-editor@rfc-editor.org>
To: ned.freed@innosoft.com, iesg@ietf.org
Cc: john-ietf@jck.com, rfc-editor@rfc-editor.org
Subject: [Technical Errata Reported] RFC2978 (6265)

The following errata report has been submitted for RFC2978,
"IANA Charset Registration Procedures".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6265

--------------------------------------
Type: Technical
Reported by: John Klensin <john-ietf@jck.com>

Section: 3.1

Original Text
-------------
Proposed charsets are not formally registered and must not be
used; the "x-" prefix specified in RFC 2045 can be used until
registration is complete.

Corrected Text
--------------
Proposed charsets are not formally registered and must not be
used.

Notes
-----
This section contains a recommendation for temporary use of
charset names with an "X-" prefix.  Given the problems those
have caused and the general prohibition in RFC 6648, probably
that provision should be considered updated and removed by 6648.
Given that the review period is only two weeks, it would seem
that there is little reason for for having proposed charsets
floating around anyway.

Comment: Despite Alexey's 2018 comment on erratum 5433, perhaps
it is time to create a revised document, not only to incorporate
the syntax corrections of prior errata and to get rid of the
"X-" advice, but to put in some text that actively discourages
new registrations and uses of charsets that are not based on
Unicode.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary,
please use "Reply All" to discuss whether it should be verified
or rejected. When a decision is reached, the verifying party  
can log in to change the status and edit the report, if
necessary. 

--------------------------------------
RFC2978 (draft-freed-charset-regist-03)
--------------------------------------
Title               : IANA Charset Registration Procedures
Publication Date    : October 2000
Author(s)           : N. Freed, J. Postel
Category            : BEST CURRENT PRACTICE
Source              : Legacy
Area                : Legacy
Stream              : IETF
Verifying Party     : IESG

---------- End Forwarded Message ----------