Hello FreedomBoxers, I hadn't heard of your project but I like it. There's far too much tapping in this world (and especially in my country, where we seem to check on everyone except the CA that signs most of the country's credentials.
> 6bed4 is a protocol for tunneling IPv6 over > IPv4 UDP packets, which lets it cross all sorts of dumb legacy > networks. Another aspect of the protocol which is highly relevant to > FreedomBox, is the fact that it auto-assigns addresses with no help > from the user. Plus, so far, it seems to work everywhere. > As far as I can tell, the main drawbacks are: > > 1. 6bed4 relies on the kindness of whoever provides the tunnels - > kindness may not scale. This is particularly true for v00, and indeed it is not designed to pull heavy loads. It is designed to support modest apps such as SIP telephony or chat. The v01 draft will add bypasses that go directly to a remote router, as point-wise indicated on these slides, http://openfortress.nl/tmp/nluug2011.pdf > 2. It's IPv6, so it's not useful for communicating with the IPv4 world. Who cares ;-) My SIP project, of which this is an outgrowth, has as an explicit goal to support IPv6-only SIP telephony. It is also a strong supporter of ZRTP. Supplying everyone with a zero-config IPv6 address is just part of that game I suppose. The FreedomBox servers (somewhat) different goals, so it may be a problem to your project of course. > The foundation may be able to help out with #1? I'm certainly eager to get more parties from the routing community involved by adding nodes. > Here is the URL: http://devel.0cpm.org/6bed4/ A few links to the background project, in case you care: http://devel.0cpm.org/firmerware/ http://reverse.0cpm.org/grandstream/ http://devel.0cpm.org/sipproxy64/ Cheers, -Rick _______________________________________________ Freedombox-discuss mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
