Re: [rtcweb] Transports: RFC 4941 support?

Justin Uberti <juberti@google.com> Thu, 20 March 2014 16:30 UTC

Return-Path: <juberti@google.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 A24C31A03BF for <rtcweb@ietfa.amsl.com>; Thu, 20 Mar 2014 09:30:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.925
X-Spam-Level:
X-Spam-Status: No, score=-1.925 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 8REbjcoeeY2O for <rtcweb@ietfa.amsl.com>; Thu, 20 Mar 2014 09:30:38 -0700 (PDT)
Received: from mail-vc0-x231.google.com (mail-vc0-x231.google.com [IPv6:2607:f8b0:400c:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id DD9BF1A0782 for <rtcweb@ietf.org>; Thu, 20 Mar 2014 09:30:37 -0700 (PDT)
Received: by mail-vc0-f177.google.com with SMTP id if17so1219165vcb.8 for <rtcweb@ietf.org>; Thu, 20 Mar 2014 09:30:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=rRRs3esRzkDZZ6+HpIG1HAfz2RqHsHJWjRUN+0ZDG8M=; b=WP/j9mMbs8/WWSRyLMyexIIyrPDdiY1LJ/5mdSEKYrOTaHbQijKFoLNkxK3HXZoS/f dy+IrgTck1RyAbv/6u69b+uxyJ94rzHJwj6gQ0NSvFa2WK0hwG85RnTOxYGpPnTYoQnf xL1HQVPQIB3/j2CUVVudNnMAsc9SC97AM8UmBhQxrLYLSrJGORFGzQ41Z7+pPCrJZfY+ g1+b26NJJuDlDUAoCxEIbuLkOTTnJDQRWX5T31okiXDLY+fejfhaWSiWoZsZKeXVv2wr DUvgmNoZFUJgkZeUkx8YAEtcwQg4r5MxLRMXhjm4MvOc2w67abnvabZwg5S1rJ27w0ye 6CEA==
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:from:date :message-id:subject:to:cc:content-type; bh=rRRs3esRzkDZZ6+HpIG1HAfz2RqHsHJWjRUN+0ZDG8M=; b=Ky/SzWpV35tSySc8Cl7GfppICeRahHoPuS7hArTTixkpEZw9T8FAuejTypVDw5m48D ZuQVSui6DW8R2L40M+/xNyppFBByhgtrinwSys6FMQ9yCzN7xSVys5869f/lj6/1iiv4 Rbv6BCKz5k0VEwmcjZ6VPptAkfyv+geds7kp0TF5SlV18hZKi4JuvZYP+D3wS15mmHhL 3cgg+KGPbblBJw/GSeGqnt22iDeRrhhmAWVG5ZPPnpYCBnX8un3yNYlEzR+vPPXJpil7 EdUYBty8VKiXB7qz5SptRj4pSFjzsFqyaNB92UgZumSpJIQTSiwCV9ZfE277wSO4bXq3 y8Uw==
X-Gm-Message-State: ALoCoQlacUI3Et3e7ZQKGnjzFPjxwl22QkvMUe7PTbKZ9Y6paoJdRsvDU4xBmMJgo8wn79szov4+GpGEqAewPfSi6OA6L+EO6jiYxumQjodf5OWMki5T38grkchAk5dxNkM1YLiubNtCy5cW59e43b+DYF4osnUCfTVO9IsUR/kxGZ2iFnSF04coJVF0x11ibnbO8I3yyRbS
X-Received: by 10.58.152.142 with SMTP id uy14mr2394712veb.4.1395333028677; Thu, 20 Mar 2014 09:30:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.26.43 with HTTP; Thu, 20 Mar 2014 09:30:08 -0700 (PDT)
In-Reply-To: <532B0E8F.3000002@viagenie.ca>
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> <532B0E8F.3000002@viagenie.ca>
From: Justin Uberti <juberti@google.com>
Date: Thu, 20 Mar 2014 09:30:08 -0700
Message-ID: <CAOJ7v-0b1VpavUUuRmnKCD1r0at61Ag7BKy3_d0Cw14h8kfWMA@mail.gmail.com>
To: Simon Perreault <simon.perreault@viagenie.ca>
Content-Type: multipart/alternative; boundary="089e0129421884a16104f50c499c"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/_CxAbGs0qCntND5k1BJGfcA-XT0
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: Thu, 20 Mar 2014 16:30:39 -0000

On Thu, Mar 20, 2014 at 8:51 AM, Simon Perreault <
simon.perreault@viagenie.ca> wrote:

> 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.
>
>
On Mac, the temporary addresses seem to change every day, but any existing
addresses seem to remain valid for a week.