IETF Logo Mail Archive

Re: [hackathon] Open Source Software and network protocol standards

Lars Eggert <lars@eggert.org> Sat, 19 March 2022 14:03 UTC

Return-Path: <lars@eggert.org>
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 12FDC3A13CA for <hackathon@ietfa.amsl.com>; Sat, 19 Mar 2022 07:03:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eggert.org
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 sLFpnrV8dBGi for <hackathon@ietfa.amsl.com>; Sat, 19 Mar 2022 07:03:33 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65FD93A13AA for <hackathon@ietf.org>; Sat, 19 Mar 2022 07:03:33 -0700 (PDT)
Received: from smtpclient.apple (unknown [IPv6:2001:67c:370:128:d003:2102:94d4:fdda]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id A8760280112; Sat, 19 Mar 2022 16:03:06 +0200 (EET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1647698586; bh=HDF/JNcBjxuaa2g0qKo1LF+csKwnTqlP9PdT8bEH1Aw=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=ps/anD/pYF3vfGCi7kXeV2dy5BV/OeqwmzjlrcGqMA7ORj881FSlAVfxlNK5akbd8 RRIwuwbD/DnzzfxqHaJ19tZ/Nrmkx8ej/aMvjD+lktzSHOIyKrqI5QwLSbEHBTMeB0 JvlksUkkFYvi3NrpdyxRE75Ln8dcoF6hYUYdK4HY=
Content-Type: multipart/signed; boundary="Apple-Mail=_7278B1EE-BFE3-47AA-B7C2-5045BBF9343F"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.82.1.1\))
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <BA619D4C-1167-4107-98FB-C01DBAFFC0E3@apple.com>
Date: Sat, 19 Mar 2022 15:03:05 +0100
Cc: hackathon@ietf.org
Message-Id: <C1BE8C92-36AB-4C15-9066-E3CACCE407DF@eggert.org>
References: <BA619D4C-1167-4107-98FB-C01DBAFFC0E3@apple.com>
To: Stuart Cheshire <cheshire=40apple.com@dmarc.ietf.org>
X-MailScanner-ID: A8760280112.A15B7
X-MailScanner: Not scanned: please contact your Internet E-Mail Service Provider for details
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/hackathon/1-VkV6__N4Zayjlqif9KsueROKQ>
Subject: Re: [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: Sat, 19 Mar 2022 14:03:40 -0000

Hi,

On 2022-3-19, at 0:47, Stuart Cheshire <cheshire=40apple.com@dmarc.ietf.org> wrote:
> 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?

QUIC qualifies, I think. Almost all the implementations (including the initial Google-proprietary version) are open source, and for the IETF version, implementations and standardization were tightly coupled. We did combined WG interims plus interop events six times a year for several years.

Thanks,
Lars

v2.23.0 | Report a Bug | By Email