Re: [Fud] Editorial Charter Update

Hannes Tschofenig <hannes.tschofenig@gmx.net> Wed, 04 October 2017 13:54 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 4F00F1321DC for <fud@ietfa.amsl.com>; Wed, 4 Oct 2017 06:54:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.499
X-Spam-Level:
X-Spam-Status: No, score=-3.499 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, 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 eZXT6VbdX6FS for <fud@ietfa.amsl.com>; Wed, 4 Oct 2017 06:54:10 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (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 D722A1241F3 for <fud@ietf.org>; Wed, 4 Oct 2017 06:54:09 -0700 (PDT)
Received: from [192.168.91.203] ([31.168.171.66]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LZiQy-1daHBq486u-00lXBL; Wed, 04 Oct 2017 15:54:07 +0200
To: Chris Rouland <chris@phosphorus.io>, fud@ietf.org
References: <c14c92bf-cf99-efdb-6693-0e33519fbb0a@gmx.net> <CANK0pbaOHTb85xEZuAQ=3ju0P0HdU-8W4Gt8Ma_N3N90-YPSnw@mail.gmail.com> <8E6DE4EA-ADC8-434D-9BFD-87AFE2387DCE@phosphorus.io>
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Openpgp: id=071A97A9ECBADCA8E31E678554D9CEEF4D776BC9
Message-ID: <ea8d6bd6-0c23-92d7-df3f-db7a47977546@gmx.net>
Date: Wed, 04 Oct 2017 15:54:01 +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: <8E6DE4EA-ADC8-434D-9BFD-87AFE2387DCE@phosphorus.io>
Content-Type: text/plain; charset="windows-1252"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:1p+84j/LoBYFiwDXBPn8mya3lwCP4ZhtKDrcqLNhxYIQmNbQuU3 /szVS12LQznVU5Y4kAtVQ1yg1yl6Ea6iO2BA2Eig1R2iqooAULgX/higLx5nUFHZOukSsq4 r+3MG3pOGOtkSI0Dz8hS351DtxgZJp0NI3z+bCEW06gD4b+9JcuZGPFXSMVgf1AqFxxGrnp z+MToHNh2hACOoTGX6mgA==
X-UI-Out-Filterresults: notjunk:1;V01:K0:CdFc7B/xWdI=:94UVVKRmWTfUE4tvgL0A7V 9IYzGnaA2M2vWIsyNCpIW0pW8fEL+X0JS6Y3IvmXtak2UVJt5WAbol7RlQf5zgvvJkSuNVin+ IasK9T+Gk/wOsc5Ps6I7uqn//JtQDPY2KKvnWWm57+s8tQLDD9ji8SIFSBYo8hfY/JkcJyIsn ATUJvafgn1C2kLGRWkpIRLRcAISfUKQQgveWfsx+S+0MBmXxh/cP0q4dtBoS+MElPYVUjAGb/ 6cNRZQHdj89St8BMfdvI782k/wwvXY11PDnpRAqIb/2pXYMbiE3nT6l0yarnqG/pwPqSKvIAG AGwW6zhM0VykM41iLT2Oa0cPqrhc1fW6gjDionwIb395Ks88LgKUjVq9rcL/xEGEw6jJEUPEM ATXpIxsH6+8KQtQOa2rBYsNl6OdIuWhQzUN+gZk5wWtyrO1JeWkpinAq93QDe6d5azR8B0ttB iHOM1lOSnQI0cOzqRXrzgr1LyZvMz3XB+/KfalNOrSsB0JQIZljRrY9KFZWwXpF3wec0hE0JF SGlfViE25/JLLOmf+WOxvY3DtZ9f74n722KQ0NbWAPzBTkzSxLBAFIYGJm9AnbXJ1ofCNSXvM zh+rT4LPSGtK8Pm2FwMf6zqcFS5bYqIdIRkT6SbpSLjuDmQ+gAWobXgPxll+6gykuVj67ucn6 uO+geE/traRTOUXkBMF7Z0XYmjZdHemz8a3tdp4fJH1teftu8Zqs7zdzjw9GHdbNPJcIzReWO eVVRUOT+Tmf4FWj1Wroo146Gr+rcR+funqLIH0FA88wiKQpGWK5uXVMrs+LceqrstBp5wcvVn XqLO00TMVrV/53xghUj9ZTmh/207mXW6S2/jrbsHYyBwKi8f3U=
Archived-At: <https://mailarchive.ietf.org/arch/msg/fud/qicnPPen-8rrGWrCOpVzPzkIChM>
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: Wed, 04 Oct 2017 13:54:12 -0000

Hi Chris,

my intention is to describe a reasonable starting point that helps solve
a security problem in the IoT world.

You have to start somewhere and I am sure there is more work to be done
and charters can be extended over time as progress is being made.
Furthermore, nothing is saying at the work will not be useful for other
areas as well but it should at least define the core problem.

I hope my clarification makes sense.

Ciao
Hannes

On 10/01/2017 04:11 PM, Chris Rouland wrote:
> 
> Hi,
> 
> I do think that locking into the firmware binary itself could exclude a
> significant part of the problem set around updating embedded IOT
> operating systems that would not technically be classified as FW.
> 
> I think SUIT is good and broad.
> 
> 
> -Chris
> 
> 
>> On Oct 1, 2017, at 3:20 AM, Emmanuel Baccelli
>> <Emmanuel.Baccelli@inria.fr <mailto:Emmanuel.Baccelli@inria.fr>> wrote:
>>
>> Hi Hannes,
>>
>> thanks for the update. Reads well in my opinion. 
>> A couple of comments below:
>>
>> On Fri, Sep 29, 2017 at 1:00 PM, Hannes Tschofenig
>> <hannes.tschofenig@gmx.net <mailto:hannes.tschofenig@gmx.net>> wrote:
>>
>>
>>
>>     Firmware Updating Description (FUD)
>>     [Alternative proposal: SUIT (Software Updates for Internet of
>>     Things).]
>>
>>
>> To no surprise, I really like SUIT, but if the WG focuses only on
>> firmware and excludes other types of software updates, we should
>> probably keep that name for another working group ;)
>>
>> On the other hand, FUD is still a problematic name. How about an
>> alternative such as:
>>
>> FiDeL : Firmware Description for Low-end IoT devices
>>
>>
>>     out of scope are
>>     software update solutions that aim to take the features of scripting
>>     languages, such as JavaScript variants like JerryScript, into account.
>>
>>
>> FYI JerryScript is fully compliant with ECMA5.1, hence not really a
>> "variant".
>> Here, I don't think we need to be that precise anyway to get the
>> message across.
>> How about rephrasing with something like:
>>
>> "Software update solutions that target updating software other than
>> the firmware binary (e.g. updating scripts) are out of scope".
>>
>> Cheers
>>
>> Emmanuel
>>  
>> _______________________________________________
>> Fud mailing list
>> Fud@ietf.org <mailto:Fud@ietf.org>
>> https://www.ietf.org/mailman/listinfo/fud
> 
> 
> 
> _______________________________________________
> Fud mailing list
> Fud@ietf.org
> https://www.ietf.org/mailman/listinfo/fud
>