[freehaven-cvs] notes on deployed systems and reputations

[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:
notes on deployed systems and reputations


Index: sync-batching.tex
===================================================================
RCS file: /home/freehaven/cvsroot/doc/sync-batching/sync-batching.tex,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -d -r1.5 -r1.6
--- sync-batching.tex	20 Jan 2004 09:23:30 -0000	1.5
+++ sync-batching.tex	20 Jan 2004 09:36:01 -0000	1.6
@@ -178,10 +178,14 @@
 section later in the paper where we'll talk about active
 attacks on the matrix topology.
 
-\subsection{Mixminion}
+\subsection{Currently deployed mix networks}
 
-explain the current free route node selection. motivation for
-loosely federated network. number of nodes.
+Mixmaster/Mixminion: rough number of deployed nodes.
+explain the current free route node selection. motivation for loosely
+federated network.
+
+Jap: describe overall design -- low-latency. how many cascades are
+there? how long are they? talk about web-mixes ticket design?
 
 \subsection{Danezis's restricted routes paper}
 
@@ -235,10 +239,9 @@
 gets dropped). Also, I think this only applies to re-encryption mixes,
 so, e.g.,  current remailer networks couldn't be based on them."
 
-
-\subsection{Reliable mixes}
-
-reputation systems a la mix-acc and casc-rep.
+The only reason I thought to put these in here is that for some
+reason I thought of them as synchronized-batching. If this is not
+the case, then this subsection should be removed entirely. -RD
 
 \section{Scenarios}
 
@@ -357,7 +360,19 @@
 talk about the possible uses of some minimum level of padding on each
 link.
 
-\subsection{
+\subsection{Reputations and node preference}
+
+most deployed systems let users choose their preferred entry or
+exit hops, which will mess with our distribution. but this is
+ok because after just a few hops of mixing, the distribution
+of the incoming batch doesn't matter as much anymore.
+
+reputation systems a la mix-acc and casc-rep make people prefer one
+node over another, _throughout_ the mix network, not just at entries or
+exits. but we have to tolerate this sort of thing. one approach would be
+to put like-reputationed nodes in the same column of the SA or in the same
+row of the cascade \cite{casc-rep}, so distribution (at each hop or in each
+cascade, respectively) will be more uniform.
 
 \section{Extensions and Future Work}
 

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