Sorry, I actually read TEP 123 a bit too fast, and I missed the link estimator components and the engines of ctp, in which I am interested.
But CTP only applies to trees, so I'll have to make a number of changes to the interfaces so that they fit to what I need. Is there ongoing or planned work about generic routing protocols ? Or should I design this on my own and provide it at the end as a basis for future work (the code will be GPL) ? Regards, Romain On 2/28/07, Philip Levis <[EMAIL PROTECTED]> wrote:
On Feb 27, 2007, at 9:43 AM, Romain Thouvenin wrote: > It's not exactly what I am looking for. Collection and Dissemination > are about routing pieces of data (transport layer) in a tree, but what > I am going to implement (DYMO) is a generic routing protocol for any > MANET, only concerned with updating the routing table (network layer). > In terms of the OSI terminology, collection and dissemination are both transport protocols. But they of course have underlying routing layers. As far as transport protocols go, the collection protocol is very simple: it adds a single byte header for higher-level dispatch (think port/protocol ID). Everything else is part of the routing layer. > I didn't enter the details of RouteSelect, MultiHopSend and > MultiHopRoute, but their descriptions on > http://www.tinyos.net/tinyos-1.x/doc/ad-hoc.pdf looked like what I am > looking for. > > Maybe I have misread something, but Collection and Dissemination > seemed to high level for what I am looking for. Please look at the code carefully. In particular, CtpRoutingEngineP, and le/LinkEstimatorP. Phil
_______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
