- From: Iñaki Baz Castillo via GitHub <sysbot+gh@w3.org>
- Date: Thu, 21 Jun 2018 09:51:45 +0000
- To: public-webrtc-logs@w3.org
> ORTC mentions the direction here: http://draft.ortc.org/#rtcrtpheaderextensionparameters* but does not include a direction member either Such a `direction` attribute is not needed in ORTC `RTCRtpHeaderExtensionParameters` because those params are given to a sender or to a receiver, so the direction is implicit. But, probably the `direction` attribute should be present in the `RTCRtpHeaderExtension` dictionary (within the `RTCRtpCapabilities`) to tell the app whether a specific RTP header extension can be used for sending and/or receiving. -- GitHub Notification of comment by ibc Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1912#issuecomment-399044599 using your GitHub account
Received on Thursday, 21 June 2018 09:51:47 UTC