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

Vijay Gurbani <vijay.gurbani@gmail.com> Fri, 21 August 2020 01:34 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 4B5323A0FFB for <wgchairs@ietfa.amsl.com>; Thu, 20 Aug 2020 18:34:34 -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 qfZ548fDUgtq for <wgchairs@ietfa.amsl.com>; Thu, 20 Aug 2020 18:34:33 -0700 (PDT)
Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [IPv6:2a00:1450:4864:20::633]) (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 EF8E83A0FD2 for <wgchairs@ietf.org>; Thu, 20 Aug 2020 18:34:32 -0700 (PDT)
Received: by mail-ej1-x633.google.com with SMTP id bo3so440213ejb.11 for <wgchairs@ietf.org>; Thu, 20 Aug 2020 18:34:32 -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=C3uNiPNLeBFKxfS5B5x8n4pA0PkHx0d/rYRXQ/C9vRg=; b=XnT1rrxXGKlbgB128388iy/1V2LFdgd3e+ISNiJRzW96JIeSYNVfgbyNyQYC3BXg0e TRrcOAX0+yroNfMHd705sFCsRWrjKFhgUtsRtMKRt8A+/+RkeUbXB7OVS6VLFnX4XZR+ OpBEVu2wGLe6XQB7a6jWXHhR5lnIdaqmhwZ4VRqCb29MKEfpKEoty74Jp7CqYvej1ASD w2pmfXke9xtBgy+tPHSyTbkdslxL1reHFWZ5xp10GxjynH4eheqL8gdYW72VWCntkAae Qz7i3rOCzsZjjVLeAku/F6pLmB9LKn4iKWKCnXm7MLXuEsNyHqfu8SZ2d3bQYRdLEvmt mcTA==
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=C3uNiPNLeBFKxfS5B5x8n4pA0PkHx0d/rYRXQ/C9vRg=; b=I7JSdcgs8CSzAF3cR4NAubFoQ12jsUjNcPzKav/GWkkOGAfdQ/H8eqa4AWxqp4BT2V R+e8Xp2xi0B5usy58+CZzsSpv2d6vVgFcNThJW6HMQjpT0YPgn7c4KTMbbTf+QlyVyOx UGddaUv5Rz0GokoOJ1VEG3U+XD6DCTLA+hoyMtkIcbIqWBElJfAhv+y2e5MVmmQpkTpB NIZwTbKWf5Mxs0aOvJxrEyVPw1zJuGH78rtv/KOQjRmuB1/DdmbRS8AT9cHsbeYwD3eq 9HlBW+UWVF/Y/TzlvX81XAOQ/Xb+wWf0kIqyg+3c5DztzjlMnJp3irampey6jugPQI9X imwA==
X-Gm-Message-State: AOAM5318u1brFJoqVrBiF7eo9h7KhznbrqfxYTFNT1BhX/ylqKkVQe85 6QS87HFSoU/UgeC9SlnnCuLRCeA75A5WewdshxU=
X-Google-Smtp-Source: ABdhPJxtqnf1RnGX7nNOIZRmVaaQ+2Wr34gjwHkzQHAR35OogIP2BMQOuX9KRyA/w4z48Qchc4uzz1z2BoZoqVh3gr4=
X-Received: by 2002:a17:906:4f8c:: with SMTP id o12mr684699eju.69.1597973671379; Thu, 20 Aug 2020 18:34:31 -0700 (PDT)
MIME-Version: 1.0
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> <6b2b4391-3b63-436e-f517-b0a97a4fcf9b@gmail.com> <CAMMTW_+FHEso7_PhFUyjuPG605YFYuG8bOvpmBKxZWgtcHwAzw@mail.gmail.com> <376c20c9-cdd3-79e2-b562-82361ce1b1ef@joelhalpern.com>
In-Reply-To: <376c20c9-cdd3-79e2-b562-82361ce1b1ef@joelhalpern.com>
From: Vijay Gurbani <vijay.gurbani@gmail.com>
Date: Thu, 20 Aug 2020 20:34:21 -0500
Message-ID: <CAMMTW_KwvHJhEswZdwex1t1bZefhA3Vp5SWqZ4Tyujw4hDYNww@mail.gmail.com>
Subject: Re: An IETF repository for working code in our protocols?
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Cc: Melinda Shore <melinda.shore@gmail.com>, IETF WG Chairs <wgchairs@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000b082e05ad593da5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/phaK5ZWF8VnRLYXpne2VVTUFyak>
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: Fri, 21 Aug 2020 01:34:34 -0000

On Thu, Aug 20, 2020 at 6:05 PM Joel M. Halpern <jmh@joelhalpern.com> wrote:

> Vijay, I do not see how the code quality things is too work.  While I do
> not like the idea, if the community wantede it I could see the IETF
> providing repositories for any code that claims to implement  specific RFCs.
> Even if we were to do that, I can not see how or why we would want to  get
> into judging the quality of the code.   that sounds like a recipe  for
> disaster.
>

Dear Joel: You are absolutely right!  We do not want to get into the
business of judging the quality of the code.

My response to Melinda that included the "high quality code" phrase was
mostly driven by the Gen-ART review I did that triggered the thoughts I
have attempted to capture in this email thread.  The code pointers
mentioned in that I-D in the "Implementation Status" section appeared to be
of good quality.

But in general, if we embark on such a code repository, then we definitely
do not want to undertake a code beauty contest of any kind.

Thank you for your time.

Cheers,

- vijay