[freehaven-cvs] clean up a wrong statement in the intro

[arma@seul.org (Roger Dingledine)]

Update of /home/freehaven/cvsroot/doc/sync-batching
In directory moria.mit.edu:/home2/arma/work/freehaven/doc/sync-batching

Modified Files:
	sync-batching.tex 
Log Message:
clean up a wrong statement in the intro


Index: sync-batching.tex
===================================================================
RCS file: /home/freehaven/cvsroot/doc/sync-batching/sync-batching.tex,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- sync-batching.tex	13 Jan 2004 02:05:12 -0000	1.1
+++ sync-batching.tex	13 Jan 2004 10:08:36 -0000	1.2
@@ -48,9 +48,11 @@
 path. They suggest instead a \emph{cascade} topology, where all senders
 use the same fixed path through the mix network.
 
-Here we argue that topology is not the issue. We investigate a strategy
-called \emph{synchronous batching}, which provides the following
-advantages over Mixminion:
+Here we argue that the cascade design resolves the attacks not because
+of the network topology but because of a property of its batching
+strategy. We investigate this \emph{synchronous batching} approach in a
+variety of topologies, and find that it provides the following advantages
+over Mixminion:
 
 \begin{tightlist}
 \item It prevents the attacks in \cite{disad-free-routes} even when free
@@ -59,7 +61,7 @@
 routes are used.
 \item It allows senders to verify message processing, enabling reputation
 systems such as those described in \cite{mix-acc,casc-rep}.
-\item It makes blending attacks harder because mixes cannot delay messages
+\item It helps block blending attacks because mixes cannot delay messages
 without permanently dropping them.
 % though rgb, but there the adversary can still drop sender messages
 

***********************************************************************
To unsubscribe, send an e-mail to majordomo@seul.org with
unsubscribe freehaven-cvs       in the body. http://freehaven.net/