Re: [Fud] Charter Text

[Carsten Bormann <[e-mail]>]

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 <[e-mail]> 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