Re: [Suit] Firmware Update Paper

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 29 November 2019 19:29 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: suit@ietfa.amsl.com
Delivered-To: suit@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B088A1201AA for <suit@ietfa.amsl.com>; Fri, 29 Nov 2019 11:29:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] 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 IIQgoK_dFXrw for <suit@ietfa.amsl.com>; Fri, 29 Nov 2019 11:29:38 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F3DF120105 for <suit@ietf.org>; Fri, 29 Nov 2019 11:28:28 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id D78793897B; Fri, 29 Nov 2019 14:24:57 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id B77B966D; Fri, 29 Nov 2019 14:28:27 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: David Brown <david.brown@linaro.org>
cc: Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>, "suit\@ietf.org" <suit@ietf.org>
In-Reply-To: <20191129183627.GA16289@davidb.org>
References: <VI1PR08MB53600B1D1A194F49B67B90DFFAC60@VI1PR08MB5360.eurprd08.prod.outlook.com> <20191127203651.GA117656@davidb.org> <CANK0pbaWkn7w2swRgkOqsTubE1os=rDo2BLjrTZ5eW6ePv3WnA@mail.gmail.com> <20191129183627.GA16289@davidb.org>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Fri, 29 Nov 2019 14:28:27 -0500
Message-ID: <4269.1575055707@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/suit/hqZgwSAFDho5ATBUiwJOy00vGs4>
Subject: Re: [Suit] Firmware Update Paper
X-BeenThere: suit@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Software Updates for Internet of Things <suit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/suit>, <mailto:suit-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/suit/>
List-Post: <mailto:suit@ietf.org>
List-Help: <mailto:suit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/suit>, <mailto:suit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Nov 2019 19:29:41 -0000

David Brown <david.brown@linaro.org> wrote:
    > On Fri, Nov 29, 2019 at 12:46:42PM +0100, Emmanuel Baccelli wrote:

    >> The open source implementation stemming from our paper [1] is embedded
    >> into the RIOT operating system, which is indeed licensed with LGPL.
    >> The implementation is compliant with draft-ietf-suit-manifest-00 and
    >> has recently been merged into the main branch of RIOT, see [2].  Reuse
    >> and further contributions to this code base are welcome!
    >> 
    >> Relicensing this code is not planned as far as I know (@ code
    >> co-authors: please correct me if I'm wrong).

    > This is fine.  The authors of the code are free to license the code
    > however they wish.  I just want to make sure it is clear that this code
    > is not useful as a general example, and if the SUIT wishes to have
    > reference code, it will need to be licensed differently.

If by reference code, do you mean code that people look at while doing their own
proprietary code under a more restrictive license?
Is the issue that those authors can't read LGPL code because lawyers feel they
will become "tainted"?  

My experience with 2-clause BSD/MIT licensed reference code is that they get
turned into products, not used as "reference".  They aren't used as a
"reference", but as prototype code.  Companies fix bugs, do not contribute the
fixes back, and then the actual base "reference" code actually becomes known
to be non-compliant. 

    > One example is that both Zephyr and MCUboot are licensed under the
    > Apache 2.0 license.  Most parties feel that the Apache 2.0 and the LGPL
    > 2 license are incompatible, and this code cannot be linked together
    > into a single product.  Since I'd like to include SUIT support into
    > MCUboot, this means I'll have to be doing an implementation from
    > scratch.

But, you can still read the code, and you can still benefit from test vectors.

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [