[net2-wg] Network level names and mapping

[Rodrigo Fonseca]

Hi,

checked in a fairly complete skeleton of TreeRoutingEngineImplP.nc,
missing is the function that chooses the current parent given the
state of the neighbors and the simpler sendBeaconTask.

It interfaces with Phil's ForwardingEngine, and with the LinkEstimator.
Specifically, from the link estimator it uses the Packet and
LinkSrcPacket interfaces.
It maintains its own network level table with the route info about the
neighbors: their parent, hopcount, cost (metric), and this table is
synchronized with the LinkEstimator neighbor table. For this, it only
needs an event evicted, that informs when a neighbor should be removed
from the table.

Rodrigo


On 4/25/06, Rodrigo Fonseca <rfonseca at cs.berkeley.edu> wrote:
> Hi Om,
>
> I will check in today a version of the TreeRoutingEngineImplP.
>
> On 4/24/06, Omprakash Gnawali <gnawali at usc.edu> wrote:
> >
> > I have checked in a skeleton of LE: collection/LinkEstimatorP.nc. As
> > soon as these two issues are cleared up I will fill in the code. Right
> > now I am keeping the file short.
> >
> > 1. How should LE tell the routing engine the incoming link id? I am
> > assuming that the we decided that LE will provide send/receive
> > interfaces to be used by the routing engine for control messages.
>
> That's right. So this interface adds its LE header. I think the best
> way is for it to provide, alongside with AMPacket and Packet, a
> LinkSrcPacket interface:
>
> interface LinkSrcPacket {
>       command am_addr_t getSrc(message_t* );
> }
>
> >
> > 2. Is neighbortable exchange triggered using a command (as Phil's
> > suggestion) or using some form of timer/mechanism internal to the LE?
> >
>
> So we decided against piggybacking this in the normal routing
> exchanges? That is fine.
> If so, I think the safest is to provide a command to do it. It is also
> possible to provide the command and make it periodic, with the period
> being a parameter for a generic module.
> If the parameter is 0, it means no periodic exchange.
>
>
> > Thanks.
> >
> > > I've checked in a completed ForwardingEngineP. It now handles packet
> > > forwarding, etc.
> > >
> > > If the link layer does not support acknowledgments, then
> > > ForwardingEngineP does not provide reliability. If it does, then
> > > ForwardingEngineP does not stop forwarding a packet until it receives an
> > > acknowledgment.
> > >
> > > Comments/questions welcome.
> > >
> > > Kyle is going to start working on the upper interfaces, where you can
> > > instantiate collection clients, etc. What's the status with the LE and
> > > routing engine?
> > >
> > > Phil
> > >
> > >
> > > _______________________________________________
> > > net2-wg mailing list
> > > net2-wg at millennium.berkeley.edu
> > > https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/net2-wg
> > _______________________________________________
> > net2-wg mailing list
> > net2-wg at millennium.berkeley.edu
> > https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/net2-wg
> >
>