/
IETF Hackathon: Software IETF Hackathon: Software

IETF Hackathon: Software - PowerPoint Presentation

mentegor
mentegor . @mentegor
Follow
343 views
Uploaded On 2020-06-30

IETF Hackathon: Software - PPT Presentation

Updates for IoT SUIT IETF 10 2 1415 July 2018 Montreal Hackathon Plan Software Updates for IoT Generate a manifest Encode it in CBOR Sign it with ID: 790767

development suit board manifest suit development manifest board ietf cbor hackathon parsing iot time cose project group multiple sign

Share:

Link:

Embed:

Download Presentation from below link

Download The PPT/PDF document "IETF Hackathon: Software" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.


Presentation Transcript

Slide1

IETF Hackathon:Software Updates for IoT (SUIT)

IETF 10214-15 July, 2018 Montreal

Slide2

Hackathon PlanSoftware Updates for IoT

Generate a manifestEncode

it

in CBOR

Sign it with COSEVerify it on a SUIT prototyping board.

2

Slide3

The Group

Team:Hannes TschofenigJaime JiménezFelipe EspinozaAlexandra IbarraThomas Fossatti

Bill

Silverajan

David WaltermireLaurence Lundblade3

1

st

time IETF

1

st

time SUIT Hackathon

Slide4

What got doneSet up

development environment for use with new

board

on multiple OSs. Mbed OS was used as an

IoT operating system.

Generate

the

manifest

Encode

it

Sign

it Verify it on the deviceDetailed write-up available at https://git.io/fNYC6

4

Slide5

What was learned?Development environments

: Making setup for 1st time users easier would be good. A preconfigured environment would be good.We need to use IDEs for debugging (e.g., Keil

uVision

5)  example project or software packsHardware: New development board workedUnfortunately, we bricked 3 boards (potential issue on Macs).

Coding: Getting to a small codesize for the bootloader will be difficult with CBOR and COSE.

Parsing of CBOR encoded manifest is not straightforward

. (Most likely a

TinyCBOR

API issue.)

Spec

:

Manifest could use map instead of array for simpler parsing. (Depends on how we anticipate the parsing to happen.)

5

Slide6

The SUIT project was well received

Slide7

What is next?Focus on running code: Update reference implementations based on the evolving manifest format.Release further COSE libraries

(with other licenses)Make use of development board for advanced features (encryption, multiple images, etc.)More involvement from the working group. Less talk – more code.