I think that we need some additional dimensions (yes, time awareness is one). I'd like to also add something about field upgrade constraints.
I'd like to have a class 3 defined: I'm thinking about the endless devices which we have come to hate with about 4M of hard to upgrade flash (sometimes execute in place), a *nix kernel, and a single useful process running in addition to the unwanted telnetd with stock password. I'd like to have a class defined (8? 9?) that matches what we see in current mobile phones. And another that matches what we see in current (router) control plane CPUs (very similar to class 3 above, btw) -- Michael Richardson <[email protected]>, Sandelman Software Works -= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ Lwip mailing list [email protected] https://www.ietf.org/mailman/listinfo/lwip
