1 / 5

AODV status update

Learn about recent changes in the AODV draft, including routing information updates, terminology changes, and comments received for further development. Stay informed on AODV implementations, mailing lists, and upcoming workshops.

randolphf
Download Presentation

AODV status update

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. AODV status update • Changes in draft …-10 • Progress towards Experimental RFC • Implementer’s mailing list • Interoperability testing • Futures workshop

  2. Changes since draft …-09 • Reorganized text so that: • Incoming messages change routing information • Outgoing messages utilize information from route table • Affected: RERR, RREP • Specified that sequence numbers are to be compared as signed ints • Changed terminology to replace “FLOODING_ID” by “RREQ_ID”, since the exact meaning of what “flooding” means is up for discussion now • Clarified that RREQs do not have to be retransmitted over every network interface, depending upon type of medium and domain of ad hoc coverage.

  3. Progress towards Experimental RFC • Very good but late comments received from Yih-Chun Hu • Good but late comment received from Manel Guerrero Zapata • should a node remember its sequence number across reboots • Excellent comments received from Bill Fenner and Alex Zinin • All of these comments will be resolved in a new draft version of AODV to be produced before April. Discussion should continue on the mailing list; I will try to send text tonight or tomorrow with proposed resolutions • No changes in packet formats will be needed. There are two egregious mistakes in draft …-10 that need to be fixed right away • missing RREQ_RETRIES definition (should be 2) • RREQ_IDs should be stored for PATH_DISCOVERY_TIME, not PATH_TRAVERSAL_TIME

  4. AODV Interoperability testing • Starts next week with 7 different implementations from different organizations • Implementers mailing list (currently almost 100 members): • aodvimpl-public@lists.sourceforge.net • https://lists.sourceforge.net/lists/listinfo/aodvimpl-public • Linux freeware implementations (forgot the URL ) • Possibly AODV-6 release upcoming (Ryuji Wakikawa)

  5. AODV workshop • Held immediately preceding MobiHOC 2002 in Lausanne, Switzerland • Intended for anyone who wants to provide vision for the future evolution of AODV • progress towards Proposed Standard • QoS extensions • Multipath (very encouraging results from Samir Das) • Flooding backbone • Multicast • Interoperability with Mobile IP{,v6} • Service Location • Any other business • Progress of Globalv6 and Globalv4 draft

More Related