W3C home > Mailing lists > Public > public-webrtc@w3.org > January 2020

(no subject)

From: Harald Alvestrand <harald@alvestrand.no>
Date: Tue, 14 Jan 2020 09:02:09 +0100
To: public-webrtc@w3.org
Message-ID: <97843934-4ca8-6a2f-53f6-39d219a72434@alvestrand.no>

On 1/13/20 10:19 PM, Bernard Aboba wrote:
> *Depending on the direction, we could potentially be looking at header 
> extensions that would be sent and received, only sent or only received 
> (inactive header extensions aren't included in the SDP).   So if we 
> were to do this at the sender/receiver level, we would need two APIs, 
> RTCRtpSender.setOfferedRtpHeaderExtensions() and 
> RTCRtpReceiver.setOfferedRtpHeaderExtensions().  This would remove the 
> need for a direction attribute (which could be determined based on the 
> header extensions configured for the sender and receiver).  But it 
> would require applications to make two API calls instead of one.
> *

 From a model standpoint, I also don't want to have API on 
sender/receiver that would go away if we used something other than SDP 
to do negotiation.
Received on Tuesday, 14 January 2020 08:02:16 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:18:51 UTC