Make good use of unstable relays

changed milestone to %Tor: unspecified

added component::core tor/tor milestone::Tor: unspecified needs-proposal priority::medium reporter::jeffluo35 severity::normal status::new tor-relay type::enhancement version::tor unspecified labels

Well, "keeping their flags" isn't possible as things stand now. For example, the Guard flag means that a relay would be a good guard... and a server that disappears half of the time isn't a good guard. The "Stable" flag means that the server doesn't go down very often... and a server that does down once a day does indeed go down pretty often.

But the root idea here is an interesting one. Maybe we can come up with some way to make intermittent nodes useful to the Tor network.

Trac:
Milestone: N/A to Tor: unspecified
Keywords: N/A deleted, tor-relay needs-proposal added

This enhancement is developable.

Let's assume we talk about capable (>10Mbit/s uplink) and always online tor nodes on end-user ISP links (e.g. dialups with forces IP change on daily,weekly basis by ISP)

In intermediate-term future we will see live rotation/moving IPv6 network prefixes provided by ISP dhcp/ra, for preventing long-term privacy identification by always online end-user links with same network prefix.

These nodes will never receive the STABLE flag and may not operate at full line capacity.

if STABLE flag means always reachable at same given IP address, we need a new flag UPTIME for respecting long-living tor nodes with changing IP addresses.

<< open topic is the weight and technique design of such an UPTIME flag >>

greets anonymous "cyberpunk"

Set all open tickets without a severity to "Normal"

Trac:
Severity: N/A to Normal

longlivedports option should respect STABLE but does actually not UPTIME. only relys on STABLE flag witch could drop your "longlived" (irc) connection if node is shutdown

Trac:
Reviewer: N/A to N/A
Sponsor: N/A to N/A

moved to tpo/core/tor#13230 (closed)

Make good use of unstable relays

Child items ...

Activity