You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I failed to find any text in webrtc-pc or JSEP which indicates that the createOffer() call should fail if no RtpTransceiver or data channel has been added to a PeerConnection.
Webrtc-pc contains the following:
If this inspection failed for any reason, reject p with a newly created OperationError and abort these steps.
But section 5.2.1. Initial Offers does not seem to contain any wording indicating to treat the absence of any RtpTransceiver and DataChannel as such an failure.
I think such a scenario should be treated as a failure, as I fail to see any value in generating an empty offer.
The text was updated successfully, but these errors were encountered:
Good observation. Personally, I'm inclined to allow this, unless it's forbidden by 3264 - we would just generate the session-level values with no m= sections.
The offer will contain zero or more media streams (each media stream
is described by an "m=" line and its associated attributes). Zero
media streams implies that the offerer wishes to communicate, but
that the streams for the session will be added at a later time
through a modified offer.
I think we should explicitly mention that this is allowed, but otherwise take no action.
I failed to find any text in webrtc-pc or JSEP which indicates that the createOffer() call should fail if no RtpTransceiver or data channel has been added to a PeerConnection.
Webrtc-pc contains the following:
But section
5.2.1. Initial Offers
does not seem to contain any wording indicating to treat the absence of any RtpTransceiver and DataChannel as such an failure.I think such a scenario should be treated as a failure, as I fail to see any value in generating an empty offer.
The text was updated successfully, but these errors were encountered: