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

Vijay Gurbani <vijay.gurbani@gmail.com> Thu, 20 August 2020 17:09 UTC

Return-Path: <vijay.gurbani@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 C19313A0D25 for <wgchairs@ietfa.amsl.com>; Thu, 20 Aug 2020 10:09:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 Cjo4d5dal3Ti for <wgchairs@ietfa.amsl.com>; Thu, 20 Aug 2020 10:09:02 -0700 (PDT)
Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (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 5F1F93A0D1E for <wgchairs@ietf.org>; Thu, 20 Aug 2020 10:09:02 -0700 (PDT)
Received: by mail-ed1-x529.google.com with SMTP id w2so1938150edv.7 for <wgchairs@ietf.org>; Thu, 20 Aug 2020 10:09:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=tAvYv0ABJpKYjBm1xjctLfXZSJqqDV7jbfYPLmX8u6o=; b=uiT/zQUBVeq4gePZImQj33ZISN/JCP1Ue2r5IwuX6QWUbtzPVNO3kj9ET9GDRUDBi4 0Eqlg9ppfSr2bmslOdp6chJw+x4WPlTGUmfK7D/dsTAyeP3dOlPqrkfoZEOdc6oQ71Mf oA+UvGXQte2s23ZH/GOoDKzLrIdFxt7QW1vSCAIuORUGR4bKZFYkPUwqCsvzX/n5Z9zR VMo323Vf3CUlBahS9ggaK0rr9PxVKGnBSkGx+XxZVKRdnt43ziYgY7S9JX9Nt7i6ODdJ 1Yt+NpeQU+cRvCtFatjgrmN1qwzzuHlKGp7MlGSn31QiKU1ZcjGU9dUqUaF6eKWTSvbP G9pg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=tAvYv0ABJpKYjBm1xjctLfXZSJqqDV7jbfYPLmX8u6o=; b=HLsSNA2j9FO0B4ykmQVVsTX302hERBxIWtiI3zVKIfjbc4SqEcNTyEq0g/uIXdANQc ldexKhI/dHGJgCVQrGA282wkYaPyoLH4VmgTeQFhCglc5JdCkx8Or+goUkYMOFJpwCfG oUPr0dj+vBmvrQu09Kgf2ku3r3DTbPtynFKSjVbD/p3+EbidwrZhcuxOlAN+i7ldKgQ8 O9yRRADKAJ0yEBjGoH8wN6QrYg7LvKXaJCkeRX7tqcDS8xIT9cEI6IR8x5+drOCt/lt1 Zp7OWsKBPspcI+5RsLhqxZlYSTM0kmfOTYtIXyw7aGFwczkCwA8J+eUKndLldcateVc5 afSA==
X-Gm-Message-State: AOAM533Fym3R0BlsPE0t608Uq6/t2dszZE0qzZxcJbLf3HT8MovrTZXJ 18hAVjIFTOpin39YDCf4sYBHPXTTuASYcmr0zLA=
X-Google-Smtp-Source: ABdhPJxvew49dddq+3ScIn659e8k0Dnd+tUrXOu16Zd41E+MaCyjA3KMfmnqhHZhJ7KIpyAc/pKKXxAKkFsMLmoM1K8=
X-Received: by 2002:a05:6402:1a57:: with SMTP id bf23mr2274993edb.185.1597943340877; Thu, 20 Aug 2020 10:09:00 -0700 (PDT)
MIME-Version: 1.0
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> <9AF9FB0F-B620-4C66-AC5B-A14AC4FBB34E@cisco.com> <20200820151841.GW62842@faui48f.informatik.uni-erlangen.de> <E00EBF47-01E3-4D97-BEEE-C6B9C15D1449@akamai.com>
In-Reply-To: <E00EBF47-01E3-4D97-BEEE-C6B9C15D1449@akamai.com>
From: Vijay Gurbani <vijay.gurbani@gmail.com>
Date: Thu, 20 Aug 2020 12:07:31 -0500
Message-ID: <CAMMTW_+2nn=Y5c6EQZtPFZBs87YJvGUg-jdr_Xu-Ke+nNO2rMQ@mail.gmail.com>
Subject: Re: [irsg] An IETF repository for working code in our protocols?
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
Cc: Toerless Eckert <tte@cs.fau.de>, Eliot Lear <lear=40cisco.com@dmarc.ietf.org>, "wgchairs@ietf.org" <wgchairs@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000344a7005ad522d5a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/DgF9oyyv_X2JnhThcuRGd85xYZ4>
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 17:09:04 -0000

On Thu, Aug 20, 2020 at 10:40 AM Salz, Rich <rsalz=
40akamai.com@dmarc.ietf.org> wrote:

> There is ongoing tussle with one person in the NTP working group who keeps
> calling their code "the NTP reference implementation." I would be cautious
> about enabling others to do same.  Yes, for many years TLS was defined as
> "works with OpenSSL" and I don't think most folks thought was an ideal
> state either.
>

Dear Rich: Indeed, I agree.  This was the implicit "advertisement" part
that folks referred to in earlier emails in the thread.  I think it can be
managed (don't know how successful we will be at it, though).

Thanks,

- vijay