-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > > Here's how it'd work - a router in C would build, for instance, a > > 3 hop outbound tunnel, using a peer in B as the first hop, and > > peers in either A, B, or C as the second and third hop. > > Does this mean that i2p is now using telescopic tunnel construction?
No[1], and I doubt we will [2]. We use existing tunnels for building new ones. Turtles, all the way down. [1] http://dev.i2p.net/cgi-bin/cvsweb.cgi/i2p/router/doc/ tunnel-alt.html?rev=HEAD#tunnel.request [2] http://dev.i2p.net/cgi-bin/cvsweb.cgi/i2p/router/doc/ tunnel-alt.html?rev=HEAD#tunnel.building.telescoping You're right though, for brevity I didn't explain how the user would first build their own exploratory tunnels, and how a separate set of tunnels would be used for delivering the actual client messages, but I didn't think it was necessary for explaining what peers in groups A, B, or C would be used. I2P has lots of details to its design that we use to provide anonymity, but going through them all here would not be appropriate. Swing on by the I2P list for that stuff. =jr -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDT34EWYfZ3rPnHH0RAoyIAJ4k4jesRk/Z6lT98+WW5Dj5Lm5zSgCdELgA Po7YLS7csb9LHInEYkQNjzY= =CFGn -----END PGP SIGNATURE-----
