W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > July 2017

Re: [webrtc-pc] Direction of newly created transceiver in setRemoteDescription

From: Soares Chen via GitHub <sysbot+gh@w3.org>
Date: Wed, 12 Jul 2017 03:06:54 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-314631840-1499828812-sysbot+gh@w3.org>
Hmm my interpretation for JSEP is that if there is no suitable transceiver exist, the newly created transceiver has `recvonly` direction regardless of direction specified in the m= section. 

For example in a fresh state, `setRemoteDescription(offer)` with one m= section with direction `recvonly` (meaning `sendonly` for the local peer right?), it still result in creating a transceiver with direction `recvonly`. The same applies to m= sections with `inactive` direction.

If JSEP is correct then step 2.2.8. in section 4.4.1.6. of webrtc-pc is inconsistent with it, because it simply creates new transceiver with direction reversed from what's specified in the m= section.

-- 
GitHub Notification of comment by soareschen
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1473#issuecomment-314631840 using your GitHub account
Received on Wednesday, 12 July 2017 03:06:59 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:21:40 UTC