This article is within the scope of WikiProject Internet, a collaborative effort to improve the coverage of the Internet on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.InternetWikipedia:WikiProject InternetTemplate:WikiProject InternetInternet
This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
This article is within the scope of WikiProject Telecommunications, a collaborative effort to improve the coverage of Telecommunications on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.TelecommunicationsWikipedia:WikiProject TelecommunicationsTemplate:WikiProject TelecommunicationsTelecommunications
Latest comment: 10 years ago2 comments2 people in discussion
Add long name of DYMO to first paragraph, e.g.:
The Dynamic MANET On-demand (DYMO) routing protocol is successor to the popular Ad hoc On-Demand Distance Vector (AODV) Routing protocol and shares many of its benefits. It is, however, slightly easier to implement and designed with future enhancements in mind.
I cannot edit this page right now. NotDifficult (talk) 13:07, 29 April 2011 (UTC)Reply
This article has no actual intro paragraph. I got here on an unrelated search so I have no context or required information - after reading a bunch of text that appears to be pulled from an RFC I now know a bit about how DYMO functions but still have no idea what it is. Is this some sort of microcontroller communications protocol? Is it used by phone companies? ISPs? Where is it found and what does it do? —Preceding unsigned comment added by 213.186.4.38 (talk) 18:34, 20 July 2016 (UTC)Reply