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

Vijay Gurbani <> Thu, 20 August 2020 20:42 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CE9BA3A1401 for <>; Thu, 20 Aug 2020 13:42:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.097
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: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id tOVq42RwaX91 for <>; Thu, 20 Aug 2020 13:42:21 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::631]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DE9F43A09A0 for <>; Thu, 20 Aug 2020 13:42:20 -0700 (PDT)
Received: by with SMTP id m22so4059252eje.10 for <>; Thu, 20 Aug 2020 13:42:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=osUCAqqmQCHKJwFiqcNPuPGAaqOPmj85gzQ7J/PG+TI=; b=d5b5YDZZM0flHb5ZZbTDr9z5fdNhFUkY9/T8+MNxa0CcBhf+JXL9yBPznhLJwJdF+Z z7lEws9yUlMGj4GaRCp6wACzg2Iq3QhO4lwY3cfgsP+8sTnfz+PygTWwpcUnwDNx6el8 S5Mgt/pEEVnTZbQM85eObF/qsScryu0L1yBf5MbFNCF6loD5MFObzWp8DUYtwUHqweZu zaNfChzYdUrwRvhIV12wq+wqLs1D301VhvRvVL882bt19VAr4VgNZT7rFbGeKuN//GR0 fFInbXQNZ3LL6rKh38bXEN9nOT0tBYe3eCuT0P4IXCgrn4qsgL3W7kz4zX87fdxtYW6o pWug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=osUCAqqmQCHKJwFiqcNPuPGAaqOPmj85gzQ7J/PG+TI=; b=Oy0zTFAQMxH0gqX/3MO816ot1HZ2FyMPWVt+VVMYTqVQoXw7YT9wakPIcHTkxQRfOB KNE15zM7Lqq/wLxTAExT6C0xcjviNwyLoRpZqxPpW2Y4VmaDChXC1cROEMkSL5LJSmSU ECm/RAOo59PmKLiuxjw9YF5oJoMI1EKVdcQxyuGXFi8smS8Z2J63BKBEJLouwrxM62BL DluEdQaQ3X+/baaGqRfL1om7MwBqyNxbQLSnQn+JiaMUHDOgYTgxrsz69LtjGtuZCoLU cfiux4ITg4U7irELE37hEDZDdH95ApxU4HGnqZaWPmQbxH83qX3aCUbtr0fTEB+ZPF3l mDdg==
X-Gm-Message-State: AOAM5315fu1B4IT6eJEtH4I+Nw2OGJ1qX5kHayfAVia+T2kBqYajEfAC OO2m/fgHyzxexS3JWS6uP3zmuWkj9ALjBC1sshpMzAbmXKG0bg==
X-Google-Smtp-Source: ABdhPJz4uRFwkgJ0KKXtoSldYZ60x+rYNc4jCSeaFmWKW7vbxvTc0lKmtf8joKtyjzFQ7qaK+5SpECMFN1/P8V6zVPk=
X-Received: by 2002:a17:907:2082:: with SMTP id pv2mr466994ejb.188.1597956139444; Thu, 20 Aug 2020 13:42:19 -0700 (PDT)
MIME-Version: 1.0
References: <> <21487.1597887258@localhost> <> <30258.1597954601@localhost>
In-Reply-To: <30258.1597954601@localhost>
From: Vijay Gurbani <>
Date: Thu, 20 Aug 2020 15:40:50 -0500
Message-ID: <>
Subject: Re: An IETF repository for working code in our protocols?
To: Michael Richardson <>
Cc: IETF WG Chairs <>
Content-Type: multipart/alternative; boundary="0000000000000eef8205ad552865"
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 20 Aug 2020 20:42:23 -0000

Dear Michael: Thanks!  Please see inline.

On Thu, Aug 20, 2020 at 3:16 PM Michael Richardson <>

> Vijay Gurbani <> wrote:
>     > In the days when code lived at, the Internet
> had
>     > equivalent tools to find it.  Remember gopher(1), and archie(1), and
>     > veronica(1).  They were the github of their days.
> No, I was there. They sucked for finding out where the latest patches
> for the foobar project is.  You couldn't submit patches or bug reports or
> anything to those FTP servers.  The code got unknowingly forked multiple
> times.

Sure, but those were simpler times, and in their context, the tools held.
I remember when rsync(1) was a wrapper around cvs(1) (the version control
system); collectively it was called rCVS.  It took a bit to get it to work,
but it did work, and provided the illusion of what git(1) and hg(1) provide
seamlessly today.

> I'm not really trying to make a value judgement: just observation.  I'm
> trying to say: if there is a community active around X, then X won't appear
> orphaned.  If there is no community around X... then maybe people voted
> with their wallets (mindshare) already.
> For instance, can you find the latest patch set for Pathalias? (why would
> you care?)

Perhaps we don't need to anymore, if Pathalias has been successful.  If I
go back to when we were working on SIP, having some code to bootstrap a SIP
implementation would have been invaluable.  As the protocol became more
important, other high quality  open source and closed source
implementations appeared, obviating the need to have bootstrap code.  But
there is a need for one when a protocol is finding its footing.


- vijay