kytv/I2P_Website
1
0
Fork 0
forked from I2P_Developers/i2p.www
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

updated schedule - reordered milestones and updated dates

Browse Source
This commit is contained in:
jrandom
2004-07-20 18:05:06 +00:00
committed by zzz
parent ca60af28a7
commit 6dbd571780
1 changed files with 19 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files

47
pages/roadmap.html
View File

@@ -1,58 +1,49 @@
<h2>0.3.2 (May)</h2>
<h2>0.4 (August)</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>
<li>All previous code functional and reliable</li>
<li>New installer and deployment architecture</li>
<li>New web based console and configuration</li>
<li>Implementation docs for I2PTunnel, the SAM bridge, the router, and the SDK</li>
<li>Technical docs for the network describing the use cases, anonymity, and scalability attributes</li>
</ul>
<h2>0.3.3 (July)</h2>
<h2>0.4.1 (August)</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>
<li>Remove the SourceRouteReplyMessage, replace the SourceRouteBlock with a ReplyBlock</li>
<li>Full ElGamal precalculation (instead of just 1/2 of it)</li>
</ul>
<h2>0.4.0 (July)</h2>
<h2>0.4.2 (September)</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="sam">SAM</a> bridge and client libraries implemented and tested</li>
<li>AMOC transport to allow operation behind firewalls and NATs without administrative control</li>
</ul>
<h2>0.4.1 (July)</h2>
<h2>0.4.3 (October)</h2>
<ul>
<li><a href="amoc">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>
<li>UDP transport for scalable high connectivity</li>
</ul>
<h2>1.0 (August)</h2>
<h2>1.0 (November)</h2>
<ul>
<li>Javadoc and code walkthrough / guidebook updated</li>
<li>Comprehensive management tool available</li>
<li>MyI2P available</li>
<li>Internal code audit complete</li>
<li><a href="myi2p">MyI2P</a> available</li>
</ul>
<h2>1.1 (September)</h2>
<h2>1.1 (December)</h2>
<ul>
<li>Full streaming protocol implemented</li>
<li>Full streaming protocol implemented with a moving window size</li>
</ul>
<h2>2.0 (October)</h2>
<h2>2.0 (March)</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>
<h2>3.0 (June)</h2>
<ul>
<li>Sender defined message delays</li>
<li>Creator defined tunnel mixing and pooling of messages, as well as optional chaff messages</li>