[or-cvs] minor tweaks and paul claims a subsection

syverson at seul.org syverson at seul.org
Sun Jan 30 12:52:51 UTC 2005


Update of /home/or/cvsroot/tor/doc/design-paper
In directory moria.mit.edu:/tmp/cvs-serv816/tor/doc/design-paper

Modified Files:
	challenges.tex 
Log Message:
minor tweaks and paul claims a subsection


Index: challenges.tex
===================================================================
RCS file: /home/or/cvsroot/tor/doc/design-paper/challenges.tex,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -d -r1.23 -r1.24
--- challenges.tex	30 Jan 2005 01:13:29 -0000	1.23
+++ challenges.tex	30 Jan 2005 12:52:49 -0000	1.24
@@ -85,17 +85,19 @@
 decreased flexibility in application support (typically because of increased
 latency).  Such research does not typically abandon aspirations towards
 deployability or utility, but instead tries to maximize deployability and
-utility subject to a certain degree of anonymity.  We believe that these
+utility subject to a certain degree of inherent anonymity (inherent because
+usability and practicality affect usage which affects the actual anonymity
+provided by the network \cite{back01,econymics}). We believe that these
 approaches can be promising and useful, but that by focusing on deploying a
 usable system in the wild, Tor helps us experiment with the actual parameters
 of what makes a system ``practical'' for volunteer operators and ``useful''
 for home users, and helps illuminate undernoticed issues which any deployed
-volunteer anonymity network will need to address.
+volunteer anonymity network will need to address. 
 
 While~\cite{tor-design} gives an overall view of the Tor design and goals,
-this paper describes the policy and technical issues that Tor faces are
+this paper describes the policy and technical issues that Tor faces as
 we continue deployment. Rather than trying to provide complete solutions
-to every problem here, we try to lay out the assumptions and constraints
+to every problem here, we lay out the assumptions and constraints
 that we have observed through deploying Tor in the wild. In doing so, we
 aim to create a research agenda for others to
 help in addressing these issues. Section~\ref{sec:what-is-tor} gives an
@@ -528,6 +530,8 @@
 than we think. We certainly wouldn't mind if Tor one day is able to
 transport a greater variety of protocols.
 
+[paul will work on this]
+
 \subsection{Mid-latency}
 \label{subsec:mid-latency}
 



More information about the tor-commits mailing list