W3C home > Mailing lists > Public > public-webrtc@w3.org > August 2016

[webrtc-pc] Figure out backward-compatible way to indicate ufrag+mid on end-of-candidates

From: Justin Uberti via GitHub <sysbot+gh@w3.org>
Date: Tue, 23 Aug 2016 21:19:59 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-172809594-1471987196-sysbot+gh@w3.org>
juberti has just created a new issue for 
https://github.com/w3c/webrtc-pc:

== Figure out backward-compatible way to indicate ufrag+mid on 
end-of-candidates ==
Split off of https://github.com/w3c/webrtc-pc/issues/726.

Want to indicate end-of-candidates for each mid, as well as a ufrag 
indicator in both these and the global mid.

Problem is that surfacing an object of type { ufrag, mid, null } may 
cause some apps to explode since they expect a real candidate. So we 
need a way to ensure these things are ignored by old apps.

Some proposed options:
1) RTCConfiguration option to turn these on, off by default. [+ clean 
API, - off by default]
2) New event for end-of-candidates (separate from onicecandidate and 
onicegatheringstatechange) (+ clean API, - new API, - more work for 
client)
3) Fake candidates (e.g. ufrag, mid, "candidate: 0 0.0.0.0 0 type 
blah" ) (+ no new APIs, - ugly, might still break some things)
4) Ufrag decoration on null candidate event (+ no new APIs, - doesn't 
work for mid, - ufrag in different places for candidate and e-o-c)

Please view or discuss this issue at 
https://github.com/w3c/webrtc-pc/issues/760 using your GitHub account
Received on Tuesday, 23 August 2016 21:20:07 UTC

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