Re: [Fud] Charter Text

Carsten Bormann <cabo@tzi.org> Thu, 10 August 2017 21:51 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 CA2D813245E for <fud@ietfa.amsl.com>; Thu, 10 Aug 2017 14:51:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 1lx-1ynVOv-X for <fud@ietfa.amsl.com>; Thu, 10 Aug 2017 14:51:11 -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 70A0D132379 for <fud@ietf.org>; Thu, 10 Aug 2017 14:51:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v7ALp7pX009335; Thu, 10 Aug 2017 23:51:07 +0200 (CEST)
Received: from client-0031.vpn.uni-bremen.de (client-0031.vpn.uni-bremen.de [134.102.107.31]) (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 3xT1zb488yzDL5g; Thu, 10 Aug 2017 23:51:07 +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: <76330c36-4e99-3013-e6bf-61e9c627ba46@gmx.net>
Date: Thu, 10 Aug 2017 23:51:06 +0200
Cc: Inria Paris <Emmanuel.Baccelli@inria.fr>, fud@ietf.org
X-Mao-Original-Outgoing-Id: 524094666.785967-597143cddc62f394c1cf2db89cccc75c
Content-Transfer-Encoding: quoted-printable
Message-Id: <149A55E2-29FE-49CB-834D-8C6827460EAE@tzi.org>
References: <8f8528da-d1eb-08c7-b3fe-b1f4febed595@gmx.net> <CANK0pbbbgEONiCeuQGOuRO9Gq62RpAVhh53xLxd5JOMQtJg-_g@mail.gmail.com> <76330c36-4e99-3013-e6bf-61e9c627ba46@gmx.net>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/fud/JHoksMH66w7-w5ofBFLjc8LHqEY>
Subject: Re: [Fud] Charter Text
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 21:51:14 -0000

Hi Hannes,

We always have this tension of different classes of hardware target.
Most of the work of CoRE was about targeting class 1, but not in the sense of targeting it exclusively, but just in the sense that class 1 can be part of the solution as well as the higher classes (see also the 7228bis for a way to extend the class nomenclature — https://lwig-wg.github.io/terminology/ ).

On Aug 8, 2017, at 12:29, Hannes Tschofenig <hannes.tschofenig@gmx.net> wrote:
> 
> 
> "
> This group focuses on defining a firmware update solution for Class 1
> devices, as defined in RFC 7228, i.e., IoT devices with ~10 KiB RAM and
> ~100 KiB flash.
> "

Maybe s/for/that is applicable to/ (so it’s not just limited to class-1, but can also work for class-2).

Maybe add that the sweet spot (full range of capabilities) is likely to start about factor 2 or 3 above those numbers, as you mentioned.

And maybe also give an impression of where the range of applicability we are shooting for will end (i.e., this is not meant for updating Linux, which 7228bis calls J-group and ARM calls A-class).

Grüße, Carsten