Delivery-Date: Thu, 19 Jun 2014 15:57:26 -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 moria.seul.org (Postfix) with ESMTPS id 766281E0E33
	for <archiver@seul.org>; Thu, 19 Jun 2014 15:57:24 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 493692FC62;
	Thu, 19 Jun 2014 19:57:19 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id D03CE2FBC6
 for <tor-talk@lists.torproject.org>; Thu, 19 Jun 2014 19:43:18 +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 if0s9k-Cagio for <tor-talk@lists.torproject.org>;
 Thu, 19 Jun 2014 19:43:18 +0000 (UTC)
Received: from moria.seul.org (unknown [128.31.0.47])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "moria.seul.org", Issuer "moria.seul.org" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id ABBE62FBC4
 for <tor-talk@lists.torproject.org>; Thu, 19 Jun 2014 19:43:18 +0000 (UTC)
Received: by moria.seul.org (Postfix, from userid 501)
 id 3CAC91E0E3E; Thu, 19 Jun 2014 15:43:16 -0400 (EDT)
Date: Thu, 19 Jun 2014 15:43:16 -0400
From: Roger Dingledine <arma@mit.edu>
To: tor-talk@lists.torproject.org
Message-ID: <20140619194316.GN4350@moria.seul.org>
References: <CAKMgAkQ+RB3gLt0dF9hUN6hONMXYGdt1nwC8N_cCPjmpEMorkQ@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <CAKMgAkQ+RB3gLt0dF9hUN6hONMXYGdt1nwC8N_cCPjmpEMorkQ@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-12-10)
Subject: Re: [tor-talk] Calculation of Bandwidth weights
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

On Thu, Jun 19, 2014 at 02:58:12PM +0900, saurav dahal wrote:
> Hello,
> 
> I studied about computing bandwidth from
> 
> https://gitweb.torproject.org/torspec.git/blob/HEAD:/dir-spec.txt#l2157
> 
> But I could not understand the procedure. Can anyone please explain me
> about calculating the bandwidth weights in simple way.

The bandwidth weight in the consensus is calculated in a simple way:
it's the median of the bandwidth weights in each vote.

So now you should ask how each directory authority calculates the weight
it will use for its vote.

These two documents are good starts there:
https://gitweb.torproject.org/torflow.git/blob/HEAD:/NetworkScanners/BwAuthority/README.BwAuthorities
https://gitweb.torproject.org/torflow.git/blob/HEAD:/NetworkScanners/BwAuthority/README.spec.txt
and for distant history, you might like Mike's hotpets paper:
https://blog.torproject.org/blog/torflow-node-capacity-integrity-and-reliability-measurements-hotpets

Or if you want the simpler answer: "Sorry, there is no simple way to
explain it. It is all a pile of hacks stacked on top of each other. It's
a great research area where somebody could improve it. Please do."

--Roger

-- 
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

