#30219: Add Tom's bandwidth file archive to CollecTor -------------------------------------------------+------------------------- 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: -------------------------------------------------+-------------------------
Comment (by karsten): Alright, it sounds like specifying annotations, including this one, is already under discussion in #28067. What remains to be discussed is what annotation we're using in this case. Regarding `"@source"` annotations, it's true that tor writes these as "FQDN (or IP) and port", but it also accepts other values such as `"@source controller"` when it attempts to parse a router descriptor received via the controller in `router_load_single_router()`. So it really doesn't care what's written in that annotation, which is fine. In this case we might want to use the directory authority nickname rather than IP address or domain name, with a port, because nicknames work so much better in file names than the others. How about we include an ''optional'' `"@source $nickname"` annotation for bandwidth files that we also add to the file name, such as: {{{ 2019-04-21-09-00-00-bandwidth-file-$nickname- 42D07217935283D42CC559A61E7F788E3A92F0E2CB54BE58B5B83E25563C55A2 // nickname given 2019-04-21-09-00-00-bandwidth-file- 42D07217935283D42CC559A61E7F788E3A92F0E2CB54BE58B5B83E25563C55A2 // no nickname given }}} -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30219#comment:10> 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