Re: [Fud] Editorial Charter Update

Carsten Bormann <cabo@tzi.org> Tue, 10 October 2017 08:42 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 37DD9134AB9 for <fud@ietfa.amsl.com>; Tue, 10 Oct 2017 01:42:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 bmKemLaPGHvf for <fud@ietfa.amsl.com>; Tue, 10 Oct 2017 01:42:05 -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 606AE134704 for <fud@ietf.org>; Tue, 10 Oct 2017 01:41:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v9A8ffUu028274; Tue, 10 Oct 2017 10:41:41 +0200 (CEST)
Received: from sev.localdomain (unknown [212.98.163.82]) (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 3yB9ZY2KnZzDL16; Tue, 10 Oct 2017 10:41:41 +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: <66e408f7-44b5-b1a3-a53b-82454b8260a4@gmx.net>
Date: Tue, 10 Oct 2017 10:41:39 +0200
Cc: Russ Housley <housley@vigilsec.com>, "Fud@ietf.org" <fud@ietf.org>
X-Mao-Original-Outgoing-Id: 529317698.836866-a20132724784cc4203c499da80c83c0b
Content-Transfer-Encoding: quoted-printable
Message-Id: <22E7B666-4035-401D-8A7C-C67FCA78E326@tzi.org>
References: <c14c92bf-cf99-efdb-6693-0e33519fbb0a@gmx.net> <578DD8B8-E786-4913-AE6A-65FFA29019AD@vigilsec.com> <FD3975C8-C252-4E70-8D96-29918FC0DAB3@tzi.org> <66e408f7-44b5-b1a3-a53b-82454b8260a4@gmx.net>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/fud/JvOuFBsD314QnY6stDp3VtGQ4xo>
Subject: Re: [Fud] Editorial Charter Update
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, 10 Oct 2017 08:42:12 -0000

On Oct 9, 2017, at 10:24, Hannes Tschofenig <hannes.tschofenig@gmx.net> wrote:
> 
> Hi Carsten
> 
> I had provided a response to your comment and asked whether it clarifies
> things.
> 
> I don't believe you have responded.

Sorry, I’m way behind in my mail.

> So far, I haven't heard you saying anything about what you would like to
> see done in this working group.

I think the discussion has evolved towards focusing on data formats for describing software update packages and their applicability in a secure way.  Being able for a set of managing entities (for the device owner, for the device manufacturer, for authorized third parties) to properly authorize the update of a (potentially low-resource) device with firmware that is fresh, appropriate for the device and its configuration, and appropriate for the usage situation that device is in.

> I would also like to know what you see
> wrong with bug fixing and tweaking?

Nothing is wrong with that if what is being fixed and tweaked is solving the problem after finishing the fixing and tweaking.  Not sure we are in that position.

Grüße, Carsten