from this paper:<br>"First, bandwidth is already a key factor in Tor<br>design. Second, bandwidth is typically a property of a node<br>rather than a link between two nodes, since the bottleneck is<br>likely to be close to the node rather than in the intermediate<br>
network."<br><br><div class="gmail_quote">On Tue, Nov 25, 2008 at 8:46 PM, Daniel Juyung Seo <span dir="ltr"><<a href="mailto:seojuyung2@gmail.com">seojuyung2@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello,<br>
<br>
Using Tor, I wondered why Tor use bandwidth capacity as a key factor<br>
of Tor router selecting algorithm.<br>
After a brief view of Tor source codes, I realized that the bandwidth<br>
capacity of Tor is more similar to the Tor router's packet processing<br>
capability than the network transfer capacity.<br>
While calculating the bandwidth capacity, the capacity of network link<br>
among Tor routers is not considered.<br>
<br>
Isn't it better to use the capacity of network link among Tor routers?<br>
Robin Snader's paper, A Tune-up for Tor: Improving Security and<br>
Performance in the Tor Network. has some idea using the network link<br>
capacity.<br>
I think it is feasible to measure each link capacity among all Tor<br>
routers by using ping packets or other simple mechanisms.<br>
<br>
When each router knows the linke capacity with all the other routers,<br>
we can build better circuits than before.<br>
Let's assume that there are 1,200 Tor routers in the world.<br>
In this case, each router needs to have 1,199 link capacity<br>
information with the other Tor routers, not the bandwidth capacity of<br>
the other Tor routers.<br>
<br>
The total number of the links that Tor directory server should save is<br>
up to 1,438,800 (1,199 x 1,200).<br>
I guess this mechanism will improve Tor router selection algorithm.<br>
<br>
Waiting for some replies.<br>
</blockquote></div><br>