aboutsummaryrefslogtreecommitdiff
path: root/spec/dir-spec
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2023-11-06 10:32:03 -0500
committerNick Mathewson <nickm@torproject.org>2023-11-06 10:32:03 -0500
commit74930cae857d92fe028874e82dab792fd5ea6d14 (patch)
treee9748d91d270ecf4643bd7160e57704a0ebd28b0 /spec/dir-spec
parent6025739984c782356a6122cbae9bba8e360859ac (diff)
downloadtorspec-74930cae857d92fe028874e82dab792fd5ea6d14.tar.gz
torspec-74930cae857d92fe028874e82dab792fd5ea6d14.zip
Fold a misplaced section of dir-spec into path-spec
(Notes about Valid/Fast/Running/Stable/Guard were already elsewhere in path-spec.)
Diffstat (limited to 'spec/dir-spec')
-rw-r--r--spec/dir-spec/client-operation.md41
1 files changed, 0 insertions, 41 deletions
diff --git a/spec/dir-spec/client-operation.md b/spec/dir-spec/client-operation.md
index ff1232c..a59fae4 100644
--- a/spec/dir-spec/client-operation.md
+++ b/spec/dir-spec/client-operation.md
@@ -178,47 +178,6 @@ documents currently held. If so, it downloads whatever extra-info
documents are missing. Clients try to download from caches.
We follow the same splitting and back-off rules as in section 5.2.
-<a id="dir-spec.txt-5.4"></a>
-
-## Using directory information { #using-info }
-
-\[XXX This subsection really belongs in path-spec.txt, not here. -KL\]
-
-Everyone besides directory authorities uses the approaches in this section
-to decide which relays to use and what their keys are likely to be.
-(Directory authorities just believe their own opinions, as in section 3.4.2
-above.)
-
-<a id="dir-spec.txt-5.4.1"></a>
-
-### Choosing routers for circuits { #choosing-routers }
-
-Circuits SHOULD NOT be built until the client has enough directory
-information; see ["When we build"](../path-spec/when-we-build.md) for
-more information.
-
-A relay is "listed" if it is included by the consensus network-status
-document. Clients SHOULD NOT use unlisted relays.
-
-These flags are used as follows:
-
-```text
- - Clients SHOULD NOT use non-'Valid' or non-'Running' routers unless
- requested to do so.
-
- - Clients SHOULD NOT use non-'Fast' routers for any purpose other than
- very-low-bandwidth circuits (such as introduction circuits).
-
- - Clients SHOULD NOT use non-'Stable' routers for circuits that are
- likely to need to be open for a very long time (such as those used for
- IRC or SSH connections).
-
- - Clients SHOULD NOT choose non-'Guard' nodes when picking entry guard
- nodes.
-
- See the "path-spec.txt" document for more details.
-```
-
<a id="dir-spec.txt-5.5"></a>
## Retrying failed downloads