Re: bettering open source involvement

Brian E Carpenter <> Mon, 01 August 2016 20:44 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4F35A12D98A for <>; Mon, 1 Aug 2016 13:44:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 7QSYRDm_UyQb for <>; Mon, 1 Aug 2016 13:44:47 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:400e:c03::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 28CC112DA1F for <>; Mon, 1 Aug 2016 13:44:47 -0700 (PDT)
Received: by with SMTP id b2so3276376pat.0 for <>; Mon, 01 Aug 2016 13:44:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=G67CizrFdBms2JXGP4tG8YV/ibct6oZyfUmilPqeFzg=; b=JSxjCi2XxPQ5Kkz+HdgObFN6ENcf+ZfWQs6U2B6XU3TYKJUcPyDzlw08zuMAY7i4C6 BQki/cvRD9bvVKdjhb1VmOCcXleXV07bd2izpWDFbJNe1uF+r55NEp0Yzah90WLn21+a yjadohEUXg4pzueITj6k/KMlnKtWMITXcsFg81ufPxjftPdGgkIeUgud/1z+wY/J4POk gfStcfVDCxGprIYdgQCyK8ShrQZ7cRzVRwYEsc9ICerQsHKtYRVRlQNPjaUu4DeMmWtp twusJSX750O+BZV5wBSD4MabLWHbaji20+x3NDUbui9UBoRw994ANMb7SgjGS2dIrk2K +Drw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=G67CizrFdBms2JXGP4tG8YV/ibct6oZyfUmilPqeFzg=; b=ZUTqNPG8kS5dT15mhcYR/xBfR6jEuvM26+Zrxg/222zqj4hGf8wXELrfdM9xrtRVAn J3sMn2I2idUYZBcw4U2NG0riDokJinJIbnDLdAVOEh0V1509EP0u5TFDy3P2Pye+sB2N KkU9z+NdYct3XJ7yt49iJWyOhPkMi781SsPxWMLyVySLW3uJVDhENp0d27l9nS8BBwW8 nl7jTFqN5tD2A45QP0fnxJkDQaQiMKflyxKJFYn2BmS3XlNZNzKYWreU5zAuh5EagzuW u2CEWemfsSWOxWtcj1kKBRaZaxHz0H24/fWnIFQyGWwTSwEbyuysEoPJbbXmW6/86i0f GQ5A==
X-Gm-Message-State: AEkoouvebYDwKq3vK5WDpfrA5JcFivpI4uoGma8Ju2lewRKhaMVOr/VobN8C+mtiEyQdhA==
X-Received: by with SMTP id eh8mr99450147pac.146.1470084286569; Mon, 01 Aug 2016 13:44:46 -0700 (PDT)
Received: from ?IPv6:2406:e007:5f50:1:28cc:dc4c:9703:6781? ([2406:e007:5f50:1:28cc:dc4c:9703:6781]) by with ESMTPSA id q1sm47753892pfd.48.2016. for <> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 01 Aug 2016 13:44:45 -0700 (PDT)
Subject: Re: bettering open source involvement
References: <> <> <> <>
From: Brian E Carpenter <>
Organization: University of Auckland
Message-ID: <>
Date: Tue, 2 Aug 2016 08:44:45 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <>
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 01 Aug 2016 20:44:49 -0000

On 02/08/2016 02:36, Eggert, Lars wrote:
> Hi,
> On 2016-08-01, at 15:44, Livingood, Jason <> wrote:
>> What if, in some future state, a given working group had a code repository and the working group was chartered not just with developing the standards but maintaining implementations of the code?
> as an addition to developing specs, that might be useful, if the spec remains the canonical standards output.
> "Go read the code" is not a useful answer if the code comes under a license (such as GPL) that taints the developer. 

This is a *very* important point. If an IETF WG sponsors code development, it needs to
be under an IETF-friendly licence. One way is to post it as an I-D. Another way is the
BSD 2-Clause "Simplified" or "FreeBSD" License. GPL is not a useful option.


> (This is a major reason what we are doing IETF specs for DCTCP and CUBIC - so that they can be implemented without needing to
read Linux kernel code.)
> Lars