[manet] Re: A partial response to <Re: Review draft-perk ins-manet-aodvv2-05>

Charlie

It would be useful if you could persuade the authors to make the paper - or the draft they submitted to the IEEE, which is usually where rights transfer - available other than behind a paywall.

(Maybe most people here have institutional access, so not critical, but I for one don’t. Of course that’s not critical was I won’t be implementing it, but maybe others would find it useful.)

> On 16 Jul 2025, at 23:39, Charlie Perkins <[email protected]> wrote:
> 
> Hello Juliusz,
> 
> My days as a Unix systems programmer are distant and pleasant memories.  I was, however, quite involved with implementations of AODV 20 years ago.  AODV and AODVv2 place similar demands on the operating system. I reckon that AODVv2 will be equally implementable as AODV.
> 
> I recently obtained the following paper which provides a much more detailed discussion about how to implement AODVv2 in user space.
>     Sergio Machado, Israel Martín-Escalona, Enrica Zola, and Francisco Barceló-Arroyo, "A User Space Implementation of the AODVv2 Routing Protocol", 2021 International Conference on Software, Telecommunications and Computer Networks (SoftCOM 2021), October 2021, Split, Hvar, Croatia, DOI 10.23919/SoftCOM52868.2021.9559121
> At first glance, it seems to me that this paper answers your question.  If desired, and if I have time (not guaranteed) I could try to present some interesting points about the paper next week.
> 
> PS. I have a 9-track tape with the New South Wales source code.  I guess I ought to send it to somebody for safekeeping.  Also, most of the news articles from Usenet from the days when a person could read every newsgroup.
> 
> 
> On 5/12/2025 6:42 AM, Juliusz Chroboczek wrote:
>> Hello Charlie,
>> 
>>> Prior to resubmission last year, I reviewed the comments I was able to
>>> find about AODVv2, plus some I had received by private email.  All of
>>> those comments were addressed, except for the observation that AODVv2
>>> needed to have a publicly available implementation for evaluation.  And,
>>> now, there is an NS-3 implementation being made ready for general release.
>> If I'm not mistaken, NS-3 is a discrete event simulator running in
>> userspace.  It is not clear to me at all how the experience of an
>> implementation in NS-3 carries over to implementations on real hardware.
>> 
>> I think that AODV(v2) is a nice protocol, and I have learnt a lot from it
>> when designing Babel.  However, one important property that I took into
>> account when designing Babel was implementability.
>> 
>> Charlie, could you please outline how you would envision an implementation
>> of AODVv2 running on a general pupose OS such as Linux?  What would need
>> to run in userspace, what would run in the kernel, and what would the
>> user/kernel interface look like?
>> 
>> Thanks,
>> 
>> -- Juliusz
> 
> _______________________________________________
> manet mailing list -- [email protected]
> To unsubscribe send an email to [email protected]

_______________________________________________
manet mailing list -- [email protected]
To unsubscribe send an email to [email protected]