How to manage RTCRtpTransceivers for incoming MediaStreamTracks?

[mparis]

Hello,
when a remote MediaStreamTrack is processed, what happens if there is not any transceiver to manage it?

1. Should a new transceiver be created automatically?
2. Should the API have an event to notify the user if he wants to create a new transceiver to manage the incoming media? So:
   • if the user creates a new one, the media will be accepted (local SDP with "a=recvonly" or "a=sendrecv")
   • if the user does not create a new one, the media will be rejected (local SDP with: "a=sendonly" or "a=inactive")

From my point of view, this question is quite interesting in the case that an endpoint does not know how many tracks the remote endpoint will offer it.

In the current document, [1] only says that a new receiver has to be created.

Refs
[1] http://w3c.github.io/webrtc-pc/#processing-remote-mediastreamtracks

[taylor-b]

This may be the same as issue #563.

[alvestrand]

Duplicate of #563. Closing.