Re: [Suit] Fwd: Firmware Update Paper

All,

Thanks for the helpful answers.

Michael,

>
>
>
> *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
> appropriatelydone in the 6tisch WG, since I actually think that the
> bandwidth andscheduling of the update is probably the critical part.SUIT
> has the security done... so we have the HOW.  We just have the WHEN.*

One other approach to explore, very applicable to FW updates, is multi-hop
multicast, as in many scenarios you are updating more than one device, and
many of them are identical (like lights on a big parking lot).

--Simon

On Thu, Dec 5, 2019 at 4:02 AM Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> Hannes Tschofenig <Hannes.Tschofenig@arm.com> wrote:
>     > The signature verification was performed with the HACL library
> (ed25519) on
>     > an ARM Cortex-M0+ and took approx. 7 seconds -- so yes, pretty long
> indeed,
>     > in this case.
>
>     > [SS] Does that scale linearly with image size? Do memory
> requirements (RAM
>     > usage) increase with the image size?
>
> I guess what we want to know is how much of that 7s time was the ED25519
> operation, and
> how much time was the hash calculation.  Only the hash calculation would
> scale with the image size.
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
> _______________________________________________
> Suit mailing list
> Suit@ietf.org
> https://www.ietf.org/mailman/listinfo/suit
>