IETF Logo Mail Archive

Re: [rtcweb] Transports: RFC 4941 support?

Dmitry Anipko <Dmitry.Anipko@microsoft.com> Fri, 21 March 2014 17:28 UTC

Return-Path: <Dmitry.Anipko@microsoft.com>
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 2957C1A0A07 for <rtcweb@ietfa.amsl.com>; Fri, 21 Mar 2014 10:28:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 5JhCqqTTHPPu for <rtcweb@ietfa.amsl.com>; Fri, 21 Mar 2014 10:28:54 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0242.outbound.protection.outlook.com [207.46.163.242]) by ietfa.amsl.com (Postfix) with ESMTP id 149621A046A for <rtcweb@ietf.org>; Fri, 21 Mar 2014 10:28:53 -0700 (PDT)
Received: from SN2PR03MB077.namprd03.prod.outlook.com (10.255.175.153) by SN2PR03MB079.namprd03.prod.outlook.com (10.255.175.155) with Microsoft SMTP Server (TLS) id 15.0.898.11; Fri, 21 Mar 2014 17:28:43 +0000
Received: from SN2PR03MB077.namprd03.prod.outlook.com ([169.254.14.128]) by SN2PR03MB077.namprd03.prod.outlook.com ([169.254.14.134]) with mapi id 15.00.0898.005; Fri, 21 Mar 2014 17:28:43 +0000
From: Dmitry Anipko <Dmitry.Anipko@microsoft.com>
To: Roman Shpount <roman@telurix.com>, Ted Hardie <ted.ietf@gmail.com>
Thread-Topic: [rtcweb] Transports: RFC 4941 support?
Thread-Index: AQHPREwi0jHh8qWwMUaGOZ51kT+Nj5rqK/aAgAAJUwCAAD+7AIAAI7UAgAAD5wCAABOuAIAAJLQAgADhu4CAABGDAIAABE3Q
Date: Fri, 21 Mar 2014 17:28:42 +0000
Message-ID: <adf8e32e91564028bc97623b7dd6e938@SN2PR03MB077.namprd03.prod.outlook.com>
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>
In-Reply-To: <CAD5OKxtwH-rrkN5BA7zt9kFLC6+sTZAnGjBh+JvFc7FmYMoKVg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [2001:4898:80e0:ee43::4]
x-forefront-prvs: 0157DEB61B
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(428001)(24454002)(377454003)(189002)(199002)(4396001)(54356001)(33646001)(51856001)(85852003)(85306002)(47976001)(50986001)(54316002)(92566001)(19580395003)(76482001)(49866001)(47736001)(56776001)(53806001)(79102001)(59766001)(81342001)(77982001)(46102001)(63696002)(76796001)(81542001)(83322001)(94316002)(19580405001)(86362001)(93516002)(80976001)(95666003)(86612001)(95416001)(94946001)(76786001)(97186001)(69226001)(93136001)(65816001)(20776003)(80022001)(76576001)(77096001)(74316001)(90146001)(74876001)(16236675002)(56816005)(81816001)(83072002)(74366001)(74502001)(74662001)(31966008)(47446002)(74706001)(81686001)(2656002)(87266001)(87936001)(24736002)(3826001); DIR:OUT; SFP:1101; SCL:1; SRVR:SN2PR03MB079; H:SN2PR03MB077.namprd03.prod.outlook.com; FPR:3CEEF5A0.C3EA7CD.77F07F34.4CE93160.20250; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (: microsoft.com does not designate permitted sender hosts)
Content-Type: multipart/alternative; boundary="_000_adf8e32e91564028bc97623b7dd6e938SN2PR03MB077namprd03pro_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.onmicrosoft.com
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/2cNJRJOXl2exF9l9KXjEBZIiZ-0
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
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: Fri, 21 Mar 2014 17:28:59 -0000

>>What I meant is situation where you have both temp and permanent addresses on the same interface


This is a default for interfaces of Windows computers, using SLAAC.


________________________________
From: rtcweb <rtcweb-bounces@ietf.org> on behalf of Roman Shpount <roman@telurix.com>
Sent: Friday, March 21, 2014 10:10 AM
To: Ted Hardie
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Transports: RFC 4941 support?


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.
_____________
Roman Shpount

v2.23.0 | Report a Bug | By Email