Re: [Suit] Fwd: Firmware Update Paper

Michael Richardson <> Wed, 04 December 2019 19:00 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 03EB4120A1F; Wed, 4 Dec 2019 11:00:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Status: No, score=-4.199 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 4vgyANEGlBGY; Wed, 4 Dec 2019 11:00:52 -0800 (PST)
Received: from ( [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 (Postfix) with ESMTPS id BCABE1209EA; Wed, 4 Dec 2019 11:00:51 -0800 (PST)
Received: from ( [IPv6:2607:f0b0:f:2::247]) by (Postfix) with ESMTP id 4E23E3818F; Wed, 4 Dec 2019 13:57:13 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by (Postfix) with ESMTP id AF51DAAB; Wed, 4 Dec 2019 14:00:50 -0500 (EST)
From: Michael Richardson <>
To: =?us-ascii?Q?=3D=3FUTF-8=3FQ=3FSzymon=5FS=3DC5=3D82upik=3F=3D?= <>, Emmanuel Baccelli <>,,
In-Reply-To: <>
References: <> <> <> <> <> <> <> <> <> <>
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: Wed, 04 Dec 2019 14:00:50 -0500
Message-ID: <5379.1575486050@localhost>
Archived-At: <>
Subject: Re: [Suit] Fwd: Firmware Update Paper
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Software Updates for Internet of Things <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 04 Dec 2019 19:00:57 -0000

Szymon Słupik <> wrote:
    > [SS] yeah... that 35kB is a bit unrealistic... for production stacks
    > (including application functionality) we see the FW sizes (uncompressed) to
    > be in 200kB range. But I take it the times scale linearly, so for 200kB the
    > transfer time would be about 1 minute. Have you considered the link
    > saturation during the transfer? In many cases you do not want the transfer to
    > [significantly] affect the operation of the network, so a strategy to reduce
    > the transfer duty cycle may be prudent.

I also agree with your question, and with the need to do the updates at a
lower priority.  6tisch has a whole bunch of mechanism here.

It occurs to me now that the development of an update protocol over 802.15.4
(which I mentioned in another email in this thread) might be appropriately
done in the 6tisch WG, since I actually think that the bandwidth and
scheduling of the update is probably the critical part.
SUIT has the security done... so we have the HOW.  We just have the WHEN.

Michael Richardson <>, Sandelman Software Works
 -= IPv6 IoT consulting =-