Delivery-Date: Sun, 10 Aug 2014 14:26:05 -0400
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	RP_MATCHES_RCVD autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 94B8F1E04FF;
	Sun, 10 Aug 2014 14:26:03 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 2E953304C9;
	Sun, 10 Aug 2014 18:25:43 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 0F3852F847
 for <tor-talk@lists.torproject.org>; Sun, 10 Aug 2014 18:25:36 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id p-6fce2bqjpk for <tor-talk@lists.torproject.org>;
 Sun, 10 Aug 2014 18:25:35 +0000 (UTC)
Received: from exch-2010-smtp-out-04.livemail.co.uk
 (exch-smtp-out.livemail.co.uk [213.171.216.29])
 by eugeni.torproject.org (Postfix) with ESMTP id A16E621528
 for <tor-talk@lists.torproject.org>; Sun, 10 Aug 2014 18:25:35 +0000 (UTC)
Received: by exch-2010-smtp-out-04.livemail.co.uk (Postfix, from userid 500)
 id B41995BA595; Sun, 10 Aug 2014 19:25:32 +0100 (BST)
Received: from exch2-ht02.email2.local (mail213-171-216-56.livemail.co.uk
 [213.171.216.56])
 by exch-2010-smtp-out-04.livemail.co.uk (Postfix) with ESMTP id 7BE255BA4D0
 for <tor-talk@lists.torproject.org>; Sun, 10 Aug 2014 19:25:32 +0100 (BST)
Received: from EXCH2-MB06.email2.local ([fe80::c8b9:7294:42b4:c26b]) by
 exch2-ht02.email2.local ([fe80::7c27:1a98:86e:56ac%21]) with mapi id
 14.02.0387.000; Sun, 10 Aug 2014 19:25:32 +0100
From: Mike Fikuart <mike@fikuart.com>
To: "tor-talk@lists.torproject.org" <tor-talk@lists.torproject.org>
Thread-Topic: Scaling Tor
Thread-Index: AQHPtMh3CQuTGXcsrEWkZy1GjJcsmw==
Date: Sun, 10 Aug 2014 18:25:31 +0000
Message-ID: <1A5344A8-68D8-470B-84A2-74888A471A66@fikuart.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [86.202.25.65]
MIME-Version: 1.0
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [tor-talk] Scaling Tor
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============8723240589593751960=="
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

--===============8723240589593751960==
Content-Language: en-US
Content-Type: multipart/signed;
	boundary="Apple-Mail=_9338A05D-D12F-4DC3-9AA1-355A1333D7F0";
	protocol="application/pgp-signature"; micalg=pgp-sha512

--Apple-Mail=_9338A05D-D12F-4DC3-9AA1-355A1333D7F0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Hi Tor-Talk,

I am doing an MSc in Telecommunications and Network at City University, =
London.  For my dissertation I am looking at the limitations of scaling =
Tor up and how the limits could be overcome and should state that I am =
not a programmer, though would love to be involved in Tor=92s progress.

I=92m not sure if I am confusing Authority Server and Directory =
Authority and Directory Server or if they are all one and the same...

Firstly, in the original Tor documentation (Tor-Design 18/05/2004) =
initial =93theoretical=94 limits were stated that Tor could operate, =
then three, but as many as, up to nine DA=92s (Directory Authorities); =
however I note from the documentation you have gone through various =
version releases; have introduced directory caches etc to mitigate the =
overloading of the DA=92s and now have ten DA=92s operating and overall =
improved network performance. =20

Later (section 8) "Early experiences: Tor in the Wild=94 states initial =
expectations "of the network to support a few hundred nodes and 10,000 =
users before we=92re forced to become more distributed=94.  This =
reference was made to the =93clique topology=94 and =93full-visibility =
directories=94, yet you now operate almost 6,000 relays and around 2.25M =
users (directly connected).  Have you fundamentally changed the topology =
or have you found gains in the reporting of relays for form the =
consensus (or elsewhere) to allow this scale factor?

Two of the bottle necks identified in dir-spec (section 0.3 Some =
Remaining Questions) are that having every client know about every =
relay; and to have every Directory Cache to know about every router =
won=92t scale ad infinitum.=20

A question raised in Tor-Design (section 9) is, "if clients can no =
longer have a complete picture of the network, how can they perform =
discovery while preventing attackers from manipulating or exploiting =
gaps in their knowledge?=94.  If the network were to be considered to =
scale up to significant number of all Internet users, could it be that =
the Directory Authority(Ies) release (to Directory Caches and clients) a =
even random sample of relays/nodes from the FULL set of nodes, such that =
the randomness of the path selection is still maintained.  The random =
selection could be sampled on a per client basis with enough of a sample =
as is currently downloaded (6000 relays).  What this means is that each =
client (or possibly groupings of clients) is getting a different =93view=94=
 of the network, but there would need to be a scaling down from the full =
set to the sample set at some point before the client. =20

I have looked over the documentation for the path selection, directory =
protocol and the consensus, but have not documented the timing of the =
exchanges of communications.  I imagine that this is an area that could =
present a limit if scaled up.  What are the current areas that present =
limitations for large scaling up?

I have been able to access most of the relevant documentation through =
the https://www.torproject.org/docs/documentation.html.en but would =
appreciate it if there are any other repositories of info.  As mentioned =
at the start, I am not a programmer so the code base is meaningless to =
me :(

A small note; it would be useful for the documentation to be dated (and =
reversioner with dates) to indicate the freshness and relevance of the =
data.  I am aware that this may be a resource issue.

I appreciate your support with the network and hope to be able to =
contribute more in the future.

Yours sincerely
=20
Mike Fikuart IEng MIET
=20
Mobile: 07801 070580
Office: 020 33840275
Blog: mikefikuart
Skype: mikefikuart
Twitter: mikefikuart
LinkedIn: mikefikuart


--Apple-Mail=_9338A05D-D12F-4DC3-9AA1-355A1333D7F0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJT57kaAAoJELAnAPRS6UrkCmMH/iJycZk1oQEAA3XGgo5IOBLV
J3m/I49Bixy1mU3IWoOBkOwwBvD+poPqT0DmRkr02xmrqFFJFIA0YJX7UDVSixr8
BioCbe/BdkQJq3nH+ezikzCdSFWDe02CaSsigbqCpE/50G4J9WP7/qm92P/aHkdU
7COnziQKP9xadk3efCh+uqn6vlHsXKJ/DJVF26hsrbEWNy3OMXDzigt1Xf1mF+3C
mxAFGRR0DlyTZUEEM5v1fL0wp6W1vhi1pK063eCsdj+YCeLCzjd00XRfzAOBcc6m
QjHZsQ11FkJ048e/JNnQj7AWIZfJkzZ7iDu/es+lgrtUUTgPS9rzcjvae5+7YUM=
=YkST
-----END PGP SIGNATURE-----

--Apple-Mail=_9338A05D-D12F-4DC3-9AA1-355A1333D7F0--

--===============8723240589593751960==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

--===============8723240589593751960==--

