Re: [tor-bugs] #29624 [Metrics/Exit Scanner]: New version of exit list format

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#29624: New version of exit list format
-------------------------------------+--------------------------------
 Reporter:  irl                      |          Owner:  karsten
     Type:  task                     |         Status:  needs_revision
 Priority:  Medium                   |      Milestone:
Component:  Metrics/Exit Scanner     |        Version:
 Severity:  Normal                   |     Resolution:
 Keywords:  metrics-roadmap-2019-q2  |  Actual Points:
Parent ID:  #29650                   |         Points:
 Reviewer:  irl                      |        Sponsor:
-------------------------------------+--------------------------------
Changes (by notirl):

 * status:  needs_review => needs_revision


Comment:

 We need to work on the use of words like "may". Unless Tor already has
 something for this, let's refer to RFC2119.

 I don't believe we need to prefix keywords with "Scanner". Was there a
 specific reason for this?

 dir-spec uses kebab-case for keywords, not CamelCase.

 For fields that are already defined in dir-spec, like "contact" we should
 refer to those semantics instead of making up our own.

 As above, for date/time formats.

 We should be specific on our use of country codes. There are extensions
 added by the databases we are using, and we also use our own extensions.
 Maybe we should talk to OONI and see what they are using too so we can be
 unified.

 How does the "Downloaded" keyword work with signed documents? How do you
 see it being used?

 On point 1, this sounds OK. I am starting to think of exit lists in the
 new scanner context as a derived format from the raw measurement results
 in a similar way that our current torperf files are derived from onionperf
 analysis results which are derived from tor/tgen logs.

 As an aside, the format we are deriving from will most likely be
 [[https://pathspider.readthedocs.io/en/latest/using.html#data-
 formats|PATHspider ndjson]]. This is not important for the spec.

 On point 2, this also sounds OK. Should we specify that an exit list
 should be used with a specific consensus in applications like ExoneraTor?
 I think no, we should always use the latest exit list and latest consensus
 to give the most up-to-date information available.

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

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs