AODV update Charles E Perkins Elizabeth M Royer

  • Slides: 8
Download presentation
AODV update Charles E. Perkins Elizabeth M. Royer Samir R. Das

AODV update Charles E. Perkins Elizabeth M. Royer Samir R. Das

Mobi. HOC • http: //users. ece. gatech. edu/~cktoh/workshop. html

Mobi. HOC • http: //users. ece. gatech. edu/~cktoh/workshop. html

Forgetting sequence numbers C A • • B D Suppose A D via B,

Forgetting sequence numbers C A • • B D Suppose A D via B, C D via B Suppose B reboots and forgets everything Suppose A does not know this yet If B sends RREQ to C a routing loop results

DELETE PERIOD • Long enough for B’s neighbors to find out that links to

DELETE PERIOD • Long enough for B’s neighbors to find out that links to B have broken • After neighbors find out, they maintain last sequence number for at least DELETE_PERIOD • After reboot, B sends RERRs in response to receiving any data packets • Lifetime of route assumes dual role

Multicast – after reboot • A node loses all of its multicast tree info

Multicast – after reboot • A node loses all of its multicast tree info • Broadcast a MACT with ‘R’ bit set • Upstream neighbors delete the node from any relevant lists of next hops • Downstream neighbors try to rebuild their tree branch

IP Address Autoconfiguration • • Some nodes may not have IP addresses Following zeroconf

IP Address Autoconfiguration • • Some nodes may not have IP addresses Following zeroconf idea, try 169. 254/16 Pick an address from upper 62 k range Perform duplicate address detection by sending RREQ for that address • For source address of RREQ, pretend to be a node in lower 2 k range • Sequence numbers to be zero

Other details • • Assigned type numbers for extensions Changes appendix added Typos, improvements

Other details • • Assigned type numbers for extensions Changes appendix added Typos, improvements Corrected sequence number handling in RERR message

Other issues • IPv 6 versions for messages by next IETF • Should RREQ/RREP

Other issues • IPv 6 versions for messages by next IETF • Should RREQ/RREP contain source routes? – if so, how long should route information persist? • Rethink service discovery extensions?