[Tinyos-8051wg] [Tinyos-2.0wg] 5/25 agenda

[Philip Levis]

I've started working through OSKI, and there are a bunch of issues we  
need to figure out with regards to the TinyOS networking stack. We  
should talk through these, as they have big effects on the rest of  
the system. We've avoided tackling these issues so far, but need to  
deal with them if we're going to make forward progress.

1) Do AM packets have a platform independent address field?
   - The basic question here is address. Do AM packets have a 16-bit  
address, or is the address determined by the underlying platform? If  
the former, then we need to be able to map between platform addresses  
and AM addresses (data link vs. AM addresses). If the latter, then  
I'd argue that address is not part of AM itself (for interface reasons).

2) Is AM an HIL abstraction, or does it sit above an underlying HIL  
packet abstraction?
   - The former means that AM implementations are platform/chip  
specific. On one hand, this lets AM take advantage of the underlying  
radio headers; on the other, it requires many implementations. The  
latter means that we need to decide exactly what the HIL is, in terms  
of a packet layer.

3) What fields does an AM header have?
   - Do we get rid of group? Does the AM header have an actual length  
field, or do we assume that is part of an underlying packet layer?

A lot of this boils down to deciding what the AMPacket interface  
looks like, and whether ActiveMessageC is HIL or built on top of the  
HIL.

Phil


-------

"We shall not cease from exploration
And the end of all our exploring
Will be to arrive where we started
And know the place for the first time."

- T. S. Eliot,  'Little Gidding'

_______________________________________________
Tinyos-2.0wg mailing list
Tinyos-2.0wg at Mail.Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-2.0wg