Re: [tor-bugs] #1116 [Tor Relay]: 'Stable' flag assignment inconsistant

["Tor Bug Tracker & Wiki" <torproject-admin@xxxxxxxxxxxxxx>]

#1116: 'Stable' flag assignment inconsistant
------------------------------+---------------------------------------------
 Reporter:  StrangeCharm      |         Type:  defect   
   Status:  new               |     Priority:  minor    
Milestone:  Tor: unspecified  |    Component:  Tor Relay
  Version:  0.2.1.19          |   Resolution:  None     
 Keywords:                    |       Parent:           
------------------------------+---------------------------------------------
Changes (by nickm):

  * milestone:  => Tor: unspecified


Old description:

> Looking at a consensus document [though I used torstatus.all.de for ease
> of sorting data] it seems that the 'stable' flag
> is not being consistently assigned.
>
> According to the v3 directory specification at
> https://git.torproject.org/checkout/tor/master/doc/spec/dir-spec.txt ,
> routers with a weighted MTBF more than either the median or seven days
> should be marked stable, and MTBF data more
> than a month old shouldn't be that relevant when assigning the flag.
> Since the median uptime is about 3 days, one should
> roughly expect that any router with more than 30 days of uptime (and
> which are still valid) should have the stable flag.
> However when relays are sorted in order of uptime, several apparently-
> longrunning routers do not have the flag.
>
> Since this data is liable to change as relays go up an down, here are
> some noted not-'stable' routers at the time of
> writing. The routers have uptimes more than a month, so their (correctly)
> weighted MTBF should certainly be more than
> a week, and more than the median, about three days.
>
> wie6ud6be - 148d
> anonymde - 112d
> torpfaffenederorg - 110d
> rentalsponge - 70d
> xhyG5r96QGlRqL - 57d
> niugnip - 56d
> oeiwuqej - 49d
> gremlin - 42d
> editingconfigishard - 39d
>
> [Automatically added by flyspray2trac: Operating System: All]

New description:

 Looking at a consensus document [though I used torstatus.all.de for ease
 of sorting data] it seems that the 'stable' flag
 is not being consistently assigned.

 According to the v3 directory specification at
 https://git.torproject.org/checkout/tor/master/doc/spec/dir-spec.txt ,
 routers with a weighted MTBF more than either the median or seven days
 should be marked stable, and MTBF data more
 than a month old shouldn't be that relevant when assigning the flag. Since
 the median uptime is about 3 days, one should
 roughly expect that any router with more than 30 days of uptime (and which
 are still valid) should have the stable flag.
 However when relays are sorted in order of uptime, several apparently-
 longrunning routers do not have the flag.

 Since this data is liable to change as relays go up an down, here are some
 noted not-'stable' routers at the time of
 writing. The routers have uptimes more than a month, so their (correctly)
 weighted MTBF should certainly be more than
 a week, and more than the median, about three days.

 wie6ud6be - 148d
 anonymde - 112d
 torpfaffenederorg - 110d
 rentalsponge - 70d
 xhyG5r96QGlRqL - 57d
 niugnip - 56d
 oeiwuqej - 49d
 gremlin - 42d
 editingconfigishard - 39d

 [Automatically added by flyspray2trac: Operating System: All]

--

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/1116#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs