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

"Joel M. Halpern" <jmh@joelhalpern.com> Wed, 19 August 2020 23:42 UTC

Return-Path: <jmh@joelhalpern.com>
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 2C8993A0F82 for <wgchairs@ietfa.amsl.com>; Wed, 19 Aug 2020 16:42:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.047
X-Spam-Level:
X-Spam-Status: No, score=-3.047 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, NICE_REPLY_A=-0.949, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 7juYA1pEpJ4a for <wgchairs@ietfa.amsl.com>; Wed, 19 Aug 2020 16:42:09 -0700 (PDT)
Received: from maila1.tigertech.net (maila1.tigertech.net [208.80.4.151]) (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 E8ECB3A0F7D for <wgchairs@ietf.org>; Wed, 19 Aug 2020 16:42:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila1.tigertech.net (Postfix) with ESMTP id 4BX47j5xBbz4TFQp; Wed, 19 Aug 2020 16:42:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1597880529; bh=XE6z0YzTuJw8qty6Py0K+5gagWE/yr5g1B6Q7z6b4gM=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=PE9somoYxusgaNoJhM74ymOb7ozWU0507TNqxIPDmh/Zis1DwUylWQhx2hQqkBxI3 CYYwUycCy6rjFYslvp66CbexShpvy9n2F+pyz83ljOTR+HkKlrJjV5bgWzcyqJAJKS Hbl0z8OqlVsH0VL6S9dPhU6qQbvIyoF/TEfW+96s=
X-Quarantine-ID: <NDNg-XeBYsus>
X-Virus-Scanned: Debian amavisd-new at a1.tigertech.net
Received: from [192.168.128.43] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila1.tigertech.net (Postfix) with ESMTPSA id 4BX47h4QCPz4TF7R; Wed, 19 Aug 2020 16:42:08 -0700 (PDT)
Subject: Re: [irsg] An IETF repository for working code in our protocols?
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
References: <81300C20-AC38-465C-A17C-743F3D4CD947@nbcuni.com> <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>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <536362ab-3a8a-d584-eb17-b5e8c927bfc6@joelhalpern.com>
Date: Wed, 19 Aug 2020 19:42:06 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0
MIME-Version: 1.0
In-Reply-To: <e99af73a-0ffa-f4e3-dcc8-6666066ceaa6@cs.tcd.ie>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/-wTxsCU1GSZB-hBVwcsv7slNM1Y>
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: Wed, 19 Aug 2020 23:42:11 -0000

For IETF purposes, the existence of implementations is very important.
For some purposes, open source code is useful.
Depending upon the license, for many purposes looking at open source 
code can actually be harmful to the implementation work.

If we want to make available pointers to specific versions of open 
source, as well as pointers to the information about the implementation, 
that is fine.  For many uses, it is as or more important to be able to 
look at the implementors summary of what they actually support than it 
is to look at the code.  For other purposes, looking at the code is 
clearly useful.

I am not asking that the IETF not point to such available code.
I am asking that if we are going to identify implementations that we 
identify implementations regardless of their status.

I presume even for open source we will not attempt to verify the code 
correctness, operability, or quality.  We are not talking about 
reference implementations.  For different consumers of this information, 
different implementations will have different value.  We do not 
currently second-guess implementation or interoperability reports, and I 
do not suggest we start.

As just one example, if I am looking for things to interoeprate with, I 
may well be just as happy with commercial implementations as with open 
source.  Maybe happier as I do not have to figure out how to build 
someone else's structures.

Archiving the soruce has many complications.  And very little value I 
can understand.  After all, if it is open soruce, then it is available 
somewhere else.  if the people making it available do not want to 
continue to do so, it is not the IETF's job to take care of their code 
for them.  Conversely, if they are interested in their work being 
pointed to by the IETF, I am happy to see us do so.

Yours,
Joel

On 8/19/2020 7:09 PM, Stephen Farrell wrote:
> 
> Hiya,
> 
> On 19/08/2020 23:51, Joel M. Halpern wrote:
>> There is different value in open and closed source implementations.  But
>> bother are valuable.
> 
> I maintain that, for implementers of RFCs, the existence of
> open-source code is valuable in a way that closed-source
> can never match. ISTM, that means OSS is inherently better
> for the purpose we're discussing here.
> 
>> There is as far as I can tell no benefit in the IETF actually storing
>> the source for these projects.
> 
> I disagree. Finding the commit that matches the time at
> which the RFC was written can be non-trivial and will
> sometimes be useful/needed.
> 
>>    Either they are being maintained or they
>> aren't.  If they aren't, the source has much less value.
> 
> I disagree. For an implementer of an RFC, there is still a
> lot of value in looking at someone else's code that matches
> the RFC (or nearly does).
> 
>>   If they are,
>> the maintained one is what people should look at.
> 
> Not necessarily. The not-very-good but easy to read code
> that existed at the time the RFC was written might well be
> the most useful thing for an implementer.
> 
>>
>> So again, having an easily findable and easily maintained set of
>> pointers to any implementations that folks want to list, with whatever
>> terms those folks like (whether that be creative commons open source,
>> GPL, or descriptions of proprietary implementations) seems very useful.
>> The problem of findability is real, but is not different for an archive
>> compared with a set of pointers.
> 
> Given the above, I fail to see how you can think closed-
> source can be as useful there, regardless of the mechanism
> for de-referencing a pointer.
> 
> Cheers,
> S.
> 
> 
>>
>> A set of input / output vectors along the lines Erik suggested also
>> sounds useful.  For some protocols.  (I don't quite know how one would
>> do that for something like OSPF.)
>>
>> Yours,
>> Joel
>>
>> On 8/19/2020 6:33 PM, Stephen Farrell wrote:
>>>
>>> Hiya,
>>>
>>> On 19/08/2020 23:22, Joel M. Halpern wrote:
>>>> One of the advantages of pointers to implementations is that it can
>>>> include equally pointers to open source and pointers to closed source of
>>>> various forms.  The IETF doesn't take a stance among implementations.
>>>
>>> Entirely surmountable problem IMO. Add caveats to avoid
>>> misperceptions wrt stance.
>>>
>>> That said, open source implementations are plainly more
>>> useful for people who want to implement RFCs, compared to
>>> equivalent closed-source implementations. It'd be folly
>>> to ignore that reality.
>>>
>>> I just now discovered that what I thought ought be a
>>> compressed-point representation of a DH shared secret is
>>> supposed to use the uncompressed format thanks to being
>>> able to add more trace lines to someone else's code. That's
>>> the kind of thing could suck up many more hours of effort,
>>> or that might lead to non-interop, (as it only affects some
>>> groups), if no open-source code were available.
>>>
>>> S.
>>>
>>>>
>>>> Yours,
>>>> Joel
>>>>
>>>> On 8/19/2020 2:46 PM, Vijay Gurbani wrote:
>>>>> Dear Glenn: Thank you very much for your note.  More inline.
>>>>>
>>>>> On Wed, Aug 19, 2020 at 1:19 PM Deen, Glenn (NBCUniversal)
>>>>> <Glenn.Deen@nbcuni.com <mailto:Glenn.Deen@nbcuni.com>> wrote:
>>>>>
>>>>>       Hi Vijay,
>>>>>
>>>>>         In additional to the points others have made, I’ll add that an
>>>>>       IETF code repository would need to carefully work out license
>>>>> issues
>>>>>       and also how it fits into the IETF’s Intellectual Property set up
>>>>>       that is managed by the IETF  Trust.
>>>>>
>>>>>       [...]
>>>>>
>>>>>       There may be more that pop up once the topic was looked at deeper.
>>>>>
>>>>>       I’m not saying that any of these are show stoppers, but there’s a
>>>>>       lot of legal elements that would be need to worked out before any
>>>>>       bits got checked into a repository.
>>>>>
>>>>>
>>>>> Yes, absolutely.  All of what you listed are important and weighty
>>>>> concerns.  But none of them appear to be insurmountable if we decided
>>>>> to do this.  Clearly, the precedent set by IEEE and ACM in similar
>>>>> areas seems to point to the possible existence of a happy medium,
>>>>> should we go this route.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> - vijay
>>>>>
>>>>
>>