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