Re: bettering open source involvement

Brian E Carpenter <> Mon, 01 August 2016 23:06 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2625012D732 for <>; Mon, 1 Aug 2016 16:06:19 -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 1kJ9IqbE6O-D for <>; Mon, 1 Aug 2016 16:06:18 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:400e:c03::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B25F712D615 for <>; Mon, 1 Aug 2016 16:06:16 -0700 (PDT)
Received: by with SMTP id iw10so56773326pac.2 for <>; Mon, 01 Aug 2016 16:06:16 -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=1OhIjSfvvdnP0U4GoClvXd1FUSPTMtcdOrnGU09oRnk=; b=McDZ9grpi6gu2CKxCOs1GIhhdT1GP7eQLI+DQhJ5NhmrME4W0Gw1EATW/bEMyoQ45b KDnx8f8qX1jMliKIo3Xbx8WliQ5assYcmR8nz2yaZsacW6tof+5nNwNWt6kBBheXi/Fy HcJK3vxs6uu3yAlX/pufmodV6so1IhBE3zCHRq7+jIH1CvtyLajs4bLtilizyWWulOQQ 6pGb+ii99bAbAFFD2j8w5b0fsoV4jBVjoqI1oVJ06bAx+DI205xsnXGq2GPOV1PI5Luw dJeMzVoyAjPAmkO0C09TYUz82n2CwwlTEoCPQrOX0U5v0N9+Vm41tV4iGyM0s/mTRaV5 SC7w==
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=1OhIjSfvvdnP0U4GoClvXd1FUSPTMtcdOrnGU09oRnk=; b=BAmnrT5UAc+DVAOiZspAZXPmjPo5ZRrgqgLZjBjqJOUGdJngsKONJf7DB+JL0dpwZu oRH44a0sXcii/YIiizILL7MSPqzkQqYv3nN4HW64eNqo8KjXqntyKSouWj/0tEILUNOX 1cxG0d6MJggxIl9n05/7azn1azNippzC0AE0/XEvIQgWry5jn8gf3YoSzSYhB9r5rb69 RL/zQSMp1N0weeTHdrDZ7Sk/ANiKp2LXPPuWxLcOwKUEdIKfQn/C+j64H9+YDZL4dm74 1HvcbzgnyW8Rmq5dmTgin0PkXdunOsrPwgthtceJTrkK4I19fe6uc9IGm870s1+7me0I hVYQ==
X-Gm-Message-State: AEkoousGNkw4YwdT7pXQuVVPwxInyk7LSG2utrwCuj1p5pfr1MDbd5bsb/hlh0934S2/XQ==
X-Received: by with SMTP id g9mr99067996paw.51.1470092776263; Mon, 01 Aug 2016 16:06:16 -0700 (PDT)
Received: from ?IPv6:2001:df0:0:2006:c0da:ac17:5f6d:8e76? ([2001:df0:0:2006:c0da:ac17:5f6d:8e76]) by with ESMTPSA id i62sm48105485pfg.62.2016. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 01 Aug 2016 16:06:14 -0700 (PDT)
Subject: Re: bettering open source involvement
To: joel jaeggli <>,
References: <> <> <> <> <> <>
From: Brian E Carpenter <>
Organization: University of Auckland
Message-ID: <>
Date: Tue, 2 Aug 2016 11:06:15 +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 23:06:19 -0000

On 02/08/2016 10:40, joel jaeggli wrote:
> On 8/1/16 1:44 PM, Brian E Carpenter wrote:
>> 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.
> "IETF WG sponsors code development"
> I'm not sure what this means, are you paying for a developer?

No, "sponsor" does not automatically mean payment. One of the
Merriam-Webster meanings is "assumes responsibility for some other
person or thing."

> I certainly have opinions as to what terms I'm willing to accept on IPR,
> patented or otherwise.

Of course. But if you're in IETF-land, you've already accepted IETF rules.

> if it's a question of the inclusion of code in a working-group doc then
> that's a question of consensus...

Correct. But if I include code in any old I-D, I'm automatically placing
it under the IETF Trust licence, which is simplified BSD. That's nothing
to do with consensus.


> joel
>>    Brian
>>> (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