IETF Logo Mail Archive

Re: [Fud] Editorial Charter Update

Hannes Tschofenig <hannes.tschofenig@gmx.net> Tue, 10 October 2017 09:08 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 60CD2134B23 for <fud@ietfa.amsl.com>; Tue, 10 Oct 2017 02:08:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 3aOeCAqCIZlw for <fud@ietfa.amsl.com>; Tue, 10 Oct 2017 02:08:19 -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 B9D97134B18 for <fud@ietf.org>; Tue, 10 Oct 2017 02:08:18 -0700 (PDT)
Received: from [192.168.91.203] ([80.92.122.248]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MTMzb-1dss4X0N4J-00SO08; Tue, 10 Oct 2017 11:08:06 +0200
To: Carsten Bormann <cabo@tzi.org>
Cc: "Fud@ietf.org" <fud@ietf.org>, Russ Housley <housley@vigilsec.com>
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> <22E7B666-4035-401D-8A7C-C67FCA78E326@tzi.org>
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Openpgp: id=071A97A9ECBADCA8E31E678554D9CEEF4D776BC9
Message-ID: <1397063d-b0b3-d7cf-4c0e-72cf18d20958@gmx.net>
Date: Tue, 10 Oct 2017 11:08:04 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <22E7B666-4035-401D-8A7C-C67FCA78E326@tzi.org>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:noYN2huvTvDLKEhTMZ5opzrnTp6yCN50Hkm3JFaT/QMsmCK4I0l 0wXh8XfxzP7N4S9wkjTTn/lPgUCMKFPTO0eCGJYfNDFLIFXhj0OUBfOaY1Ujh3QGNc2B1f7 psG5M6/s1ekkP9tIZ8Njvju9qtdWpKeg0SG4c9nRMJ1+rXg8+f1h+V1zcqCAgG2jLKVTKoU 9fP9CptoZEQm7K2yZn0Gw==
X-UI-Out-Filterresults: notjunk:1;V01:K0:cjRl9fUIMag=:0ACMxsQRdMOHgq1I4jmeSe 0GzVipru/R+bLmQHh5Km+Uj7GYu2mpc3q+OD5CcKNyxKDi2X9UkJWjF3PojcmgRCV43X6dh8P byHSBKbXrdOra66j7CTcLzB2hpQjMA+1jv+UM0Yw9TDmPxT5dDsJqfiBbgnAGL6aQdlhWupl0 zJd41ISD9NiI2A9MQMVI/CNtCgdhO8VUcJvh00Omwcs09GhmqAJLs9ZUOMgLMf1JLC0mxh56T u3PtY4c9BHprqTvF4comNvXYvkoiubyT60rNwCSDc1lPWH6txEhh72HfKa9UekqV223YICNbr dHeVet7RH3uDazwul2jS739OXukEZCdYxEAt6smybP/sJVVGBL2B7mfbgYiO7kXtTvTUF8BgT v6GpaQAlm+wKJ6seyGXqt8qK8M879D82CjxFMj+bboXhRVDbJEUJUg7HK+giE8SuVG3EL4pfi WMmSKBfz1vU2LhTdRby2DDTTwjHuvv9VjrksAF/EnbJTz2BpOTThZGqoxwm8MKMBoocMH+GY7 8uy7LQaYFkIhuIA3K2hSTbvvQY9KMWEVOybe5ZfUU1oQwHKQZ2x2bZJ2EIsPOWphxqx8ObSxw KtH4UsdrbBEPqgsf+oZ2fIzOIg2xbKTHG1F3pCKaZmbARe8PRW3oW6umwt+M3Fz1dLlOIr6Fb w4b7C663jMJ+kYwfqWWWBntXoDCzsbtmvLO8J/2B6YX0mSg/YcgKJZhzPXtmw/0OOqIM+1Wbp uP1Of7MWhv+WKFaOdhCfFRxEPjb9aeXRe0JB4kL9WQyN/lfjZFAzBf3XeXToiwJBGeZ0HUtlz T1/8LpMqJJai5txLL0VIOuleG7EF0phZmg3iF6FPDtIPeHyOPY=
Archived-At: <https://mailarchive.ietf.org/arch/msg/fud/O2kk_IO6_0iA59GTBOnL0Hl2N84>
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 09:08:20 -0000

Hi Carsten,

On 10/10/2017 10:41 AM, Carsten Bormann wrote:
> 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 wouldn't say it has evolved but it is now more clearly described.

But if you like the current text then I am happy.

Ciao
Hannes

v2.23.0 | Report a Bug | By Email