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

"Joel M. Halpern" <jmh@joelhalpern.com> Wed, 19 August 2020 22:23 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 CDFAD3A0C45 for <wgchairs@ietfa.amsl.com>; Wed, 19 Aug 2020 15:23:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.049
X-Spam-Level:
X-Spam-Status: No, score=-3.049 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, 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 Tvudim_tkk2G for <wgchairs@ietfa.amsl.com>; Wed, 19 Aug 2020 15:22:59 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 CAF473A0D88 for <wgchairs@ietf.org>; Wed, 19 Aug 2020 15:22:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4BX2NM4JxTz6GD2M; Wed, 19 Aug 2020 15:22:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1597875779; bh=mORi1AaDcMF6hv3UvoUsN1WEklUL5sfWdRr1Jek3UIA=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=TQwmi1+hNHUbojIWugwLVZ8Zm8foWHenntYFEMJebSV5/zKtN9lfpldgORgIovQ8M 7WtnaP9qGz4zAhtTIwjvbp5kfYYVmjbYp0zf/EtnNvKBq61OiBu0TvvQRtIERooptV ZpBQyoApBdq7b1X1p6ouy8v4aknlBD9AgYOoP0gw=
X-Quarantine-ID: <vVCFuP7RRQ06>
X-Virus-Scanned: Debian amavisd-new at a2.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 maila2.tigertech.net (Postfix) with ESMTPSA id 4BX2NL6hRsz6GBxC; Wed, 19 Aug 2020 15:22:58 -0700 (PDT)
Subject: Re: An IETF repository for working code in our protocols?
To: Vijay Gurbani <vijay.gurbani@gmail.com>, "Deen, Glenn (NBCUniversal)" <Glenn.Deen@nbcuni.com>
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, Martin Duke <martin.h.duke@gmail.com>
References: <81300C20-AC38-465C-A17C-743F3D4CD947@nbcuni.com> <CAMMTW_+P60jB-MLsB6R_x7z3uk5xK56ZwkZnHOtzaxex3tDREA@mail.gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <90cb740e-8663-58df-5c99-cbc053142566@joelhalpern.com>
Date: Wed, 19 Aug 2020 18:22:57 -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: <CAMMTW_+P60jB-MLsB6R_x7z3uk5xK56ZwkZnHOtzaxex3tDREA@mail.gmail.com>
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/8E-Tmnyb4m8tY0CFSNLKG4FUrVo>
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 22:23:02 -0000

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.

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
>