Limited Application of ExOR Yao Zhao

Limited Application Static –No mobility Small Scale –Tens of nodes Dense network Maybe Only Rooftop Networks File downloading application –No voice, maybe not web –No reliable guarantee No Cross Traffic

Static Knowing the whole topology –In a mobile network, this is expensive EXT is costly –Measure link states of all possible links Route change –During a batch, route may change

Small Scale Knowing the whole topology –In a mobile network, this is expensive EXT is costly –Measure link states of all possible links Large overhead in ExOR packet header –All the forwarders are included in ExOR header –Long vain waiting of forwarding timer –The larger the network, the longer the average distance between S and D, the more forwarders in the list Traditional header (24~48 -> 8 if AODV) ExOR header (44~114 for 38-node network)

Dense Networks S A B C D E X

Rooftop Networks

Limited Applications No TCP and hence proxy Voice –Jitter Web service –Is batch good? –May introduce large delay Large file download –Best for ExOR

Cross Traffic Forwarding timer –Give higher-priority nodes enough time to send? –Assume 5 packets sent if a node cannot hear another node with higher priority – Rough – use CSMA/CA, competition based MAC –If there is cross traffic, hard to estimate the transmission time of other nodes

Unfair Comparison Bad Traditional routing (DSR) –Don’t think about link state changing –Long packet header –Send the entire file to the next node before the next node starts sending Bad MAC Selection –Retransmit packet if ACK is lost –Why not packet train? A Paper in 2005 compared to some works before 1999

Just For Fun 32? 38? Routing? MAC? Routing?