Re: bettering open source involvement

"Doug Ewell" <doug@ewellic.org> Mon, 01 August 2016 22:24 UTC

Return-Path: <doug@ewellic.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 007BD12D93F for <ietf@ietfa.amsl.com>; Mon, 1 Aug 2016 15:24:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZLRpCz35inai for <ietf@ietfa.amsl.com>; Mon, 1 Aug 2016 15:23:58 -0700 (PDT)
Received: from p3plwbeout03-02.prod.phx3.secureserver.net (p3plsmtp03-02-2.prod.phx3.secureserver.net [72.167.218.214]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 683F012D927 for <ietf@ietf.org>; Mon, 1 Aug 2016 15:23:58 -0700 (PDT)
Received: from localhost ([72.167.218.133]) by p3plwbeout03-02.prod.phx3.secureserver.net with bizsmtp id RyPy1t0012tGlPL01yPyvC; Mon, 01 Aug 2016 15:23:58 -0700
X-SID: RyPy1t0012tGlPL01
Received: (qmail 4248 invoked by uid 99); 1 Aug 2016 22:23:58 -0000
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
X-Originating-IP: 208.51.143.189
User-Agent: Workspace Webmail 6.4.2
Message-Id: <20160801152356.665a7a7059d7ee80bb4d670165c8327d.80c069a022.wbe@email03.godaddy.com>
From: "Doug Ewell" <doug@ewellic.org>
To: ietf@ietf.org
Subject: Re: bettering open source involvement
Date: Mon, 01 Aug 2016 15:23:56 -0700
Mime-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hJe56-beLA6-dEqENONfWUpCj5k>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2016 22:24:01 -0000

"Eggert, Lars" 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 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.)

Source code, regardless of license, should never serve as the
specification of any protocol or algorithm. A spec must be expressed in
prose, tables, formulas, pseudocode, flowcharts, ABNF, what have you,
not in actual code in an actual programming language.

--
Doug Ewell | Thornton, CO, US | ewellic.org