Re: Disabling temporary addresses by default?

[Fernando Gont <[e-mail]>]

On 28/1/20 13:27, Christian Huitema wrote:
> 
> On Jan 28, 2020, at 6:59 AM, Lorenzo Colitti <lorenzo=[e-mail]> wrote:
>>
>> Instead of disabling, why not change the default of the number of addresses maintained? For example, instead of maintaining 1 permanent + 1 valid + 7 deprecated, why not just default to maintaining 1 permanent + 1 valid + 1 deprecated. That means that applications would have to re-establish their connections once a day instead of once every 7 days. But if they use privacy addresses, they already need to re-establish connections after 7 days. And they can always use not to use privacy addresses via the appropriate socket option.
> 
> That seems plausible, but how about going one step further and for clients just have one temporary and one deprecated address, without any stable address? If the client is not running any server, that makes address management much simpler.

rfc4041 bis already allows for that.

The only thing is that if the Preferred Lifetime is 1 day, and Valid 
Lifetime is 2*Preferred Lifetime, and you only do temporary addresses, 
then your sessions (e.g. SSH) cannot span past one day, *unless* we 
recommend that invalid addresses are still okay for established connections.

-- 
Fernando Gont
SI6 Networks
e-mail: [e-mail]
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492