[Tinyos-devel] b6lowpan stack release

[Stephen Dawson-Haggerty]

TEP125 (as I understand it) is for tinyos networks wishing to coexist
with 6lowpan networks.  In other words, tinyos can use I-frames so as
not to get confused by my 6lowpan packets, but tinyos doesn't have a
way to generate non-AM packets.  That's the reason for the modified
radio component which doesn't insert the AM field; other tinyos nodes
using I-frames should discard the 6lowpan frames becasue their
dispatch is not NALP.

Steve

On Thu, Jul 17, 2008 at 2:57 AM, Miklos Maroti <mmaroti at math.u-szeged.hu> wrote:
>> Have you read TEP 125?
>>
>> As of 2.1, I-Frames will be the standard packet format in TinyOS networks.
>> So all that's needed is putting the logic down in the CC2420 stacks that
>> pass up packets that don't match the TinyOS NALP byte. The 6lowpan stack
>> would then not require any ActiveMessageC shadowing.
>
> IRIS is compatible with TEP125, so maybe you can write a platform
> independent 6lowpan component. (Although IRIS does not have the packet
> link layer, but that can be implemented trivially).
>
> Miklos
>