Re: [rtcweb] Transports: RFC 4941 support?

Simon Perreault <simon.perreault@viagenie.ca> Thu, 20 March 2014 15:51 UTC

Return-Path: <simon.perreault@viagenie.ca>
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 712B01A076C for <rtcweb@ietfa.amsl.com>; Thu, 20 Mar 2014 08:51:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level:
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, 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 vjKx_QvWi3mp for <rtcweb@ietfa.amsl.com>; Thu, 20 Mar 2014 08:51:53 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 0B7001A0743 for <rtcweb@ietf.org>; Thu, 20 Mar 2014 08:51:53 -0700 (PDT)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:f981:e226:281f:c92d]) by jazz.viagenie.ca (Postfix) with ESMTPSA id E2BF6403B0; Thu, 20 Mar 2014 11:51:43 -0400 (EDT)
Message-ID: <532B0E8F.3000002@viagenie.ca>
Date: Thu, 20 Mar 2014 11:51:43 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
References: <CAOJ7v-0Hw0NFs_avsB2Z8do21BCws2LRZSeSh6HP0t455SPXyw@mail.gmail.com> <B6836FFA-867A-4CBF-9855-D265425EC5E1@cisco.com> <CAOqqYVE=i2L7FxGgKuV0DVaaxYOPnxzSEbDoq0_4Tqapna575g@mail.gmail.com> <5329BA17.7080701@viagenie.ca> <BA544098-72C9-42AD-B180-5F177D053DA5@cisco.com>
In-Reply-To: <BA544098-72C9-42AD-B180-5F177D053DA5@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/CbB6Wre8Ou8OyWoYwf_PlQHPYZY
Cc: 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: Thu, 20 Mar 2014 15:51:58 -0000

Le 2014-03-20 10:54, Dan Wing a écrit :
> 
> On Mar 19, 2014, at 8:39 AM, Simon Perreault <simon.perreault@viagenie.ca> wrote:
> 
>> Le 2014-03-19 03:02, Harald Alvestrand a écrit :
>>> I'd like to be silent on the issue, since which IPv6 addresses to prefer
>>> is likely to be a matter of system policy. Trying to override system
>>> policy in an application specific profile usually leads to sadness.
>>
>> What would be useful to mention IMHO is that ICE restart should be used
>> to gracefully handle the issue of IP address expiry, of which temporary
>> IPv6 addresses are a frequently-encountered example.
> 
> When a temporary address expires, existing sockets bound that address should continue working with that expired address -- have you found otherwise on any OS, such that we would need ICE Mobility for temporary address expiration?

When the address is removed from the interface, it doesn't matter if the
socket is still "good" or not. The address is no longer on the interface
so you will not receive packets sent to that address.

I'm looking at the Linux and OpenBSD IPv6 stacks right now and neither
seems to care about existing sockets before expiring an address. Haven't
tried it though.

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca