Re: Disabling temporary addresses by default?

[Erik Kline <[e-mail]>]

On Thu, Jan 30, 2020 at 8:52 AM Gyan Mishra <[e-mail]> wrote:

>
>
> On Wed, Jan 29, 2020 at 6:26 AM Nick Hilliard <[e-mail]> wrote:
>
>> Lorenzo Colitti wrote on 29/01/2020 11:13:
>> > But don't enterprises care about not leaking the habits of their
>> employees?
>>
>> This is only a problem in SLAAC environments where privacy addresses are
>> turned off.  In DHCP environments, the network operator can change
>> endpoint addresses by policy if this is what they want to do.
>>
>
>    Gyan> Enterprises fall into a totally different camp altogether as far
> as “employee” privacy as that is non existent as all traffic is monitored
> to be business related traffic to the extent of web content blocking which
> most all companies implement.   The use of temporary addresses does not
> make sense for enterprises to employ as operations stability and 99.99999%
> available and MTTR( mean time to recovery) is of utmost importance.  By
> disabling the temporary address - simplified the enterprise network
> troubleshooting tremendously as only a single “stable” random address
> exists at all times.  As far as temporary address and “long lived”
> connections for enterprise business critical applications that can all be
> solved by disabling the temporary address..
>

There's difference between "the enterprise can track the employees' work
devices' connections" and "the whole word can track the enterprise's
employees' work devices' connections".  Disabling temporary addresses
altogether is more in the 2nd category.  Temporary addresses + enterprise
logging (on premises' equipment and on the devices themselves) fits
comfortably in the first category.