Re: [Fud] Constrained Firmware update challenge

Carsten Bormann <cabo@tzi.org> Mon, 17 April 2017 07:36 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: fud@ietfa.amsl.com
Delivered-To: fud@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73E7C128B44 for <fud@ietfa.amsl.com>; Mon, 17 Apr 2017 00:36:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] 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 Vh6tGysR-0ZW for <fud@ietfa.amsl.com>; Mon, 17 Apr 2017 00:36:08 -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 ADC96124C27 for <fud@ietf.org>; Mon, 17 Apr 2017 00:36:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v3H7a3RE000564; Mon, 17 Apr 2017 09:36:03 +0200 (CEST)
Received: from [192.168.217.124] (p5DCCCDC2.dip0.t-ipconnect.de [93.204.205.194]) (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 3w60S31DFxzDHQw; Mon, 17 Apr 2017 09:36:03 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <1980.1492374868@obiwan.sandelman.ca>
Date: Mon, 17 Apr 2017 09:36:02 +0200
Cc: fud@ietf.org
X-Mao-Original-Outgoing-Id: 514107362.440925-6f6e54d81b2ef9f2a0f5f9f3ded8785c
Content-Transfer-Encoding: quoted-printable
Message-Id: <E3933EC6-88AD-4754-9FC1-98F55B6755FC@tzi.org>
References: <1980.1492374868@obiwan.sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/fud/MnW0SjR70pwowB7M2tpeKD1SV_k>
Subject: Re: [Fud] Constrained Firmware update challenge
X-BeenThere: fud@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: FUD - Firmware Updating Description <fud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/fud>, <mailto:fud-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/fud/>
List-Post: <mailto:fud@ietf.org>
List-Help: <mailto:fud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/fud>, <mailto:fud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Apr 2017 07:36:10 -0000

How do you update that bootloader (which now contains the majority of the code on the device, by the way)?

Grüße, Carsten

> On Apr 16, 2017, at 22:34, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> 
> In the BarBOF I tried to explain my belief that there is a place for in-place
> (not double/triple buffered) firmware update, via some kind of setup-process
> followed by a very constrained CoAP/DTLS/OSCOAP Block Transfer mechanism that
> a recovery bootloader could run.  I imagine pretty much *all* the protocol
> mechanism being cached.. (ND, IPv6 addresses, DTLS setup, etc.)
> 
> So I wrote up my challenge, and my straw-man concept of a solution.
> 
> Please disagree with me... preferably by sending text (or pull requests):
>     https://datatracker.ietf.org/doc/draft-richardson-fud-constrained-update/
>     https://github.com/mcr/fud-constrained-update
> 
> Ignore my strawman, or perhaps, provide your own.
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works
> -= IPv6 IoT consulting =-
> 
> 
> 
> _______________________________________________
> Fud mailing list
> Fud@ietf.org
> https://www.ietf.org/mailman/listinfo/fud