Changes between Version 9 and Version 10 of petconpaper


Ignore:
Timestamp:
Feb 27, 2009 1:20:00 PM (10 years ago)
Author:
anonymous
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • petconpaper

    v9 v10  
    3232</ul>
    3333
    34 <p><b>I2P</b></p>
    35 
    36 Abstract
    37 <p>
    38 In the following we explain the I2P network, a message based low latency mixing network build
    39 for anonymity and security. In detail the functions to sort and measure the
    40 capacity and speed of the network nodes will be described. We show that this
    41 approach works better than fixed speed rating used e.g. in the TOR network.
    42 </p>
    43 
    44 I2P Overview
     34
     35
     36<h2>I2P Overview</h2>
     37
    4538<p>
    4639I2P itself is a overlay network based on unidirectional tunnels routed between
    4740the I2P nodes. The used garlic routing is similar to the onion routing used by
    48 TOR, trnasmitting data from hop to hop until the endpoint of the tunnel is
     41TOR (ref), transmitting data from peer to peer until the endpoint of tunnel is
    4942reached. In contrast to TOR we use only hidden services in I2P with addition
    50 of a few otproxies operated by private individuals.
    51 The ancestor of the I2P project was IIP - a specialiced IRC server and clients
    52 transmiting their data via a mix network between themself. I2P was first started
    53 as a specialized low latency transport protocal for The Freenet Project but soon
     43of a few outproxies operated by private individuals.
     44
     45The ancestor of the I2P project was IIP (ref) - a specialiced IRC server with clients
     46transmitting their data via a mix network between themself. I2P was first started
     47as a specialized low latency transport protocol for The Freenet Project but soon
    5448grew into a independent software project, driven by the author jrandom from
    55 2003 on until end of 2007. Other people joined coding and vanished in time between and
    56 after jrandom vanished the project end of 2007, zzz and complication took over
     492003 on until end of 2007. Other people joined coding and vanished in time between.
     50After jrandom vanished the project end of 2007, zzz and complication took over
    5751active programming. The codebase itself is public domain or licensed under GPL
    58 with exception, MIT or other free licenses. Most code is written in JAVA to
    59 support the three main operating systems, Windows,Linux and MacOS X.
    60 To maintain 1024bit pub-key encryption, some external libs as the GMP (GNU MP
    61 Bignum Library) are interweaved with the java code.
     52with exception, MIT or other free licenses (ref). Most code is written in JAVA to
     53support the three main operating systems, Windows, Linux and MacOS X.
     54To maintain faster 1024bit pub-key encryption, some external libs as the GMP (GNU MP
     55Bignum Library) are interweaved within the java code.
    6256The codebase is under active development with 7 releases in the year 2008 and
    6357more than 100 development builds between those public releases.
    6458Beside the core router itself some bundled software (e.g. a bittorrent client
    65 based on snark, I2Psnark) are maintained by zzz and complication.
    66 
    67 In time writing this paper 830 active nodes are active in the I2P net. This
    68 varies over time, as 50-100 new nodes joining the network every day and others
     59based on snark, I2Psnark) is maintained by zzz and complication.
     60
     61<p>
     62In time writing this paper 830 peers are active in the I2P net (pic). This
     63varies over time, as 50-100 new nodes (pic) joining the network every day and others
    6964vanish. Usual on weekend times the peak of 1000 active nodes are reached and
    7065in weekdays night the lower peak at 700 active routers happens. This shows a
    71 quite stable base net on which the ~550 active destinations can act on.
     66quite stable base net on which the ~550 active destinations (pic) can act on.
    7267I2P is oriented towards hidden services, all destinations inside the network
    73 upon the nodes. Only one http outproxy (exit node in TOR terms) is known running
    74 beside a IRC gateway for I2P development discussion. In contrast to TOR is I2P
    75 peer to peer friendly and distributes the encrypted traffic between all
    76 participating nodes.
    77 The current bandwith used by all nodes is roughly 11 MByte/sec with peaks at 16
    78 MByte/sec and the net builds ~40.000 tunnels producing this load.
    79 In the last 6 month the net grew from 400 up to 800 nodes, from 5 to 10 MByte/sec
     68are upon those active peers. Only one http outproxy (exit node in TOR terms) is
     69public known running beside a IRC gateway for I2P development discussion.
     70In contrast to TOR, I2P is peer to peer traffic friendly while it distributes the
     71encrypted traffic between all participating nodes.
     72The current bandwith used by all peers is roughly 11 MByte/sec with peaks at 16
     73MByte/sec (pic) and the peers builds ~40.000 tunnels (pic) producing this load.
     74In the last 6 month the net grew from 400 up to 800 peers (pic), from 5 to 10 MByte/sec
    8075and from ~20.000 to ~40.000 tunnls, which shows the vital stats of the net
    8176doubled in half a year. The forthcoming time shows ongoing stable growth.
    82 
    83  Tunnel Overview
     77<p>
     78
    8479
    8580</p>
     
    342337<h2>References                   </h2><ul>
    343338<li>This paper includes material adapted from http://www.i2p2.de/ written by jrandom and others.
     339<li><i>TOR http://www.torproject.org/</i>
     340<li><i>IIP http://invisibleip.sourceforge.net/iip/ and http://en.wikipedia.org/wiki/Invisible_IRC_Project</i>
     341<li><i>Licences http://www.i2p2.de/licenses.html</i>
     342<li><i>Pics should be taken from stats.i2p<(i>
     343
    344344<li><i>A Tune-up for Tor: Improving Security and Performance in the Tor Network</i>
    345345Robin Snader and Nikita Borisov @ UIUC