21878 2013-04-30 17:14:39 +0000 Unable to learn of unknown inbound media 2014-10-31 16:25:57 +0000 1 1 1 Unclassified WebRTC Working Group WebRTC API unspecified All All RESOLVED FIXED P2 normal --- 1 martin.thomson public-webrtc harald public-webrtc renzoe1r oldest_to_newest 87015 0 martin.thomson 2013-04-30 17:14:39 +0000 Bug #21877 notes that there are situations where media can arrive unannounced. In that case, the media arrives prior to an answer and there is an expectation that ultimately the inbound media will be dealt with. However, it's possible that packets could arrive that the browser did not offer to receive. Media with unexpected SSRC or packet types such that identification of a correct MediaStreamTrack is not possible. For diagnostic purposes, it is helpful to inform an application of this media because it is often a result of misconfiguration or programming error. Surfacing this information is highly valuable, especially when applications are forced to create or manipulate SDP in order to get things to work. CU-RTC-Web defines an event for unknown media (see also #21877). This turns out to be a valuable tool. There is also a potential need to identify other unannounced noise (SCTP associations or DTLS handshakes). 114170 1 harald 2014-10-28 19:00:40 +0000 draft-ietf-mmusic-msid suggests creating an "unknown" track for these kinds of streams. Would that be an adequate solution to the problem? This is also affected by the switch from AddStream to AddTrack; these new tracks would presumably be stream-less. 114340 2 harald 2014-10-31 16:25:57 +0000 Overtaken by events (Plan A).