IETF Logo Mail Archive

Re: [rfc-i] Example RFC numbers?

Carsten Bormann <cabo@tzi.org> Tue, 22 August 2023 12:31 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: rfc-interest@ietfa.amsl.com
Delivered-To: rfc-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 953ACC14CE4A for <rfc-interest@ietfa.amsl.com>; Tue, 22 Aug 2023 05:31:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Sg2aaO8DWL2 for <rfc-interest@ietfa.amsl.com>; Tue, 22 Aug 2023 05:31:33 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21008C14CF15 for <rfc-interest@rfc-editor.org>; Tue, 22 Aug 2023 05:31:31 -0700 (PDT)
Received: from [192.168.217.124] (p548dc15c.dip0.t-ipconnect.de [84.141.193.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4RVTH443gRzDChK; Tue, 22 Aug 2023 14:31:28 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <84f90c6b-b967-8bc2-ede8-f49c6304dc1a@gmail.com>
Date: Tue, 22 Aug 2023 14:31:28 +0200
Cc: Robert Sparks <rjsparks@nostrum.com>, Donald Eastlake <d3e3e3@gmail.com>, rfc-interest@rfc-editor.org
X-Mao-Original-Outgoing-Id: 714400288.2080311-702045fc394b514eea10e3fb0e3a860f
Content-Transfer-Encoding: quoted-printable
Message-Id: <2236F4D2-6A1A-4815-9012-41E3845E77F2@tzi.org>
References: <b0cba5ce-120f-c179-e1f2-8c0efae2612a@gmail.com> <409.1691333628@localhost> <dbeea75d-8f8b-5ddc-fefd-65b2bb116d21@gmail.com> <75980934-A6F1-4C2A-9F4E-4C0D8975CE40@vpnc.org> <85f95c42-5f6d-aef2-89ba-f38c59e2f1c0@it.aoyama.ac.jp> <F9ED87E5-C745-4F70-A1D7-6A8FBC1F7300@vpnc.org> <405e097f-8ad5-6096-35f4-f48c86fcef82@gmail.com> <ZNB8SoSkSB7COCYo@faui48e.informatik.uni-erlangen.de> <891E278E-C0A0-4F8A-8DFD-245BC3D1EAF5@tzi.org> <VI1PR07MB6704C7259871B1A2F87CF959C60CA@VI1PR07MB6704.eurprd07.prod.outlook.com> <62936f8e-4a26-10bc-4915-adc8129e8e4a@nthpermutation.com> <fbc53279-6949-e1a9-f977-9916564e9bfa@amsl.com> <CAF4+nEGXb3_Eq5eAn4xoAzjzKYX0K44P66X+P=1WYF6rvmBBNg@mail.gmail.com> <61BFB9FA-0B38-4ED2-B193-D176D6EB3C24@gmail.com> <acc1ee3d-987b-3061-2ee9-c7de4628836e@gmail.com> <3104599A-BCD6-47F1-A063-690ABB85D50E@gmail.com> <CAF4+nEF3g_zBFzdKXZGeU4MnE5NQUOmBEdMn+LwbqokQBaEGUw@mail.gmail.com> <26a71eda-6a09-b3a1-2912-2663d32bacb3@nostrum.com> <84f90c6b-b967-8bc2-ede8-f49c6304dc1a@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/Dy-Em9-iPdyR03wiMv-XTn3dxas>
Subject: Re: [rfc-i] Example RFC numbers?
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Aug 2023 12:31:37 -0000

On 2023-08-21, at 22:40, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> Amen to that. The leading zeros have always seemed like an odd choice
> to me, almost as if they were designed for the punched card era of
> computing. Are they used anywhere except the RFC index?

In RFCs, I find (*) about 4000 three-digit RFCnnn constructs, and about 9000 RFC0nnn constructs.  Yes, they are in use in our documents.

BTW, RFCnnn (counting occurrences, not documents):

1278 RFC822 Mail message format
 473 RFC791 IP
 472 RFC793 TCP
 219 RFC792 ICMP
 199 RFC826 ARP
 191 RFC768 UDP

Grüße, Carsten

(*) non-scientific

v2.23.0 | Report a Bug | By Email