Status of RFC 20 (was: Re: Gen-ART and OPS-Dir review of draft-ietf-json-text-sequence-09)

John C Klensin <john-ietf@jck.com> Sat, 06 December 2014 03:52 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D3E01A8AA3 for <ietf@ietfa.amsl.com>; Fri, 5 Dec 2014 19:52:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level:
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] 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 EwZqVpH0dOQf for <ietf@ietfa.amsl.com>; Fri, 5 Dec 2014 19:52:03 -0800 (PST)
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 8E9BE1A8824 for <ietf@ietf.org>; Fri, 5 Dec 2014 19:52:03 -0800 (PST)
Received: from h8.int.jck.com ([198.252.137.35] helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Xx6PR-0000fF-ID; Fri, 05 Dec 2014 22:51:53 -0500
Date: Fri, 05 Dec 2014 22:51:48 -0500
From: John C Klensin <john-ietf@jck.com>
To: Barry Leiba <barryleiba@computer.org>, "Black, David" <david.black@emc.com>
Subject: Status of RFC 20 (was: Re: Gen-ART and OPS-Dir review of draft-ietf-json-text-sequence-09)
Message-ID: <BB4CB3D8CA03EB4A03FEA99B@JcK-HP8200.jck.com>
In-Reply-To: <CAC4RtVA10gUzmug4+H5SW2JL4Q7-Yh_ntiqPTswYSUUgXMoczA@mail.gmail.com>
References: <CE03DB3D7B45C245BCA0D24327794936289DC7@MX104CL02.corp.emc.com> <CAC4RtVA10gUzmug4+H5SW2JL4Q7-Yh_ntiqPTswYSUUgXMoczA@mail.gmail.c om>
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.35
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/0STzv1XzMA57o94pbJtBiRvSgHU
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Dec 2014 03:52:05 -0000

Barry (and IESG generally),

This has come up multiple times and will undoubtedly keep coming
up, especially since RFC 20 is a stable reference to one
particular version of ASCII and actually includes the code
tables while X3.4-1968 (the version to which it refers) is
largely unobtainable today (only the current version is) and
ANSI X3.4, aka ANSI/INCITS 4, is not a stable reference without
a date.

Most, perhaps all, versions of ANSI X3.4 (and ANSI/INCITS 4)
also specify the repertoire and coding, i.e., the CCS, but not
what we would call the encoding form today (in the case of RFC
20, the familiar "seven bits in and eight bit byte with high
order bit always zero").  So, for most IETF purposes, RFC 20
really should be the normative reference for ASCII (or, if one
prefers, "US-ASCII").

RFC 20 has status "Unknown" only because it comes from a time
that predates both the IETF and our use of the term "standard"
(with or without qualifications) to describe Internet technical
specifications.

So, rather than go through a discussion about downrefs and the
like every time RFC 20 is referenced from a Standards-Track
specification, I suggest that the IESG reclassify it to Internet
Standard and waste as little more time doing so as possible.  

The implementation report is that, whether they explicitly
reference RFC 20 or not, substantially every application-layer
protocol we have depends on the ASCII CCS and encoding form
specified in that RFC.  In addition, RFC 5234 and its
predecessors are heavily dependent on ASCII so that
substantially any specification that depends on ABNF is also an
ASCII implementation.

Thanks,
    john


--On Friday, December 05, 2014 17:38 -0500 Barry Leiba
<barryleiba@computer.org> wrote:

> Hi, David.  One note on your review:
> 
>> idnits didn't like the reference to RFC 20 for ASCII:
>> 
>>   ** Downref: Normative reference to an Unknown state RFC:
>>   RFC   20
>> 
>> RFC 5234 (ABNF) uses this, which looks like a better
>> reference:
>> 
>>    [US-ASCII]  American National Standards Institute, "Coded
>>    Character Set -- 7-bit American Standard Code for
>>                Information Interchange", ANSI X3.4, 1986.
> 
> Except that (1) many IETF documents do use RFC 20 and (2) the
> RFC 20 reference is not for ASCII: it's for RS, the Record
> Separator character, which is explained in RFC 20, Section 5.2.
> 
> Barry
>