Re: [Gendispatch] Speed of the standards process

Colin Perkins <csp@csperkins.org> Wed, 26 July 2023 00:30 UTC

Return-Path: <csp@csperkins.org>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 712FAC151B0D; Tue, 25 Jul 2023 17:30:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=csperkins.org
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 RCDP4AKCuzyX; Tue, 25 Jul 2023 17:30:24 -0700 (PDT)
Received: from mx2.mythic-beasts.com (mx2.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69D6AC151B0F; Tue, 25 Jul 2023 17:30:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=csperkins.org; s=mythic-beasts-k1; h=Date:Subject:To:From; bh=g33uuDDZ76ESujCKCOJChfk/KZyzcUZoQAKihd0vzF8=; b=JBytcfUNbFQhgza0SWyUl7qloJ TdxsPV2ZRnKEjkRBrzq4qDU2TdV4ulPuMon7zat+J61MrpTX+5/r/EFkPoaf2Z04D4O+WAy2ExqhX 8yi3daxWhpcQq3U3JElhWG+wE7k6DGApS6BCP0bI0qyUtbVQD5jofhviUOFuOM0JeNb25YdZ5Xag5 XUqWDPqLWHYhcI9UyRsJmPN79cIXEfC0zI48/PnyJbA6TeXD+5PB1lyU/ziM0yYsrTv27Kea9Zdmb sTQ2loX9nnibfQMKuS6vTfcJxHGZ9ZAep52L1jw5y5+xlPRd4azlXIH4Pw3FWmOhV4h8LSavmY4W6 yw9hD2EA==;
Received: by mailhub-hex-d.mythic-beasts.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <csp@csperkins.org>) id 1qOSPm-00BVNM-9Q; Wed, 26 Jul 2023 01:30:09 +0100
From: Colin Perkins <csp@csperkins.org>
To: Jay Daley <exec-director@ietf.org>
Cc: GENDISPATCH List <gendispatch@ietf.org>
Date: Tue, 25 Jul 2023 17:29:59 -0700
X-Mailer: MailMate (1.14r5964)
Message-ID: <F892278B-4D75-4F10-9285-3DFF438831FD@csperkins.org>
In-Reply-To: <980E5639-1F75-4CAA-BB47-A7D483FDD893@ietf.org>
References: <980E5639-1F75-4CAA-BB47-A7D483FDD893@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/related; boundary="=_MailMate_322C784A-D4DB-4382-AECF-B2C5EC493C30_="
X-BlackCat-Spam-Score: 0
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/_L3PJ4NM75bll4eFqSiXZ5NDPos>
Subject: Re: [Gendispatch] Speed of the standards process
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2023 00:30:29 -0000

Hi,

On 25 Jul 2023, at 17:04, Jay Daley wrote:
> In Adrian’s talk today he suggested that there was a negative 
> perception of the IETF due to the length of time it takes to get 
> standards out.  This is something we tested in the most recent IETF 
> Community Survey where the question was:
…

We also looked at this in an IMC paper a couple of years ago:
https://sodestream.github.io/publications/characterising-ietf-rfc-deployment.pdf

The figures below show changes in the time taken from the submission of 
the first draft of a document through to its publication as an RFC and 
the number of intermediate drafts each document goes through prior to 
publication. There's a clear trend: drafts are taking longer to publish. 
The average time to publication was 469 days (~15 months) in 2001, 
rising to 1170 days (~38 months) in 2020. The number of revisions each 
document went though more than doubled in the same time period. The time 
to publish and the number of drafts prior to publication are strongly 
correlated, suggesting that the time is spent making changes to the 
document.

![](cid:76BF2412-F563-4106-A77A-348C104ACD51@csperkins.org 
"day_counts_yearly.png")
![](cid:F53D2755-474A-4C3D-AD01-FBBCFADF35E6@csperkins.org 
"draft_counts_yearly.png")

What's causing this? There's no clear increase in draft length over 
time, but there is a a significant increase in the number of citations 
and cross references between drafts over the years (see plot below): 
work submitted to the IETF recently is much more likely to refer to 
prior work.

Similarly, the proportion of drafts published each year that update or 
obsolete one or more previously published RFCs has increased over time. 
In 2020, more then 30% of documents published updated or made obsolete a 
previously published document in the RFC series. Recent drafts also 
include more RFC 2119 keywords than earlier drafts.

![](cid:DE0F7922-B6F9-474B-A42E-86ADC0ADFFCD@csperkins.org 
"cite_counts_yearly.png")

Our conclusion was that this data suggests that the delays are coming 
from the increasing complexity of the network and the increasing need to 
take into account backwards compatibility with increasing numbers of 
prior RFCs. The working group process is taking longer because on the 
increased complexity of the work.

As I said in the chat during the meeting, RASPRG is working to collect 
such data and better understand the standards process. Anyone interested 
in this sort of analysis might want to participate. 
https://datatracker.ietf.org/rg/rasprg/about/

Colin