[Fud] Constrained Firmware update challenge

Michael Richardson <mcr+ietf@sandelman.ca> Sun, 16 April 2017 20:34 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 771D01292AE for <fud@ietfa.amsl.com>; Sun, 16 Apr 2017 13:34:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 lHZ2QrzM383I for <fud@ietfa.amsl.com>; Sun, 16 Apr 2017 13:34:29 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [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 ietfa.amsl.com (Postfix) with ESMTPS id 4E896128DF6 for <fud@ietf.org>; Sun, 16 Apr 2017 13:34:29 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id DA80C20569 for <fud@ietf.org>; Sun, 16 Apr 2017 16:59:25 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 0CE99636BB for <fud@ietf.org>; Sun, 16 Apr 2017 16:34:28 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
to: fud@ietf.org
X-Mailer: MH-E 8.6; nmh 1.6+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: Sun, 16 Apr 2017 16:34:28 -0400
Message-ID: <1980.1492374868@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/fud/vP--xCarIKurpQjWY7NecZ1o97o>
Subject: [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: Sun, 16 Apr 2017 20:34:31 -0000

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 =-