[tor-bugs] #29056 [Core Tor/Stem]: Implement bandwidth file parser and formater

[Tor Bug Tracker & Wiki]

#29056: Implement bandwidth file parser and formater
---------------------------+--------------------------
 Reporter:  juga           |          Owner:  juga
     Type:  defect         |         Status:  assigned
 Priority:  Medium         |      Milestone:
Component:  Core Tor/Stem  |        Version:
 Severity:  Normal         |     Resolution:
 Keywords:  tor-bwauth     |  Actual Points:
Parent ID:                 |         Points:
 Reviewer:                 |        Sponsor:
---------------------------+--------------------------

Comment (by teor):

 Replying to [comment:8 juga]:
 > Replying to [comment:7 teor]:
 > > In fact, you should have 4 files in your unit tests, because there are
 two different kinds of 1.2.0 files.
 >
 > Since it'll change again with 1.0.3 (not released yet) and since, except
 for longclaw, there're no other authorities that has used sbws, do you
 really think it's needed to support the files produced by sbws 1.2.0?.

 People will expect stem to parse all available format versions.

 Here's why we might need to parse each format version:
 * stem will need to parse 1.0.0 format files, because they're produced by
 Torflow on most authorities.
 * if anyone is keeping an archive of bandwidth files from longclaw, then
 it may contain 1.1.0 format files, and it will contain 1.2.0 format files.
 * if stem's parser is ready before longclaw deploys sbws 1.0.3, then it
 should be able to parse 1.2.0 format files.

 And more generally:

 The bandwidth file format is forward-compatible: a well-written parser
 should be able to handle 1.0.0, 1.1.0, 1.2.0, and all future 1.x format
 versions. And it's worth testing the parser with all available format
 versions, to make sure it produces useful results.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/29056#comment:10>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online