Re: [Edm] A modest proposal (?) for archiving code

Tommy Pauly <> Mon, 31 August 2020 21:57 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 529A53A08DB for <>; Mon, 31 Aug 2020 14:57:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.102
X-Spam-Status: No, score=-2.102 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id RgIevZA7vPC2 for <>; Mon, 31 Aug 2020 14:57:56 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 757FC3A08C3 for <>; Mon, 31 Aug 2020 14:57:56 -0700 (PDT)
Received: from pps.filterd ( []) by ( with SMTP id 07VLrqP1013108; Mon, 31 Aug 2020 14:57:53 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; h=content-type : mime-version : subject : from : in-reply-to : date : cc : content-transfer-encoding : message-id : references : to; s=20180706; bh=ZZzQ3ODByhr7MsBex7mq9nJV/KdCuaxFrjzgXfZje5c=; b=ij5iKdBrZEWX7C+H/W9FHaNYUDreA58i8X7ZJTlsJbir40aBayOefkShCB1aR6YEMemi ZaovjUyfWURwGnM6QFG1b/tB0VpIxbTWW5WiamDlipgHQQXd2rHp0gjsLAh1h+w+ClZ6 qlFBorpU5jGWtVli6DJtClMOEA0P/g4wR/GgZfs8Prffu1elNIt0RNHpKxOOeCloMvo7 BM7j6FcgV7j8eUpEi2fzlknhzvYMl1f1qlh05hlyxVjUupr6YJQ8LLyokuhf2MRU0Qk8 Qf92Df21/q/m7whapg4cfTcoQts1d/sX/6nsn9+Lhc1lqBxyiSNmoycBJF+iG2fLnlc+ 4A==
Received: from ( []) by with ESMTP id 337p0u5sa9-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 31 Aug 2020 14:57:53 -0700
Received: from ( []) by (Oracle Communications Messaging Server 64bit (built Jul 29 2020)) with ESMTPS id <>; Mon, 31 Aug 2020 14:57:53 -0700 (PDT)
Received: from by (Oracle Communications Messaging Server 64bit (built Jul 29 2020)) id <>; Mon, 31 Aug 2020 14:57:53 -0700 (PDT)
X-Va-T-CD: da535c4073f98b0aaf118f024224a2bc
X-Va-E-CD: afe280754a635ec45f4a2165ad073415
X-Va-R-CD: f0b5c6ca852f0fb4c68db7be83cb27e2
X-Va-CD: 0
X-Va-ID: 48cf2d65-cd7a-4351-a290-b683b1eaf2e7
X-V-T-CD: da535c4073f98b0aaf118f024224a2bc
X-V-E-CD: afe280754a635ec45f4a2165ad073415
X-V-R-CD: f0b5c6ca852f0fb4c68db7be83cb27e2
X-V-CD: 0
X-V-ID: a88c4e02-bd61-4f97-962c-04fcf5fbe339
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-08-31_10:2020-08-31, 2020-08-31 signatures=0
Received: from localhost.localdomain (unknown []) by (Oracle Communications Messaging Server 64bit (built Jul 29 2020)) with ESMTPSA id <>; Mon, 31 Aug 2020 14:57:52 -0700 (PDT)
Content-type: text/plain; charset=utf-8
MIME-version: 1.0 (Mac OS X Mail 14.0 \(3654.\))
From: Tommy Pauly <>
In-reply-to: <>
Date: Mon, 31 Aug 2020 14:57:51 -0700
Content-transfer-encoding: quoted-printable
Message-id: <>
References: <> <>
To: Mirja Kuehlewind <>, Vijay Gurbani <>
X-Mailer: Apple Mail (2.3654.
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-08-31_10:2020-08-31, 2020-08-31 signatures=0
Archived-At: <>
Subject: Re: [Edm] A modest proposal (?) for archiving code
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Evolvability, Deployability, & Maintainability \(Proposed\) Program" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 31 Aug 2020 21:57:58 -0000

RFC 7942 does mention the direction of adding metadata to an RFC in the tools view:

"Later, the IETF Tools may support this
   functionality, e.g., by including such a link in the HTML file of the
   document, similar to the IPR link.”

It certainly is frustrating that different views of RFCs show different metadata, but if we had more formal repositories of implementation information, I think we’d want to be able to link to them.

A step can be figuring out how it would make sense present implementer information in a standard location and format, and we can figure out how to best tie it to documents next.


> On Aug 31, 2020, at 3:25 AM, Mirja Kuehlewind <> wrote:
> Hi Vijay,
> Thanks for bringing this discussion to this list!
> I agree with the goal to make it easier or easy for implementors to find reference implementation or any kind of existing code. However, I'm not sure if putting this information in the RFC is the right approach. As you mentioned errata below, this are actually also not part of the RFC itself but only the metadata and it depends on the page that you look at if you see them or not. That a separate problem but I just wanted to underline that putting more information in the metadata might not be the right/only solution. I guess as a first step it would be nice get a better understand about how people usually find and use RFCs and maybe also how to redirect people to the right page then.
> Mirja
>> On 28. Aug 2020, at 17:12, Vijay Gurbani <> wrote:
>> All: I proposed what I write below in the WG Chairs list; the list saw a good amount of discussion, ranging from summary dismissal to exploring the issue further.  One feedback from there was to engage EDM.  So here we go.
>> Let me provide some context below, including links to the postings on the WG chairs list for those of you who may be interested in exploring that discussion further.
>> The genesis of what I am trying to affect is simple: We produce standards that describe protocols. As a protocol is being defined in an I-D, there are often implementers implementing the protocol or portions of it. These implementations are important, enough that RFC 7942 [1] recognizes the import of these implementations and exhorts I-D authors to create an"Implementation Section" to document these implementations. RFC 7942 also asks I-D authors to remove this section before the I-D becomes an RFC. My question is if there are implementations that are worthy of being mentioned in an "Implementation Section" of a I-D, why don't we preserve these implementations in an IETF repository and link the repository in the RFC.This way, new implementers of the protocol can quickly bootstrap their implementations, leading to a diversity of implementations, which can only be good for a protocol that is trying to find its footing.
>> Why is this important? Simple: Reaching out to developers outside of those of us who are already in the IETF is my biggest incentive. They are the ultimate consumers of what we produce.
>> When I talk to developers at companies and students at universities, if they have heard of IETF at all, it is mostly through knowing that someorganization called IETF produces these things called RFCs. That's it.Perhaps for them that is enough. And if you buy that argument, then the corollary is that we should do everything in our power to make sure that they have all of the information they need to implement the protocol from the RFC itself. Consider the errata we maintain in an RFC. Imagine instead of us providing the errata, we simply told implementers that it is out there, go find it. The errata is important, so we list it in an RFC.When a protocol is finding its footing, early implementations that allow other developers to understand its behaviour and derive their own implementations from it is also important. So why not formalize the process of archiving implementations that are worthy of being listed as per RFC 7942?
>> People have pointed out that we have WG pages, Wikis, datatrackers, and other such accoutrements for this purpose? WG pages, WG Wiki pages, datatrackers, all make sense to you and me. Many people will like to implement our protocols without burying themselves deep into IETF to know the difference between a WG page and datatracker. Their visibility into the IETF is through the RFC. So, put as much information in there that will make a developer productive.
>> I don't claim that this will be easy; the length of thread discussion in the WG chairs list indicates the passion of the participants around the issue. However, I don't think that the issues raised are insurmountable.  The fact that an entire RFC [1] was standardizes around the issue leads credence to the fact that it is an issue deserving some sustained attention.
>> My initial email that started this discussion in the WG chairs list is in [3]. It has more information and context, including how organizations like IEEE and ACM have dealt with similar issues.
>> [1]
>> [2]
>> [3]
>> Thanks,
>> - vijay
>> -- 
>> Edm mailing list
> -- 
> Edm mailing list