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

Vijay Gurbani <> Wed, 19 August 2020 18:48 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 041043A0925 for <>; Wed, 19 Aug 2020 11:48:05 -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 5TWWjQ0Wtsk7 for <>; Wed, 19 Aug 2020 11:48:03 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::531]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0EBEE3A0882 for <>; Wed, 19 Aug 2020 11:48:02 -0700 (PDT)
Received: by with SMTP id i6so18957997edy.5 for <>; Wed, 19 Aug 2020 11:48:02 -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=mH8uDO8yjQNVkYAyeUDv93BHLIfcyM2ysP9+o255JPo=; b=iEf2L313i75cjpjWYyZu7pHw+sj34uMneN/qQLMcPVDCuC9QTL4wymKa3yCiODjzoU OfLOSl9wKbb1BecXVXYUAInQCQ1sZePEA9Gve0X8+LsiE9a4UuttekmPwxWmhO9+G1c4 maP0nqtTcYq6sgbrIlVoY11beXTil98c3L8KRNH6ozMMDN/CPRk/rV30L4ovs1l17Uu9 99fc+fCmlwLRICEBF9KxZMRMgCm8NJsa/7ntkYFG1SbaWPNlrxjBFgLPTKYcE4zrjFS/ DKUUChVk0gWnOQ5H97jhNyF0gmDOEQn6rQH4FqhljNvgXlzSoeZhVfOjbPz29FwU93yR drAw==
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=mH8uDO8yjQNVkYAyeUDv93BHLIfcyM2ysP9+o255JPo=; b=hSvjrf0xBoeH/IHvLdqYwL5TryZuXez3xSHr0tqNFOlAhZVqgl0xghl48/lxfol+ot eU3N+/9/UstGPlAMyHsidOmDwGXCNEZ6r9SghcKkdTp6FErvcwFe0nGugCNlVnWII4oI ppZ7fzR9x1H/uWR6bEMrAV+hbYNDp2aI/2DMGN3Jwg0hNIvzOpKk2lWvW+2k/bMfkPMY q9xyWgWDg2QGq3GbeiSVYIR0qWVT0SpnlyN27JHqYaUn3wXVtLelW2Obc0EsnxVsIbQH BPwu2D1WTgTjqkZfhHrMw9ti5Z9czxzHJG+kimlSVd8ENsAN0kLqYWYGLnd5LVMFTqt2 XVAw==
X-Gm-Message-State: AOAM531g91+ttsseVp5zqWoikhZuuYcuOat0B6ZYaBx8hEfRfNp3gx02 +pGyNCHEBx6XdKIoWYEFqO4XycQdVSweJaOXQ40=
X-Google-Smtp-Source: ABdhPJxXidzVJP9Y2zM99/7zJ8DDV6+MovotsP4s4c42lemfks4YiPUr+KdFFwfTgQAvBvSYbfg1AHkw9OMl5PJcmcw=
X-Received: by 2002:a05:6402:1643:: with SMTP id s3mr27098091edx.185.1597862881391; Wed, 19 Aug 2020 11:48:01 -0700 (PDT)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Vijay Gurbani <>
Date: Wed, 19 Aug 2020 13:46:32 -0500
Message-ID: <>
Subject: Re: An IETF repository for working code in our protocols?
To: "Deen, Glenn (NBCUniversal)" <>
Cc: Alissa Cooper <>, Martin Duke <>, "" <>
Content-Type: multipart/alternative; boundary="00000000000071f97805ad3f710a"
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 18:48:05 -0000

Dear Glenn: Thank you very much for your note.  More inline.

On Wed, Aug 19, 2020 at 1:19 PM Deen, Glenn (NBCUniversal) <> wrote:

> Hi Vijay,
>  In additional to the points others have made, I’ll add that an IETF code
> repository would need to carefully work out license issues and also how it
> fits into the IETF’s Intellectual Property set up that is managed by the
> IETF  Trust.
> [...]
There may be more that pop up once the topic was looked at deeper.
> I’m not saying that any of these are show stoppers, but there’s a lot of
> legal elements that would be need to worked out before any bits got checked
> into a repository.

Yes, absolutely.  All of what you listed are important and weighty
concerns.  But none of them appear to be insurmountable if we decided to do
this.  Clearly, the precedent set by IEEE and ACM in similar areas seems to
point to the possible existence of a happy medium, should we go this route.


- vijay