From dfbeee69a631129905b42868c68a81c425db76a5 Mon Sep 17 00:00:00 2001 From: Peter Palfrader Date: Mon, 11 Aug 2008 20:09:43 +0000 Subject: Describe how clients should use the exit summaries, what they may use a locally cached descriptor for, and that enclave exiting is still allowed svn:r16501 --- proposals/141-jit-sd-downloads.txt | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) (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 991bc05..3664e45 100644 --- a/proposals/141-jit-sd-downloads.txt +++ b/proposals/141-jit-sd-downloads.txt @@ -232,6 +232,22 @@ Status: Draft should list the exit policy matching the descriptor digest referenced in the consensus document. +3.4.1 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 + by the consensus document. If a client has additional knowledge (like + cached full descriptors) that indicates the so chosen exit node will + reject the request then it MAY use that knowledge (or not include such + nodes in the selection to begin with). However, clients MUST NOT use + nodes that do not list the port as accepted in the summary (but for + which they know that the node would exit to that address from other + sources, like a cached descriptor). + + An exception to this is exit enclave behaviour: A client MAY use the + node at a specific IP address to exit to any port on the same address + even if that node is not listed as exiting to the port in the summary. + 4. Migration 4.1 Consensus document changes. -- cgit v1.2.3-54-g00ecf