commit de1664718555a2baca0600bba8a39521384dcd15
Author: Karsten Loesing <[email protected]>
Date: Tue Aug 7 16:59:03 2012 +0200
Update flagrequirements report to new style.
---
2009/flagrequirements/flagrequirements.tex | 33 +++++++++++++++++-----------
2009/flagrequirements/tortechrep.cls | 1 +
2 files changed, 21 insertions(+), 13 deletions(-)
diff --git a/2009/flagrequirements/flagrequirements.tex
b/2009/flagrequirements/flagrequirements.tex
index d9f9a7c..5f3895a 100644
--- a/2009/flagrequirements/flagrequirements.tex
+++ b/2009/flagrequirements/flagrequirements.tex
@@ -1,35 +1,42 @@
-\documentclass{article}
-\usepackage{url}
-\usepackage[dvips]{graphicx}
-\usepackage{graphics}
-\usepackage{color}
+\documentclass{tortechrep}
+\usepackage{graphicx}
\begin{document}
-\title{Measuring the Tor Network\\{\large Alternative Requirements for Relay
Flags}}
-\author{Sebastian Hahn, Karsten Loesing, Steven J.\ Murdoch}
+
+\title{Measuring the Tor Network}
+\subtitle{Alternative Requirements for Relay Flags}
+\author{Sebastian Hahn, Karsten Loesing, and Steven J.\ Murdoch}
+\contact{\{sebastian,karsten\}@torproject.org,[email protected]}
+\reportid{2009-04-001\footnote{This report is mostly superseded by report
2011-06-001.}}
+\date{April 11, 2009}
\maketitle
\begin{abstract}
This document describes the simulation results of alternative requirements for
relays to obtain the \texttt{Fast}, \texttt{Stable}, and \texttt{Guard} flags.
The simulation is based on the directory archives of descriptors between
January 2008 and February 2009.
-All scripts and a howto for performing the evaluation can be found under:
\url{git://git.torproject.org/~karsten/git/metrics/}
+%All scripts and a howto for performing the evaluation can be found under:
\url{git://git.torproject.org/~karsten/git/metrics/}
\end{abstract}
\begin{figure}
-\includegraphics[width=\textwidth]{discrepancy.pdf}
+\centering
+\includegraphics[width=0.8\textwidth]{discrepancy.pdf}
\caption{This first graph shows the inevitable discrepancy between simulation
results and reality. There are at least three sources of error: First, only a
sample of 1/8 of all relays was considered in the simulation for performance
reasons. Second, the simulation is limited to relay uptimes as referenced from
hourly snapshots which are more coarse-grained than continuous connectivity
information. Third, the number of relays with \texttt{Stable} and
\texttt{Guard} flags in the archive data varies by up to 200 relays due to a
bug in the consensus process which is not contained in the simulation.}
\end{figure}
\begin{figure}
-\includegraphics[width=\textwidth]{stable.pdf}
+\centering
+\includegraphics[width=0.8\textwidth]{stable.pdf}
\caption{One requirement for being assigning the \texttt{Stable} flag is a
relay's weighted mean time between failures (MTBF). A relay gets the
\texttt{Stable} flag if it has a higher MTBF than the median of all active
relays. The graph shows alternative percentiles between 25 and 75\%. Obviously,
if the requirement is relaxed to having a MTBF higher than only 25\% of all
relays, the number of \texttt{Stable} flags increases; if the requirement is
raised to 75\%, the number of \texttt{Stable} flags decreases. The lines for
62.5 and 75\% overlap in parts, because of a fixed MTBF limit of 5 days which
some relays reach even though not being in the top 25\% of all relays.}
\end{figure}
\begin{figure}
-\includegraphics[width=\textwidth]{guardexits.pdf}
+\centering
+\includegraphics[width=0.8\textwidth]{guardexits.pdf}
\caption{Currently, a relay cannot be assigned both the \texttt{Guard} and the
\texttt{Exit} flag. The reason for the two sets being distinct is the attempt
not to overload the rare exit nodes with guard traffic. Unsurprisingly, if this
requirement was dropped, the number of relays with the \texttt{Guard} flag
would increase significantly.}
\end{figure}
\begin{figure}
-\includegraphics[width=\textwidth]{guardbw.pdf}
+\centering
+\includegraphics[width=0.8\textwidth]{guardbw.pdf}
\caption{One requirement for obtaining the \texttt{Guard} flag is having an
advertised bandwidth that is at least the median of all ``familiar'' relays
(familiar means being in the set of 7/8 of relays with highest weighted time
known). If the requirement of having an advertised bandwidth of the median of
familiar relays is relaxed to the advertised bandwidth only 25\% of familiar
relays, the number of \texttt{Guard} flags increases. Likewise, requiring 75\%
leads to decrease of \texttt{Guard} flags.}
\end{figure}
\begin{figure}
-\includegraphics[width=\textwidth]{guardwfu.pdf}
+\centering
+\includegraphics[width=0.8\textwidth]{guardwfu.pdf}
\caption{Another requirement for the \texttt{Guard} flag is a weighted
fractional uptime of at least 0.995, i.e., that a relay was available for at
least 99.5\% of the time it is known to a directory. If this requirement is
relaxed to 0.95, 0.9, 0.8, or even 0.7, the number of \texttt{Guard} flags
increases as shown in this graph.}
\end{figure}
\end{document}
diff --git a/2009/flagrequirements/tortechrep.cls
b/2009/flagrequirements/tortechrep.cls
new file mode 120000
index 0000000..4c24db2
--- /dev/null
+++ b/2009/flagrequirements/tortechrep.cls
@@ -0,0 +1 @@
+../../tortechrep.cls
\ No newline at end of file
_______________________________________________
tor-commits mailing list
[email protected]
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
