IETF Logo Mail Archive

Re: [rtcweb] Transports: RFC 4941 support?

Roman Shpount <roman@telurix.com> Fri, 21 March 2014 17:10 UTC

Return-Path: <roman@telurix.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 5034B1A07A0 for <rtcweb@ietfa.amsl.com>; Fri, 21 Mar 2014 10:10:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 3txsOz4vjE1M for <rtcweb@ietfa.amsl.com>; Fri, 21 Mar 2014 10:10:28 -0700 (PDT)
Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173]) by ietfa.amsl.com (Postfix) with ESMTP id CBCB81A0904 for <rtcweb@ietf.org>; Fri, 21 Mar 2014 10:10:25 -0700 (PDT)
Received: by mail-wi0-f173.google.com with SMTP id f8so716044wiw.0 for <rtcweb@ietf.org>; Fri, 21 Mar 2014 10:10:15 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=WlbpI0aFRYjap5GcAfZEC55KmzcDFPFYPUWW4IPtDxY=; b=Ier2bV9fqzV6x4Hxas9Pb6cOFM3e60euxA/pwF09K8BkW8GuXi54EfRrKsKwP7Q6n6 BSy98xznuONPWNMO33HnxtwXPGr6ZhCwzTc0IayeguBn+Ci7MOg+MFDD7yxesNX3ZmAI IYA09d+QQwbKw5dJaYrZrCRCFfXOnO6/OPEGsdu17LJWZZk80LXdK9MP6LvaDggqf9bj YAWle3MDhijZ3ei0nGmIMiGhch4/cuoldUMpDnoyyaiQsnOLtl5tJOhnic1VHzZACwW5 yx9BgDFgw2AkkZqsWwyx2Rj/HymIJNUox0Br4BQiNWYHvGZjkrA+7jw7L06gS8lReUFN cBDw==
X-Gm-Message-State: ALoCoQmJAp7R3hnDtW7IFTEXQ+44tmy7op6YE27xOCwTZoc62WphhMOzS9yxOC9T3XpVWlVVU1Ey
X-Received: by 10.180.164.106 with SMTP id yp10mr3948285wib.48.1395421815745; Fri, 21 Mar 2014 10:10:15 -0700 (PDT)
Received: from mail-wi0-f177.google.com (mail-wi0-f177.google.com [209.85.212.177]) by mx.google.com with ESMTPSA id ga20sm6837913wic.0.2014.03.21.10.10.14 for <rtcweb@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 21 Mar 2014 10:10:14 -0700 (PDT)
Received: by mail-wi0-f177.google.com with SMTP id cc10so722721wib.4 for <rtcweb@ietf.org>; Fri, 21 Mar 2014 10:10:14 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.180.77.49 with SMTP id p17mr3972378wiw.4.1395421814602; Fri, 21 Mar 2014 10:10:14 -0700 (PDT)
Received: by 10.216.49.137 with HTTP; Fri, 21 Mar 2014 10:10:14 -0700 (PDT)
In-Reply-To: <CA+9kkMBQ=Otxq0vNgKQEoY6UmrEd73625vvBMr45h7MvJFS+Pw@mail.gmail.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>
Date: Fri, 21 Mar 2014 13:10:14 -0400
Message-ID: <CAD5OKxtwH-rrkN5BA7zt9kFLC6+sTZAnGjBh+JvFc7FmYMoKVg@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Ted Hardie <ted.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="f46d043892139242de04f520f539"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/ArxjB879m423Ub4c19J6MEfVvBA
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:10:30 -0000

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

v2.23.0 | Report a Bug | By Email