[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: Proposal 145: Separate "suitable as a guard" from "suitable as a new guard"

To: or-dev@xxxxxxxxxxxxx
Subject: Re: Proposal 145: Separate "suitable as a guard" from "suitable as a new guard"
From: Nick Mathewson <nickm@xxxxxxxxxxxxx>
Date: Fri, 11 Jul 2008 13:01:21 -0400
Delivered-to: archiver@xxxxxxxx
Delivered-to: or-dev-outgoing@xxxxxxxx
Delivered-to: or-dev@xxxxxxxx
Delivery-date: Fri, 11 Jul 2008 13:01:23 -0400
In-reply-to: <20080711164935.GV19516@xxxxxxxxxxxxxxxxxxxx>
Mail-followup-to: Nick Mathewson <nickm@xxxxxxxxxxxxx>, or-dev@xxxxxxxxxxxxx
References: <20080702180515.GL26002@xxxxxxxxxxxxxx> <20080711164935.GV19516@xxxxxxxxxxxxxxxxxxxx>
Reply-to: or-dev@xxxxxxxxxxxxx
Sender: owner-or-dev@xxxxxxxxxxxxx
User-agent: Mutt/1.5.13 (2006-08-11)

On Fri, Jul 11, 2008 at 06:49:35PM +0200, Peter Palfrader wrote:
> On Wed, 02 Jul 2008, Nick Mathewson wrote:
> 
> >    We might instead have authorities list weights with which nodes
> >    should be picked as guards.
> 
> That is something I will need to do anyway, I think.  In that case the
> guard _flag_ would mean "keep as your guard", and the guard _weight_
> would mean "pick with propability $p"?

Good point.  I'm going to defer accepting 145, pending a finished 141.

(I should be sending a proposal status email to the list Really Soon
Now.)

References:
- Proposal 145: Separate "suitable as a guard" from "suitable as a new guard"
  - From: Nick Mathewson
- Re: Proposal 145: Separate "suitable as a guard" from "suitable as a new guard"
  - From: Peter Palfrader

Prev by Author: Re: Patch: correct configure check for netfilter_ipv4 support on some platforms.
Next by Author: Proposal statuses for Tor 0.2.1.x [Part 1]
Previous by thread: Re: Proposal 145: Separate "suitable as a guard" from "suitable as a new guard"
Next by thread: Re: Proposal 145: Separate "suitable as a guard" from "suitable as a new guard"
Index(es):
- Author
- Thread