Delivery-Date: Tue, 12 Aug 2014 05:52:53 -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.7 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID
	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 C428A1E0A64;
	Tue, 12 Aug 2014 05:52:51 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id A77B230709;
	Tue, 12 Aug 2014 09:52:47 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id B71E3303AB
 for <tor-talk@lists.torproject.org>; Tue, 12 Aug 2014 09:52:43 +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 wm46lyo6ERpL for <tor-talk@lists.torproject.org>;
 Tue, 12 Aug 2014 09:52:43 +0000 (UTC)
Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com
 [IPv6:2a00:1450:400c:c00::22b])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 6F802301D3
 for <tor-talk@lists.torproject.org>; Tue, 12 Aug 2014 09:52:43 +0000 (UTC)
Received: by mail-wg0-f43.google.com with SMTP id l18so9531217wgh.26
 for <tor-talk@lists.torproject.org>; Tue, 12 Aug 2014 02:52:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=pbfuaaXxdsiH6uk9cRtWurSnleqwh/1LknWTXeQ3L8A=;
 b=BfDcCFYPZWhbomxTXCajtd8cbALKy9QKStak+bvSRadJ5ih8GKjkGi72keqD53QZwF
 Ilccf+lrWuVHTVoIgmZdFGXRuJ0EKbFS/QlUgOoCoRnPQOOcDA76yfXNec/tOlApEyfG
 m5XJj4FOT/wmu3uP22ZdAm4EYUbBeHRlmd+BRKQQxqUq2Z6sPlRjm5pxjWeBs2hFJFh8
 IH6GaP+6WOlchgFor1DXPdDleJTDwQIOXGk1vKZIjk0YrxoGYhjTts8pFYfGce0Q8F1K
 AI9UyC693LEPuA7Iwdv1AjT17bvhRp02goBxctAkfDa+aUT6vW831rpd1kaz9MAZ2iJR
 zM/Q==
MIME-Version: 1.0
X-Received: by 10.180.188.203 with SMTP id gc11mr31110050wic.59.1407837160245; 
 Tue, 12 Aug 2014 02:52:40 -0700 (PDT)
Received: by 10.180.221.12 with HTTP; Tue, 12 Aug 2014 02:52:40 -0700 (PDT)
In-Reply-To: <87ppg6152h.fsf@riseup.net>
References: <CAKMgAkSgH_3SR=z80is6RxUR=FVdvdYEDzxDn_MOPyzkyyGVXQ@mail.gmail.com>
 <87ppg6152h.fsf@riseup.net>
Date: Tue, 12 Aug 2014 18:52:40 +0900
Message-ID: <CAKMgAkS-aS+7Vte6QGKe+7xwSgOynHA9eXJrUNBOv=8NJD7dNQ@mail.gmail.com>
From: saurav dahal <dahal.saurav@gmail.com>
To: tor-talk@lists.torproject.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] About bandwidth weights selection
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>

Under which condition, the client will choose Guard flagged node and
Guard+Exit flagged node for guard position?


On Tue, Aug 12, 2014 at 5:32 PM, George Kadianakis <desnacked@riseup.net>
wrote:

> saurav dahal <dahal.saurav@gmail.com> writes:
>
> > Hello,
> >
> > While choosing a possible guard, a client multiplies Wgg with the
> bandwidth
> > weight of a possible relay having guard flag.
> >
> > But if a client wants to choose a relay, for guard position, having both
> > Guard and Exit flag (EE), then will it multiply bandwidth weight with Wgg
> > or Wgd?
> >
>
> If it's a Guard+Exit, it will multiply the bandwidth weight with Wgd:
> Wgd - Weight for Guard+Exit-flagged nodes in the guard Position
> --
> 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
>



-- 

Saurav Dahal,
Wireless communication and Networking lab,
Dept. of Computer Engineering,
Chosun University,
309 Pilmun-daero, Dong-gu
Gwangju, 501-759 S.KOREA
-- 
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

