« Return to Thread: ipv6 plans for ns-3
Re: ipv6 plans for ns-3
by Sébastien Vincent
::
Rate this Message:
Hi Tom,
Tom Henderson a écrit :
> Sebastien,
> I'd like to put the IPv6 code back on track for merging into ns-3-dev. Can
> you please provide a status update on the repos that you or your group are
> maintaining at https://svnet.u-strasbg.fr/hg/ and what you might suggest
> for next steps? Also, I'd like to know where the effort to refactor the
> transport protocols and network layer to allow a common transport protocol
> implementation to use IPv4 and IPv6 ended up-- I see that the current
> ns-3-ipv6 repo has separate IPv4 and IPv6 implementations for TCP.
>
>
Currently, https://svnet.u-strasbg.fr/hg/ns-3-ipv6 is very outdated.
Two day ago I begin to work with up-to-date ns-3-dev and port some of
the IPv6 components. It is located at
https://svnet.u-strasbg.fr/hg/ns-3-ipv6-2nd (not publicly available yet
but I will unlock access tomorrow or next monday).
For the next release, I really would like to have IPv6 routing, ICMPv6
(+ neighbor discovery protocol), UDP, IPv6 applications such as UdpEcho,
basic examples. If I had time radvd application to have IPv6 address
autoconfiguration, multihoming.
The features delayed will be TCP (if we can not find a good and easy
solution to integrate it nicely), IPv6 header extension (fragmentation,
loose routing, ...).
As I have a lot of work for my job arround wireless sensor network, I
can not work as long as I want on ns-3. But I will do my best during my
spare time on my holidays (tomorrow) to propose a working IPv6 stack.
For ns-3-ipv6-2nd repo I have also integrated Ipv6InterfaceAddress,
Ipv6Interface, NdiscCache. For routing code located in src/node, I think
it will be exactly the same for IPv6 (except changing Ipv4* to Ipv6* ).
For transport protocol, the main problem is (if I remember correctly)
that Tcp/UdpL4Protocol' and Tcp/UdpSocketImpl functions take Ipv4Address
arguments. We already have some discusses here with Mathieu but we have
not found a good solution to handle this. By the way same problem for
IPv4EndPoint / Ipv4EndPointDemux which majority of code will be duplicated.
To resume, I will open my private repository next couple of days. I will
continue to read code about recent IPv4 refactoring and implement
routing stuff (Ipv6L3Protocol), ICMPv6 (and neighbor discovery protocol)
and wait about transport protocol problem. Now all of us interrested in
IPv6 can begin to find a nice way to handle transport protocol in both
IPv4 and IPv6 without copy/paste code. And to finish It will be really
good if we can put great efforts on IPv6 integration for ns-3.6 to bring
ns-3 users the power of IPv6 ;)
Regards,
--
Seb
> Thanks,
> Tom
>
>
Tom Henderson a écrit :
> Sebastien,
> I'd like to put the IPv6 code back on track for merging into ns-3-dev. Can
> you please provide a status update on the repos that you or your group are
> maintaining at https://svnet.u-strasbg.fr/hg/ and what you might suggest
> for next steps? Also, I'd like to know where the effort to refactor the
> transport protocols and network layer to allow a common transport protocol
> implementation to use IPv4 and IPv6 ended up-- I see that the current
> ns-3-ipv6 repo has separate IPv4 and IPv6 implementations for TCP.
>
>
Currently, https://svnet.u-strasbg.fr/hg/ns-3-ipv6 is very outdated.
Two day ago I begin to work with up-to-date ns-3-dev and port some of
the IPv6 components. It is located at
https://svnet.u-strasbg.fr/hg/ns-3-ipv6-2nd (not publicly available yet
but I will unlock access tomorrow or next monday).
For the next release, I really would like to have IPv6 routing, ICMPv6
(+ neighbor discovery protocol), UDP, IPv6 applications such as UdpEcho,
basic examples. If I had time radvd application to have IPv6 address
autoconfiguration, multihoming.
The features delayed will be TCP (if we can not find a good and easy
solution to integrate it nicely), IPv6 header extension (fragmentation,
loose routing, ...).
As I have a lot of work for my job arround wireless sensor network, I
can not work as long as I want on ns-3. But I will do my best during my
spare time on my holidays (tomorrow) to propose a working IPv6 stack.
For ns-3-ipv6-2nd repo I have also integrated Ipv6InterfaceAddress,
Ipv6Interface, NdiscCache. For routing code located in src/node, I think
it will be exactly the same for IPv6 (except changing Ipv4* to Ipv6* ).
For transport protocol, the main problem is (if I remember correctly)
that Tcp/UdpL4Protocol' and Tcp/UdpSocketImpl functions take Ipv4Address
arguments. We already have some discusses here with Mathieu but we have
not found a good solution to handle this. By the way same problem for
IPv4EndPoint / Ipv4EndPointDemux which majority of code will be duplicated.
To resume, I will open my private repository next couple of days. I will
continue to read code about recent IPv4 refactoring and implement
routing stuff (Ipv6L3Protocol), ICMPv6 (and neighbor discovery protocol)
and wait about transport protocol problem. Now all of us interrested in
IPv6 can begin to find a nice way to handle transport protocol in both
IPv4 and IPv6 without copy/paste code. And to finish It will be really
good if we can put great efforts on IPv6 integration for ns-3.6 to bring
ns-3 users the power of IPv6 ;)
Regards,
--
Seb
> Thanks,
> Tom
>
>
« Return to Thread: ipv6 plans for ns-3
| Free embeddable forum powered by Nabble | Forum Help |
