[Tinyos-devel] net2 goals/timeline for 2.1.1

[Stephen Dawson-Haggerty]

The major issue for core is the frame format.  The 6lowpan standard
when used over 802.15.4 requires the 6lowpan payload to start
immediately following the 802.15.4 frame header; the first byte is an
IANA assigned dispatch value.

This dispatch value is the same as the "network" field when I-frames
are enabled, and so it is possible to have a radio stack which
supports both Active Messages and other network protocols.  This is
pretty much the same as the dispatching of packets base on the
ethernet header in other systems-- IP and non-IP protocols can
coexist.

Conceptually, the layering would be (for AM)
--------------------------
| 802.15.4 | network (6LOWPAN_NALP) | AM  | ...
--------------------------

What is needed is an interface to intercept the non-NALP network
values and feed them into blip, and an interface to allow blip to send
packets with its own (arbitrary) network ids.

Steve


On Fri, Jun 12, 2009 at 11:37 AM, Omprakash Gnawali<gnawali at usc.edu> wrote:
> We would like to include bls and blip in 2.1.1. We will be ready by
> the end of August.
>
> During net2 meeting, we discussed what (software/suggestions) we would
> need from core for that to happen. Steve will send a follow-up email
> on that.
>
> Thanks.
>
> - om_p
> _______________________________________________
> Tinyos-devel mailing list
> Tinyos-devel at millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-devel
>