Re: [Suit] Firmware Update Paper

Szymon Słupik <simon@silvair.com> Mon, 02 December 2019 23:58 UTC

Return-Path: <simon@silvair.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 45D3712008F for <suit@ietfa.amsl.com>; Mon, 2 Dec 2019 15:58:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=silvair-com.20150623.gappssmtp.com
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 L1Hly54k_-xH for <suit@ietfa.amsl.com>; Mon, 2 Dec 2019 15:58:36 -0800 (PST)
Received: from mail-lj1-x22e.google.com (mail-lj1-x22e.google.com [IPv6:2a00:1450:4864:20::22e]) (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 89E92120058 for <suit@ietf.org>; Mon, 2 Dec 2019 15:58:36 -0800 (PST)
Received: by mail-lj1-x22e.google.com with SMTP id 21so1626643ljr.0 for <suit@ietf.org>; Mon, 02 Dec 2019 15:58:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=silvair-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=SapTPaaoew5LGBHYqHDIgSU8/D9Q936kDUh61HalSzA=; b=1RtBO6c1lrppd6plBzTJgh5/SK9Ti/PhX8IqUu3eN/LSuoZgRG4UfdNrbTsOHMk0Im +2BaW1ddQzZ8ezXafP1cOwqsFrRY7ClXW6dEOkPR/WGrn63LAnN5fPNf7TIdT4dcGtpK lsCC8wiJTYXYROyoHWIInko7MI5T6CVKcgJLNZniYOkJa9jam0Jl2324NGHxKrAYjkRG bGA4ddIxjzoZQ/1v8qtLxnYAXoWv5KtKXYydIy+9vIQDY5gHgX+mHy5ZtZR8Xb2hE7K5 c5iqm3b/IbBSXxVDh/mdfoasFl8T45b60UsvjYQhl1tCAo+y4y7ugAZmZIgsrF1h3f7q 7QpA==
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=SapTPaaoew5LGBHYqHDIgSU8/D9Q936kDUh61HalSzA=; b=NIB5xZ1nVa/8nDVw87SuJC6STZUNr7PevFJuVORf8RkXriKks1CWcsMEmbAgZTvB/K SpI/IFg2MriyhInIlwFF+dzaJG7gR270tbFNVoBME/mhLy51NciVcuZ8YFLPGfrVWTQB 5W6REu55eu4lJeH1M9XXETy4TUjMjtpI2RamdjaWcFKMNC3ZUD/OtyBy84KcfiNqK3hH tavcGLXJZ9ghhDeY1pw5kWHmP9FHKzVI3Esz6GgmKDSY4WHEJCOlhDUJhf9xYi7CPaQX CrWgCH7ZCaz2jz6tpmNGTwrmmZj5YgASqOcOBXA+y3eL3hH7aMW/TnGj0bzloRUo1mZr YX8g==
X-Gm-Message-State: APjAAAV9t56emxVpL6uPPNbugvcKvaRZ9+EDLILelciusUi1A1wApHX+ ZP8YiEVO+saA7o7QRf17HvWI8XdGVx8Mt7Mr6RGc+g==
X-Google-Smtp-Source: APXvYqw99g53PH4D2eLLpW6Kp3wUxeU5pALXuF+8DnY0iTrhaLHxrtfo7XD13NDDrV7mN4s4ndDtSRaRCnioM4kXZTQ=
X-Received: by 2002:a2e:9093:: with SMTP id l19mr679439ljg.235.1575331114637; Mon, 02 Dec 2019 15:58:34 -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>
In-Reply-To: <DB6PR0801MB1879D9742622EA0AE08A8B72EA430@DB6PR0801MB1879.eurprd08.prod.outlook.com>
From: =?UTF-8?Q?Szymon_S=C5=82upik?= <simon@silvair.com>
Date: Tue, 3 Dec 2019 08:57:57 +0900
Message-ID: <CABNHR1yEFvgEzHjBhpqTW-FX+LQTVYuSJE_9SP9OMwzjWsdORQ@mail.gmail.com>
To: Brendan Moran <Brendan.Moran@arm.com>
Cc: David Brown <david.brown@linaro.org>, Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>, "suit@ietf.org" <suit@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007defd50598c15b07"
Archived-At: <https://mailarchive.ietf.org/arch/msg/suit/KzA6FaY49qtfOLApcPyKjg0z_EI>
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: Mon, 02 Dec 2019 23:58:39 -0000

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
>