- From: Michał Śledź via GitHub <sysbot+gh@w3.org>
- Date: Tue, 02 Jan 2024 08:18:47 +0000
- To: public-webrtc-logs@w3.org
Assuming the following labels: ``` tr_direction - transceiver's direction local_mline_direction - transceiver's direction in current local description remote_mline_direction - transceiver's direction in current remote description ``` What is the algorithm when current local description is of type "answer"? I understand this >If description is of type "[answer](https://www.w3.org/TR/webrtc/#dom-rtcsdptype-answer)", and the direction of the [associated](https://www.w3.org/TR/webrtc/#dfn-associated) m= section in the description does not match transceiver.[[[Direction]]](https://www.w3.org/TR/webrtc/#dfn-direction) intersected with the offered direction (as described in [[RFC8829](https://www.w3.org/TR/webrtc/#bib-rfc8829)] ([section 5.3.1.](https://datatracker.ietf.org/doc/html/rfc8829#section-5.3.1))), return true. where "description is described as: >Let description be connection.[[[CurrentLocalDescription]]](https://www.w3.org/TR/webrtc/#dfn-currentlocaldescription). as: 1. Calculate intersection of tr_direction and remote_mline_direction and save the result as "x" 2. Return x == local_mline_direction while the reasoning you described sounds like 1. Calculate intersection of tr_direction and local_mline_direction and save the results as "x" 2. Return x == tr_direction -- GitHub Notification of comment by mickel8 Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2919#issuecomment-1873722763 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 2 January 2024 08:18:49 UTC