Re: [rfc-i] Example RFC numbers?

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 22 August 2023 21:52 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 369ACC1522CD for <rfc-interest@ietfa.amsl.com>; Tue, 22 Aug 2023 14:52:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.199
X-Spam-Level:
X-Spam-Status: No, score=-2.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.091, RCVD_IN_DNSWL_NONE=-0.0001, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 sSTewoo7Bw8K for <rfc-interest@ietfa.amsl.com>; Tue, 22 Aug 2023 14:52:55 -0700 (PDT)
Received: from mail-pl1-x632.google.com (mail-pl1-x632.google.com [IPv6:2607:f8b0:4864:20::632]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 9E219C151089 for <rfc-interest@rfc-editor.org>; Tue, 22 Aug 2023 14:52:55 -0700 (PDT)
Received: by mail-pl1-x632.google.com with SMTP id d9443c01a7336-1bc5acc627dso33024775ad.1 for <rfc-interest@rfc-editor.org>; Tue, 22 Aug 2023 14:52:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1692741175; x=1693345975; h=content-transfer-encoding:in-reply-to:content-language:references :cc:to:subject:from:user-agent:mime-version:date:message-id:sender :from:to:cc:subject:date:message-id:reply-to; bh=RfMvPua5tUACXik6i1t8NO3ONL3wfqEANCXdJVwUah4=; b=ZBKsDvMIc2WInDqvWcI5eSHo0IzJ+JlOfokmHco7TyFrDWN+zJHph1sLUREY+Qg28/ 75P2mcCiCZISRaXOvCIMKLLtuRhN3T/T5hWSBp581xOhv8vbZ+DILh0j+BZUg0umGYli xJTErorDkj+z0kjpYuXamySxDWT5K5NmP1ODuqL1qfEGXvfs1B9VkYqgjYaCRHiv0lHi kvAAaGF0Yvi6pYCztTuuiDnrbaz/KqZ3I9E8iKo0dOIAd97x4V5rtbkOiHcMFkvrcyOt KgU98FlyxECe22sJkFT0/nn293jIBvKUBsqcFJhF1wJoMz75WBMRR1oowSc0fdCwj4Jo Rerw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692741175; x=1693345975; h=content-transfer-encoding:in-reply-to:content-language:references :cc:to:subject:from:user-agent:mime-version:date:message-id:sender :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=RfMvPua5tUACXik6i1t8NO3ONL3wfqEANCXdJVwUah4=; b=Pjj3F9HsSAOJXZw+ocpR6Um+83gvC7OA8wWa9fJYzXNwjm2ZhgrA+ciGzCr7hbCls0 d6FdM98TbI/ZISxUTOYnsXYh1jY9vu7AjQ6A+puhUp/UAwaqTbLtuTurCkF9cJNcdRB9 3UFXbLNiualgP9wJmnEE5b7u0ZaMRANyVVU95a9OzyjzT0hy/XiGY2N/9geNZz2Dm2xH l6mfa4RLOfaLrq5j5GfTeLBB5VamjzEdxc+fgPN8/Emfy6I193NvycgCwweDf4GGg6x/ FKmb/umPoVuzS/znmFzftTSQ4FslyPRrVmQhDa7D464IgOnW5lRVqmjIB0VzKHgWky4m h/lA==
X-Gm-Message-State: AOJu0Yyy9ZFWM/MCxlILLS84htfPq0o3HNz3URchinIl5xFqBTP8CpzT j0lcGiHkRha3lsMbUYewnxo=
X-Google-Smtp-Source: AGHT+IGUyYmVOiRcI1TOIPYxzBSzC/g1F6y6wt0IxHFmLEMQJRsAs+VeucHWTjafnhXstEu1AkTA/g==
X-Received: by 2002:a17:902:f547:b0:1b7:f443:c7f8 with SMTP id h7-20020a170902f54700b001b7f443c7f8mr8480648plf.15.1692741174859; Tue, 22 Aug 2023 14:52:54 -0700 (PDT)
Received: from ?IPV6:2406:e003:10cc:9901:b2e1:1101:7ba7:19fd? ([2406:e003:10cc:9901:b2e1:1101:7ba7:19fd]) by smtp.gmail.com with ESMTPSA id jw24-20020a170903279800b001adf6b21c77sm9489565plb.107.2023.08.22.14.52.52 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 22 Aug 2023 14:52:54 -0700 (PDT)
Sender: Brian Carpenter <becarpenter46@gmail.com>
Message-ID: <1b4e832a-97ec-a007-5435-6c20f0735da7@gmail.com>
Date: Wed, 23 Aug 2023 09:51:36 +1200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: Robert Sparks <rjsparks@nostrum.com>, Donald Eastlake <d3e3e3@gmail.com>, rfc-interest@rfc-editor.org
References: <b0cba5ce-120f-c179-e1f2-8c0efae2612a@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> <2236F4D2-6A1A-4815-9012-41E3845E77F2@tzi.org>
Content-Language: en-US
In-Reply-To: <2236F4D2-6A1A-4815-9012-41E3845E77F2@tzi.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/2xqyv3Om1XUJwEbHefvguwBFWk4>
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 21:52:56 -0000

On 23-Aug-23 00:31, Carsten Bormann wrote:
> 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.

Oh, groan. Especially, we apparently chose to use them for DOIs. So RFC-processing software is stuck with this for ever.

      Brian

> 
> 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
> 
> .