Hey,
> > This algorithm keeps track of the unreachability status for guards
> > in state private to the algorithm - this is re-initialized every time
> > START is called.
> >
>
> Hmm, didn't we decide to persist the unreachability status over runs, right?
> Or not?
Yeah, I think we did dec
Great, lots of good comments. I'll respond in depth once the fever has
left my brain! =D
On Thu, Mar 03, 2016 at 03:15:26PM +0100, George Kadianakis wrote:
> Ola Bini writes:
>
> > Hi,
>
> Here are some more comments to the latest version of the proposal, as seen
> here:
> https://github.com/t
Ola Bini writes:
> Hi,
Here are some more comments to the latest version of the proposal, as seen here:
https://github.com/twstrike/torspec
> Filename: 259-guard-selection.txt
> Title: New Guard Selection Behaviour
> Author: Isis Lovecruft, George Kadianakis, [Ola Bini]
> Created: 2015-10-28
>
Reinaldo de Souza Jr writes:
> On 2/16/16 12:20, George Kadianakis wrote:
>> The
>> very latest prop259 basically forgets the unreachable guard status as soon as
>> the algorithm terminates. I wonder if we actually want this. Hopefully
>> guardsim
>> has a simulation scenario that will illustrat
On 2/16/16 12:20, George Kadianakis wrote:
> The
> very latest prop259 basically forgets the unreachable guard status as soon as
> the algorithm terminates. I wonder if we actually want this. Hopefully
> guardsim
> has a simulation scenario that will illustrate whether that's a good idea or
> not.
Ola Bini writes:
> Hey,
>
>>
>> Returning to this for a bit. I think it would be good to decide whether we
>> should keep the unreachable status of guards on permannet disk state or
>> not. The
>> very latest prop259 basically forgets the unreachable guard status as soon as
>> the algorithm termi
Hey,
>
> Returning to this for a bit. I think it would be good to decide whether we
> should keep the unreachable status of guards on permannet disk state or
> not. The
> very latest prop259 basically forgets the unreachable guard status as soon as
> the algorithm terminates. I wonder if we actual
> Hi there,
>
> >
>
>
>
> ALGO_CHOOSE_ENTRY_GUARD keeps track of unreachable status for guards in state
> private to the algorithm - this is
Ola Bini writes:
> Hi George,
>
> Sorry I've been slow to answer and send more info - was spending all
> day Saturday and Sunday, and this week I'll be in all day meetings.
>
> Anyway, just to avoid confusion - After getting the algorithm to the
> latest stage you saw below, we started work on im
Chelsea Komlo writes:
> Hi George,
>
> We were having a similar discussion about what to include in the "receive
> new consensus" action.
>
> We currently have three actions to remove dead/unused guards. They are:
>
>1. Marking guards that are not listed in the latest consensus as "bad"
>
Hi George,
Sorry I've been slow to answer and send more info - was spending all
day Saturday and Sunday, and this week I'll be in all day meetings.
Anyway, just to avoid confusion - After getting the algorithm to the
latest stage you saw below, we started work on implementing it to
simulate it. I
Hi George,
We were having a similar discussion about what to include in the "receive
new consensus" action.
We currently have three actions to remove dead/unused guards. They are:
1. Marking guards that are not listed in the latest consensus as "bad"
2. Remove guards that have been dead fo
Ola Bini writes:
> Hi again,
>
> Here is the newest version of the algorithm:
> https://gist.github.com/olabini/343da01de8e01491bf5c
>
Thanks! Looks better!
I think we are reaching the point that we need good simulations and actually
running and stepping through the algorithm with actual data t
Hi again,
Here is the newest version of the algorithm:
https://gist.github.com/olabini/343da01de8e01491bf5c
The biggest change is the addition of the state
STATE_TRY_ONLY_TRIED. Once it enters this state, it will never exit it
again.
Cheers
--
Ola Bini (https://olabini.se)
"Yields falsehood
Hi there,
Thanks again! Really appreciate you spending so much time with us fine
tuning this.
> > The full algorithm is referred to as ALGO_CHOOSE_ENTRY_GUARD. It is divided
> > into three components, such that the full algorithm is implemented by first
> > invocing ALGO_CHOOSE_ENTRY_GUARD_START,
Ola Bini writes:
> Hi,
>
> Here is the next version of the algorithm - put it in a gist to make
> it easier to look at:
> https://gist.github.com/olabini/343da01de8e01491bf5c
>
> Cheers
Thanks for this.
Here we go with another review!
> The full algorithm is referred to as ALGO_CHOOSE_ENTRY_
Hi,
Here is the next version of the algorithm - put it in a gist to make
it easier to look at:
https://gist.github.com/olabini/343da01de8e01491bf5c
Cheers
--
Ola Bini (https://olabini.se)
"Yields falsehood when quined" yields falsehood when quined.
signature.asc
Description: PGP signature
17 matches
Mail list logo
