other cleanups that have been sitting in my sandbox

svn:r13649

3 files changed, 9 insertions, 6 deletions

diff --git a/doc/design-paper/blocking.pdf b/doc/design-paper/blocking.pdf
index 8b02ff4adf..1ee0eb0bbd 100644
--- a/doc/design-paper/blocking.pdf
+++ b/doc/design-paper/blocking.pdf
diff --git a/doc/design-paper/blocking.tex b/doc/design-paper/blocking.tex
index 56153aa524..c05df692c3 100644
--- a/doc/design-paper/blocking.tex
+++ b/doc/design-paper/blocking.tex
@@ -25,7 +25,7 @@
 %\newcommand{\workingnote}[1]{(**#1)}   % makes the note visible.
 
 \date{}
-\title{Design of a blocking-resistant anonymity system}
+\title{Design of a blocking-resistant anonymity system\\DRAFT}
 
 %\author{Roger Dingledine\inst{1} \and Nick Mathewson\inst{1}}
 \author{Roger Dingledine \\ The Tor Project \\ arma@torproject.org \and
@@ -46,7 +46,8 @@ itself, blocked users can no longer benefit from the security Tor offers.
 
 Here we describe a design that builds upon the current Tor network
 to provide an anonymizing network that resists blocking
-by government-level attackers.
+by government-level attackers. We have implemented and deployed this
+design, and talk briefly about early use.
 
 \end{abstract}
 
@@ -194,7 +195,7 @@ currently~\cite{clayton:pet2006}:
   certain strings or patterns in TCP packets.  Offending packets can be
   dropped, or can trigger a response like closing the
   connection.
-\item Block a destination by listing its IP address at a
+\item Block certain IP addresses or destination ports at a
   firewall or other routing control point.
 \item Intercept DNS requests and give bogus responses for certain
   destination hostnames.
diff --git a/doc/design-paper/roadmap-future.tex b/doc/design-paper/roadmap-future.tex
index 2d9b5d89b0..5c1fa34f69 100644
--- a/doc/design-paper/roadmap-future.tex
+++ b/doc/design-paper/roadmap-future.tex
@@ -52,7 +52,7 @@ into Vidalia.
 
 We should add a new option ``auto'' that cycles through a set of preferred
 ports, testing bindability and reachability for each of them, and only
-complains to the user once it's given up on the common options.
+complains to the user once it's given up on the common choices.
 
 \subsection{Incentives design}
 
@@ -112,8 +112,9 @@ routers can't handle this many connections in their routing table.
 
 One approach is a restricted-route topology~\cite{danezis:pet2003}:
 predefine which relays can reach which other relays, and communicate
-these restrictions to the clients. We would need to compute which links
-are acceptable in a way that's decentralized yet scalable, and we would
+these restrictions to the relays and the clients. We need to compute
+which links are acceptable in a way that's decentralized yet scalable,
+and in a way that achieves a small-worlds property; and we
 need an efficient (compact) way to characterize the topology information
 so all the users could keep up to date.
 
@@ -162,6 +163,7 @@ Metrics for deciding when you're fast enough and stable enough
 \subsection{Continue Torbutton improvements}
       especially better docs
 \subsection{Vidalia and stability (especially wrt ongoing Windows problems)}
+      learn how to get useful crash reports (tracebacks) from Windows users
 \subsection{Polipo support on Windows}
 \subsection{Auto update for Tor, Vidalia, others}
 \subsection{Tor browser bundle for USB and standalone use}