IETF Logo Mail Archive

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

Vijay Gurbani <vijay.gurbani@gmail.com> Thu, 20 August 2020 20:10 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 2BC793A13E8 for <wgchairs@ietfa.amsl.com>; Thu, 20 Aug 2020 13:10:16 -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 R8mRmG3ePBDE for <wgchairs@ietfa.amsl.com>; Thu, 20 Aug 2020 13:10:14 -0700 (PDT)
Received: from mail-ej1-x632.google.com (mail-ej1-x632.google.com [IPv6:2a00:1450:4864:20::632]) (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 E33153A13ED for <wgchairs@ietf.org>; Thu, 20 Aug 2020 13:10:13 -0700 (PDT)
Received: by mail-ej1-x632.google.com with SMTP id o23so4024235ejr.1 for <wgchairs@ietf.org>; Thu, 20 Aug 2020 13:10:13 -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=tyYlKOdBWGjVIMLbgxzaOUss9OSRDSLxQaHwbSN7LPk=; b=hM6DNyRTFZUL6B6k5e7nk8hT8nFtXkVEtZ0cG13enfwcB9XtW0mG+huhjSxrAwr4LZ 9+Au6Wr1VMmZRyQN/3GW408V5W3YwaBP0mSEuvbAMqfj1IWL5e6d/vleEEByoJwy9FRs 2MBAW7Q2CtI58xLbMCWbPbFVFDzebw7XV59b9dVZIU+x5QeVwsVjEAXHMxlCMLtS5/wf q+EgdMrcWGmKXQur4wl/j3ptB+0D/gQoV/hndqh3m+sCc3cz/GxtliwCTuQEUW3OOPTg 189Bm8t3HvEh45DVcqQ1CQjs8sRuPcOvDbskJJj3T/YBAkqCID3IqV/amnhCFfS2JlXp Oi4Q==
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=tyYlKOdBWGjVIMLbgxzaOUss9OSRDSLxQaHwbSN7LPk=; b=DL4KoFq8nph0xWjG6BxMCaugpXx3ZPLv/pqWqe21iaf9cFlER9eef5yQf535Hxk6tW 7ds4sUm1k/YrvXXY/YFH8f3tG2JDqJikKHTucazfYMh60zBg9+1xLbB4VpuJG2yQfDQX jc2UOpV6JtlbJdgyi7EqqY/nDWiySx6G4vlgh4S7wFkEG0zwPzTPdrG+naV0Hb/qT9uW aHQE0QTUO/dUZQ900ff9sgFI/Pb0jc1BCdmlaZEYKTiQECZRT+CgdIHmvSlhY8qqPRYI 6SCmI9SqaDIT9BIGgv/m+pxL4f+ubjjnvGJM2WnyyzvYAgVOLG2IdjJ5mj14qFDh27T9 Wwdw==
X-Gm-Message-State: AOAM533nsqfp330lRGmS064OUHwSNqQ0S7QpqpXBL3DSUYes/5apmXBm vEK4DdvMfgNB0vTx9flqvCIugCGSp414/p3xrUQ=
X-Google-Smtp-Source: ABdhPJzU15cGUppl3hyA2SeCcUU78GZNvUCiuoowAOSx3vl0pzZ9nX8BxpGXDOCc7vf7iBSmX3naTKeVAktrvxzcyiw=
X-Received: by 2002:a17:907:2082:: with SMTP id pv2mr355851ejb.188.1597954212261; Thu, 20 Aug 2020 13:10:12 -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> <7B2534FB-5044-45A3-94E0-F81483E8F743@akamai.com>
In-Reply-To: <7B2534FB-5044-45A3-94E0-F81483E8F743@akamai.com>
From: Vijay Gurbani <vijay.gurbani@gmail.com>
Date: Thu, 20 Aug 2020 15:08:42 -0500
Message-ID: <CAMMTW_J3caWM2Vz6NaG_U7=QWwkCwg5mvsirHvNYxZ367VZ9Og@mail.gmail.com>
Subject: Re: An IETF repository for working code in our protocols?
To: "Salz, Rich" <rsalz@akamai.com>
Cc: Mark Nottingham <mnot@mnot.net>, IETF WG Chairs <wgchairs@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003072a405ad54b541"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/3KGDPoR9fhvYBF73kbHKrbvptKc>
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:10:18 -0000

Dear Rich: Thanks for your time; please see inline.

On Thu, Aug 20, 2020 at 1:31 PM Salz, Rich <rsalz@akamai.com> wrote:

>
>    - I maintain that the average developer who is implementing an RFC
>    will not, on the average, have the required background to know where in the
>    ietf.org
>    <https://urldefense.proofpoint.com/v2/url?u=http-3A__ietf.org&d=DwMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=4LM0GbR0h9Fvx86FtsKI-w&m=7OS-Ssh5clxZ5_hRwIAmZPGsyCme5AoxJiHn5hU9ysc&s=UCRGl3jyjE8QIb-sDIRsf66T4SAPkjdN5TecABoYqR8&e=>
>    domain it should go to in order to find all of these additions.  They will
>    only know one thing, the RFC.  They will know the errata associated with
>    the RFC because a link to the errata is on the RFC title masthead.  It will
>    be great if there was a link to some starter code for new protocols.
>
> RFC’s can trivially have a non-normative appendix of links.
>

Yes, absolutely.  The problem is the quality of the links external to IETF;
IETF has no control over these.  On the other hand, IETF has control over
everything under the ietf.org domain.  So hosting something under that
domain implies the permanence that is lacking with other approaches.

Thanks,

- vijay

v2.23.0 | Report a Bug | By Email