I'm sorry, somehow I missed the point where you mentioned 802.15.4e. Feel free to ignore me. After last night I shouldn't be allowed to post in public forums full of people smarter than I.
--adam On Nov 6, 2014 9:46 AM, "Martine Lenders" <[email protected]> wrote: > Hi Adam, > > Am 06.11.2014 18:38 schrieb "Adam Hunt" <[email protected]>: > > > > Is support for TSCH in there somewhere? While I'm not entirely read up > on the spec it would seem to be fairly important these days. > > > > What is the current state of TSCH support in RIOT these days? I'm stuck > on my phone at the moment or I'd take a look for myself (really, it > probably has a bit more to do with my being hungover and slightly lazy this > morning). > > Currently use the already existing TSCH implentation OpenWSN. So that's > where it is hiding ;) > > Cheers, > Martine > > > > > --adam > > > > On Nov 5, 2014 9:15 AM, "Martine Lenders" <[email protected]> > wrote: > >> > >> Hi, > >> as discussed on the virtual meeting we aim to have the new network > stack running with the next release (end of November or before christmas). > Currently, I'm the only one directly involved into the development (appart > from several radio driver implementations), and while parts of the model > come from me, Hauke is currently refining it. As for development it is > clear, that I can't be the only one working on it. > >> > >> I'm currently in the testing stage of 6LoWPAN but it is mostly done, > but I still need some kind of way to communicate with the transceiver > module for older boards (alternative would be to remove it, but for this we > need #1772 and #1733 merged and all boards moved to the low-level driver > model). I hope I have this done at the end of next week. > >> > >> All in all it's still a long way to the transport layer and to speed > things up, I thought some of you guys may want to help me. I tried to split > down the tasks at hand and assigned preliminary some people who might be > able to do it. If you do not want/can not do this task, please notify this. > Also if you want to take over a task do tell so too, please. Every > assignment with a question mark is not fixed yet. > >> > >> * Model (Martine? and Hauke) > >> * 6LoWPAN > >> - backwards compatibility with transceiver module (Martine) > >> - bug-hunting (Martine) > >> - ND according to https://tools.ietf.org/html/rfc6775 (Martine?, > depends on a running ND for IPv6) > >> - optional: Next header compression (Oleg?) > >> * IPv6 > >> - port to netapi and pktbuf and remove 6LoWPAN dependency (Martine?) > >> - consistent and extendable IPv6 Extension Header API (Martine?) > >> - consistent and extendable ICMPv6 API (Lotte?) > >> - Neighbor discovery according to http://tools.ietf.org/html/rfc4861 > (Martine?, depends maybe on ICMPv6 API, but can be done without it, I guess) > >> * Transport layer > >> - port to netapi and pktbuf (Cenk?) > >> > >> * optional tasks for full deprecation of `transceiver`: > >> - port OpenWSN (would this also include an IEEE 802.15.4e MAC layer?) > and CCNlite to netapi or netdev > >> - port boards that use cc110x to periph API or port cc110x_legacy and > cc110x_legacy_csma to netdev > >> - either removal or port to netdev of redbee-econotag > >> > >> > >> _______________________________________________ > >> devel mailing list > >> [email protected] > >> http://lists.riot-os.org/mailman/listinfo/devel > >> > > > > _______________________________________________ > > devel mailing list > > [email protected] > > http://lists.riot-os.org/mailman/listinfo/devel > > > > _______________________________________________ > devel mailing list > [email protected] > http://lists.riot-os.org/mailman/listinfo/devel > >
_______________________________________________ devel mailing list [email protected] http://lists.riot-os.org/mailman/listinfo/devel
