aboutsummaryrefslogtreecommitdiff
path: root/dir-spec.txt
diff options
context:
space:
mode:
Diffstat (limited to 'dir-spec.txt')
-rw-r--r--dir-spec.txt50
1 files changed, 25 insertions, 25 deletions
diff --git a/dir-spec.txt b/dir-spec.txt
index 3786d48..7ae5acd 100644
--- a/dir-spec.txt
+++ b/dir-spec.txt
@@ -703,16 +703,8 @@
"write-history" YYYY-MM-DD HH:MM:SS (NSEC s) NUM,NUM,NUM,NUM,NUM... NL
[At most once]
- Declare how much bandwidth the OR has used recently. Usage is divided
- into intervals of NSEC seconds. The YYYY-MM-DD HH:MM:SS field
- defines the end of the most recent interval. The numbers are the
- number of bytes used in the most recent intervals, ordered from
- oldest to newest.
-
- [We didn't start parsing these lines until Tor 0.1.0.6-rc; they should
- be marked with "opt" until earlier versions of Tor are obsolete.]
-
- [See also migration notes in section 2.1.2.1.]
+ (These fields once appeared in router descriptors, but have
+ appeared in extrainfo descriptors since 0.2.0.x.)
"eventdns" bool NL
@@ -876,8 +868,21 @@
"write-history" YYYY-MM-DD HH:MM:SS (NSEC s) NUM,NUM,NUM,NUM,NUM... NL
[At most once.]
- As documented in section 2.1.1 above. See migration notes in
- section 2.1.2.1.
+ Declare how much bandwidth the OR has used recently. Usage is divided
+ into intervals of NSEC seconds. The YYYY-MM-DD HH:MM:SS field
+ defines the end of the most recent interval. The numbers are the
+ number of bytes used in the most recent intervals, ordered from
+ oldest to newest.
+
+ These fields include both IPv4 and IPv6 traffic.
+
+ "ipv6-read-history" YYYY-MM-DD HH:MM:SS (NSEC s) NUM,NUM,NUM... NL
+ [At most once]
+ "ipv6-write-history" YYYY-MM-DD HH:MM:SS (NSEC s) NUM,NUM,NUM... NL
+ [At most once]
+
+ Declare how much bandwidth the OR has used recently, on IPv6
+ connections. See "read-history" and "write-history" for full details.
"geoip-db-digest" Digest NL
[At most once.]
@@ -1161,6 +1166,14 @@
connection, read and write counters are reset for the next
10-second interval.
+ This measurement includes both IPv4 and IPv6 connections.
+
+ "ipv6-conn-bi-direct" YYYY-MM-DD HH:MM:SS (NSEC s) BELOW,READ,WRITE,BOTH NL
+ [At most once]
+
+ Number of IPv6 connections that are used uni-directionally or
+ bi-directionally. See "conn-bi-direct" for more details.
+
"exit-stats-end" YYYY-MM-DD HH:MM:SS (NSEC s) NL
[At most once.]
@@ -1294,19 +1307,6 @@
initial item "extra-info" and the final item "router-signature",
signed with the router's identity key.
-2.1.2.1. Moving history fields to extra-info documents
-
- Tools that want to use the read-history and write-history values SHOULD
- download extra-info documents as well as server descriptors. Such
- tools SHOULD accept history values from both sources; if they appear in
- both documents, the values in the extra-info documents are authoritative.
-
- New versions of Tor no longer generate server descriptors
- containing read-history or write-history. Tools should continue to
- accept read-history and write-history values in server descriptors
- produced by older versions of Tor until all Tor versions earlier
- than 0.2.0.x are obsolete.
-
2.1.3. Nonterminals in server descriptors
nickname ::= between 1 and 19 alphanumeric characters ([A-Za-z0-9]),