[freehaven-cvs] new convention: "alpha-mixing" vs "$\alpha".

[arma@xxxxxxxx]

Update of /home/freehaven/cvsroot/doc/alpha-mixing
In directory moria:/home/arma/work/freehaven/doc/alpha-mixing

Modified Files:
	alpha-mixing.bib alpha-mixing.pdf alpha-mixing.tex 
Log Message:
new convention: "alpha-mixing" vs "$\alpha".
also, cite my weis2006 paper since it's related.


Index: alpha-mixing.bib
===================================================================
RCS file: /home/freehaven/cvsroot/doc/alpha-mixing/alpha-mixing.bib,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -d -r1.7 -r1.8
--- alpha-mixing.bib	11 Mar 2006 02:34:19 -0000	1.7
+++ alpha-mixing.bib	2 Jun 2006 21:49:33 -0000	1.8
@@ -539,3 +539,11 @@
   www_pdf_url = {http://www.cl.cam.ac.uk/~gd216/ExpMix.pdf},
 }
 
+@inproceedings{weis06-usability,
+  title = {Anonymity Loves Company: Usability and the Network Effect},
+  author = {Roger Dingledine and Nick Mathewson},
+  booktitle = {Proceedings of Workshop on Economics and Information Security (WEIS06)},
+  year = {2006},
+  month = {June},
+}
+

Index: alpha-mixing.pdf
===================================================================
RCS file: /home/freehaven/cvsroot/doc/alpha-mixing/alpha-mixing.pdf,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
Binary files /tmp/cvs84ORDT and /tmp/cvsIpW36D differ

Index: alpha-mixing.tex
===================================================================
RCS file: /home/freehaven/cvsroot/doc/alpha-mixing/alpha-mixing.tex,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -d -r1.37 -r1.38
--- alpha-mixing.tex	1 Jun 2006 12:55:29 -0000	1.37
+++ alpha-mixing.tex	2 Jun 2006 21:49:33 -0000	1.38
@@ -30,7 +30,7 @@
 
 \begin{document}
 
-\title{Blending different latency traffic with alpha-mixing\\
+\title{Blending different latency traffic\\with alpha-mixing\\
 \normalsize{(Pre-proceedings Draft)}}
 %\title{Alpha-mixing or Getting Personal with the Adversary}
 
@@ -56,10 +56,10 @@
 ensuring that all traffic is mixed together, we hope to lower delay and
 improve anonymity for both sets of users.
 
-$\alpha$-mixing is an approach that can be added to traditional
+Alpha-mixing is an approach that can be added to traditional
 batching strategies to let senders specify for each message whether
 they prefer security or speed. Here we describe how to add
-$\alpha$-mixing to various mix designs, and show that mix networks
+alpha-mixing to various mix designs, and show that mix networks
 with this feature can provide increased anonymity for all senders in
 the network. Along the way we encounter subtle issues to do with the
 attacker's knowledge of the security parameters of the users.
@@ -78,7 +78,7 @@
 strong security against a global attacker by adding high variance
 in latency, but this latency has crippled adoption --- which in turn
 decreases the security that the network can provide, discouraging even
-the users who need high security~\cite{econymics}.
+the users who need high security~\cite{econymics,weis06-usability}.
 
 Here we design a hybrid mix batching strategy that combines users with
 different anonymity and performance goals into the same network.
@@ -117,14 +117,14 @@
 %knowledge of the alphas in the messages, and this is what we are
 %relying on, see the analysis section.
 
-In this paper we start by outlining some simple $\alpha$-mix designs
+In this paper we start by outlining some simple alpha-mix designs
 and analysing the anonymity properties they can provide to users with
 different security preferences. Next we look at the strategies users
 should follow when picking the security parameter for each mix in the
 message's path.  Thirdly, we look at the incentives users have for
 choosing a high security parameter themselves rather than expecting
 others to take the latency penalty (and thus provide more anonymity to
-everyone). Lastly we consider more sophisticated $\alpha$-mixing
+everyone). Lastly we consider more sophisticated alpha-mixing
 strategies which should provide better properties but are hard to
 analyse.
 
@@ -710,7 +710,7 @@
 There are various ways to have realtime and threshold properties together
 in one mix design. We note two of them next.
 
-\subsection{Dynamic-$\alpha$ mixing}
+\subsection{Dynamic-alpha mixing}
 
 In this design, alphas are assigned to messages as they have been
 all along, except instead
@@ -732,7 +732,7 @@
 is not necessary. This effectively puts each message in a dynamic
 pool, which could also be timed.
 
-\subsection{$\tau$ mixing}
+\subsection{Tau mixing}
 
 We have been describing alpha all along as a level which determines a
 batch of messages that a given message will be sent with, after (or

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