#30217: Extend CollecTor filesystem protocol for bandwidth files
-------------------------------------------------+-------------------------
Reporter: irl | Owner:
| metrics-team
Type: enhancement | Status: new
Priority: Medium | Milestone:
Component: Metrics/CollecTor | Version:
Severity: Normal | Resolution:
Keywords: tor-bwauth,tor-dirauth,metrics- | Actual Points:
roadmap-2019-q2 |
Parent ID: #21378 | Points:
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Changes (by teor):
* cc: juga (added)
Comment:
Replying to #21378 comment 32:
> #30217 is an open question. We need to work out how to store these in a
way that identifies which scanner collected the data, and the timestamp,
and have these things be unique too. There are multiple timestamps in the
file format,
In format version 1.0.0 (Torflow), the unnamed latest bandwidth Timestamp
is not unique: multiple files can be created with the same "newest
result".
In format versions 1.1.0 and later, the file_created timestamp should be
reasonably unique: files should be created every 30-60 minutes, and each
file should have a different timestamp.
If you need a unique identifier, you should use the bandwidth file digest.
If the authority is running 0.4.0.4-rc or later, there will be a
bandwidth-file-digest in the vote:
https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n2154
> and not currently any identifier of the bandwidth scanner.
We thought about adding a scanner name. And now I can't remember why we
didn't. Maybe juga knows?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30217#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
