[tor-dev] Dealing with frequent suspends on Android

[teor]

> On 6 Nov 2018, at 03:38, Michael Rogers <michael at briarproject.org> wrote:
> 
> One of the difficulties with this option is that under some conditions,
> the controller can only schedule one alarm every 15 minutes. Traffic
> from the guard would also wake the CPU, so if we could ask the guard for
> regular keepalives, we might be able to promise that the CPU will wake
> once every keepalive interval, unless the guard connection's lost, in
> which case it will wake once every 15 minutes. But keepalives from the
> guard would require a protocol change, which would take time to roll
> out, and would let the guard know (if it doesn't already) that the
> client's running on Android.

Tor implemented netflow padding in 0.3.1.1-alpha (May 2017):
https://gitweb.torproject.org/torspec.git/tree/padding-spec.txt

Connection padding may act like a keepalive, we should consider this
use case as we improve our padding designs.

T
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20181106/aa75a899/attachment-0001.sig>