Opened 8 years ago

Closed 4 years ago

#4117 closed defect (wontfix)

Definition of LastTestedTimestamp in TorBEL export data format specification is unclear

Reported by: karsten Owned by: Sebastian
Priority: Low Milestone:
Component: Core Tor/TorDNSEL Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

TorBEL's data-spec.txt says that there can be more than 1 entry for each RouterID. This happens when a router was found to exit via different IP addresses for different ports.

The specification does not specify whether all lines belonging to the same RouterID contain the same LastTestedTimestamp or not. Technically, it's the time when "TorBEL last completed testing this node's exit policy" (Section 1.2), so it should be the same timestamp for all lines with the same RouterID. Not a big issue, but maybe the spec should say what behavior one can expect here.

Child Tickets

Change History (2)

comment:1 in reply to:  description Changed 8 years ago by karsten

Replying to karsten:

Technically, it's the time when "TorBEL last completed testing this node's exit policy" (Section 1.2), so it should be the same timestamp for all lines with the same RouterID. Not a big issue, but maybe the spec should say what behavior one can expect here.

On second thought, TorBEL only includes the results from the most recent scan per relay, right? If this is correct, the timestamp should be the same, and the spec should say so.

comment:2 Changed 4 years ago by arlolra

Resolution: wontfix
Severity: Normal
Status: newclosed

TorBEL is unmaintained.

Note: See TracTickets for help on using tickets.