Re: [webrtc-pc] does rtcrtpheaderextensionparameters need a direction?

> ORTC mentions the direction here:*
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 using your GitHub account

Received on Thursday, 21 June 2018 09:51:47 UTC