IETF Logo Mail Archive

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

Hannes Tschofenig <hannes.tschofenig@gmx.net> Tue, 22 August 2017 11:33 UTC

Return-Path: <hannes.tschofenig@gmx.net>
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 493AE132983 for <fud@ietfa.amsl.com>; Tue, 22 Aug 2017 04:33:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level:
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 5DeoIEtcHcHP for <fud@ietfa.amsl.com>; Tue, 22 Aug 2017 04:33:18 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D51F8132977 for <fud@ietf.org>; Tue, 22 Aug 2017 04:33:17 -0700 (PDT)
Received: from [192.168.91.203] ([80.92.118.73]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MHokD-1dh6E20oY9-003i1g; Tue, 22 Aug 2017 13:33:15 +0200
To: Thomas Eichinger <thomas@riot-os.org>, fud@ietf.org
References: <C64FB690-1EB9-46A0-989F-DAC57E1CA819@riot-os.org>
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Openpgp: id=071A97A9ECBADCA8E31E678554D9CEEF4D776BC9
Message-ID: <eb247364-e4d6-1c22-c882-0e53df6c2902@gmx.net>
Date: Tue, 22 Aug 2017 13:33:14 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <C64FB690-1EB9-46A0-989F-DAC57E1CA819@riot-os.org>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:Spz5U15R842r3WYJCx6xwKQCFB68vdmK1CTNql81mdsrOmNTplw 9Z36dmFitlFHYIPcxEMHrZdXFwFpB70Y1SFw81HqcrN2GeilDYQ4lHJbF9svGBQSjMbcM0P Sj/QbjzjbwQcYzpZORMytWQYUlczCyH191CHmwEcUKW9vgtgHmPphoDCAR6ovhshx5kDxEC z+SpHgcxMgD0xHS4Qu+SA==
X-UI-Out-Filterresults: notjunk:1;V01:K0:yE2U5XLcri8=:aaNyu7CEpjt15HBYX53hND N+ZT+QhwY5aLj4ugeK9CCtWETGiLbxXUUAU8hv+Ap972r1UBD9sR5ApI3P3k0UdkkJcIxPHzg a28qTxX+3Yhn+1ztAjLfoNDc872byzBrRdzOMWrXUpgQcmzv75crbzecjaxgEW+jblij3URvQ NNmN6uSgJvpKi/PTIv07jPn3qHVqFDlR6MESD7ZbxQeIx/QnVMdZS6lHeEnV8d4pSFYvOd8o2 xepEr7fPttxomt7aGCoVKHxYH6WLR2GcDu1q/paghQuXrnR5ytXAaGX8qliemtCAHDukwkJev btM6FyRbMPCF7xBD/oMjsC33FSGMaT6tyshClceMTR1QqagaN58XiNpx3Nsbg3Q9/FoT6ZgPf /ev36dnF9VXULgW6qWcNyXLiPqZFs2cjJTyq0buhhokXKllUlMnz8qjoEfoV8KP4+Rj+QMVE1 fzgxfZj1Cx/VL5iTT1q/GNFJ/BfuUHw95G9N/job92YCTsS4iEZBwNOJeGow9W5B/KY7Wd7uU w2nGtllREjkMxSBWPPytLpiJPKbVYcB4Yv5IPl2rfs6k7VQK3QRQNvw4KNRg5I9dr923FFpgo 9GkeGzJzbzGhuRMCyGxqj7gxbieWOpsFtyA/9ZkfiwZ7vp6OJX22dcycbxAjyC2j43JIOAksx LSBB6GTaDQSA1+7JQHDOqsaop0o3pWXeTFr3yzrIISR2FP1lM/aIDwgTJOAYWqbFdq3lHgZz2 0zLQ2k5586slPOdDYjFne3OSdetJahHmrHzsQHfeXQ2GdTQQ5vwk7S5xD2ZGN5XVAXyOF3NwM EnezO5OL3NHXPQTkGQUlWLhDTTaMxbDvObJgN9T78DgOlP3nbY=
Archived-At: <https://mailarchive.ietf.org/arch/msg/fud/Qw756lsQvpLkn5bJTl5J34TcW_0>
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: Tue, 22 Aug 2017 11:33:20 -0000

Hi Thomas,

interesting idea.

As an optional feature I don't see a problem with it.

How exactly the approval process for applying a firmware update in a
particular product looks like will of course vary a lot. At the IOTSU
workshop we had people describing a healthcare setting where any code
changes need to go through certification first. In smart home
environments the firmware updates are most likely facing fewer
regulatory restrictions.

Ciao
Hannes



On 08/11/2017 12:37 AM, Thomas Eichinger wrote:
> Hi,
> 
> reading draft-moran-fud-manifest-00 I am wondering what people think about
> adding a component to the manifest classifying the described update as a
> security and/or feature update (others are imaginable) in a machine-readable
> manner.
> 
> The use case I see is that users then can define rules to deploy security
> only updates in an automated timely fashion while being able to review
> others before. Similar to Directive.applyImmediately but not forced by the
> Author of the update.
> 
> Any opinions on that?
> 
> Best,
> Thomas
> 
> _______________________________________________
> Fud mailing list
> Fud@ietf.org
> https://www.ietf.org/mailman/listinfo/fud
>

v2.23.0 | Report a Bug | By Email