Overview for the 2nd nlnet project. (6a902af26) - tor-webwml.git

...	...	@@ -0,0 +1,157 @@
	1	+## translation metadata
	2	+# Revision: $Revision: 14486 $
	3	+# Translation-Priority: 3-low
	4	+
	5	+#include "head.wmi" TITLE="NLnet Project: Tor for Low Bandwidth Clients"
	6	+
	7	+<div class="main-column">
	8	+
	9	+<!-- PUT CONTENT AFTER THIS TAG -->
	10	+
	11	+<h2>NLnet Project: Tor for Low Bandwidth Clients</h2>
	12	+<hr />
	13	+
	14	+<p>
	15	+The Tor anonymity system is currently only usable by internet users who
	16	+have high-bandwidth connections. Upon the start of the Tor client, a large file
	17	+with all Tor server descriptions is being downloaded. This file is the so-called Tor
	18	+Directory and enables the client to choose from the available mix-servers in the Tor network. The
	19	+download of the full Tor Directory is required by the current Tor protocol. This directory
	20	+file is too large for users on modem lines or on mobile data networks like GPRS as the initial
	21	+download that is triggered every time an user logs in takes 10 to 30 minutes over a slow
	22	+line. As a result, Tor is not usable by modem and mobile users. One of the major goals of
	23	+the Tor project is to provide secure anonymous internet access to users in dictatorships
	24	+and repressive states. These locations often have very slow internet connections,
	25	+either by modem or due to low-bandwidth links to the outside world. By enabling these users to
	26	+use the Tor network, significant progress can be made towards free communication and
	27	+information in these countries.
	28	+</p>
	29	+
	30	+<p>
	31	+To make Tor usable also for users on low-bandwidth connections, an
	32	+evolution of the Tor protocol is needed to reduce the initial download size. This new Tor
	33	+protocol version should change the way a client receives the information for its Tor
	34	+circuit setup in a way, that the initial download can be performed over a 14.4 kbps modem line
	35	+in about three minutes. The work to be conducted under the proposal has the ultimate
	36	+goal of getting the protocol change production ready and propagated to the Tor users
	37	+within a timeframe of less then 12 months. The resulting software will be published under
	38	+the 3-Clause BSD license, as all of the Tor code. All deliverables will be fully public.
	39	+</p>
	40	+
	41	+<p>
	42	+This project is generously funded by:
	43	+</p>
	44	+
	45	+<p>
	46	+<a href="http://www.nlnet.nl/news/2008/20080514-awards.html">
	47	+<img src="$(IMGROOT)/nlnet-160x60.png" alt="The NLnet foundation" /></a>
	48	+</p>
	49	+
	50	+<a id="Timetable"></a>
	51	+<h2><a class="anchor" href="#Timetable">Timetable</a></h2>
	52	+<table width="100%" border="0" cellspacing="0" cellpadding="3">
	53	+<!-- <thead>
	54	+<tr bgcolor="#e5e5e5">
	55	+<th>Deliverable</th>
	56	+<th>Due Date</th>
	57	+</tr>
	58	+</thead> -->
	59	+
	60	+<tr bgcolor="#e5e5e5">
	61	+ <td>
	62	+ <b>Deliverable A:</b> Design and evaluation of the protocol change<br />
	63	+ <small><em>This deliverable covers the detailed design and
	64	+ simulation-based evaluation of the necessary changes and design
	65	+ modifications to the current Tor protocol.
	66	+ The changes in protocol will be relatively substantial, so it requires a careful
	67	+ evaluation of possible repercussions for the security and anonymity of the Tor network. A
	68	+ two-month period is planned for this design and evaluation phase, which concludes with an
	69	+ extensive peer review. Part of Deliverable A will be a goal definition for performance
	70	+ for the implementation phase. The design goal is to shrink the Tor Directory
	71	+ size that needs to be downloaded to about 300 Kilobytes, which would enable an user on a 14.4
	72	+ kbps line to download it in roughly three minutes. There may be deviations from this
	73	+ design goal if required to maintain anonymity and security, but this is the figure to aim for.
	74	+ <em></small>
	75	+ </td>
	76	+ <td>
	77	+ July 15, 2008
	78	+ </td>
	79	+</tr>
	80	+
	81	+<tr>
	82	+ <td>
	83	+ <b>Deliverable B:</b>Implementation of protocol change<br />
	84	+ <small><em>After design, evaluation and peer review the modifications
	85	+ need to be implemented and integrated with the current Tor code base. The actual implementation of
	86	+ the necessary changes will take approximately three months.
	87	+ </em></small>
	88	+ </td>
	89	+ <td>
	90	+ October 15, 2008
	91	+ </td>
	92	+</tr>
	93	+
	94	+<tr bgcolor="#e5e5e5">
	95	+ <td>
	96	+ <b>Deliverable C:</b>Testing<br />
	97	+ <small><em>Since the modification is highly critical to the security
	98	+ and anonymity of the Tor network, it requires extensive testing and debugging in laboratory and real life
	99	+ conditions. A period of three months is projected for testing and debugging, where the
	100	+ responsible developer is committed to the testing effort with 1/3 of its time. Part of the
	101	+ testing phase will be a public beta period.
	102	+ </em></small>
	103	+ </td>
	104	+ <td>
	105	+ November 15, 2008
	106	+ </td>
	107	+</tr>
	108	+
	109	+<tr>
	110	+ <td>
	111	+ <b>Deliverable D:</b>Rollout<br />
	112	+ <small><em>The actual rollout to the Tor server network will be
	113	+ conducted in sync with the regular Tor
	114	+ release schedule. As this schedule is dependent on a number of external
	115	+ factors, like the completion of other software projects that should go into the same
	116	+ release, the actual release time and the time until this release has been accepted and
	117	+ installed by most Tor server operators can vary. From experience a period of three to four
	118	+ months can be expected. The rollout will be conducted as part of the regular Tor
	119	+ release process that is a persistent activity done by volunteers and by personal paid through
	120	+ other grants to the Tor project.
	121	+ </em></small>
	122	+ </td>
	123	+ <td>
	124	+ February 15, 2009
	125	+ </td>
	126	+</tr>
	127	+</table>
	128	+
	129	+<br />
	130	+
	131	+<a id="Reports"></a>
	132	+<h2><a class="anchor" href="#Reports">Monthly Status Reports</a></h2>
	133	+<p>
	134	+There will be in total eight monthly status reports beginning with the
	135	+first deliverable on July 15, 2008 and ending with completion of
	136	+implementation and testing work on February 15, 2009.
	137	+</p>
	138	+
	139	+<!-- Where do we put status reports? The idea here is to create separate pages.
	140	+-->
	141	+
	142	+<!-- Do we want a people section? If so, would it make sense to write what
	143	+these people will be doing? And---what exactly are these people going to
	144	+do? :)
	145	+<a id="People"></a>
	146	+<h2><a class="anchor" href="#People">People</a></h2>
	147	+<ul>
	148	+<li><a href="<page people>#Core">Peter Palfrader</a></li>
	149	+</ul>
	150	+-->
	151	+
	152	+<!-- In the future, put links to proposal, preliminary results, etc. here -->
	153	+
	154	+</div><!-- #main -->
	155	+
	156	+#include <foot.wmi>
	157	+
0	158

...	...	@@ -14,7 +14,7 @@
14	14	<p>
15	15	<ul>
16	16	<li>NLnet <a href="<page projects/hidserv>">Speed Up Hidden Services</a></li>
17		-<li>NLnet Tor for low bandwidth clients</li>
	17	+<li>NLnet <a href="<page projects/lowbandwidth>">Tor for low bandwidth clients</a></li>
18	18	<li>Google <a href="<page projects/google>">Auto-update for Tor</a></li>
19	19	</ul>
20	20	</p>