From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] Fwd: Re: Issue 1406 in webrtc: Add IPv6 support to PeerConnection
Date: Wed, 12 Mar 2014 20:01:22 +0000 [thread overview]
Message-ID: <CAA93jw7QXWeS45-njoxG9zVcjNy3cOCW6Qqqe81joc0J6QvuqA@mail.gmail.com> (raw)
In-Reply-To: <25-3113897297558728724-1347626444567971425-webrtc=googlecode.com@googlecode.com>
[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]
It looks like chrome has finally gained ipv6 support for webrtc.
---------- Forwarded message ----------
From: <webrtc@googlecode.com>
Date: Mar 12, 2014 10:36 AM
Subject: Re: Issue 1406 in webrtc: Add IPv6 support to PeerConnection
To: <dave.taht@gmail.com>
Cc:
> Updates:
> Owner: mallinath@webrtc.org
> Labels: -Mstone-34 Mstone-35
>
> Comment #25 on issue 1406 by juberti@webrtc.org: Add IPv6 support to
PeerConnection
> http://code.google.com/p/webrtc/issues/detail?id=1406
>
> Chrome 34 and later allow IPv6 to be enabled by passing the googIPv6:true
constraint to the PeerConnection constructor. I'll update the
ice-servers.html demo to include this soon.
>
> Please give us feedback on this feature. Once we are confident this works
well, we will turn it on by default.
>
>
> --
> You received this message because you starred the issue.
> You may adjust your notification preferences at:
> https://code.google.com/hosting/settings
>
> Reply to this email to add a comment.
[-- Attachment #2: Type: text/html, Size: 1540 bytes --]
parent reply other threads:[~2014-03-12 20:01 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <25-3113897297558728724-1347626444567971425-webrtc=googlecode.com@googlecode.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw7QXWeS45-njoxG9zVcjNy3cOCW6Qqqe81joc0J6QvuqA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox