IETF Logo Mail Archive

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

"Thomas Eichinger" <thomas@riot-os.org> Thu, 10 August 2017 22:37 UTC

Return-Path: <thomas@riot-os.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 C50911321EF for <fud@ietfa.amsl.com>; Thu, 10 Aug 2017 15:37:38 -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] 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 nMn5azRqsYVP for <fud@ietfa.amsl.com>; Thu, 10 Aug 2017 15:37:37 -0700 (PDT)
Received: from mail.stillroot.org (mail.stillroot.org [176.9.132.253]) by ietfa.amsl.com (Postfix) with ESMTP id 8E01F1321E9 for <fud@ietf.org>; Thu, 10 Aug 2017 15:37:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.stillroot.org (Postfix) with ESMTP id 82F0142981 for <fud@ietf.org>; Fri, 11 Aug 2017 00:37:08 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at ba.stillroot.org
Received: from mail.stillroot.org ([127.0.0.1]) by localhost (mail.stillroot.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8dAjEk8NSa4S for <fud@ietf.org>; Fri, 11 Aug 2017 00:37:02 +0200 (CEST)
Received: from [192.168.1.66] (unknown [IPv6:2602:306:36e3:3580:30a0:4032:2ca8:aab3]) by mail.stillroot.org (Postfix) with ESMTPSA id 2A02C42985 for <fud@ietf.org>; Fri, 11 Aug 2017 00:37:01 +0200 (CEST)
From: Thomas Eichinger <thomas@riot-os.org>
To: fud@ietf.org
Date: Thu, 10 Aug 2017 15:37:00 -0700
Message-ID: <C64FB690-1EB9-46A0-989F-DAC57E1CA819@riot-os.org>
MIME-Version: 1.0
X-Mailer: MailMate (2.0BETAr6090)
Archived-At: <https://mailarchive.ietf.org/arch/msg/fud/JO6ulPlASV6MMoFTUmvB9Q4dYIk>
Subject: [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: Thu, 10 Aug 2017 22:37:39 -0000

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

v2.23.0 | Report a Bug | By Email