onerror in RTCRtpReceiver and RTCRtpSender objects

[aboba]

From: Anniruddh Koppal (Persistent Systems Ltd.) v-ankopp@microsoft.com
Date: Fri, 23 May 2014 10:28:16 +0000
To: "public-ortc@w3.org" public-ortc@w3.org
URL: http://lists.w3.org/Archives/Public/public-ortc/2014May/0131.html

onerror eventhandler needs to be added to RTCRtpSender/RTCRtpReceiver objects.

[aboba]

A potential resolution to this is to add onerror eventhandlers to the sender and receiver objects.

[aboba]

From Shijun Sun: not clear when the “error” event should be fired on the RtpSender and RtpReceiver.

[aboba]

Proposed resolution: Since we don't have a use case, take it out.

[aboba]

This probably will require implementation feedback. For example, some issues with RTCRtpParameters might not be addressable via exceptions.

[aboba]

One potential use for onerror is to handle issues with RTCRtpParameters that don't result in an Exception being thrown.

[aboba]

Add the following to the onerror description in the sender and receiver objects:

" This event MUST be fired if an issue is found with the RTCRtpParameters object passed to
send/receive that is not immediately detected."