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

Melinda Shore <melinda.shore@gmail.com> Thu, 20 August 2020 20:42 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 55B3A3A0DB0 for <wgchairs@ietfa.amsl.com>; Thu, 20 Aug 2020 13:42:56 -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 Jssg6AoPxpmx for <wgchairs@ietfa.amsl.com>; Thu, 20 Aug 2020 13:42:55 -0700 (PDT)
Received: from mail-pf1-x42f.google.com (mail-pf1-x42f.google.com [IPv6:2607:f8b0:4864:20::42f]) (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 78E9E3A09A0 for <wgchairs@ietf.org>; Thu, 20 Aug 2020 13:42:41 -0700 (PDT)
Received: by mail-pf1-x42f.google.com with SMTP id 74so1605848pfx.13 for <wgchairs@ietf.org>; Thu, 20 Aug 2020 13:42:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=S9XTJw60g/r0kTu3ENN+ZsyElo2xx6lvszXeZco2XbI=; b=sZt0+hSnRE2nDgLrdMDQDvURkHHQBJtHI/oE4ZPTdDkI91vyipVaVAQZce3e/Y+y1L sVrkLDr8MzR3T9tpjRs0uyh1yYqXY9/uvmJPX9GHE02b61ukBFfNshC6vLOHtusH5cSg tiB0b7++Qi9hMBxM/cQnyb4VYS1ZMOvs7wuwe+Eh2qIhPxEbaLDlN2cVgAerP41hpl6h Afetb2FDY6kZIjEAetTCNx61yCQQ2tDvtBWcQpp1o9wn87EavZS9oiEHS4ubCc/M3D0g ZerLZNMQjzxV6P2epXWIV6R7mGRapyRbB7gpci4XCXSR6XECzFTgxKWKWYpcq34EmsCU EfZA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=S9XTJw60g/r0kTu3ENN+ZsyElo2xx6lvszXeZco2XbI=; b=dkCMQX2yOeBq3OoMMQncgtjmBC7qMkmo1qydhOjsAqHA3tI+lHc3/u/MfKvn/1E+P5 +opYid8TU+bAr6CDMOGy4HpoAsLQBv/3rlBKSrwv3XdDUuyzuXmNUcaYLXk5mqg/IhO6 iuQ4XxxPDatRwfHdx/lQPeCAKuCVXl34x4b8YJYaWyyySgYf9klVnB/gs8GJs3DhmLRX J6DqbOhivdaSjh9lnKkGe3YPBE4QfU/eCKl5G7mievlGbkOrbPhzn4WnDl9OAnCb6Fvi Vq143/G/mKkfosSXADwE44MEr021MKKw8EIGyF3v3t4uRuTGkY9c55fRvpyNfdVX2NKq 2uZQ==
X-Gm-Message-State: AOAM531PPznLwtueXZcHNg4zQnYbYd5ZONVmxmP4yH1hQySscHb7FZ2a yfpt0LjRXFvE1lSzti7erOQ+2doYAQw=
X-Google-Smtp-Source: ABdhPJxL1ynWLOiKAjD2TMyLSQjkLmRYt5UbrqZ8J2rBLz6/At2iDotSeorTV6eEkU48cRKNgh4sjQ==
X-Received: by 2002:a63:5c08:: with SMTP id q8mr420874pgb.222.1597956160428; Thu, 20 Aug 2020 13:42:40 -0700 (PDT)
Received: from aspen.local (63-140-73-14-rb1.jnu.dsl.dynamic.acsalaska.net. [63.140.73.14]) by smtp.gmail.com with ESMTPSA id 144sm3673189pfu.114.2020.08.20.13.42.38 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 20 Aug 2020 13:42:39 -0700 (PDT)
Subject: Re: An IETF repository for working code in our protocols?
To: Vijay Gurbani <vijay.gurbani@gmail.com>
Cc: IETF WG Chairs <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> <b973909d-eae3-3a9c-33ca-96d404757d6c@gmail.com> <CAMMTW_JpZLjNx75_S1CQitoi2E_CaPZCLbVPhqqAAcpe2=mq5w@mail.gmail.com>
From: Melinda Shore <melinda.shore@gmail.com>
Message-ID: <6b2b4391-3b63-436e-f517-b0a97a4fcf9b@gmail.com>
Date: Thu, 20 Aug 2020 12:42:36 -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_JpZLjNx75_S1CQitoi2E_CaPZCLbVPhqqAAcpe2=mq5w@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/mmAXzVQ5sltHmdC-RllSu1Znoxo>
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 20:42:56 -0000

On 8/20/20 12:28 PM, Vijay Gurbani wrote:
> So the problem is simple: When we have high quality implementations for
> certain protocols that we standardize, can we come up with a place to
> park these implementations so they can be used by implementers to get a
> head start? 

TBH you lost me at "high quality."

Anyway, I'm still unclear on why this would be a sufficient
improvement over existing mechanisms (basically, open source +
decent search engines + WG wiki pages with links to implementations
and other resources) to justify the effort and possible legal
complications.

Melinda

-- 
Melinda Shore
melinda.shore@gmail.com

Software longa, hardware brevis