[Ns-developers] upcoming work on Ipv4 routing
tomh at tomh.org
Tue Oct 21 12:58:21 PDT 2008
>From: craigdo at ee.washington.edu [mailto:craigdo at ee.washington.edu]
>Sent: Friday, October 10, 2008 11:26 AM
>To: ''Mathieu Lacage''
>Cc: ns-developers at ISI.EDU
>Subject: Re: [Ns-developers] Design Review of ns-3-ipv6-1st (ns-3.3 newfeature)
>> At this point, my main concern is that I would like to know what the
>> plan is to deal with the ipv4 API rework under way in tom's
>I agree completely. I just spoke to Tom about this. We agree that the approach to take is to have Tom "adopt" Sebastien's changes
>and merge them into his IPv4 work. This will ensure that the two feature sets work together consistently, and will allow reviewing
>them as one consistent whole (which makes reviewer's lives easier).
>Logistically, this seems to mean that we "withdraw" the ns-3-ipv6-1st feature proposal and allow Tom and Sebastien to coordinate how
>to merge it into the IPv4 rework feature proposal. We will then see an IPv4, IPv6 rework feature proposal appear Real Soon Now.
Last month I put together a wiki page to track and describe the changes that will be proposed for IPv4 rework:
There is a repository to track this work (http://code.nsnam.org/tomh/ns-3-ip). Presently it implements items 1 and 2 listed on the wiki page.
More recently I've been working on the possible API and design for routing rework. After some discussion with Mathieu, I have written up a sketch of how I envision the design in a file called "README.routing.txt" in the top level of that repo.
Here is a link to the overall design approach:
There is also a file "README.routing.api" with more details about the API:
I plan to work on implementing this fairly aggressively through the rest of the week (trying to meet Craig's merge deadline) so please send comments if you care to review it in the meantime. I also will try to coordinate with Sebastien along the way.
More information about the Ns-developers