Re: [rtcweb] Transports: RFC 4941 support?

Harald Alvestrand <harald@alvestrand.no> Sat, 22 March 2014 21:07 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AA5D1A0A04 for <rtcweb@ietfa.amsl.com>; Sat, 22 Mar 2014 14:07:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 33I4ucugcpFA for <rtcweb@ietfa.amsl.com>; Sat, 22 Mar 2014 14:07:12 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [IPv6:2001:700:1:2::117]) by ietfa.amsl.com (Postfix) with ESMTP id F36FF1A08DB for <rtcweb@ietf.org>; Sat, 22 Mar 2014 14:07:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 139327C5006 for <rtcweb@ietf.org>; Sat, 22 Mar 2014 22:07:11 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nuz+cX7PamtA for <rtcweb@ietf.org>; Sat, 22 Mar 2014 22:07:09 +0100 (CET)
Received: from [IPv6:2001:470:de0a:27:d014:dc1:dd24:4393] (unknown [IPv6:2001:470:de0a:27:d014:dc1:dd24:4393]) by mork.alvestrand.no (Postfix) with ESMTPSA id A956A7C4FC3 for <rtcweb@ietf.org>; Sat, 22 Mar 2014 22:07:09 +0100 (CET)
Message-ID: <532DFB7D.5080504@alvestrand.no>
Date: Sat, 22 Mar 2014 22:07:09 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CAOJ7v-0Hw0NFs_avsB2Z8do21BCws2LRZSeSh6HP0t455SPXyw@mail.gmail.com> <B6836FFA-867A-4CBF-9855-D265425EC5E1@cisco.com> <CAOqqYVE=i2L7FxGgKuV0DVaaxYOPnxzSEbDoq0_4Tqapna575g@mail.gmail.com> <CD747481-EBDA-4FFC-A31D-618E6E217420@cisco.com> <5329B617.2070001@alvestrand.no> <17885A74-50A3-49E3-8C54-E53C55019C73@cisco.com> <CAOJ7v-0Dx4Owam7NzXqs6ALPi+ps9gKbmFK9=Zu5eBr9yHYgKg@mail.gmail.com> <444DE75E-BF07-4C6F-91B1-CF57DC67FBA3@cisco.com> <CA+9kkMD5jG-w7ahHLsUX9QMSkSMArS4Wz7ZYOucAZWkrmz5YsQ@mail.gmail.com> <CAOJ7v-1JZG547KkiWeG=3zfCFk6WVzm+r9kF0MTg3SQynHMJdg@mail.gmail.com> <CAD5OKxvKJRMYGYDRNKvmdxmsc35B16P4-+73E+o85-re42yrzw@mail.gmail.com> <CAOJ7v-2hMHJUGhKKocvu5Ld9_cr+duSbJ=+rEucUaAmjiooZTA@mail.gmail.com> <CAD5OKxv5xHknbsPCYpysvo7CeA7oKFu+Yy7QJbmVd6s1UyLr7A@mail.gmail.com> <CA+9kkMBQ=Otxq0vNgKQEoY6UmrEd73625vvBMr45h7MvJFS+Pw@mail.gmail.com> <CAD5OKxtwH-rrkN5BA7zt9kFLC6+sTZAnGjBh+JvFc7FmYMoKVg@mail.gmail.com> <532DF135.1090509@alvestrand.no>
In-Reply-To: <532DF135.1090509@alvestrand.no>
Content-Type: multipart/alternative; boundary="------------070101020007090806080504"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/2saBIoLRjCBM5Zne_dmVI81w9KE
Subject: Re: [rtcweb] Transports: RFC 4941 support?
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Mar 2014 21:07:17 -0000

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 
>> <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.

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.