[hackathon] Open Source Software and network protocol standards

Stuart Cheshire <cheshire@apple.com> Fri, 18 March 2022 23:47 UTC

Return-Path: <cheshire@apple.com>
X-Original-To: hackathon@ietfa.amsl.com
Delivered-To: hackathon@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E57423A137D for <hackathon@ietfa.amsl.com>; Fri, 18 Mar 2022 16:47:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level:
X-Spam-Status: No, score=-7.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.com
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 p9fxyqzROH_4 for <hackathon@ietfa.amsl.com>; Fri, 18 Mar 2022 16:47:16 -0700 (PDT)
Received: from rn-mailsvcp-ppex-lapp15.apple.com (rn-mailsvcp-ppex-lapp15.rno.apple.com [17.179.253.34]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1EF63A137C for <hackathon@ietf.org>; Fri, 18 Mar 2022 16:47:16 -0700 (PDT)
Received: from pps.filterd (rn-mailsvcp-ppex-lapp15.rno.apple.com [127.0.0.1]) by rn-mailsvcp-ppex-lapp15.rno.apple.com (8.16.1.2/8.16.1.2) with SMTP id 22INjfc7015826 for <hackathon@ietf.org>; Fri, 18 Mar 2022 16:47:16 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=from : content-type : content-transfer-encoding : mime-version : subject : message-id : date : to; s=20180706; bh=b9tGKqQoOGKUgmNK+J1m6f1zOphYMSedb6fdvZ8QuIE=; b=gUTnVy6I5VNB2JjsSpQcr4Ahu9pSVtWxzniQZVT5/xyYI+pkUiv82eJQGZhrHTQA+eog r3hNM9KwLuMW/iT+hjQ3xIPsn1sn25+WMrnA73B0eaVYvYoBektPpi5JeSHlLrTyo8eG DLXEWxqR8d5RI1gPoB+I9sHlMTbH2A+RjVmabawbvrlRscq2sAoiV/u6RUQ/oJUplEig nLbWDS/kA/Y4D4b/5fKdKjKzLOxNNUT1Urf1mmkHDoH0GF/vUEqXVowDvA7fkVVyXFhi 0DFpFni0y2bRGN3NMvC3xXYejEVXZED896bayxygdhUdgmoz9tO2Xt3NcCFD2UfCmAc2 oA==
Received: from crk-mailsvcp-mta-lapp03.euro.apple.com (crk-mailsvcp-mta-lapp03.euro.apple.com [17.66.55.16]) by rn-mailsvcp-ppex-lapp15.rno.apple.com with ESMTP id 3et66xqwy2-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <hackathon@ietf.org>; Fri, 18 Mar 2022 16:47:16 -0700
Received: from crk-mailsvcp-mmp-lapp03.euro.apple.com (crk-mailsvcp-mmp-lapp03.euro.apple.com [17.72.136.17]) by crk-mailsvcp-mta-lapp03.euro.apple.com (Oracle Communications Messaging Server 8.1.0.16.20220118 64bit (built Jan 18 2022)) with ESMTPS id <0R8Y00L0TSQQ8300@crk-mailsvcp-mta-lapp03.euro.apple.com> for hackathon@ietf.org; Fri, 18 Mar 2022 23:47:14 +0000 (GMT)
Received: from process_milters-daemon.crk-mailsvcp-mmp-lapp03.euro.apple.com by crk-mailsvcp-mmp-lapp03.euro.apple.com (Oracle Communications Messaging Server 8.1.0.16.20220118 64bit (built Jan 18 2022)) id <0R8Y00I00SQQKD00@crk-mailsvcp-mmp-lapp03.euro.apple.com> for hackathon@ietf.org; Fri, 18 Mar 2022 23:47:14 +0000 (GMT)
X-Va-A:
X-Va-T-CD: 65e2316e368e89fe68bd75e23778031b
X-Va-E-CD: 48fad110ca52ec869dc2697e5c8f43a2
X-Va-R-CD: e204508099edb348e9ce5c554a85ea14
X-Va-CD: 0
X-Va-ID: 22951f0c-434d-46fa-bac6-d4364e8b2df7
X-V-A:
X-V-T-CD: 65e2316e368e89fe68bd75e23778031b
X-V-E-CD: 48fad110ca52ec869dc2697e5c8f43a2
X-V-R-CD: e204508099edb348e9ce5c554a85ea14
X-V-CD: 0
X-V-ID: 229d46c3-2ab1-4c98-a2b7-ec255dd5a485
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.425, 18.0.850 definitions=2022-03-18_11:2022-03-15, 2022-03-18 signatures=0
Received: from [17.235.194.60] (unknown [17.235.194.60]) by crk-mailsvcp-mmp-lapp03.euro.apple.com (Oracle Communications Messaging Server 8.1.0.16.20220118 64bit (built Jan 18 2022)) with ESMTPSA id <0R8Y00RAJSQPAI00@crk-mailsvcp-mmp-lapp03.euro.apple.com> for hackathon@ietf.org; Fri, 18 Mar 2022 23:47:14 +0000 (GMT)
From: Stuart Cheshire <cheshire@apple.com>
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: quoted-printable
MIME-version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
Message-id: <BA619D4C-1167-4107-98FB-C01DBAFFC0E3@apple.com>
Date: Sat, 19 Mar 2022 00:47:13 +0100
To: hackathon@ietf.org
X-Mailer: Apple Mail (2.3608.120.23.2.7)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.425, 18.0.850 definitions=2022-03-18_11:2022-03-15, 2022-03-18 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/hackathon/Sp11MN-gVBVuFyoxBN8vvSGlw3w>
Subject: [hackathon] Open Source Software and network protocol standards
X-BeenThere: hackathon@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion regarding past, present, and future IETF hackathons." <hackathon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hackathon>, <mailto:hackathon-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hackathon/>
List-Post: <mailto:hackathon@ietf.org>
List-Help: <mailto:hackathon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hackathon>, <mailto:hackathon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Mar 2022 23:47:21 -0000

Dear Hackathon crew!

I have a question about the relationship between Open Source Software and network protocol standards.

My intuition is that in recent years Open Source Software has had a significant impact on network protocol standards, both in the availability of easily accessible open implementations contributing to the success of network protocol standards, and, in contrast, the lack of easily accessible open implementations contributing to less success for those network protocol standards.

I suspect that many in the IETF Hackathon community share this intuition, but it would be interesting to back up that intuition with concrete data.

I’d like to build a list of compelling examples.

Can you think of cases where an Open Source Software implementation clearly helped a networking protocol become successful? Was that Open Source implementation driven by the people (or companies) actively working on the protocol standard? Or was it created by an independent community following the standards development process?

Are there cases of a networking protocol that did not become successful where, in retrospect, it seems clear that the availability of an easily accessible Open Source implementation would have helped?

And, of course, counterexamples are also interesting: recent protocols that failed despite having a robust Open Source implementation, or recent protocols that succeeded despite having no Open Source implementation.

I am not the first person to think about the growing influence of Open Source on protocol development. Indeed, the existence of the IETF Hackathon itself is, in part, an acknowledgment of this new direction in protocol development. And others have written about it in the past:

2015: <https://www.ietfjournal.org/open-standards-open-source-open-loop/>
2016: <https://datatracker.ietf.org/doc/html/draft-arkko-ietf-trends-and-observations-00>
2018: <https://www.ietfjournal.org/three-years-on-open-standards-open-source-open-loop/>

Looking back now, in 2022, how have those earlier predictions played out? Do we have clear winners we can point to? Clear losers? This will help inform companies how they might want to engage with Open Source. Should companies embrace Open Source for protocol development? Or should companies go back to the old way, with open specifications and private implementations?

Please reply on the list or to me privately, and I will compile a list of responses.

Stuart Cheshire