Re: An IETF repository for working code in our protocols?

Pete Resnick <resnick@episteme.net> Thu, 20 August 2020 20:57 UTC

Return-Path: <resnick@episteme.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B744D3A1412 for <wgchairs@ietfa.amsl.com>; Thu, 20 Aug 2020 13:57:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 bGaXiBGa2cBo for <wgchairs@ietfa.amsl.com>; Thu, 20 Aug 2020 13:57:31 -0700 (PDT)
Received: from episteme.net (episteme.net [216.169.5.102]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 924BB3A1411 for <wgchairs@ietf.org>; Thu, 20 Aug 2020 13:57:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by episteme.net (Postfix) with ESMTP id CC9C8B964DE4; Thu, 20 Aug 2020 15:57:26 -0500 (CDT)
Received: from episteme.net ([127.0.0.1]) by localhost (episteme.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CQCJQLlPXd6v; Thu, 20 Aug 2020 15:57:23 -0500 (CDT)
Received: from [172.16.1.10] (episteme.net [216.169.5.102]) by episteme.net (Postfix) with ESMTPSA id 3CCA5B964DD1; Thu, 20 Aug 2020 15:57:23 -0500 (CDT)
From: "Pete Resnick" <resnick@episteme.net>
To: "Vijay Gurbani" <vijay.gurbani@gmail.com>
Cc: "Mark Nottingham" <mnot@mnot.net>, "IETF WG Chairs" <wgchairs@ietf.org>
Subject: Re: An IETF repository for working code in our protocols?
Date: Thu, 20 Aug 2020 15:57:22 -0500
X-Mailer: MailMate (1.13.1r5706)
Message-ID: <5569BEF0-1782-4D93-8BB1-276ECD42D6ED@episteme.net>
In-Reply-To: <CAMMTW_KVRVaz0tUXLaAQH2V0bY2ws+CZDy=XUKC=Jc3aiAU58w@mail.gmail.com>
References: <CAMMTW_+Di=ZBJFLNPaVK6f3w3Yq-V-qau8G_rfGt96SX_aYAAA@mail.gmail.com> <8193D927-DDA8-4C74-BBD3-1AF6C9AFE98B@mnot.net> <CAMMTW_KVRVaz0tUXLaAQH2V0bY2ws+CZDy=XUKC=Jc3aiAU58w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/zybBs4FEHqZArVJDQslpTUVy5xg>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Aug 2020 20:57:33 -0000

On 20 Aug 2020, at 13:26, Vijay Gurbani wrote:

>> I also don't think that it's necessary, once a protocol is 
>> successful; after broad deployment, people don't need to go searching 
>> for implementations. It *is* useful when a project is starting, to 
>> help early implementers find each other, though. 
>
> Yes, agreed!  The idea would be light the fire of widespread 
> implementation by the kindling (code) that tracked the I-D as it 
> became an RFC.  

It might be useful (for you all and for the IAB program) to look at the 
codestand (originally codematch) project, both its successes and its 
failures. The email lists are still in the archives. I followed it at 
the beginning, but don't know much about it other than it was in part 
trying to help match up implementors with standards.

pr
-- 
Pete Resnick https://www.episteme.net/
All connections to the world are tenuous at best