This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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).
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.
Overtaken by events (Plan A).