Hello,

I am evaluating possible solutions for implementing a topology control
algorithm in ns-2. The goal of our implementation is to analyze the
presence of a topology control algorithm on existing routing protocols
(AODV, DSR), ... and in our special case to see whether the information
obtained during algorithm execution is of any use to routing protocols.
However, I would like to ask some questions to find out whether my
approach sounds reasonable.

I have already looked into into the wireless node initialization code
and the interface between the link layers (ll.{cc,hh}) and the node
entry point where the packets get dispatched. From what I understand
local packets are dispatched to the port multiplexer and non local ones
are sent to the routing agent. In addition some routing agents hold a
direct link to the link layer component for special actions (for example
in AODV where packets are purged.)

These observations from above made me believe that replacing the link
layer would be an easy solution because I don't have to change anything
in the other layers. My actual implementation would look like the following:

  - Create a new special LinkDelay component which has the same
    interface as the LinkLayer component.
  - This new component directly processes messages used by the
    topology control algorithm (or -in the initial development phase-
    uses some static information).
  - The new component limits the view for the upper layers. E.g. the
    routing protocol only sees its "allowed" neighbors.
  - It either sits between the existing LL component and the node and
    routing interface, replaces the existing LL component or sits
    below it. I am not sure here which choice would be the most flexible
    one.

Does this implementation sound reasonable or am I missing something? I
looked on the web and found some other people implementing topology
control algorithms but the available (public) information is quite scarce.

Regards,
        Christian Walter

-- 
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ \\\\\\ \\ \
Christian Walter Bakk. techn.\
email: [EMAIL PROTECTED]          \

Reply via email to