From fd05b385e3eb703902b8d276cd4c9a6298773b1f Mon Sep 17 00:00:00 2001 From: Peter Palfrader Date: Thu, 14 Aug 2008 23:01:31 +0000 Subject: Add exitpolicy summaries to the consensus svn:r16554 --- proposals/141-jit-sd-downloads.txt | 31 ++++++++++++++++++++++++++----- 1 file changed, 26 insertions(+), 5 deletions(-) (limited to 'proposals/141-jit-sd-downloads.txt') diff --git a/proposals/141-jit-sd-downloads.txt b/proposals/141-jit-sd-downloads.txt index 07dea64..b0c2b2c 100644 --- a/proposals/141-jit-sd-downloads.txt +++ b/proposals/141-jit-sd-downloads.txt @@ -259,11 +259,32 @@ Status: Draft use an accept-style summary and list as much of the port list as is possible within these 1000 bytes. - Similarly to IP address, ports, and timestamp a consensus should list - the exit policy matching the descriptor digest referenced in the - consensus document (See dir-spec section 3.4). - -3.4.1 Client behaviour +3.4.1 Consensus selection + + When building a consensus, authorities have to agree on a digest of + the server descriptor to list in the router line for each router. + This is documented in dir-spec section 3.4. + + All authorities that listed that agreed upon descriptor digest in + their vote should also list the same exit policy summary - or list + none at all if the authority has not been upgraded to list that + information in their vote. + + If we have votes with matching server descriptor digest of which at + least one of them has an exit policy then we differ between two cases: + a) all authorities agree (or abstained) on the policy summary, and we + use the exit policy summary that they all listed in their vote, + b) something went wrong (or some authority is playing foul) and we + have different policy summaries. In that case we pick the one + that is most commonly listed in votes with the matching + descriptor. We break ties in favour of the lexigraphically larger + vote. + + If none one of the votes with a matching server descriptor digest has + an exit policy summary we use the most commonly listed one in all + votes, breaking ties like in case b above. + +3.4.2 Client behaviour When choosing an exit node for a specific request a Tor client will choose from the list of nodes that exit to the requested port as given -- cgit v1.2.3-54-g00ecf