[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[freehaven-cvs] add ieee style files
Update of /home/freehaven/cvsroot/doc/econp2p03
In directory moria.mit.edu:/home/arma/work/freehaven/doc/econp2p03
Modified Files:
econp2p03.pdf econp2p03.tex
Added Files:
latex8.bst latex8.sty
Log Message:
add ieee style files
--- NEW FILE: latex8.bst ---
% ---------------------------------------------------------------
%
% $Id: latex8.bst,v 1.1 2003/05/22 20:28:24 arma Exp $
%
% by Paolo.Ienne@di.epfl.ch
%
% ---------------------------------------------------------------
%
% no guarantee is given that the format corresponds perfectly to
% IEEE 8.5" x 11" Proceedings, but most features should be ok.
%
% ---------------------------------------------------------------
%
% `latex8' from BibTeX standard bibliography style `abbrv'
% version 0.99a for BibTeX versions 0.99a or later, LaTeX version 2.09.
% Copyright (C) 1985, all rights reserved.
% Copying of this file is authorized only if either
[...1085 lines suppressed...]
}
EXECUTE {begin.bib}
EXECUTE {init.state.consts}
ITERATE {call.type$}
FUNCTION {end.bib}
{ newline$
"\end{thebibliography}" write$ newline$
}
EXECUTE {end.bib}
% end of file latex8.bst
% ---------------------------------------------------------------
--- NEW FILE: latex8.sty ---
% ---------------------------------------------------------------
%
% $Id: latex8.sty,v 1.1 2003/05/22 20:28:24 arma Exp $
%
% by Paolo.Ienne@di.epfl.ch
%
% ---------------------------------------------------------------
%
% no guarantee is given that the format corresponds perfectly to
% IEEE 8.5" x 11" Proceedings, but most features should be ok.
%
% ---------------------------------------------------------------
% with LaTeX2e:
% =============
%
% use as
% \documentclass[times,10pt,twocolumn]{article}
% \usepackage{latex8}
% \usepackage{times}
%
% ---------------------------------------------------------------
% with LaTeX 2.09:
% ================
%
% use as
% \documentstyle[times,art10,twocolumn,latex8]{article}
%
% ---------------------------------------------------------------
% with both versions:
% ===================
%
% specify \pagestyle{empty} to omit page numbers in the final
% version
%
% specify references as
% \bibliographystyle{latex8}
% \bibliography{...your files...}
%
% use Section{} and SubSection{} instead of standard section{}
% and subsection{} to obtain headings in the form
% "1.3. My heading"
%
% ---------------------------------------------------------------
\typeout{IEEE 8.5 x 11-Inch Proceedings Style `latex8.sty'.}
% ten point helvetica bold required for captions
% in some sites the name of the helvetica bold font may differ,
% change the name here:
\font\tenhv = phvb at 10pt
%\font\tenhv = phvb7t at 10pt
% eleven point times bold required for second-order headings
% \font\elvbf = cmbx10 scaled 1100
\font\elvbf = ptmb scaled 1100
% set dimensions of columns, gap between columns, and paragraph indent
\setlength{\textheight}{8.875in}
\setlength{\textwidth}{6.875in}
\setlength{\columnsep}{0.3125in}
\setlength{\topmargin}{0in}
\setlength{\headheight}{0in}
\setlength{\headsep}{0in}
\setlength{\parindent}{1pc}
\setlength{\oddsidemargin}{-.304in}
\setlength{\evensidemargin}{-.304in}
% memento from size10.clo
% \normalsize{\@setfontsize\normalsize\@xpt\@xiipt}
% \small{\@setfontsize\small\@ixpt{11}}
% \footnotesize{\@setfontsize\footnotesize\@viiipt{9.5}}
% \scriptsize{\@setfontsize\scriptsize\@viipt\@viiipt}
% \tiny{\@setfontsize\tiny\@vpt\@vipt}
% \large{\@setfontsize\large\@xiipt{14}}
% \Large{\@setfontsize\Large\@xivpt{18}}
% \LARGE{\@setfontsize\LARGE\@xviipt{22}}
% \huge{\@setfontsize\huge\@xxpt{25}}
% \Huge{\@setfontsize\Huge\@xxvpt{30}}
\def\@maketitle
{
\newpage
\null
\vskip .375in
\begin{center}
{\Large \bf \@title \par}
% additional two empty lines at the end of the title
\vspace*{24pt}
{
\large
\lineskip .5em
\begin{tabular}[t]{c}
\@author
\end{tabular}
\par
}
% additional small space at the end of the author name
\vskip .5em
{
\large
\begin{tabular}[t]{c}
\@affiliation
\end{tabular}
\par
\ifx \@empty \@email
\else
\begin{tabular}{r@{~}l}
E-mail: & {\tt \@email}
\end{tabular}
\par
\fi
}
% additional empty line at the end of the title block
\vspace*{12pt}
\end{center}
}
\def\abstract
{%
\centerline{\large\bf Abstract}%
\vspace*{12pt}%
\it%
}
\def\endabstract
{
% additional empty line at the end of the abstract
\vspace*{12pt}
}
\def\affiliation#1{\gdef\@affiliation{#1}} \gdef\@affiliation{}
\def\email#1{\gdef\@email{#1}}
\gdef\@email{}
\newlength{\@ctmp}
\newlength{\@figindent}
\setlength{\@figindent}{1pc}
\long\def\@makecaption#1#2{
\vskip 10pt
\setbox\@tempboxa\hbox{\tenhv\noindent #1.~#2}
\setlength{\@ctmp}{\hsize}
\addtolength{\@ctmp}{-\@figindent}\addtolength{\@ctmp}{-\@figindent}
% IF longer than one indented paragraph line
\ifdim \wd\@tempboxa >\@ctmp
% THEN set as an indented paragraph
\begin{list}{}{\leftmargin\@figindent \rightmargin\leftmargin}
\item[]\tenhv #1.~#2\par
\end{list}
\else
% ELSE center
\hbox to\hsize{\hfil\box\@tempboxa\hfil}
\fi}
% correct heading spacing and type
\def\section{\@startsection {section}{1}{\z@}
{14pt plus 2pt minus 2pt}{14pt plus 2pt minus 2pt} {\large\bf}}
\def\subsection{\@startsection {subsection}{2}{\z@}
{13pt plus 2pt minus 2pt}{13pt plus 2pt minus 2pt} {\elvbf}}
% add the period after section numbers
\newcommand{\Section}[1]{\section{\hskip -1em.~#1}}
\newcommand{\SubSection}[1]{\subsection{\hskip -1em.~#1}}
% end of file latex8.sty
% ---------------------------------------------------------------
Index: econp2p03.pdf
===================================================================
RCS file: /home/freehaven/cvsroot/doc/econp2p03/econp2p03.pdf,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
Binary files /tmp/cvsSiDYE9 and /tmp/cvsK2c8Qa differ
Index: econp2p03.tex
===================================================================
RCS file: /home/freehaven/cvsroot/doc/econp2p03/econp2p03.tex,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -d -r1.10 -r1.11
--- econp2p03.tex 2 Apr 2003 03:08:29 -0000 1.10
+++ econp2p03.tex 22 May 2003 20:28:24 -0000 1.11
@@ -1,8 +1,6 @@
-\documentclass{llncs}
-% \documentclass{llncs}
-
-\usepackage{fullpage}
+\documentclass[times,10pt,twocolumn]{article}
+\usepackage{latex8}
\usepackage{url}
\usepackage{graphics}
\usepackage{amsmath}
@@ -29,22 +27,19 @@
\title{Reputation in P2P Anonymity Systems}
-\author{Roger Dingledine\inst{1} \and Nick Mathewson\inst{1} \and Paul Syverson\inst{2}}
-\institute{The Free Haven Project
-\email{(\{arma,nickm\}@freehaven.net)}
-\and
-Naval Research Lab
-\email{(syverson@itd.nrl.navy.mil)}}
+\author{Roger Dingledine \\ The Free Haven Project \\ arma@freehaven.net \and
+Nick Mathewson \\ The Free Haven Project \\ nickm@freehaven.net \and
+Paul Syverson \\ Naval Research Lab \\ syverson@itd.nrl.navy.mil}
\maketitle
-\pagestyle{plain}
+%\thispagestyle{empty}
\begin{abstract}
Decentralized anonymity systems tend to be unreliable, because users
-must choose paths through the network without knowing the entire state
-of the network. Reputation systems can improve reliability by predicting
-the state of the network. In this paper we focus on anonymous remailers
+must choose nodes in the network without knowing the entire state
+of the network. Reputation systems promise to improve reliability by
+predicting network state. In this paper we focus on anonymous remailers
and anonymous publishing, explain why the systems can benefit from
reputation, and describe our experiences designing reputation systems
for them while still ensuring anonymity. We find that in each example we
@@ -69,10 +64,10 @@
But when the network's very purpose is to provide anonymity, reputation
itself becomes problematic. Firstly, location protection enables an
attacker or freeloader to cheaply throw away a pseudonym that has acquired
-a bad reputation. Secondly, it is hard to detect or verify whether a
-participant is behaving correctly while at the same time maintaining
+a bad reputation. Secondly, it is hard to detect or verify a participant's
+behavior while at the same time maintaining
his anonymity. And thirdly, reputation information can be exploited by
-an adversary to better analyze and subvert the anonymity provided.
+an adversary to reduce a participant's anonymity.
So we are left with a conundrum: if the network's stability relies
on the good behavior of individual nodes, reputation may be the
@@ -99,7 +94,7 @@
always better off on crowded systems because of the noise other users provide.
Because high traffic is necessary for strong anonymity, agents must
-balance their incentives to find a common equilibrium, rather than
+balance their incentives and find a common equilibrium, rather than
each using a system of their own.
The high traffic they create together
also enables better performance: a system that processes only light
@@ -122,7 +117,7 @@
the incentives for participants to act as senders and nodes, providing
three results: Firstly, systems must attract cover traffic (many
low-sensitivity users) before they can attract the high-sensitivity
-users. Weak security parameters (e.g. smaller batches) may produce
+users. Weak security parameters (e.g. smaller batches or lower latency) may produce
\emph{stronger} anonymity by bringing more users. But to attract this
cover traffic, they may well have to address the fact that most users do
not want (or do not realize they want) anonymity protection. Secondly,
@@ -190,7 +185,7 @@
This reputation system attempts to improve reliability in a long-term
sense, rather than giving provable delivery guarantees for each
-message, a la \cite{shuffle}.
+message \cite{shuffle}.
On the other hand, it still relies both on proofs of correct behavior
to establish reputations, and trusted witnesses to determine and
keep track of them. These witnesses are both a trust bottleneck and a
@@ -217,10 +212,10 @@
selectively, each of the cascade members is responsible for a portion of
the messages that go through a cascade in each batch. In effect, each
member is the head for some of the messages. Similarly, the tail of
-the cascade sends each message in a batch to each of the other cascade
+the cascade sends each outgoing message to each of the other cascade
members rather than just directly to the recipient. All then attempt to
deliver the message to the recipient. (Efficiency of communication for
-final delivery can be improved by using receipts when that is feasible.)
+final delivery can be improved by using delivery receipts when that is feasible.)
In both of these remailer reputation systems, it was necessary to redesign the
remailer protocol so we could track remailer behavior. In the first
@@ -282,7 +277,7 @@
Given our experience designing the remailer reputation systems above,
it seems most promising to redesign the entire system from the ground up,
this time with verifiable claims in mind. Designing the original system
-without a clear idea of the reputation requirements made Free Haven's
+without a clear idea of the reputation and verifiability requirements made Free Haven's
design complex and brittle.
It's tempting to scale down the reputation system instead. That is,
@@ -382,7 +377,7 @@
problems we can solve with reputation would explode overnight.
We have already seen how reputation can enhance privacy. Can we go one step
-farther, and assign reputation based on an expectation of protecting
+further, and assign reputation based on an expectation of protecting
privacy? In distributed privacy systems, the privacy provided is typically
based on an assumption that some subset of system components will both
perform duties correctly {\it and} will not reveal some parts of their data
@@ -415,8 +410,7 @@
decentralized interaction and protecting privacy in ways that today's
systems of trust cannot.
-\bibliographystyle{plain}
-
+\bibliographystyle{latex8}
\bibliography{econp2p03}
\end{document}
***********************************************************************
To unsubscribe, send an e-mail to majordomo@seul.org with
unsubscribe freehaven-cvs in the body. http://freehaven.net/