Does IPV6 make SocialVPN useless?

[JustDoIt Ly]

We just had a World IPv6 Day on June 8.

I am wondering SocialVPN is useless when IPv6 is ready.

Can some body answer my question?


Ying

[Renato Figueiredo]

There's a few reasons why IPv6 does not make it useless:

- IPv6 adoption does not necessarily mean that IPv4 goes away and NATs will no longer be around; actually, during IPv4/IPv6 transition, NATs are seen as key - http://www.networkworld.com/news/2008/072108-ipv6nat.html 

- Even if IPv6 is fully deployed, it's not clear that NATs/firewalls will not be still around - they also provide a layer of 'defense' in that resources not directly addressable from the public network are less likely to be subject to attacks. If you have computer running an O/S with a security vulnerability, IPv6 will not stop attackers to compromise it.

- If you want to establish a trusted, private link between two trusted peers, IPv6 supports IPsec, but you still need to exchange keys and configure links. This is at the core of socialvpn, automatically mapping trust relationships to configuration of security, and this is not solved by IPv6. 

- socialvpn supports IP multicast among peers across a WAN

--rf

--
You received this message because you are subscribed to the Google Groups "acis.p2p" group.
To post to this group, send email to aci...@googlegroups.com.
To unsubscribe from this group, send email to acisp2p+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/acisp2p?hl=en.

--
Dr. Renato J. Figueiredo
Associate Professor
ACIS Lab - ECE - University of Florida
UF Site Director, Center for Autonomic Computing
http://byron.acis.ufl.edu
ph: 352-392-6430

[macbroadcast]

On Thu, Jun 9, 2011 at 3:02 PM, Renato Figueiredo <ren...@acis.ufl.edu> wrote:

> - socialvpn supports IP multicast among peers across a WAN

hello renato, thats very interesting, how can i read more about the
technical details ?

regards

Marc

[Renato Figueiredo]

Marc,

We don't have a publication focusing on the multicast aspect of socialvpn yet.

In a nutshell, the way this is done in the current implementation is by identifying a multicast packet at the source and generating unicast messages to each socialVPN peer the source is connected to. There is tree-based overlay multicasting support on Brunet (socialvpn's underlying p2p library), but this is not yet integrated with socialVPN. This is partly because we have so far mostly focused on multicasting for resource discovery, not for streaming; the multicast-to-unicast approach is simple and seems to work well for resource discovery with small number of connections.

Some protocols embed IP information on message payloads, and require further processing because of how socialvpn does dynamic IP address mapping. We have implemented protocol-specific modules for mDNS/Bonjour and UPnP.

--rf

--

You received this message because you are subscribed to the Google Groups "acis.p2p" group.
To post to this group, send email to aci...@googlegroups.com.
To unsubscribe from this group, send email to acisp2p+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/acisp2p?hl=en.