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

"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Wed, 19 August 2020 23:12 UTC

Return-Path: <eckelcu@cisco.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 94CA93A0F2A for <wgchairs@ietfa.amsl.com>; Wed, 19 Aug 2020 16:12:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.598
X-Spam-Level:
X-Spam-Status: No, score=-9.598 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_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=BrKZGCmd; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=aArq/psz
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 AJ01jK5By6Xn for <wgchairs@ietfa.amsl.com>; Wed, 19 Aug 2020 16:12:33 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B01443A0EDD for <wgchairs@ietf.org>; Wed, 19 Aug 2020 16:12:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5794; q=dns/txt; s=iport; t=1597878753; x=1599088353; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=eNdtSTHFZ4jFtw8Od2vViqrAYbtf5u3CiCjB1HhKcbA=; b=BrKZGCmddMwDhraLvAi388BLDvy00zqAxMctmjQ8gcsw4nQsI9e5HPke TS+ZK+JYJ6URtIGkuJYZWHxhan0kBPdl7Izix/ha+3PRgguLv9U1fNljH /CJKzLjeELz5472t30wk9E+4H5+qMOByHjdKbmWuZG3+aTaxjI+ArjB3A I=;
IronPort-PHdr: =?us-ascii?q?9a23=3ANicuDRFWIGv9KtMW8kpyTJ1GYnJ96bzpIg4Y7I?= =?us-ascii?q?YmgLtSc6Oluo7vJ1Hb+e401QObVp6d9/lIzevb4OjsWm0FtJCGtn1KMJlBTA?= =?us-ascii?q?QMhshemQs8SNWEBkv2IL+PDWQ6Ec1OWUUj8yS9Nk5YS83lIUHZrjuz4G1aFh?= =?us-ascii?q?D2LwEgIOPzF8bbhNi20Obn/ZrVbk1IiTOxbKk0Ig+xqFDat9Idhs1pLaNixw?= =?us-ascii?q?=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AJCAAXsT1f/49dJa1fHQEBAQEJARI?= =?us-ascii?q?BBQUBQIFKgVIjLgdwWC8shDeDRgONXJhsgUKBEQNVCwEBAQwBASMKAgQBAYR?= =?us-ascii?q?MAheCGgIkOBMCAwEBCwEBBQEBAQIBBgRthVwMhXEBAQEDARIREQwBAS4JAQ8?= =?us-ascii?q?CAQgYAgIjAwICAjAUARACBAENBSKDBAGCSwMOIAEOpiACgTmIYXaBMoMBAQE?= =?us-ascii?q?FgTMBhBgYgg4DBoEOKoJxg2KCPoQOG4IAgTgcgU9QLj6CXAKBJToXI4JdM4I?= =?us-ascii?q?tj0eDAT2jMgqCYohkkT4DHqAnkj+KR5R9AgQCBAUCDgEBBYFqI4FXcBVlAYI?= =?us-ascii?q?+UBcCDViNRwwXg06FFIVCdDcCBgEJAQEDCXyQSQEB?=
X-IronPort-AV: E=Sophos;i="5.76,332,1592870400"; d="scan'208";a="529037960"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 19 Aug 2020 23:12:32 +0000
Received: from XCH-RCD-001.cisco.com (xch-rcd-001.cisco.com [173.37.102.11]) by rcdn-core-7.cisco.com (8.15.2/8.15.2) with ESMTPS id 07JNCWgp006717 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 19 Aug 2020 23:12:32 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-RCD-001.cisco.com (173.37.102.11) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 19 Aug 2020 18:12:32 -0500
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 19 Aug 2020 19:12:31 -0400
Received: from NAM10-DM6-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Wed, 19 Aug 2020 18:12:31 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=GseALxx2O7wuAonvakvmoYFI8wDhdQknGJQ3hKE+nxR7fcNzcGku7HMzh3E9R5kFWOnreiqGx/LAZBMGfbu70VLSWcTx8BZ5OVIEWYbW8DiXnffJrBVjZMQMC5r2nEAQSgLdfX2ABwxTUyBJJOduDQd9duVn9D1dfOPxZT0iVjHLsLwwz8YuZo9Cws3gBr7YdEmnRWCfOcYSd/1jgDVKriXKLZk/ha0KwkGKPogcYZa+nnG6Qn+2FuudNDb9v2shRjDSP2JEfQw/zaPCWvScss6WSxOndfr+HWNcA+YFSmXZ5CL57/FVL8GPZbVTcNaUgj+zbi/dW/a1wBwFm6JaOA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=eNdtSTHFZ4jFtw8Od2vViqrAYbtf5u3CiCjB1HhKcbA=; b=FGb+RG7DlKs0s44yS5DJDxlrw1wYEDhMCiDndtv3s4o9+DiIDGOkN0Yd1xGRxb7fGR+ohPFTKheGw5Eu8s+OjGt6u8jS1nJGazkDTbXQYktVgCFK3kp0z/hvI/zvaGhsLTOZVoWnfG3qTeNvukt/+BcrJvNrzFUMZoLIvZTwu7dLGohAi0NKhUVG+ejD8sG0CGx7ZnQy829E2rmcknfXRaaPAGyGOnE2NWklao5ozuuVzdes8U1Af5mr0pZZnfDrA7SIFQOiUaPHMnVge2n1K/U03k5ATU7V6rz79rlpI0pBmf7QKJ3N8hqgcMX1ogHMsta5xiZ/2P8JxlUs47IbFA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=eNdtSTHFZ4jFtw8Od2vViqrAYbtf5u3CiCjB1HhKcbA=; b=aArq/pszx/XC8iCcCiH+Oj4OOxnw/zsZdYRVDcwuM09hLTqI8eybhGaUtsuI9R51q2K/thD4zxlTOejK1Eg1k9xdzf5XAqAQSsg9jNbkLVoW+7ji+0b+24st9MziZPOy7bT5Sa/edkIUXEUO0zql9NoSiN5DMTB9AAlydljcjlo=
Received: from BYAPR11MB3237.namprd11.prod.outlook.com (2603:10b6:a03:1e::19) by BYAPR11MB2950.namprd11.prod.outlook.com (2603:10b6:a03:8f::29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3305.24; Wed, 19 Aug 2020 23:12:30 +0000
Received: from BYAPR11MB3237.namprd11.prod.outlook.com ([fe80::d43b:cd64:b100:84b5]) by BYAPR11MB3237.namprd11.prod.outlook.com ([fe80::d43b:cd64:b100:84b5%7]) with mapi id 15.20.3305.024; Wed, 19 Aug 2020 23:12:30 +0000
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, "Joel M. Halpern" <jmh@joelhalpern.com>, 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>
Subject: Re: [irsg] An IETF repository for working code in our protocols?
Thread-Topic: [irsg] An IETF repository for working code in our protocols?
Thread-Index: AQHWdlVCxI8fqhJaDkmPR/oV4PiG7Kk/xXIAgAA8d4CAAAMSAP//lWyA
Date: Wed, 19 Aug 2020 23:12:30 +0000
Message-ID: <6B9263EE-639F-44AC-AC7F-5D57B102E1D4@cisco.com>
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>
In-Reply-To: <a484f593-d037-ca9e-c4e9-6e28731b3152@cs.tcd.ie>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.40.20081000
authentication-results: cs.tcd.ie; dkim=none (message not signed) header.d=none;cs.tcd.ie; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [2601:647:4401:e580:ec01:ea94:e29d:1f34]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: e5851869-fbe0-4fbe-e5c0-08d8449558be
x-ms-traffictypediagnostic: BYAPR11MB2950:
x-microsoft-antispam-prvs: <BYAPR11MB29501658441DBCC49F3996DEB25D0@BYAPR11MB2950.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:6790;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 1gQVSKKbZgvcu/ZroN/Qx13UgYTZF0hsJUQZynddKP8RSP4d3DJLzlCItEZ5wwOA0XQFDh1bAMSqDy4JkL4ISDEiWl3rroWksBQLB+vC8rDZyqaD0YgllO2aiqxicqIKSlv8yERBqHmydNYaoUzpBNaMjpfCPcCEMFJWPSs5DsX/QZ9LfoF7bahmB9zD1oayjM/PeM217dij3OD3mslMdb13XyZAGgrPYgPYj8gHQv6czkmkLTaf/1NWsmvOhOGeUSo/FOvEQPGAqDP8Xz69nNqeFGriSJuLPJNAZ2CIVwyeI8Zs7CY4FYV/c6S0RV0PUarJOsWrNXoNPfgJu7clPUnxrP/9dIl78uvRdtNhC9OwbFNfozcqsm5sN8E0kJbmMDRTpBnBkxXTzYqp/0LeOQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BYAPR11MB3237.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(136003)(396003)(366004)(376002)(346002)(39860400002)(33656002)(186003)(86362001)(6506007)(54906003)(296002)(5660300002)(316002)(6512007)(36756003)(2906002)(110136005)(8676002)(2616005)(66946007)(64756008)(66556008)(66446008)(66476007)(71200400001)(53546011)(966005)(6486002)(8936002)(4326008)(478600001)(76116006)(83380400001); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: 3VOkQZJuQ69FmWEaKzsVpC04sZPlqsN4rpqSlGKYrSNnqr44v3kwZZ4mBMD4o+JHruyG/OAACAicqh8QgO1K2NEQ0D6bWFl6C2dXA8qc2SwhiSL8qzJZ51T5sn2ALYMDgm/FHl651pemL/JG/DENOXz24AJKHEiBmx5ldZwi0dIZTegvvWLkoPVwo+QRmWdpQiEO67tCV+ld0Ulp1AiWUux1lMPlNUelDEBS305S+7onTVIopSVQXOPqmSquKgZpK91fkJ2yW3wGT9LtnKqHsiYHQu3Yy3oNfclN5HCsakGjcI79COuqCQuj3UDgmS+PYxPBXSz4D5rES8eFSYkvdqMB5hJAJ2JJ7c62COSuSqvPJEJYq7qDfbaxQ58bVcAIYZJVuARqcYt9aoNB9247huq+l76lVN16pw/Zu8Pn77aQ3nfT0IUf2fNhrEF3A5xz9JSNU7eiRzMJNEb++FdQmV8OGm3yIpS32Pbs7Lt98OcW9nn/bhncYVhWA3EuXzYaiX882cnbEK6n6vuxqDC75rXkluriZKtm8YmSH9/pDW+rxk1APbDQ5SynC+XTE1qBtBiUk8CbwtsQfkm6UFfMU5TLZ9yo9BJDFP87Z//72QSFpyNyl0KuDtjcRVu5Wl6JmwmMNb/nST33TFZzSQDegu0Uhm71/tROAhUpTAhy++HScSDRZz/xAPx40ijcoPUzzg5/3tT4Kp0GTnQwVN26DA==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <CB6548D4B6157D4DA56861805A314E1D@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BYAPR11MB3237.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: e5851869-fbe0-4fbe-e5c0-08d8449558be
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Aug 2020 23:12:30.1077 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 40y20XO7weYNwRf3nYXEz6RRKXkHvl8FLfhVZiqCQJpYPN5Imr+bL3UIr2WgDoWFBJAHtjvvGIsbsrvfhZG7nw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB2950
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.11, xch-rcd-001.cisco.com
X-Outbound-Node: rcdn-core-7.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/gseS2RO5w7WD2AzVtZXqch4i8rg>
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:12:36 -0000

I am thrilled to see this thread and all the great thoughts shared on it.
The IETF Hackathons have thankfully resulted in the creation of a great deal of code, much of which is open source and almost all of which is related to existing and evolving IETF standards. Some of this code does not have much value beyond a specific IETF Hackathon, whereas some has the potential to serves as a valuable resource for developers looking to better understand or implement what is specified in a given IETF draft or RFC. 

Each IETF Hackathon wiki provides a links to much of the code used in the context of that Hackathon (e.g.   https://trac.ietf.org/trac/ietf/meeting/wiki/108hackathon.)
We also have a the results presentations that typically provide links to code (e.g. https://github.com/IETF-Hackathon/ietf108-project-presentations). 
We also have some repos created in the IETF-Hackathon GitHub org that host Hackathon projects, https://github.com/IETF-Hackathon. 

All of this is good; however, I have been thinking for a while that we really should do something better. I would be interested in putting a bit more thought, structure, and consistency behind how and where to document the existence of code related to IETF draft and RFCs. I am would be happy to work with others to define some conventions and try to use them for the Hackathon and for code related to IETF work in general. A link in an "Additional URL" in the datatracker to one or more GitHub repos or GitHub orgs, or to a README file that contains links to corresponding code repos is an example of something simple we could try. I am sure others have better idea.

Cheers,
Charles 

On 8/19/20, 3:34 PM, "WGChairs on behalf of Stephen Farrell" <wgchairs-bounces@ietf.org on behalf of stephen.farrell@cs.tcd.ie> 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
    >>
    >