[SensorNetArch] Plan

[Cheng Tien Ee]

> We have said that every node responds to its address and the broadcast 
> address.  this is certainly a common link characteristic.  What does 
> this mean for a multiple name per node model?

Don't know if this is way off, but does it make sense to have a separate 
table, with entries that can be added / removed by network protocols. 
The columns of the table might be

1. Link
2. Address
3. Network protocol id

When a packet is received via a link, this table is consulted. For all 
matches in the table, then the packet is passed to the network protocol 
with the particular id. The address field is simply 16-bit (currently) 
numbers, it's interpretation is up to the network protocol. For data 
centric storage, the address field would carry the address of the 
immediate next hop, and at the network level, the final destination 
address is handled by dcs routing, not SP, so that won't come into the 
picture here. For a debugging / snooping protocol, it can set the 
address and link fields to be some equivalent of '*', and SP passes it 
all packets that come through.

e