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

Melinda Shore <melinda.shore@gmail.com> Thu, 20 August 2020 18:51 UTC

Return-Path: <melinda.shore@gmail.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 434203A12D2 for <wgchairs@ietfa.amsl.com>; Thu, 20 Aug 2020 11:51:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.048
X-Spam-Level:
X-Spam-Status: No, score=-3.048 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.949, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 8m0wQ2RbW61s for <wgchairs@ietfa.amsl.com>; Thu, 20 Aug 2020 11:51:04 -0700 (PDT)
Received: from mail-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40B403A12CB for <wgchairs@ietf.org>; Thu, 20 Aug 2020 11:51:04 -0700 (PDT)
Received: by mail-pl1-x62b.google.com with SMTP id t11so1454943plr.5 for <wgchairs@ietf.org>; Thu, 20 Aug 2020 11:51:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=a5lQYR/NyhmVIthhSbjnUt7AifzRLG0rqmFo6PchyxM=; b=jtJfPdNGJnr8/A9vi8aBuSJ2plNOZKiBxJ0JiC4u+m5yVrE6sUrT61lKXdhC9/uiF0 Wojp6rycghPvQGbx/+C5yK5Py8AVA7mxb/m3GvTx2wMbcsVBlTZVaPIA/igAOG2Gkfe0 SwKTKLvkQCe6PJYiuMuxp6A3kbM36HckFq7QRwQuVIMQWFaRacIdPt+SHmFBW1W1KlQv Av7+hNNnnhRMswZLIYZoRX8xZZks3N0NErQm2tAErU7iDvHEpsQikcSqSQoWkiS/kO4B ROqUW1XEU9lI1Xo0kXCizay5/BwhpJzO4XT9Vtlr5h/49GOa1bM5myouQzEL1i4kqR6r HgtQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=a5lQYR/NyhmVIthhSbjnUt7AifzRLG0rqmFo6PchyxM=; b=k85eI13PDVm2x78R6KgVJ0XzhXHcHdVUTJtrzqpXAxPFWJPPqkmDb6YwSYYT7W5HCd N1WvUDpdwWdXj1rzJzTJIgJkRZviFw3WkDGFzM03GbXbwftyfyh1JTiV88uhv0GsOLU0 J4c14nqsjxIV5i71/Q37A5WgwZlpS3yRmRV1bTylArQdp0TIM0Wyew+NTSujIEmX47S6 IVk3ON34YpDwR4cFvX6Z+fpWyUJ6t6WDnjoGQld4wYiiuxI5c46RWICVzejwbSI76YFH 9y6SsEcfmPAk+O2jXiy2A2ZEHcuR1sG6wvqN96ebz1dr+U1Xhjb5MiVo+ff1lUwrJDGR qSgg==
X-Gm-Message-State: AOAM531yDOt7PRps+pH+O8UFBgjPeRzXOcli6HVTip3zrGxln5tPq/S7 M0+f1YZpLBwgt1F0W11Hco7fHLGzK7k=
X-Google-Smtp-Source: ABdhPJyK2Myyuk1D5NXiJ3CgNSmV5z2TIISr99AKPenYl8W82bCxfRZ+PHG6/fVyPdwe1O1eo9J7HA==
X-Received: by 2002:a17:902:407:: with SMTP id 7mr3585224ple.167.1597949463164; Thu, 20 Aug 2020 11:51:03 -0700 (PDT)
Received: from Melindas-MacBook-Pro.local (63-140-73-14-rb1.jnu.dsl.dynamic.acsalaska.net. [63.140.73.14]) by smtp.gmail.com with ESMTPSA id 5sm3808975pfw.25.2020.08.20.11.51.01 for <wgchairs@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 20 Aug 2020 11:51:02 -0700 (PDT)
Subject: Re: An IETF repository for working code in our protocols?
To: wgchairs@ietf.org
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>
From: Melinda Shore <melinda.shore@gmail.com>
Message-ID: <b973909d-eae3-3a9c-33ca-96d404757d6c@gmail.com>
Date: Thu, 20 Aug 2020 10:50:59 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.11.0
MIME-Version: 1.0
In-Reply-To: <CAMMTW_KVRVaz0tUXLaAQH2V0bY2ws+CZDy=XUKC=Jc3aiAU58w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/J5gnTI0BTMVHuLcA_eOPc-aR7Bo>
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 18:51:05 -0000

Hi, Vijay:

I've been following this thread and to be honest I'm not 100%
clear on the problem you're trying to solve, which makes it a
little challenging to figure out whether or not this is the
best solution to that problem.  I do share many of the same
concerns that have been raised, particularly about what would
be implied by having code included in a repository controlled
by the IETF, but I think more clarity around perceived benefits
would be helpful.

Melinda