Comment # 12 on bug 986395 from Neil Brown

> ... but read the lifetime from the address.

as far as I can tell there is no interface to do this.

With a bit of effort I could probably get a list of interfaces, then a list of
addresses for each interface together with their lifetimes.  Then compare the
address I got when I bound my socket to each of these to deduce the lifetime of
the address.  But that is awfully clumsy.

Always requesting a public address is certainly possible but seems to go
explicitly against the configuration choice to use temporary private addresses
for outgoing connections.

I'm currently tempted to not change anything.  Once the local address does
expire the client will stop getting replies from the server, will timeout, and
will reconnect.  It should then get a new address.
This should only take about 2 minutes, and should only happen if there has been
constant traffic, with no gap of 5 minutes, for the entire lifetime of the
temporary address.
I need to test that this is what actually happens.  If it is, I would need a
very strong arguement for making any change given how clumsy such a change
would have to be.