Re: [Anima-bootstrap] IoT and scope of bootstrap

[Brian E Carpenter <[e-mail]>]

Hi Peter,

On 02/12/2015 02:11, peter van der Stok wrote:
...
> Such a network will be composed of LLNs, and includes constrained devices.
> Sleepy nodes (energy harvesting sensors) may include ANIMA services, but special provisions to include them in the network are
> more likely to be deployed.
> 
> For the moment I have no idea what ACP and Anima bootstrapping implies in terms of resources and resource consumption.
> But excluding everything smaller than a tablet may be premature.

ANs are basically nodes that participate in management actions that historically
would have been carried out by a centralised NMS or NOC. So in my view an individual
light switch isn't an AN but should be managed by an AN. The lighting controller
for a section of a building could be an AN. Or to say it another way, a node that
just does what it's told isn't an AN. (It may of course need a security bootstrap
anyway.)

However, indeed the resource question is important. An AN is going to need a
multi-threading OS, a full network stack, and a heap of software on top. For
example, GRASP alone is about 2500 lines of C (in the now-obsolete BUPT prototype)
and looks as if it will also be a couple of thousand lines of Python. Add to
that the ACP, the security bootstrap, and all the supporting code, before
you install any ASAs.

    Brian