Changes between Version 13 and Version 14 of petconpaper


Ignore:
Timestamp:
Feb 27, 2009 2:36:09 PM (11 years ago)
Author:
anonymous
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • petconpaper

    v13 v14  
    4343reached. In contrast to TOR we use only hidden services in I2P with addition
    4444of a few outproxies operated by private individuals.
    45 
     45<p>
    4646The ancestor of the I2P project was IIP (ref) - a specialiced IRC server with clients
    4747transmitting their data via a mix network between themself. I2P was first started
     
    8787- client tunnels
    8888- exploratory tunnels
    89 
     89<p>
    9090The client tunnels transports all user generated data like IRC, webpages, code,
    9191peer to peer data or any other client transmitting data throught I2P. These
    9292tunnels are usual high bandwith and can reach up to 200 kbyte/sec.
    93 
     93<p>
    9494Exploratory tunnels are low bandwith tunnels used for managing the network.
    9595Beside tunnel tests and netdb queries these tunnels are used to build up the
    9696client tunnels. Especially the exploration of other peers is the main job of
    9797this tunnel class. This will be described further down.
    98 
     98<p>
    9999Each service in I2P has a destination as a representation of the location to
    100100reach the service. Examples are servers like eepsites (the I2P internal webpages),
     
    103103clients or else. Servers got stable destinations while clients destination are
    104104created new on every start.
    105 
     105<p>
    106106Each destination have a associated set of tunnels to transport the data. The
    107107application and/or user can control the specs of the tunnels:
     
    110110- quantity: up to three tunnels can be setup and data is distributed on them
    111111- backup: built 1-2 backup tunnels in case of original tunnels die unexpected
    112 
     112<p>
    113113To provide anonymity of the destinations, the route from a client to server
    114114is devided into two tunnels: the outgoing tunnel, controlled by the client, and
     
    118118This setup allows every participant to control its security and anonymity level
    119119for himself by setting the distance and variance for his tunnels.
    120 
     120<p>
    121121Each client select the peers with which it builds his part of the tunnel by
    122122himself, based on the rating described further down.
     
    124124two or more I2P peers within the same subnet (/24,/16) cannot be used within the
    125125same tunnel, which prevents the predecessor attack.
    126 
     126<p>
    127127To secure the tunnels  and the route from client to server further more, each
    128128tunnel in I2P has a fixed lifetime of 10 minutes and will be discarded after
     
    130130Until the old tunnel times out, data will be sent on all existant tunnels (
    131131associated to the specific destination).
    132 
     132<p>
    133133Peers can reject or drop tunnel build requests send by other peers due to a lot
    134134of reasons (overload, shutdown in progress, limit reached, out of sync).
     
    137137of the destination, each tunnel is tested on a periodic base for funtion. This
    138138creates more or less 1 kbyte/minute traffic, which is considered low bandwith.
    139 
     139<p>
    140140The client tunnels on a peer are sorted into different classes:
    141141- application tunnels: the tunnel starts or ends in this peer, binded to a