Re: [rtcweb] Constraint to disable IPv6 candidate collection

[Adam Roach <[e-mail]>]

On 4/7/15 17:28, Roman Shpount wrote:
> It is possible to run into interop issues with end-points that support 
> ICE and DTLS-SRTP but do not support IPv6, such as current versions of 
> Firefox. ... [I propose we] define a constraint that can be used to 
> suppress IPv6 candidate collection, which can be provided via current 
> constraint interfaces.

While full support of IPv6 in our ICE stack is going to require a 
significant amount of development work, I think it's a flaw if Firefox 
doesn't at least parse IPv6 candidates and recognize them as something 
it can't (currently) use. Just to make sure that we're not getting our 
wires crossed here: the JSEP stack was completely revamped in Firefox 37 
(which is the most recent released version). If you find that IPv6 
candidates are tripping Firefox 37 up, we should get a bug filed on that 
and fix it.

So, if that's the case, please report it at 
https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=WebRTC%3A%20Networking 
-- or, if you'd prefer, send me an example of SDP and/or candidates that 
cause issues, and I'll file the bug myself.

But I don't think we need to make spec changes to work around 
implementation flaws. Any mishandling by Firefox is a temporary 
condition, and the spec will be around for a long time.

/a