[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[or-cvs] r15003: Overview for the 2nd nlnet project. (website/trunk/projects/en)
Author: phobos
Date: 2008-06-06 20:25:46 -0400 (Fri, 06 Jun 2008)
New Revision: 15003
Added:
website/trunk/projects/en/lowbandwidth.wml
Modified:
website/trunk/projects/en/index.wml
Log:
Overview for the 2nd nlnet project.
Modified: website/trunk/projects/en/index.wml
===================================================================
--- website/trunk/projects/en/index.wml 2008-06-07 00:01:03 UTC (rev 15002)
+++ website/trunk/projects/en/index.wml 2008-06-07 00:25:46 UTC (rev 15003)
@@ -14,7 +14,7 @@
<p>
<ul>
<li>NLnet <a href="<page projects/hidserv>">Speed Up Hidden Services</a></li>
-<li>NLnet Tor for low bandwidth clients</li>
+<li>NLnet <a href="<page projects/lowbandwidth>">Tor for low bandwidth clients</a></li>
<li>Google <a href="<page projects/google>">Auto-update for Tor</a></li>
</ul>
</p>
Added: website/trunk/projects/en/lowbandwidth.wml
===================================================================
--- website/trunk/projects/en/lowbandwidth.wml (rev 0)
+++ website/trunk/projects/en/lowbandwidth.wml 2008-06-07 00:25:46 UTC (rev 15003)
@@ -0,0 +1,157 @@
+## translation metadata
+# Revision: $Revision: 14486 $
+# Translation-Priority: 3-low
+
+#include "head.wmi" TITLE="NLnet Project: Tor for Low Bandwidth Clients"
+
+<div class="main-column">
+
+<!-- PUT CONTENT AFTER THIS TAG -->
+
+<h2>NLnet Project: Tor for Low Bandwidth Clients</h2>
+<hr />
+
+<p>
+The Tor anonymity system is currently only usable by internet users who
+have high-bandwidth connections. Upon the start of the Tor client, a large file
+with all Tor server descriptions is being downloaded. This file is the so-called Tor
+Directory and enables the client to choose from the available mix-servers in the Tor network. The
+download of the full Tor Directory is required by the current Tor protocol. This directory
+file is too large for users on modem lines or on mobile data networks like GPRS as the initial
+download that is triggered every time an user logs in takes 10 to 30 minutes over a slow
+line. As a result, Tor is not usable by modem and mobile users. One of the major goals of
+the Tor project is to provide secure anonymous internet access to users in dictatorships
+and repressive states. These locations often have very slow internet connections,
+either by modem or due to low-bandwidth links to the outside world. By enabling these users to
+use the Tor network, significant progress can be made towards free communication and
+information in these countries.
+</p>
+
+<p>
+To make Tor usable also for users on low-bandwidth connections, an
+evolution of the Tor protocol is needed to reduce the initial download size. This new Tor
+protocol version should change the way a client receives the information for its Tor
+circuit setup in a way, that the initial download can be performed over a 14.4 kbps modem line
+in about three minutes. The work to be conducted under the proposal has the ultimate
+goal of getting the protocol change production ready and propagated to the Tor users
+within a timeframe of less then 12 months. The resulting software will be published under
+the 3-Clause BSD license, as all of the Tor code. All deliverables will be fully public.
+</p>
+
+<p>
+This project is generously funded by:
+</p>
+
+<p>
+<a href="http://www.nlnet.nl/news/2008/20080514-awards.html";>
+<img src="$(IMGROOT)/nlnet-160x60.png" alt="The NLnet foundation" /></a>
+</p>
+
+<a id="Timetable"></a>
+<h2><a class="anchor" href="#Timetable">Timetable</a></h2>
+<table width="100%" border="0" cellspacing="0" cellpadding="3">
+<!-- <thead>
+<tr bgcolor="#e5e5e5">
+<th>Deliverable</th>
+<th>Due Date</th>
+</tr>
+</thead> -->
+
+<tr bgcolor="#e5e5e5">
+ <td>
+ <b>Deliverable A:</b> Design and evaluation of the protocol change<br />
+ <small><em>This deliverable covers the detailed design and
+ simulation-based evaluation of the necessary changes and design
+ modifications to the current Tor protocol.
+ The changes in protocol will be relatively substantial, so it requires a careful
+ evaluation of possible repercussions for the security and anonymity of the Tor network. A
+ two-month period is planned for this design and evaluation phase, which concludes with an
+ extensive peer review. Part of Deliverable A will be a goal definition for performance
+ for the implementation phase. The design goal is to shrink the Tor Directory
+ size that needs to be downloaded to about 300 Kilobytes, which would enable an user on a 14.4
+ kbps line to download it in roughly three minutes. There may be deviations from this
+ design goal if required to maintain anonymity and security, but this is the figure to aim for.
+ <em></small>
+ </td>
+ <td>
+ July 15, 2008
+ </td>
+</tr>
+
+<tr>
+ <td>
+ <b>Deliverable B:</b>Implementation of protocol change<br />
+ <small><em>After design, evaluation and peer review the modifications
+ need to be implemented and integrated with the current Tor code base. The actual implementation of
+ the necessary changes will take approximately three months.
+ </em></small>
+ </td>
+ <td>
+ October 15, 2008
+ </td>
+</tr>
+
+<tr bgcolor="#e5e5e5">
+ <td>
+ <b>Deliverable C:</b>Testing<br />
+ <small><em>Since the modification is highly critical to the security
+ and anonymity of the Tor network, it requires extensive testing and debugging in laboratory and real life
+ conditions. A period of three months is projected for testing and debugging, where the
+ responsible developer is committed to the testing effort with 1/3 of its time. Part of the
+ testing phase will be a public beta period.
+ </em></small>
+ </td>
+ <td>
+ November 15, 2008
+ </td>
+</tr>
+
+<tr>
+ <td>
+ <b>Deliverable D:</b>Rollout<br />
+ <small><em>The actual rollout to the Tor server network will be
+ conducted in sync with the regular Tor
+ release schedule. As this schedule is dependent on a number of external
+ factors, like the completion of other software projects that should go into the same
+ release, the actual release time and the time until this release has been accepted and
+ installed by most Tor server operators can vary. From experience a period of three to four
+ months can be expected. The rollout will be conducted as part of the regular Tor
+ release process that is a persistent activity done by volunteers and by personal paid through
+ other grants to the Tor project.
+ </em></small>
+ </td>
+ <td>
+ February 15, 2009
+ </td>
+</tr>
+</table>
+
+<br />
+
+<a id="Reports"></a>
+<h2><a class="anchor" href="#Reports">Monthly Status Reports</a></h2>
+<p>
+There will be in total eight monthly status reports beginning with the
+first deliverable on July 15, 2008 and ending with completion of
+implementation and testing work on February 15, 2009.
+</p>
+
+<!-- Where do we put status reports? The idea here is to create separate pages.
+-->
+
+<!-- Do we want a people section? If so, would it make sense to write what
+these people will be doing? And---what exactly are these people going to
+do? :)
+<a id="People"></a>
+<h2><a class="anchor" href="#People">People</a></h2>
+<ul>
+<li><a href="<page people>#Core">Peter Palfrader</a></li>
+</ul>
+-->
+
+<!-- In the future, put links to proposal, preliminary results, etc. here -->
+
+</div><!-- #main -->
+
+#include <foot.wmi>
+