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

Toerless Eckert <tte@cs.fau.de> Thu, 20 August 2020 16:18 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 DDB293A0933 for <wgchairs@ietfa.amsl.com>; Thu, 20 Aug 2020 09:18:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable 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 Zh40TKzSxVWv for <wgchairs@ietfa.amsl.com>; Thu, 20 Aug 2020 09:18:41 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65D213A0936 for <wgchairs@ietf.org>; Thu, 20 Aug 2020 09:18:38 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [131.188.34.52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id CCE4F548626; Thu, 20 Aug 2020 18:18:33 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id C57E6440059; Thu, 20 Aug 2020 18:18:33 +0200 (CEST)
Date: Thu, 20 Aug 2020 18:18:33 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: "Salz, Rich" <rsalz@akamai.com>
Cc: Eliot Lear <lear=40cisco.com@dmarc.ietf.org>, "wgchairs@ietf.org" <wgchairs@ietf.org>
Subject: Re: [irsg] An IETF repository for working code in our protocols?
Message-ID: <20200820161833.GZ62842@faui48f.informatik.uni-erlangen.de>
References: <CAMMTW_+P60jB-MLsB6R_x7z3uk5xK56ZwkZnHOtzaxex3tDREA@mail.gmail.com> <90cb740e-8663-58df-5c99-cbc053142566@joelhalpern.com> <a484f593-d037-ca9e-c4e9-6e28731b3152@cs.tcd.ie> <e6ae9107-48a9-cf04-2772-90b4b357fe3b@joelhalpern.com> <e99af73a-0ffa-f4e3-dcc8-6666066ceaa6@cs.tcd.ie> <9AF9FB0F-B620-4C66-AC5B-A14AC4FBB34E@cisco.com> <20200820151841.GW62842@faui48f.informatik.uni-erlangen.de> <E00EBF47-01E3-4D97-BEEE-C6B9C15D1449@akamai.com> <20200820160129.GY62842@faui48f.informatik.uni-erlangen.de> <40105475-68CE-4420-8AE6-5EC86D273FDC@akamai.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <40105475-68CE-4420-8AE6-5EC86D273FDC@akamai.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/9gONBoNNfxk-MxjDBhNmQKIdbwA>
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 16:18:43 -0000

On Thu, Aug 20, 2020 at 04:05:38PM +0000, Salz, Rich wrote:
> 
> >    I guess there is little that can be done against someone calling their code
>     reference implementation. Except of course having actually WG endorsed
>     reference code and calling that "IETF FOOBAR-WG <protocol> reference code".
> 
> For a long time there was only Dave Mills's NTP code, and the current maintainer insists that this is still the reference implementation.  The IETF doesn't have reference implementations, nor should it.
> 
> >    Eliot mentioned crypto code, but i don't think we have official "endorsement/work-product status"
>     for any such code... or do we ?
> 
> We have several RFC's that contain implementations. 

Right. I was just compiling the NomCom hash algo RFC code last month. Indeed ;-)

Yeah.... that kinda sucks as a way to represent source code. Maybe if there is sufficient interest this is something that could be overhauled.

Cheers
    Toerless