aboutsummaryrefslogtreecommitdiff
path: root/control-spec.txt
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2015-03-09 13:07:55 -0400
committerNick Mathewson <nickm@torproject.org>2015-03-09 13:07:55 -0400
commitb941a70418d0e4c6afc8f0c4ab5dc82576c2ea2f (patch)
treee93c74d31fd7396ee52fee3c40e97e66c785a6b1 /control-spec.txt
parentb0ebde6878b5a63afa8913205ba339944d3a6055 (diff)
downloadtorspec-b941a70418d0e4c6afc8f0c4ab5dc82576c2ea2f.tar.gz
torspec-b941a70418d0e4c6afc8f0c4ab5dc82576c2ea2f.zip
Add an atagar-suggested clarification
Diffstat (limited to 'control-spec.txt')
-rw-r--r--control-spec.txt3
1 files changed, 2 insertions, 1 deletions
diff --git a/control-spec.txt b/control-spec.txt
index c641788..a88153c 100644
--- a/control-spec.txt
+++ b/control-spec.txt
@@ -1929,7 +1929,8 @@
there's a bootstrapping problem.
The "host" value is the identity digest (in hex) of the node we're
- trying to connect to; the "hostaddr" is an address:port combination.
+ trying to connect to; the "hostaddr" is an address:port combination,
+ where 'address' is an ipv4 or ipv6 address.
Currently Tor uses recommendation=ignore for the first
nine bootstrap problem reports for a given phase, and then