[Ns-developers] GSoC proposal for ns-3-click

[Lalith Suresh]

Hello all,

I've uploaded the updated application at the GSoC website with the changes.

@Ruben: Shall I paste your previous review in the comments section of my
application? I guess it will help other mentors if they wish to comment?

On Tue, Mar 30, 2010 at 6:20 PM, Lalith Suresh <suresh.lalith at gmail.com>wrote:

> Hello Ruben,
>
> Thanks for the reply! My comments inline.
>
> On Tue, Mar 30, 2010 at 2:38 PM, Ruben Merz <ruben at net.t-labs.tu-berlin.de
> > wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hi Lalith,
>>
>> I briefly went over your proposal. Here are a few comments.
>>
>> In Section 2.4.1, you may want to explain better the problem and what
>> you want to achieve. But, I like the final design goal. One more
>> question, how would this work for Click configurations that handle MAC
>> protocols? Would you have a "ClickMAC" instance (since you are thinking
>> about a IPv4ClickRouting instance)? For this case, it might be too much
>> for a GSOC project. But it would be great that if someone comes after
>> you, no major architectural changes are necessary.
>>
>
> Although I'm not too familiar with Click handling MAC protocols, I'm not
> quite sure nsclick handles that. Either way, I'll look into it.
>
>
>>
>> One general comment: please make more explicit what Click would replace.
>> In the current state of your proposal, it is very unclear whether you
>> want Click to replace L3 components (this one, IMHO), L4 componwent (not
>> this one) or L2 components (if time permits).
>>
>> Even better, make a diagram of a typical packet path through the
>> simulator and where you would like Click to sit.
>>
>
> It will replace much of the Ipv4L3Protocol's code and the whole of the
> Ipv4RoutingProtocol as well. I will also add a diagram to explain what I
> have in mind.
>
>
>>
>> In 2.4.3.1, you suggest to do the following:
>>
>> "Develop a method Ipv4ClickRouting::RouteOutput() which can simply
>> return the necessary routing information from Click."
>>
>> I suspect this won't work, because this is typically something you do
>> inside Click. The click process might add himself IPv4 headers to
>> packets. (side note: look at the canonical Click router in the Click
>> paper). My feeling is that you only need 2. i.e. "Modify the
>> UdpL4Protocol/TcpL4Protocol Send() implementations such that for Click
>> based nodes, the packets are passed on to the Click device using the
>> simulator API."
>>
>
> Done. Will look into this as well.
>
>
>>
>> For 2.4.3.4, a very good test is to have the canonical Click router
>> example working inside ns-3.
>>
>
> You mean the IP router right? I'll include this as well.
>
> I will make the changes to the application and will inform the list when
> I'm done. :) Thanks for your time!
>
>
>>
>> Ruben
>>
>>
>>
>> On 3/30/10 04:52 , Lalith Suresh wrote:
>> > Hello Mentors,
>> >
>> > On Mon, Mar 29, 2010 at 7:12 PM, Lalith Suresh <suresh.lalith at gmail.com
>> >wrote:
>> >
>> >> Hello all,
>> >>
>> >> Attached below is the first draft for my GSoC proposal on ns-3-click.
>> >> Kindly go through the same and suggest improvements. :)
>> >>
>> >> I wasn't sure if I could send a .pdf file to the list, so I've sent it
>> as a
>> >> .txt file. It's a little harder to figure out the formatting!
>> >>
>> >
>> > I've uploaded my application at the GSoC online facility. Please do
>> review
>> > it for me. Thanks!
>> >
>> >
>> >>
>> >> --
>> >> Thanks and regards,
>> >> Lalith Suresh
>> >> Department of Computer Engineering
>> >> Malaviya National Institute of Technology, Jaipur
>> >> +91-9982190365 , www.lalith.in
>> >>
>> >
>> >
>> >
>>
>> - --
>> Ruben Merz                   Deutsche Telekom Laboratories
>> http://www.net.t-labs.tu-berlin.de/people/ruben_merz.shtml
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.10 (Darwin)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>
>> iQEcBAEBAgAGBQJLsb+lAAoJEIem9YkUyRjtjZoIAJx60jP592x9pl1byRzmZs9y
>> BXFu/Y49h8M2LpPx6ZfBYJg/3aesbBwVnZwKyycoQu9xcJCh7BZyGdQXQCZhl9pY
>> EE8vL6lruhTYoNO4FoShRXIToUHr6T4KgkoQ54wknvXSut9S5R9Pnb4ubSnLGPra
>> wvB7erjZChpsp9LuDSRr8PeZ3zcnLM/2jwB19zkeNTifRNgpARBnIoP7ZgnTo4RU
>> nNPBvbULviLkIWWDfwg5nt5j1AURLENozw/JhGSCm72PgYPzSg+KTAJj85z0R9wj
>> fhGwLvdTAUsdkfkgMm2cY1o4WopCDplUDof/w8wY4NQwBwZMHGovkADxS+JHDug=
>> =DokU
>> -----END PGP SIGNATURE-----
>>
>
>
>
> --
> Thanks and regards,
> Lalith Suresh
> Department of Computer Engineering
> Malaviya National Institute of Technology, Jaipur
> +91-9982190365 , www.lalith.in
>



-- 
Thanks and regards,
Lalith Suresh
Department of Computer Engineering
Malaviya National Institute of Technology, Jaipur
+91-9982190365 , www.lalith.in