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

Vijay Gurbani <> Wed, 19 August 2020 16:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 502D23A0F5A for <>; Wed, 19 Aug 2020 09:08:03 -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 4V-7Leqe05-O for <>; Wed, 19 Aug 2020 09:08:02 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::629]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 74B4D3A101B for <>; Wed, 19 Aug 2020 09:07:59 -0700 (PDT)
Received: by with SMTP id t10so26947098ejs.8 for <>; Wed, 19 Aug 2020 09:07:59 -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=WqMNCIB9My00mGetUmY4duaTr2ik6N1w/4M8wWGOYDs=; b=iZ1GkLoUDRKZzr08r7fu27Mbm9ORdl9YQ+irOcFsH42e2NRc+zvFgV1eJkCVyqKYMX KwVBN7RpQRN4t2o6Iqe1nIAEgrUZ73VDzt0HHlJWG0YOXvOICUsX5gZAVkWS7blFm4i9 xT2oztanL4WjBMYm4q7cq++spCLaYzwVJwNQ6fZkTtgJKpJAgBr6YiICs1n+/K9u8aIk Sl9Jmu8AzNouWGXZBsVPSTcDwRBegJrKwbeism2q5EvRWjnc9yJF9a01fSIUPyeBE+tL dPqbY9uUQXGToEkKzjJbmwTiPocu0FpXu6xSmV5fuKOTIaC144XkFpg7f7xaoj5yjpfx 9Jbg==
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=WqMNCIB9My00mGetUmY4duaTr2ik6N1w/4M8wWGOYDs=; b=BehYDzyKZMepQ7BQIB8IXB153LWwjbvITNHm7jO4cYYcb1M1FskwtEbpRdeDodT/RN hf4n4MNE06szL3stOVf5WD6lEaHzatCrShudI/RJf85LdJ941YmBXvyc/u2Roe0rQm+v F4w7S57a/POV3FRLKxKdGmkfiwiy0keMtrFClPY5EqjEbmUY+0IX5lR+MlALKJ7vZFdl /hFjkdjswvhNcy8IMYWQup3ar0iOu9PPKyFoEBuHHa39d0lLopZjWjrOylx76ANg0eSW zWfeR9Gzk5bXS5b6ne62rwwaBnky/9VG8as3TSQfupDWGvM+KhMQ5vzTuU/VXRaoUtNj t0uA==
X-Gm-Message-State: AOAM531AxCNZbUdOdfS2IzIYSYHj/1MwWavLynmHyIJlkufTIBmorLiy UR0VOiRl9vKEjVOtBEE55ix9xKOJNTsIe0ku0YY=
X-Google-Smtp-Source: ABdhPJyKBPSslIWmSwEe0mcJPwJFYLCeqxpX/jVgdUPG0FYaLM1eA1saFDxvjXri5gX0ojYZYU73JVqj/41W3zIGdok=
X-Received: by 2002:a17:906:c34e:: with SMTP id ci14mr27344264ejb.335.1597853277886; Wed, 19 Aug 2020 09:07:57 -0700 (PDT)
MIME-Version: 1.0
References: <> <056801d6763c$f0296b90$d07c42b0$> <>
In-Reply-To: <>
From: Vijay Gurbani <>
Date: Wed, 19 Aug 2020 11:06:28 -0500
Message-ID: <>
Subject: Re: An IETF repository for working code in our protocols?
To: "Salz, Rich" <>
Cc: "" <>, "" <>, Martin Duke <>
Content-Type: multipart/alternative; boundary="0000000000000824d805ad3d3567"
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: Wed, 19 Aug 2020 16:08:03 -0000

On Wed, Aug 19, 2020 at 10:30 AM Salz, Rich <> wrote:

>    - We also (rather cheekily, IMHO) floated the idea that the
>    datatracker page for a document might also contain a link to the
>    implementation page (like it does for IPR disclosures).
> Note that WG pages and document pages now have flexible “additional
> resources” section for creating just these kinds of links.

Dear Rich: Thank you for your feedback.  Indeed, yes, we do.  But as I
replied in my earlier email, these additional resources are all but hidden
to those who know the IETF way.  Query your average developer in a company
and chances are good that they will not know how to navigate through the
IETF ecosystem to get to what they would like to have.


- vijay