Re: [Fud] Comment on draft-moran-fud-manifest-00

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 13 September 2017 19:59 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 6E30A132EE2 for <fud@ietfa.amsl.com>; Wed, 13 Sep 2017 12:59:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, 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 T4esNiLWntuR for <fud@ietfa.amsl.com>; Wed, 13 Sep 2017 12:59:02 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 966E0132ED1 for <fud@ietf.org>; Wed, 13 Sep 2017 12:59:02 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 66F9BE1D3; Wed, 13 Sep 2017 16:03:16 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 7F67480CFA; Wed, 13 Sep 2017 15:59:01 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
cc: fud@ietf.org
In-Reply-To: <3d78ce15-553e-2423-3185-95e789fca3d5@gmx.net>
References: <C64FB690-1EB9-46A0-989F-DAC57E1CA819@riot-os.org> <eb247364-e4d6-1c22-c882-0e53df6c2902@gmx.net> <525.1503422326@dooku.sandelman.ca> <3d78ce15-553e-2423-3185-95e789fca3d5@gmx.net>
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: Wed, 13 Sep 2017 15:59:01 -0400
Message-ID: <28070.1505332741@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/fud/kYv2hg38_o590SWr20P-WrV3IdU>
Subject: Re: [Fud] Comment on draft-moran-fud-manifest-00
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: Wed, 13 Sep 2017 19:59:04 -0000

Hannes Tschofenig <hannes.tschofenig@gmx.net> wrote:
    > and regulator "agreed" on deploying a specific firmware update for a
    > medical device. I think that this is a too heavy for an IoT device and
    > too much policy for the device to consider. While this is not
    > impossible

I agree with you, and that's situation (b) that I described.

    > to do (even with the proposed manifest format) I believe it is more
    > likely that the party providing the firmware update to the IoT device
    > will make that policy decision (which will typically involve humans).

    >> b) devices have a built-in policy that will accept updates on from Z
    >> (the regulator)
    >> Z has a policy where it only reviews things once X and Y
    >> have signed.  Applying the signature from Z may remove the signature
    >> from X and Y (that's a space optimization only).
    >> As the device does not recognize X or Y, it would ignore those
    >> signatures.

The question is, can the signatures from X and Y *remain* for the purposes
of auditing?  Removing them then becomes an option, rather than a requirement.


--
Michael Richardson <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-