[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #25544 [Core Tor/Tor]: Complete vanguard specification
#25544: Complete vanguard specification
-------------------------------------------------+-------------------------
Reporter: asn | Owner: (none)
Type: defect | Status:
| needs_revision
Priority: Medium | Milestone: Tor:
| 0.3.4.x-final
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: tor-guard, torspec, guard- | Actual Points:
discovery, 034-roadmap-master, |
034-triage-20180328, 034-included-20180328 |
Parent ID: | Points:
Reviewer: asn | Sponsor:
| SponsorV
-------------------------------------------------+-------------------------
Changes (by asn):
* status: needs_review => needs_revision
Comment:
Mike, your changes look good to me.
I pushed another commit on my github repo at `mesh-vanguards` with some
more text on how the python script is used right now. If you think that's
inappropriate for the proposal let me now.
I think now is the time to decide what's the role of prop#247 and what's
the role of `xxx-mesh-vanguards.txt`. I think it's confusing to let both
of them live at the same time because they are pretty similar in terms of
text. We should figure this out so that we get this merged in torspec.
Should we let prop#247 be "Vanguard integration inside Tor core", whereas
this new proposal is "Mesh vanguard design using external script"? And
make both of them proper proposals (aka get a proposal number for this new
one too). Or what should be the plan?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25544#comment:8>
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