[Suit] MCUboot/Zephyr involvement
David Brown <david.brown@linaro.org> Fri, 15 June 2018 09:10 UTC
Return-Path: <david.brown@linaro.org>
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 29AC1120049 for <suit@ietfa.amsl.com>; Fri, 15 Jun 2018 02:10:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=linaro.org
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 v-VsTRBoN0nZ for <suit@ietfa.amsl.com>; Fri, 15 Jun 2018 02:10:40 -0700 (PDT)
Received: from mail-wr0-x22d.google.com (mail-wr0-x22d.google.com [IPv6:2a00:1450:400c:c0c::22d]) (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 DFF5312F1A2 for <suit@ietf.org>; Fri, 15 Jun 2018 02:10:39 -0700 (PDT)
Received: by mail-wr0-x22d.google.com with SMTP id l41-v6so9173662wre.7 for <suit@ietf.org>; Fri, 15 Jun 2018 02:10:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=user-agent:date:subject:from:to:message-id:thread-topic :mime-version; bh=hhLoUk0/q2tO5V0gAxGyW3feg0LxFyvzBKxJh9zw7Bg=; b=SfT+xod0FWLZ3if+SfGsKu3sqh++uVpx7XDOMLXcZJeuYTMUefaDnrFKPT07dQnlA3 gW+tQecypPlhoFsJrzTAFOSPCWeEj1E8h0iJGwPJ/SpkDfN+1p9VPIEcJKl/iMPnyFP1 SIBBuMuCzAAolJ8YSzwJsocXuvYPG7miwT8vE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:message-id :thread-topic:mime-version; bh=hhLoUk0/q2tO5V0gAxGyW3feg0LxFyvzBKxJh9zw7Bg=; b=Uyg4TEEdIc4kTUkSNAC4Cds+/G/aQUB15HNJVoNICDeRJ0NpRzSIauJDH7O1utRXtH ArLW/fGBfLXRyOClOr3UJ6/Lqsun6njUkxcRTjvN5xPaApa6p1jNrK2Q1jgauVZLbz1w gmN49/C7IakI1/iXS6SEXErMW2TBE1edYBDgzPLZMOUKIX5RRxIu+if1tat1X7G11FDd RFWSpLt3qQFN5/CoaTMi0gslAQCBfyuqc0MyGFlyzOEFw5oSU5PFhDKd+pgKM9L4EhmD pjmFv9TWwOrjFcnyti7DFOw9MfOlyVreAqWkFtvQon0gK6MSS2UglnJGBP0OLMM54miu asTA==
X-Gm-Message-State: APt69E21W36WN0rR7PFtrZZUnZuMEM9yCMGylSHWB0W/vOPqG2LR1EOj wNAKg7RvS375dFhpLT2LVQ5BZ9EHOyY=
X-Google-Smtp-Source: ADUXVKJ6Bp2k/Zz47bxgszpV0fvoXDTkrearuv+QIpvnfgTtCh0lv4qe4m3MH+ixSbCnWMjmQNw5yA==
X-Received: by 2002:adf:9acc:: with SMTP id a70-v6mr848147wrc.180.1529053837933; Fri, 15 Jun 2018 02:10:37 -0700 (PDT)
Received: from [192.168.0.181] (LPuteaux-656-1-48-212.w82-127.abo.wanadoo.fr. [82.127.83.212]) by smtp.gmail.com with ESMTPSA id v14-v6sm7671036wro.33.2018.06.15.02.10.30 for <suit@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 15 Jun 2018 02:10:37 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/10.e.1.180613
Date: Fri, 15 Jun 2018 11:10:18 +0200
From: David Brown <david.brown@linaro.org>
To: "suit@ietf.org" <suit@ietf.org>
Message-ID: <2E29EC1C-FAE7-47BE-B48C-F3797C1EC224@linaro.org>
Thread-Topic: MCUboot/Zephyr involvement
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3611905831_144895453"
Archived-At: <https://mailarchive.ietf.org/arch/msg/suit/ckFyGEEiSaHjM_6cAqh5tVPtz6Y>
Subject: [Suit] MCUboot/Zephyr involvement
X-BeenThere: suit@ietf.org
X-Mailman-Version: 2.1.26
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, 15 Jun 2018 09:10:43 -0000
This week, Linaro held a SPRINT where among other things, we discussed our future direction for firmware upgrade, especially in regards to two configurations: a Secure/Non-secure dual image system on a single CPU, and a similar dual image running on two separate CPUs. At this point, management of multiple images is not deeply discussed by the proposed documents, and I’m wondering if this kind of support would best be left to additional documentation. One thing I’d like to consider is how multiple images could be supported by a single manifest. There are possibilities, such as concatenating the manifests, or just having to track the multiple manifests separately. Most of the fields in the manifest allow multiple instances of that field, except for the payload, where the manifest only describes a single payload. What would be the ramifications of allowing 1 or more payload blocks in the manifest? Thanks, David
- Re: [Suit] MCUboot/Zephyr involvement Henk Birkholz
- Re: [Suit] MCUboot/Zephyr involvement Brendan Moran
- Re: [Suit] MCUboot/Zephyr involvement David Brown
- Re: [Suit] MCUboot/Zephyr involvement Henk Birkholz
- [Suit] MCUboot/Zephyr involvement David Brown