diff options
author | Nick Mathewson <nickm@torproject.org> | 2019-03-08 10:29:23 -0500 |
---|---|---|
committer | Nick Mathewson <nickm@torproject.org> | 2019-03-08 10:29:23 -0500 |
commit | e6ce3948e85c991f5d8fb9880911543083a76726 (patch) | |
tree | b3a3993fd392ee0e27e1e8d88625b1aa455dbea2 /bandwidth-file-spec.txt | |
parent | 1e3fac1afdfafc11ebe973a5b0d94aca327d661b (diff) | |
parent | 8d7d1a7ea1a1a0efed64ad3f146b2c82f00ce7d6 (diff) | |
download | torspec-e6ce3948e85c991f5d8fb9880911543083a76726.tar.gz torspec-e6ce3948e85c991f5d8fb9880911543083a76726.zip |
Merge branch 'bandwidth_file_name_squashed'
Diffstat (limited to 'bandwidth-file-spec.txt')
-rw-r--r-- | bandwidth-file-spec.txt | 24 |
1 files changed, 12 insertions, 12 deletions
diff --git a/bandwidth-file-spec.txt b/bandwidth-file-spec.txt index a241108..556aa8c 100644 --- a/bandwidth-file-spec.txt +++ b/bandwidth-file-spec.txt @@ -1,10 +1,10 @@ - Tor Bandwidth List Format + Tor Bandwidth File Format juga teor 1. Scope and preliminaries - This document describes the format of Tor's Bandwidth List, version + This document describes the format of Tor's Bandwidth File, version 1.0.0 and later. It is a new specification for the existing bandwidth file format, @@ -12,7 +12,7 @@ 1.1.0 and later, which are backwards compatible with 1.0.0 parsers. Since Tor version 0.2.4.12-alpha, the directory authorities use - the Bandwidth List file called "V3BandwidthsFile" generated by + the Bandwidth File file called "V3BandwidthsFile" generated by Torflow [1]. The details of this format are described in Torflow's README.spec.txt. We also summarise the format in this specification. @@ -36,15 +36,15 @@ The Tor directory protocol (dir-spec.txt [3]) sections 3.4.1 and 3.4.2, use the term bandwidth measurements, to refer to what - here is called Bandwidth List. + here is called Bandwidth File. - A Bandwidth List file contains information on relays' bandwidth + A Bandwidth File contains information on relays' bandwidth capacities and is produced by bandwidth generators, previously known as bandwidth scanners. 1.4. Format Versions - 1.0.0 - The legacy Bandwidth List format + 1.0.0 - The legacy Bandwidth File format 1.1.0 - Add a header containing information about the bandwidth file. Document the sbws and Torflow relay line keys. @@ -54,18 +54,18 @@ existing behaviour.) Adds new KeyValue Lines to the Header List section with statistics about the number of relays included in the file. - Add new KeyValue Lines to the Relays' Bandwidth List section - with different bandwidth values. + Add new KeyValues to Relay Bandwidth Lines, with different + bandwidth values (averages and descriptor bandwidths). All Tor versions can consume format version 1.0.0. - + All Tor versions can consume format version 1.1.0 and later, but Tor versions earlier than 0.3.5.1-alpha warn if the header contains any KeyValue lines after the Timestamp. 2. Format details - The Bandwidth List MUST contain the following sections: + The Bandwidth File MUST contain the following sections: - Header List (exactly once), which is a partially ordered list of - Header Lines (one or more times), then - Relay Lines (zero or more times), in an arbitrary order. @@ -310,10 +310,10 @@ In version 1.0.0, Header List ends when the first relay bandwidth is found conforming to the next section. - + Implementations of version 1.1.0 and later SHOULD use a 5-character terminator. - + Tor 0.4.0.1-alpha and later look for a 5-character terminator, or the first relay bandwidth line. sbws versions 0.1.0 to 1.0.2 used a 4-character terminator, this bug was fixed in 1.0.3. |