[rfc-i] Number of RFCs per year per stream
Carsten Bormann <cabo@tzi.org> Wed, 13 December 2023 17:08 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 B01E3C14F604 for <rfc-interest@ietfa.amsl.com>; Wed, 13 Dec 2023 09:08:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_TEMPERROR=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 QSbwkJIxsLSA for <rfc-interest@ietfa.amsl.com>; Wed, 13 Dec 2023 09:07:59 -0800 (PST)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::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 E0064C14F5E4 for <rfc-interest@rfc-editor.org>; Wed, 13 Dec 2023 09:07:57 -0800 (PST)
Received: from eduroam-0160.wlan.uni-bremen.de (eduroam-0160.wlan.uni-bremen.de [134.102.16.160]) (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 4Sr23t719bzDCfD; Wed, 13 Dec 2023 18:07:54 +0100 (CET)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mao-Original-Outgoing-Id: 724180071.168215-d5764f5d3ba89ed6d01b9684b73df838
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
Date: Wed, 13 Dec 2023 18:07:51 +0100
Message-Id: <3F6405B5-78B4-4EA1-A6EC-A1351CAA7EE5@tzi.org>
To: RFC Interest <rfc-interest@rfc-editor.org>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/biTMCRzqfwWeXX6abTTJarkeRSk>
Subject: [rfc-i] Number of RFCs per year per stream
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: Wed, 13 Dec 2023 17:08:06 -0000
There are various sources of statistics for the RFC publication process. I just looked at the IETF Annual Report 2022 [1], which has stats on RFCs and I-Ds on page 5. So we know we get around 200 (-10/+20 %) new RFCs per year. Is there a similar statistic that subdivides this per stream? (The I-Ds show a number of authors: 2730 in 2022; this would also be interesting, also per stream.) Grüße, Carsten
- [rfc-i] Number of RFCs per year per stream Carsten Bormann
- Re: [rfc-i] Number of RFCs per year per stream Jean Mahoney