RFC 8963 on Evaluation of a Sample of RFCs Produced in 2018

rfc-editor@rfc-editor.org Fri, 22 January 2021 19:23 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B9C03A1464 for <ietf-announce@ietfa.amsl.com>; Fri, 22 Jan 2021 11:23:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 tjYRtAn-MsLr for <ietf-announce@ietfa.amsl.com>; Fri, 22 Jan 2021 11:23:49 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B4163A144E for <ietf-announce@ietf.org>; Fri, 22 Jan 2021 11:23:48 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id D7657F4074C; Fri, 22 Jan 2021 11:23:29 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg5NjMgb24gRXZhbHVhdGlvbiBvZiBhIFNhbXBsZSBvZiBSRkNzIFByb2R1Y2VkIGluIDIwMTg=?=
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210122192329.D7657F4074C@rfc-editor.org>
Date: Fri, 22 Jan 2021 11:23:29 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/i6EIbHVzFDxz_33L97x07phS6lg>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2021 19:23:50 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8963

        Title:      Evaluation of a Sample of 
                    RFCs Produced in 2018 
        Author:     C. Huitema
        Status:     Informational
        Stream:     Independent
        Date:       January 2021
        Mailbox:    huitema@huitema.net
        Pages:      42
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-huitema-rfc-eval-project-07.txt

        URL:        https://www.rfc-editor.org/info/rfc8963

        DOI:        10.17487/RFC8963

This document presents the author's effort to understand the delays
involved in publishing an idea in the IETF or through the Independent
Stream, from the first individual draft to the publication of the
RFC. We analyze a set of randomly chosen RFCs approved in 2018,
looking for history and delays. We also use two randomly chosen sets
of RFCs published in 2008 and 1998 for comparing delays seen in 2018
to those observed 10 or 20 years ago. The average RFC in the 2018
sample was produced in 3 years and 4 months, of which 2 years and 10
months were spent in the working group, 3 to 4 months for IETF
consensus and IESG review, and 3 to 4 months in RFC production. The
main variation in RFC production delays comes from the AUTH48 phase.

We also measure the number of citations of the chosen RFC using
Semantic Scholar, and compare citation counts with what we know about
deployment. We show that citation counts indicate academic interest,
but correlate only loosely with deployment or usage of the
specifications. Counting web references could complement that.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC