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

John C Klensin <john-ietf@jck.com> Tue, 25 August 2020 20:29 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 4820C3A0B92 for <i18ndir@ietfa.amsl.com>; Tue, 25 Aug 2020 13:29:02 -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 dmZDK0W64Uyh for <i18ndir@ietfa.amsl.com>; Tue, 25 Aug 2020 13:29:01 -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 347963A0B8B for <i18ndir@ietf.org>; Tue, 25 Aug 2020 13:29:01 -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 1kAfYx-000I6C-Tt; Tue, 25 Aug 2020 16:28:59 -0400
Date: Tue, 25 Aug 2020 16:28:54 -0400
From: John C Klensin <john-ietf@jck.com>
To: John Levine <johnl@taugh.com>
cc: i18ndir@ietf.org
Message-ID: <8C3C0F6B216BE165400AFDE9@PSB>
In-Reply-To: <20200825194136.788031F27A23@ary.qy>
References: <20200825194136.788031F27A23@ary.qy>
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/u4SmMiQTY4oh-CXmCyuBN1ZT3B0>
Subject: Re: [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 20:29:02 -0000


--On Tuesday, August 25, 2020 15:41 -0400 John Levine
<johnl@taugh.com> wrote:

> In article <60280974B9488C6271DDB2D4@PSB> you write:
>> 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?
> 
> You'd hope this would be pretty easy, wouldn't it.  Might be
> nice to update this part, too:
> 
>    Charset registrations will be posted in the anonymous FTP
> file
> "ftp://ftp.isi.edu/in-notes/iana/assignments/character-sets"
> and all

Yep.  I didn't do a careful reading, partially because that felt
like step 3 as in

(1) Check here (and with Ned and, if he is not reading this,
Martin) and see if there are any reasons to not do so and if
there would be AD support for an AD-sponsored document with
minimum fuss.  That includes being sure that, if Alexey had some
reason for his "unlikely to be revised" statement that we
haven't considered, we know about it and can consider it.

(2) Probably also from this list, figure out whether a draft new
version would have sufficient reviewers who understand the
subject matter to make submission of such a revision draft
plausible.  If there are competent and willing reviewers around
W3C (use in media types) or other parts of the MIME community,
so much the better.  And see if Ned or the RFC Editor have the
XML of RFC 2978 or at least draft-freed-charset-regist-03 around.

(3) If there are positive answers at the first two steps, go
through the RFC carefully, fold in the errata, and clean out
obsolete statements (I have no idea if the "X-" issue is the
only one because I didn't look), dead references (such as the
one above), and similar things.  

Of the three, I think the third is actually the easiest.  On the
other hand, without having clear agreement about the
desirability of doing this and AD willingness to push it
through, I believe it would be a waste of time.

> Also willing to help smith what I'd hope would be a limited
> number of words.

Ack.  And thanks.

    john