W3C home > Mailing lists > Public > public-webrtc@w3.org > April 2015

Re: Mucking with SDP

From: Justin Uberti <juberti@google.com>
Date: Mon, 13 Apr 2015 18:48:00 -0700
Message-ID: <CAOJ7v-2JNVxo=p5kRjF8i+ifWgH81wV_CFpOOj4Nau3X=+oQUw@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
Cc: Harald Alvestrand <harald@alvestrand.no>, "public-webrtc@w3.org" <public-webrtc@w3.org>
FWIW, Chrome switched (in Chrome 42, IIRC) to never put a IPv6 into the c=
line when an IPv4 exists, due to problems like this.

Note that IPv6 gathering is only on for a subset of the Chrome population
at this time, which may explain some of the transient errors you are seeing.

On Tue, Apr 7, 2015 at 3:18 PM, Roman Shpount <roman@telurix.com> wrote:

> On Tue, Apr 7, 2015 at 5:16 PM, Harald Alvestrand <harald@alvestrand.no>
> wrote:
>
>>  On 04/07/2015 09:16 PM, Roman Shpount wrote:
>>
>> As a long time advocate of the need to make IPv6 universally deployed,
>> the idea that one should address interoperability issues by asking apps to
>> turn off IPv6 support makes me seriously sad.
>>
>
> Unfortunately we still deal with applications that either do not support
> IPv6. It would make sense to have a default to IPv6 and a constraint to
> turn this off, so that IPv6 use is encouraged, but can be disabled, if
> necessary.
>
>
>> I'd rather change the default in JSEP (but that's an IETF matter).
>>
>> Roman, can you raise that issue there?
>>
>>
> I will raise the issue in IETF.
> _____________
> Roman Shpount
>
>
>
Received on Tuesday, 14 April 2015 01:48:48 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:43 UTC