- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Thu, 04 Jan 2018 07:47:51 +0000
- To: public-webrtc-logs@w3.org
@fippo yes, that's a solution @aboba the difference between step 8 (replace track only) and step 10 (replace track and start sending from it) seems to be rather small; we could treat "not associated with SDP" as a special case of "negotiation not needed". For completely indepenedent operation, I suspect that we need RTPSender to have a complete representation of the allowable operation parameter envelope, and reject ReplaceTrack if the new track is not within the currently set operation parameter envelope. The initial envelope would then be "sender's maximal abilities", and the post-negotiation envelope would be "SDP-negotiated envelope". Bigger task to specify; ORTC does this as part of the send() function. Getting rid of one level of reference is good for now. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1712#issuecomment-355218522 using your GitHub account
Received on Thursday, 4 January 2018 07:47:54 UTC