Re: [Suit] Firmware Update Paper

Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr> Tue, 03 December 2019 08:37 UTC

Return-Path: <emmanuel.baccelli@gmail.com>
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 BFDD51201B7 for <suit@ietfa.amsl.com>; Tue, 3 Dec 2019 00:37:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.418
X-Spam-Level:
X-Spam-Status: No, score=-1.418 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 pZQgFn4pHduo for <suit@ietfa.amsl.com>; Tue, 3 Dec 2019 00:37:31 -0800 (PST)
Received: from mail-ot1-f53.google.com (mail-ot1-f53.google.com [209.85.210.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4629A120131 for <suit@ietf.org>; Tue, 3 Dec 2019 00:37:31 -0800 (PST)
Received: by mail-ot1-f53.google.com with SMTP id g18so2151598otj.13 for <suit@ietf.org>; Tue, 03 Dec 2019 00:37:31 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9igSzV8Q9XPlt9/7pt8tdcYpmr6buDuKKm4UNuujLQI=; b=DmLTDEeqxJiTIvUxkGJ9uORdvu1dXENqiR4b/pB+SpSF2z5kJaZ6sgv9EQ7gBtqve4 9W7woQXg8NBdPU80iWke7/SStc4yjpNXfscpQC1OUdP3PdXhwhM6kt5fTjqXZWxiGyeu mER4eBrSdtHk7pcmxB9ss6As1612xPf2HI1MWCpnbO6eXHYKiw8Vy2SAKp/Exhmiokli a6Txj/bOdvwOz3Z+vLfq23T5A6M5+oXQgN9/VjMQCBLcy2m61vgw2pOSYmDTIH3e/jWw jOdT6bMbzfwlMPrILQx/qPxXy0D+0I4l3HuGVSN/XKvF31gJxFlDTVjY3S65FG7qRNOn HfcQ==
X-Gm-Message-State: APjAAAW+geZjKYyIOnWa1FWR2dx89LgBWx9Gso+s2HK2KbJImAGKWuCP CPpcpGlhHiAkoBiAMeEUmy5YGx8mF+EIrn1hPxQ=
X-Google-Smtp-Source: APXvYqz6FIDuL0BLZqJBf/bi5fMlArLXcBDF60zebLIIhRuGGJaUolu1agykt861sSZ5Gsnv2QN0xfGMwT1lndy5b+0=
X-Received: by 2002:a9d:1295:: with SMTP id g21mr2289927otg.301.1575362250199; Tue, 03 Dec 2019 00:37:30 -0800 (PST)
MIME-Version: 1.0
References: <VI1PR08MB53600B1D1A194F49B67B90DFFAC60@VI1PR08MB5360.eurprd08.prod.outlook.com> <20191127203651.GA117656@davidb.org> <CANK0pbaWkn7w2swRgkOqsTubE1os=rDo2BLjrTZ5eW6ePv3WnA@mail.gmail.com> <20191129183627.GA16289@davidb.org> <DB6PR0801MB1879D9742622EA0AE08A8B72EA430@DB6PR0801MB1879.eurprd08.prod.outlook.com> <CABNHR1yEFvgEzHjBhpqTW-FX+LQTVYuSJE_9SP9OMwzjWsdORQ@mail.gmail.com>
In-Reply-To: <CABNHR1yEFvgEzHjBhpqTW-FX+LQTVYuSJE_9SP9OMwzjWsdORQ@mail.gmail.com>
From: Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>
Date: Tue, 3 Dec 2019 09:37:19 +0100
Message-ID: <CANK0pbaf8TTtMOSKHD0D-73+MCzSdjk7p+6hVO0WzpSxhF2fVg@mail.gmail.com>
To: =?UTF-8?Q?Szymon_S=C5=82upik?= <simon@silvair.com>
Cc: Brendan Moran <Brendan.Moran@arm.com>, David Brown <david.brown@linaro.org>, "suit@ietf.org" <suit@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000050d9ac0598c89bd6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/suit/9cjxPapNNqf_bKZU4w1F8CtOLUQ>
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: Tue, 03 Dec 2019 08:37:33 -0000

Hi Szymon

in the paper [1] for our experiements we used CoAP as transport, over UDP,
6LoWPAN and IEEE 802.15.4 low power radio.

However the open source RIOT implementation which stemmed out also works
out-of-the-box on other link layers too (among others BLE [3], wired [1]
...).

Cheers,

Emmanuel

[1] https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=8725488
[2] https://github.com/RIOT-OS/RIOT/tree/master/examples/suit_update
[3] https://github.com/RIOT-OS/RIOT/pull/12391

On Tue, Dec 3, 2019 at 12:58 AM Szymon Słupik <simon@silvair.com> wrote:

> Hi Hannes,
>
> What transport did you use? I could not find that information explicitly
> stated in the paper...
>
> Thanks!
>
> Simon
>
> On Tue, Dec 3, 2019 at 12:20 AM Brendan Moran <Brendan.Moran@arm.com>
> wrote:
>
>> Hi David,
>>
>> The manifest generator that I released previously was apache
>> 2.0-licensed. I don't plan to change that for the next release. I'm also
>> developing a manifest parser which I anticipate being released under the
>> same license.
>>
>> Best Regards,
>> Brendan
>>
>> -----Original Message-----
>> From: Suit <suit-bounces@ietf.org> On Behalf Of David Brown
>> Sent: 29 November 2019 18:36
>> To: Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>
>> Cc: suit@ietf.org
>> Subject: Re: [Suit] Firmware Update Paper
>>
>> 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.
>>
>> > Related: we know of several companies, big and small, which use RIOT
>> > in their IoT products (and thus use software including -- but not
>> > limited to -- LGPL
>> > code) and they are quite happy with it.
>>
>> I'm sure there are a few companies that are willing to use LGPL licensed
>> embedded code, but their existence doesn't negate that there are large
>> numbers of users who will be unable to use (or even look at) this code.
>>
>> 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.
>>
>> It's not my place to argue about the licensing of RIOT, but I would like
>> to see reference code for SUIT that can be used as widley as possible, and
>> the licensing of this particular code prevents it from being used for that.
>>
>> David
>>
>> _______________________________________________
>> Suit mailing list
>> Suit@ietf.org
>> https://www.ietf.org/mailman/listinfo/suit
>> IMPORTANT NOTICE: The contents of this email and any attachments are
>> confidential and may also be privileged. If you are not the intended
>> recipient, please notify the sender immediately and do not disclose the
>> contents to any other person, use it for any purpose, or store or copy the
>> information in any medium. Thank you.
>>
>> _______________________________________________
>> Suit mailing list
>> Suit@ietf.org
>> https://www.ietf.org/mailman/listinfo/suit
>>
>