Re: [rtcweb] Transports: RFC 4941 support?

I was incorrect. It is normal to get both temp and permanent IPv6 addresses
on Windows and Ubuntu.

_____________
Roman Shpount

On Sat, Mar 22, 2014 at 5:07 PM, Harald Alvestrand <harald@alvestrand.no>wrote:

>  On 03/22/2014 09:23 PM, Harald Alvestrand wrote:
>
> 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> wrote:
>
>>   On Thu, Mar 20, 2014 at 7:39 PM, Roman Shpount <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.
>
>
> And just to get people used to looking at stuff for themselves, here's my
> desktop machine, which is DEFINITELY a default Ubuntu setup:
>
> hta@liset:~$ ip addr
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>     inet 127.0.0.1/8 scope host lo
>     inet6 ::1/128 scope host
>        valid_lft forever preferred_lft forever
> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
> UP qlen 1000
>     link/ether 6c:3b:e5:0b:6a:b4 brd ff:ff:ff:ff:ff:ff
>     inet 192.168.1.17/24 brd 192.168.1.255 scope global eth0
>     inet6 2001:470:de0a:27:d014:dc1:dd24:4393/64 scope global temporary
> dynamic
>        valid_lft 86379sec preferred_lft 14379sec
>     inet6 2001:470:de0a:27:31d8:d7fc:4af4:c17a/64 scope global temporary
> deprecated dynamic
>        valid_lft 86379sec preferred_lft 0sec
>     inet6 2001:470:de0a:27:8c26:e950:a09d:814c/64 scope global temporary
> deprecated dynamic
>        valid_lft 86379sec preferred_lft 0sec
>     inet6 2001:470:de0a:27:d883:fc90:cdcd:6b8f/64 scope global temporary
> deprecated dynamic
>        valid_lft 86379sec preferred_lft 0sec
>     inet6 2001:470:de0a:27:40c9:8eca:a92b:d0ac/64 scope global temporary
> deprecated dynamic
>        valid_lft 86379sec preferred_lft 0sec
>     inet6 2001:470:de0a:27:55e8:a88d:df95:df5d/64 scope global temporary
> deprecated dynamic
>        valid_lft 86379sec preferred_lft 0sec
>     inet6 2001:470:de0a:27:accc:2652:cc97:5b17/64 scope global temporary
> deprecated dynamic
>        valid_lft 76189sec preferred_lft 0sec
>     inet6 2001:470:de0a:27:6e3b:e5ff:fe0b:6ab4/64 scope global dynamic
>        valid_lft 86379sec preferred_lft 14379sec
>     inet6 fe80::6e3b:e5ff:fe0b:6ab4/64 scope link
>        valid_lft forever preferred_lft forever
>
> Ignoring the deprecated ones, one temporary and one non-temporary.
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>