Files
i2p.www/pages/roadmap.html
duck 806e7a4cd0 ungooglify
(duck)
2004-07-06 21:38:20 +00:00

66 lines
2.2 KiB
HTML

<h1>Roadmap</h1>
<h2>0.3.2 (May)</h2>
<ul>
<li>Fixed the netDb for more reliability</li>
<li>Address the diversification issues in peer selection</li>
<li>Fix remaining "unknown tunnels" cause</li>
</ul>
<h2>0.3.3 (July)</h2>
<ul>
<li>Unique tunnelIDs per hop to increase anonymity</li>
<li>Remove SourceRouteReplyMessage, replace SourceRouteBlock with ReplyBlock (no encrypted data in it, just a sessionTag + sessionKey)</li>
<li>Out of the 0.3.* testnet - irc, eepsites, and squid should work reliably</li>
</ul>
<h2>0.4.0 (July)</h2>
<ul>
<li>Updated deployment architecture, replacing the admin console with a real web server and
allowing the integration of standard .war packages as client applications</li>
<li>New installer and web based config system</li>
<li><a href="/node/view/144?PHPSESSID=933181d1da8229467d99aad215034076">SAM</a> bridge and client libraries implemented and tested</li>
</ul>
<h2>0.4.1 (July)</h2>
<ul>
<li><a href="/node/view/164?PHPSESSID=933181d1da8229467d99aad215034076">AMOC</a> transport to allow people behind firewalls/etc to fully participate in I2P</li>
<li>Bandwidth limiter functional</li>
<li>Router throttling code (detect/adapt to overload by refusing tunnels, shrinking # connections, minimizing networkDb activity)</li>
</ul>
<h2>1.0 (August)</h2>
<ul>
<li>Javadoc and code walkthrough / guidebook updated</li>
<li>Comprehensive management tool available</li>
<li>Internal code audit complete</li>
<li><a href="/node/view/208?PHPSESSID=933181d1da8229467d99aad215034076">MyI2P</a> available</li>
</ul>
<h2>1.1 (September)</h2>
<ul>
<li>Full streaming protocol implemented</li>
</ul>
<h2>2.0 (October)</h2>
<ul>
<li>Restricted route topology (include some connected peers in routerInfo, recursive route)</li>
<li>Connectionless/alternate transports (UDP, MRTCP, SMTP+POP3/IMAP)</li>
<li>Nontrivial certificates (hashcash, other) </li>
</ul>
<h2>3.0 (December)</h2>
<ul>
<li>Sender defined message delays</li>
<li>Creator defined tunnel mixing and pooling of messages, as well as optional chaff messages</li>
<li>(Mixminion integration?) </li>
</ul>
Dates, of course, are just estimates. If you get involved and help out with some of the
coding, things will go faster