November 2018 - tor-commits - lists.torproject.org

[torspec/master] Remove line about RelayLines in version 1.1.0
by nickm＠torproject.org 26 Nov '18

26 Nov '18

commit 12e3f52446464cfb8660be9d109e33159a1a6871 Author: teor <teor(a)torproject.org> Date: Thu Nov 8 07:51:18 2018 +0000 Remove line about RelayLines in version 1.1.0 Co-Authored-By: juga0 <juga(a)riseup.net> --- bandwidth-file-spec.txt | 1 - 1 file changed, 1 deletion(-) diff --git a/bandwidth-file-spec.txt b/bandwidth-file-spec.txt index 8aa3b7b..4a9cdd9 100644 --- a/bandwidth-file-spec.txt +++ b/bandwidth-file-spec.txt @@ -46,7 +46,6 @@ 1.1.0 - Add a header containing information about the bandwidth file. Document the sbws and Torflow relay line keys. - to RelayLines and format versions. 1.2.0 - If there are not enough eligible relays, the bandwidth file SHOULD contain a header, but no relays. (To match

1 0

[torspec/master] Correct sbws version in example
by nickm＠torproject.org 26 Nov '18

26 Nov '18

commit 10fd6a98b848552cecc8d5c92152d0ee81d363b2 Author: teor <teor(a)torproject.org> Date: Thu Nov 8 07:41:48 2018 +0000 Correct sbws version in example Co-Authored-By: juga0 <juga(a)riseup.net> --- bandwidth-file-spec.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bandwidth-file-spec.txt b/bandwidth-file-spec.txt index d082a7e..fd497e5 100644 --- a/bandwidth-file-spec.txt +++ b/bandwidth-file-spec.txt @@ -549,7 +549,7 @@ This an example version 1.0.0 document: node_id=$68A483E05A2ABDCA6DA5A3EF8DB5177638A27F80 bw=760 nick=Test measured_at=1523911725 updated_at=1523911725 pid_error=4.11374090719 pid_error_sum=4.11374090719 pid_bw=57136645 pid_delta=2.12168374577 circ_fail=0.2 scanner=/filepath node_id=$96C15995F30895689291F455587BD94CA427B6FC bw=189 nick=Test2 measured_at=1523911623 updated_at=1523911623 pid_error=3.96703337994 pid_error_sum=3.96703337994 pid_bw=47422125 pid_delta=2.65469736988 circ_fail=0.0 scanner=/filepath -A.2. Generated by sbws version 0.1.X +A.2. Generated by sbws version 0.1.0 1523911758 version=1.1.0

1 0

[torspec/master] Explain better what is added in version 1.1.0
by nickm＠torproject.org 26 Nov '18

26 Nov '18

commit c45ca96db574ef04b5311ab75aaebecacd761ea8 Author: teor <teor(a)torproject.org> Date: Thu Nov 8 07:49:39 2018 +0000 Explain better what is added in version 1.1.0 Co-Authored-By: juga0 <juga(a)riseup.net> --- bandwidth-file-spec.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/bandwidth-file-spec.txt b/bandwidth-file-spec.txt index e7ee924..8aa3b7b 100644 --- a/bandwidth-file-spec.txt +++ b/bandwidth-file-spec.txt @@ -44,7 +44,8 @@ 1.0.0 - The legacy fallback Bandwidth List format - 1.1.0 - Adds KeyValue Lines to the Header List section, add KeyValues + 1.1.0 - Add a header containing information about the bandwidth file. + Document the sbws and Torflow relay line keys. to RelayLines and format versions. 1.2.0 - If there are not enough eligible relays, the bandwidth file

1 0

[torspec/master] Add later to the version Tor can consume
by nickm＠torproject.org 26 Nov '18

26 Nov '18

commit 9c91c8376959377330f415cb27654af37e519455 Author: teor <teor(a)torproject.org> Date: Thu Nov 8 07:48:19 2018 +0000 Add later to the version Tor can consume Co-Authored-By: juga0 <juga(a)riseup.net> --- bandwidth-file-spec.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bandwidth-file-spec.txt b/bandwidth-file-spec.txt index fd497e5..f6c56fc 100644 --- a/bandwidth-file-spec.txt +++ b/bandwidth-file-spec.txt @@ -53,7 +53,7 @@ with different bandwidth values. All Tor versions can consume format version 1.0.0. - All Tor versions can consume format version 1.1.0, + All Tor versions can consume format version 1.1.0 and later, but they warn on additional header Lines. [TODO: this might be fixed, and if it is fixed should be said which version of Tor]

1 0

[torspec/master] Explain better what is added in version 1.2.0
by nickm＠torproject.org 26 Nov '18

26 Nov '18

commit 1c4fbae4542e08a2b86f49556e4b71d8dfcc5dc1 Author: teor <teor(a)torproject.org> Date: Thu Nov 8 07:49:02 2018 +0000 Explain better what is added in version 1.2.0 Co-Authored-By: juga0 <juga(a)riseup.net> --- bandwidth-file-spec.txt | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/bandwidth-file-spec.txt b/bandwidth-file-spec.txt index f6c56fc..e7ee924 100644 --- a/bandwidth-file-spec.txt +++ b/bandwidth-file-spec.txt @@ -47,7 +47,10 @@ 1.1.0 - Adds KeyValue Lines to the Header List section, add KeyValues to RelayLines and format versions. - 1.2.0 - Adds new KeyValue Lines to the Header List section with + 1.2.0 - If there are not enough eligible relays, the bandwidth file + SHOULD contain a header, but no relays. (To match + Torflow's 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.

1 0

[torspec/master] Add TODO in the software_version in the examples
by nickm＠torproject.org 26 Nov '18

26 Nov '18

commit a5df39806e846e438c7f536df7de9747ee9d2c44 Author: juga0 <juga(a)riseup.net> Date: Thu Nov 8 07:52:43 2018 +0000 Add TODO in the software_version in the examples --- bandwidth-file-spec.txt | 2 ++ 1 file changed, 2 insertions(+) diff --git a/bandwidth-file-spec.txt b/bandwidth-file-spec.txt index 4a9cdd9..8f54ab3 100644 --- a/bandwidth-file-spec.txt +++ b/bandwidth-file-spec.txt @@ -581,6 +581,7 @@ perc_measured_relays=93 perc_measured_targed=60 software=sbws software_version=1.X.X +[TODO: change the version of sbws that generates this when it is implemented] ===== bw=38000 bw_mean=1127824 bw_median=1180062 desc_avg_bw=1073741824 desc_obs_bw_last=17230879 desc_obs_bw_mean=14732306 error_circ=0 error_misc=0 error_stream=1 master_key_ed25519=YaqV4vbvPYKucElk297eVdNArDz9HtIwUoIeo0+cVIpQ nick=Test node_id=$68A483E05A2ABDCA6DA5A3EF8DB5177638A27F80 rtt=380 success=1 time=2018-05-08T16:13:26 bw=1 bw_mean=199162 bw_median=185675 desc_avg_bw=409600 desc_obs_bw_last=836165 desc_obs_bw_mean=858030 error_circ=0 error_misc=0 error_stream=0 master_key_ed25519=a6a+dZadrQBtfSbmQkP7j2ardCmLnm5NJ4ZzkvDxbo0I nick=Test2 node_id=$96C15995F30895689291F455587BD94CA427B6FC rtt=378 success=1 time=2018-05-08T16:13:36 @@ -600,6 +601,7 @@ perc_measured_relays=46 perc_measured_targed=60 software=sbws software_version=1.X.X +[TODO: change the version of sbws that generates this when it is implemented] ===== B. Scaling bandwidths

1 0

[torspec/master] Correct header keyvalue names in examples
by nickm＠torproject.org 26 Nov '18

26 Nov '18

commit 36837f8a854d46fb09a9830675f90ce034376b7b Author: juga0 <juga(a)riseup.net> Date: Thu Nov 8 08:01:31 2018 +0000 Correct header keyvalue names in examples And reorder them in the way sbws does. --- bandwidth-file-spec.txt | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/bandwidth-file-spec.txt b/bandwidth-file-spec.txt index 8f54ab3..ee02a88 100644 --- a/bandwidth-file-spec.txt +++ b/bandwidth-file-spec.txt @@ -574,11 +574,11 @@ latest_bandwidth=2018-04-16T20:49:18 file_created=2018-04-16T21:49:18 generator_started=2018-04-16T15:13:25 earliest_bandwidth=2018-04-16T15:13:26 -num_measured_relays=6000 -num_net_relays=6436 -num_target_relays=3862 -perc_measured_relays=93 -perc_measured_targed=60 +minimum_number_eligible_relays=3862 +minimum_percent_eligible_relays=60 +number_consensus_relays=6436 +number_eligible_relays=6000 +percent_eligible_relays=93 software=sbws software_version=1.X.X [TODO: change the version of sbws that generates this when it is implemented] @@ -594,11 +594,11 @@ earliest_bandwidth=2018-10-20T19:35:52 file_created=2018-10-25T19:35:03 generator_started=2018-10-25T11:42:56 latest_bandwidth=2018-10-25T19:34:39 -num_measured_relays=2960 -num_net_relays=6436 -num_target_relays=3862 -perc_measured_relays=46 -perc_measured_targed=60 +minimum_number_eligible_relays=3862 +minimum_percent_eligible_relays=60 +number_consensus_relays=6436 +number_eligible_relays=2960 +percent_eligible_relays=46 software=sbws software_version=1.X.X [TODO: change the version of sbws that generates this when it is implemented]

1 0

[torspec/master] Merge remote-tracking branch 'tor-github/pr/38'
by nickm＠torproject.org 26 Nov '18

26 Nov '18

commit d41a32ae35672aa19953b44d6d113ec357d0da8c Merge: bab8a89 a5292ee Author: Nick Mathewson <nickm(a)torproject.org> Date: Mon Nov 26 16:51:52 2018 -0500 Merge remote-tracking branch 'tor-github/pr/38' bandwidth-file-spec.txt | 140 ++++++++++++++++++++++++++++++++++++++++++++++-- 1 file changed, 135 insertions(+), 5 deletions(-)

1 0

[torspec/master] Correct spaces format
by nickm＠torproject.org 26 Nov '18

26 Nov '18

commit a5292eefbda6a1e93655bf89ab3ce27ce3cfb515 Author: juga0 <juga(a)riseup.net> Date: Thu Nov 8 08:09:52 2018 +0000 Correct spaces format --- bandwidth-file-spec.txt | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/bandwidth-file-spec.txt b/bandwidth-file-spec.txt index ee02a88..3d95927 100644 --- a/bandwidth-file-spec.txt +++ b/bandwidth-file-spec.txt @@ -44,13 +44,13 @@ 1.0.0 - The legacy fallback Bandwidth List format - 1.1.0 - Add a header containing information about the bandwidth file. - Document the sbws and Torflow relay line keys. + 1.1.0 - Add a header containing information about the bandwidth + file. Document the sbws and Torflow relay line keys. 1.2.0 - If there are not enough eligible relays, the bandwidth file - SHOULD contain a header, but no relays. (To match - Torflow's existing behaviour.) Adds new - KeyValue Lines to the Header List section with + SHOULD contain a header, but no relays. (To match Torflow's + 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.

1 0

[torspec/master] Merge remote-tracking branch 'tor-github/pr/43'
by nickm＠torproject.org 26 Nov '18

26 Nov '18

commit bab8a89223eebd28445aa3c4c9e41370b891b8c2 Merge: 4421149 2decb3e Author: Nick Mathewson <nickm(a)torproject.org> Date: Mon Nov 26 16:50:47 2018 -0500 Merge remote-tracking branch 'tor-github/pr/43' dir-spec.txt | 18 ------------------ 1 file changed, 18 deletions(-) diff --cc dir-spec.txt index 3058180,7312dd2..a6547ce --- a/dir-spec.txt +++ b/dir-spec.txt @@@ -2105,44 -2105,8 +2105,26 @@@ If an authority is configured with a V3BandwidthsFile, but parsing fails, this line SHOULD appear in its vote, but without any headers. - Current Keywords: - "timestamp" -- the Unix Epoch time in seconds of the most recent - generator result. - "version" -- the Bandwidth List format document specification version. - "software" -- the name of the software that created the document. - "software_version" -- the version of the software that created the - document. - "file_created" -- the date and time timestamp in ISO 8601 format - and UTC time zone when the file was created. - "generator_started" -- the date and time timestamp in ISO 8601 format - and UTC time zone when the generator started. - "earliest_bandwidth" -- the date and time timestamp in ISO 8601 format - and UTC time zone when the first relay bandwidth was obtained. - "latest_bandwidth" -- the date and time timestamp in ISO 8601 format - and UTC time zone of the most recent generator result. - This time MUST be identical to the initial Timestamp line. - This duplicate value is included to make the format easier for people - to read. First-appeared: Tor 0.3.5.1-alpha. + "bandwidth-file-digest" 1*(SP algorithm "=" digest) NL + + [At most once for votes; does not occur in consensuses.] + + A digest of the bandwidth file used to generate this vote. + "algorithm" is the name of the hash algorithm producing "digest", + which can be "sha256" or another algorithm. "digest" is the + base64 encoding of the hash of the bandwidth file, with trailing =s + omitted. + + If an authority is not configured with a V3BandwidthsFile, this line + SHOULD NOT appear in its vote. + + If an authority is configured with a V3BandwidthsFile, but parsing + fails, this line SHOULD appear in its vote, with the digest(s) of the + unparseable file. + First-appeared: Tor 0.4.0.1-alpha + The authority section of a vote contains the following items, followed in turn by the authority's current key certificate:

1 0