Opened 21 months ago

Last modified 5 months ago

#29111 new enhancement

Optional heartbeat message from PT's

Reported by: ahf Owned by:
Priority: Low Milestone: Tor: unspecified
Component: Circumvention/Pluggable transport Version: Tor: unspecified
Severity: Normal Keywords: network-team-roadmap-2020Q1, network-team-roadmap-2020Q2
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor: Sponsor28-must


Would it make sense to have a specified STATUS message for Tor-style heartbeat messages for PT's?

When running a Tor relay/bridge it's useful to have the Tor heartbeat message to see the activity of your relay/bridge - maybe the same would make sense for PT's too.

Lame anecdotal note: I ran a test bridge for my quic-pt code and just received an email from someone who was using it. I was turning it off because I had an idea that nobody used it.

Child Tickets

Change History (11)

comment:1 Changed 21 months ago by teor

Owner: asn deleted
Status: newassigned

asn does not need to own any obfuscation tickets any more. Default owners are trouble.

comment:2 Changed 21 months ago by cohosh

Status: assignednew

tickets were assigned to asn, setting them as unassigned (new) again.

comment:3 Changed 20 months ago by arma

Is this ticket accomplishable now that there is a LOG message equivalent from PTs to Tor? Or is this about tagging the log message in a special way so that Tor knows to treat it as a contribution to its own heartbeat messages?

If it's this second one, I wonder if we want to generalize to adding a domain or something to the log messages coming from PTs, so the PT can label its messages however it likes. And then the first use case there would be for some of the log messages to be in the heartbeat domain, and then Tor would know how the PT thinks the user should be informed.

comment:4 Changed 20 months ago by ahf

This should be done using the other new message (STATUS) rather than LOG. In this ticket we should figure out what information would be useful to note here and standardize the parameters to the given STATUS message (which values we emit).

If a PT process today want to just do a "plain text" heartbeat like log line (like Tor does) they can do it via the LOG statement. This is less useful for Tor though since we would have to parse the text message, which is what STATUS tries to solve.

comment:5 Changed 17 months ago by phw

Sponsor: Sponsor19Sponsor28-must

Moving from Sponsor 19 to Sponsor 28.

comment:6 Changed 15 months ago by gaba

Keywords: network-team-roadmap-november added

comment:7 Changed 9 months ago by gaba

Keywords: network-team-roadmap-2020Q1 added; network-team-roadmap-november removed

Leftover from roadmap in November. Move into the roadmap for this year as this is a must for sponsor 28.

comment:8 Changed 7 months ago by gaba

Owner: set to catalyst
Status: newassigned

comment:9 Changed 7 months ago by gaba

Keywords: network-team-roadmap-2020Q2 added

move tickets into the 2020 Q2 roadmap for the network team

comment:10 Changed 5 months ago by nickm

Owner: catalyst deleted

Un-assign tickets.

comment:11 Changed 5 months ago by nickm

Status: assignednew
Note: See TracTickets for help on using tickets.