Re: [rtcweb] Transports: RFC 4941 support?

On 03/21/2014 06:10 PM, Roman Shpount wrote:
>
> On Fri, Mar 21, 2014 at 12:07 PM, Ted Hardie <ted.ietf@gmail.com
> <mailto:ted.ietf@gmail.com>> wrote:
>
>     On Thu, Mar 20, 2014 at 7:39 PM, Roman Shpount <roman@telurix.com
>     <mailto:roman@telurix.com>> wrote:
>
>         The whole problem (with using temp or permanent addresses) is
>         a bit imaginary since under most common client setups you only
>         see temporary addresses. Permanent IPv6 addresses show up only
>         on servers or if specifically configured on the host.
>
>
>     It's actually not imaginary in enterprise contexts, as there are
>     shops that disable temporary addresses to make tracking or other
>     security activities easier.  Not my favorite reasoning,
>     personally, but there you go.
>
>
> What I meant is situation where you have both temp and permanent
> addresses on the same interface is quite unusual. In most cases it is
> one or the other. Getting both addresses configured usually requires
> some very deliberate administrative action, and unless I am mistaken,
> is not common.

I think you are mistaken..... at least, your claim does not fit with my
data.

This laptop, on a default-configured IPv6 home network:

    inet6 2001:470:de0a:27:9964:c162:8161:9a2e/64 scope global temporary
dynamic
       valid_lft 86356sec preferred_lft 14356sec
    inet6 2001:470:de0a:27:863a:4bff:fe0b:28b0/64 scope global dynamic
       valid_lft 86356sec preferred_lft 14356sec

Some very deliberate administrative action may have been taken (this is
a Google corporate device), but I suspect that it's a default Ubuntu
configuration.

> _____________
> Roman Shpount
>  
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

-- 
Surveillance is pervasive. Go Dark.