Feature description

The status quo is that the QUIC reconnection interval is max(reconnectionIntervalS/3, 10).

IMHO the QUIC reconnection interval shouldn't be hardcoded to be a third of the TCP reconnection interval.

Problem or use case

The current logic makes it so if I want to decrease the reconnection interval to 20 seconds on TCP to increase the chances of TCP hole punching working, it dials the QUIC addresses unnecessarily frequently, or worse, if I want to increase the reconnection interval to save energy, it will dial QUIC addresses at thrice the rate of the TCP addresses, negating the energy savings.

Alternatives or workarounds

Triple the TCP reconnection interval, but this can throw off the (subjective) balance between energy usage and time until connection for TCP addresses.