Fwd: Re: Hello?
"Lance James" <[email protected]> Thu, 14 Aug 2003 09:57:55 -0700
| Newsgroups | gmane.comp.security.invisiblenet.iip.devel |
|---|---|
| Message-ID | <[email protected]> |
Fred's a lawyer :) not a latency expert. Lance -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of auto97841-revL73yDgGBWk0Htik3J/[email protected] Sent: Thursday, August 14, 2003 4:40 AM To: [email protected] Subject: [iip-dev] Fwd: Re: Hello? heh I know it was a rhetorical question, and that you know these answers as well, but just for clarity: > *distributed network of generic TCP proxying nodes check. [note that handling TCP proxying requires lossless delivery and strict ordering, so applications running plain TCP proxies on top of I2P will need to configure their routers for this mode of operation. UDP is handled directly with no specific I2P settings] > *nodes implemented to provide a generic service to any TCP-aware > application (not optimized for email, http, ftp, IM, etc). check. > *nodes implemented to run on typical desktops (win, mac, nix) with > minimum user involvement check. > *node default settings that respect user needs (bandwidth throttling, > middleman mode, etc) check. > *nodes capable of running in "middleman mode" (relay only, no exit to > TCP) check. [I2P itself is only "middleman mode" - exit proxies are applications and must be explicitly run] > *distributed discovery mechanism (auto-updating node table? distributed > bootstrapping?) check. [DHT operating as I2P's network information system handles announcements and network integration. more details forthcoming in the spec shortly] > *encryption and camouflage for all traffic between relays (equal packet > sizes? chaffing? etc) check. [I2NP (network proto) does not require a specific set of transports for inter-router traffic, but they must secure the data from alteration or viewing. they may use chaffe, constant bit rates, message padding, proxies, as well as stego.] > *nodes capable of basic NAT evasion (assuming most users will not know > how to config firewalls) check. [again, I2NP leaves the transport layer open, so polling HTTP, tricky udp, email, and the like can be used to bridge across any network topology transparently] Its interesting to notice that Fred's outline doesn't include latency requirements. -jrandom Concerned about your privacy? Follow this link to get FREE encrypted email: https://www.hushmail.com/?l=2 Free, ultra-private instant messaging with Hush Messenger https://www.hushmail.com/services.php?subloc=messenger&l=434 Promote security and make money with the Hushmail Affiliate Program: https://www.hushmail.com/about.php?subloc=affiliate&l=427