Re: [Suit] CBOR and Firmware Word Alignment
Carsten Bormann <cabo@tzi.org> Wed, 27 June 2018 08:27 UTC
Return-Path: <cabo@tzi.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 E9D3912872C for <suit@ietfa.amsl.com>; Wed, 27 Jun 2018 01:27:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_MED=-2.3] 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 5BK0IettESuA for <suit@ietfa.amsl.com>; Wed, 27 Jun 2018 01:27:27 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0BA0C1277D2 for <suit@ietf.org>; Wed, 27 Jun 2018 01:27:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id w5R8RNiu020001; Wed, 27 Jun 2018 10:27:23 +0200 (CEST)
Received: from [100.76.202.113] (ip-109-41-67-209.web.vodafone.de [109.41.67.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 41Fwy26jRCzDWqt; Wed, 27 Jun 2018 10:27:22 +0200 (CEST)
Content-Type: multipart/alternative; boundary="Apple-Mail-12CB2B3B-C445-4460-9CEE-726CD52260F5"
Mime-Version: 1.0 (1.0)
From: Carsten Bormann <cabo@tzi.org>
X-Mailer: iPhone Mail (15F79)
In-Reply-To: <de4c2bdc8e944f6691591ddd71fb6736@nordicsemi.no>
Date: Wed, 27 Jun 2018 10:27:21 +0200
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, suit <suit@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <45FFC315-6D5A-4E08-BE4C-0DE2DEBA3C19@tzi.org>
References: <5DF0B5F0-85E2-4681-9581-E28A3F0A5446@intrinsic-id.com> <19378.1530055961@localhost> <de4c2bdc8e944f6691591ddd71fb6736@nordicsemi.no>
To: "\"Rønningstad, Øyvind\"" <Oyvind.Ronningstad@nordicsemi.no>
Archived-At: <https://mailarchive.ietf.org/arch/msg/suit/58TRk6W0iRDE09j3jXZIU-F8YUg>
Subject: Re: [Suit] CBOR and Firmware Word Alignment
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: Wed, 27 Jun 2018 08:27:30 -0000
So what is the container format for delivering manifest and image? You could solve the problem there. (eg, round up before spending the next thing.) Sent from mobile > On 27. Jun 2018, at 08:46, Rønningstad, Øyvind <Oyvind.Ronningstad@nordicsemi.no> wrote: > > > >> -----Original Message----- >> From: Suit [mailto:suit-bounces@ietf.org] On Behalf Of Michael >> Richardson >> Sent: 27. juni 2018 01:33 >> To: suit <suit@ietf.org> >> Subject: Re: [Suit] CBOR and Firmware Word Alignment >> >> >> Paul Lambert <paul.lambert@intrinsic-id.com> wrote: >>> Has any thought gone into word alignment issues? >> >>> Many platforms require firmware or other data objects to be word >>> aligned. It waould be especially desirable to have large objects (like >>> the firmware) be packaged such that the data does not have to be >> copied >>> to a new location just to ensure word alignment. Word alignment >> would >>> also facilitate in-place decryption of the firmeare. >> >> AFAIK, the firmware image is not *in* the manifest, so the actual >> firmware alignment does not depend upon any feature of the manifest. >> The firmware image can be put anywhere one likes. >> I find it unlikely that the manifest contents will need any specific >> alignment for a bulk operation. If so, it's small enough to copy around >> the place. >> >> Over on the mcuboot list, it seems that they currently putting their image >> TLV at the end of the firmware image, and they will place the manifest >> there. That would seem to align the firmware image nicely. >> > > In some cases it makes sense to concatenate the payload after the manifest to simplify delivery, In which case I think it would be useful to have the option of padding. There could be a bstr padding entry at the end of the manifest, or maybe a padding extension. > > _______________________________________________ > Suit mailing list > Suit@ietf.org > https://www.ietf.org/mailman/listinfo/suit >
- Re: [Suit] CBOR and Firmware Word Alignment Carsten Bormann
- Re: [Suit] CBOR and Firmware Word Alignment Rønningstad
- Re: [Suit] CBOR and Firmware Word Alignment Michael Richardson
- Re: [Suit] CBOR and Firmware Word Alignment Carsten Bormann
- [Suit] CBOR and Firmware Word Alignment Paul Lambert
- Re: [Suit] CBOR and Firmware Word Alignment David Brown
- Re: [Suit] CBOR and Firmware Word Alignment Rønningstad