# [tor-commits] [tech-reports/master] Update dirarch report to new style.

karsten at torproject.org karsten at torproject.org
Tue Aug 7 18:35:09 UTC 2012

commit 14967e1e3adbcd3e432ad7c94ebabe949db256c8
Author: Karsten Loesing <karsten.loesing at gmx.net>
Date:   Tue Aug 7 17:21:42 2012 +0200

Update dirarch report to new style.
---
2009/dirarch/dirarch.tex    |   27 +++++++++++++++++----------
2009/dirarch/tortechrep.cls |    1 +
2 files changed, 18 insertions(+), 10 deletions(-)

diff --git a/2009/dirarch/dirarch.tex b/2009/dirarch/dirarch.tex
index 58a0a6f..82ccc76 100644
--- a/2009/dirarch/dirarch.tex
+++ b/2009/dirarch/dirarch.tex
@@ -1,29 +1,36 @@
-\documentclass{article}
-\usepackage{url}
-\usepackage[dvips]{graphicx}
-\usepackage{graphics}
-\usepackage{color}
+\documentclass{tortechrep}
+\usepackage{graphicx}
\begin{document}
-\title{Measuring the Tor Network\\{\large Evaluation of Relays from Public Directory Data}}
+
+\title{Measuring the Tor Network}
+\subtitle{Evaluation of Relays from Public Directory Data}
\author{Karsten Loesing}
+\contact{karsten at torproject.org}
+\reportid{2009-06-001\footnote{This report is superseded by: Karsten
+Loesing. Measuring the Tor Network from Public Directory Information.
+2nd Hot Topics in Privacy Enhancing Technologies (HotPETs 2009), Seattle,
+WA, USA, August 2009.}}
\date{June 22, 2009}
\maketitle

\begin{abstract}
This document contains the results of an evaluation of the directory archives containing network status consensuses, router descriptors, and extra-info documents of relays from February 2006 to June 2009.
-All scripts and a howto for performing the evaluation can be found under: \url{git://git.torproject.org/git/metrics/}
+%All scripts and a howto for performing the evaluation can be found under: \url{git://git.torproject.org/git/metrics/}
\end{abstract}

\begin{figure}
-\includegraphics[width=\textwidth]{relayflags.pdf}
+\centering
+\includegraphics[width=0.72\textwidth]{relayflags.pdf}
\caption{The lines represent the number of \emph{running} relays with certain flags as listed in network status consensuses from February 2006 to June 2009. This diagram can be useful to decide whether conditions to assign certain flags might require modification. It is questionable whether the Fast flag is assigned too often to make a good distinction between fast and slow nodes. The volatility of the Stable and Guard flags might be the result of problems in the directory voting process. The average number of guard nodes has become rather low, given that these nodes need to push one third of all user traffic; changes to the requirements for becoming a guard node should be considered.}
\end{figure}
\begin{figure}
-\includegraphics[width=\textwidth]{platforms.pdf}
+\centering
+\includegraphics[width=0.72\textwidth]{platforms.pdf}
\caption{This graph visualizes the version life cycle of Tor relays as declared in router descriptors. Each version life cycle can be subdivided into an alpha and release candidate phase (April 2006 to April 2007 for 0.1.2.x), a stable phase (April 2007 to July 2008), and an out-of-date phase (July 2008 until today). For all versions there is an upper limit of approximately 200 relay operators running alpha or release candidate versions. There is no visible increase when versions are moved from alpha state to release candidate state (March 2, 2007 for 0.1.2.x, February 24, 2008 for 0.2.0.x). The stable phases for all versions show that it can take months until relay operators switch from an out-of-date version to the current stable version (April 2007 to end of 2007 for 0.2.0.x). Accordingly, the out-of-date phases show that old versions are used even years after new stable versions are available (0.1.1.x still in use in 2009). These results indicate that a semi-automatic up
dating mechanism is desirable.}
\end{figure}
\begin{figure}
+\centering
\caption{Relays report their observed bandwidth capacity and bandwidth usage to the directories. The bandwidth capacity (green line) is the maximum bandwidth as observed over any ten seconds in the past day. Bandwidth usage (red line) is calculated as the total size of relayed bytes in 15-minutes intervals over the past day. The graph shows that roughly half of the available bandwidth capacity is used by clients---and that the other half remains unused. Further investigations should focus on relays which leave most of their bandwidth capacity unused. Either the approach to measure capacity by 10-seconds bandwidth peaks is infeasible, or clients do not make us of the available bandwidth sufficiently.}
\end{figure}
diff --git a/2009/dirarch/tortechrep.cls b/2009/dirarch/tortechrep.cls
new file mode 120000
index 0000000..4c24db2
--- /dev/null
+++ b/2009/dirarch/tortechrep.cls
@@ -0,0 +1 @@
+../../tortechrep.cls
\ No newline at end of file