aboutsummaryrefslogtreecommitdiff
path: root/proposals/141-jit-sd-downloads.txt
diff options
context:
space:
mode:
authorPeter Palfrader <peter@palfrader.org>2008-08-14 23:01:31 +0000
committerPeter Palfrader <peter@palfrader.org>2008-08-14 23:01:31 +0000
commitfd05b385e3eb703902b8d276cd4c9a6298773b1f (patch)
treec2ca5967f903887acfd1e1aaef788b30abf2ac65 /proposals/141-jit-sd-downloads.txt
parente4f426a306a7f07b645845e86aa83ef378f1cb3f (diff)
downloadtorspec-fd05b385e3eb703902b8d276cd4c9a6298773b1f.tar.gz
torspec-fd05b385e3eb703902b8d276cd4c9a6298773b1f.zip
Add exitpolicy summaries to the consensus
svn:r16554
Diffstat (limited to 'proposals/141-jit-sd-downloads.txt')
-rw-r--r--proposals/141-jit-sd-downloads.txt31
1 files changed, 26 insertions, 5 deletions
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