commit cdbb85ee3def5cc908c7f84948edb22be7351f84 Author: Karsten Loesing karsten.loesing@gmx.net Date: Tue Jan 28 11:28:59 2014 +0100
Make it clearer that authorities scan other votes.
See git commits 2e692bd8 and eaf5487d, which went into 0.2.2.12-alpha: o Major bugfixes: - Many relays have been falling out of the consensus lately because not enough authorities know about their descriptor for them to get a majority of votes. When we deprecated the v2 directory protocol, we got rid of the only way that v3 authorities can hear from each other about other descriptors. Now authorities examine every v3 vote for new descriptors, and fetch them from that authority. Bugfix on 0.2.1.23.
Section 3.6 already says this implicitly when specifying how authorities download missing router descriptors, but that doesn't mean we can't also make it more explicit when specifying how authorities exchange votes. --- dir-spec.txt | 7 +++++++ 1 file changed, 7 insertions(+)
diff --git a/dir-spec.txt b/dir-spec.txt index a594948..7d63c90 100644 --- a/dir-spec.txt +++ b/dir-spec.txt @@ -1247,6 +1247,13 @@ http://<hostname>/tor/status-vote/next/d/<d>.z where <d> is the digest of the vote document.
+ Also, once an authority receives a vote from another authority, it + examines it for new descriptors and fetches them from that authority. + This may the only way for an authority to hear about relays that didn't + publish their descriptor to all authorities, and while it's too late + for the authority to include relays in its current vote, it can include + them in its next vote. See section 3.6 below for details. + 3.4.1. Vote and consensus status document formats
Votes and consensuses are more strictly formatted than other documents