On Wed, May 23, 2007 at 12:33:49PM -0700, Philip Levis wrote: > Have you taken a look at TEP 125? Jonathan Hui, David Moss, and I > proposed introducing a new frame format for TinyOS (the I-Frame) which > would allow it to exist along side a 6lowpan network without causing > packet confusion.
Yes, TEP 125 promises the implementation of an I-Frame to show up soon in tinyos-2.x/tos/chips/cc2420. I was hoping that this would allow me to use the whole 802.15.4 payload once it shows up without having to change things in tinyos-2.x/tos/chips/cc2420 or at least minimize the necessary changes. Hence, I have not tried to implement something myself. > To some degree, we were waiting for a solid 6lowpan > implementation before pushing this forward. The 2.0.2 release is slated > for early July. If an I-Frame implementation would make it easier to get rid of the AM Type field I'm happy to use it. I also have not optimized my buffers and structures heavily, but it may be then possible to directly embed something like a message_t in lowpan_pkt_t and use it instead of a uint8_t[102]. lowpan_pkt_t is a struct I am using to represent a packet. Matus _______________________________________________ 6lowpan mailing list [email protected] https://www1.ietf.org/mailman/listinfo/6lowpan
