Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
T
tor
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Terraform modules
Analyze
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
jarl
tor
Commits
16fc9463
Commit
16fc9463
authored
19 years ago
by
Nick Mathewson
Browse files
Options
Downloads
Patches
Plain Diff
Add some bullet points to write up
svn:r6416
parent
7497ca7e
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/path-spec.txt
+24
-2
24 additions, 2 deletions
doc/path-spec.txt
with
24 additions
and
2 deletions
doc/path-spec.txt
+
24
−
2
View file @
16fc9463
...
...
@@ -14,9 +14,31 @@ implementors should be aware of the anonymity and load-balancing implications
of their choices.
THIS SPEC ISN'T DONE OR CORRECT. I'm just copying in relevant info so
far. -NM
far. The starred points are things we should cover, but not an exhaustive
list. -NM
X. Guard nodes
1. General operation
* We build some circuits preemptively, and some on-demand.
* We attach greedily, and expire after time.
2. Building circuits
* Preemptive building
* On-demand building
* Choosing the path first, building second.
* Choosing the length of the circuit.
* Choosing entries, midpoints, exits.
* What to do when an extend fails
* Keeping track of 'expected' ports
* Backing off from circuit building when a long time has passed
*
3. Attaching streams to circuits
4. Rendezvous circuits
5. Guard nodes
(From some emails by arma)
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment