W3C home > Mailing lists > Public > public-webrtc@w3.org > May 2018

Re: ICE freezing and Bandwidth Estimation

From: Harald Alvestrand <harald@alvestrand.no>
Date: Wed, 23 May 2018 21:11:32 +0200
To: public-webrtc@w3.org
Message-ID: <047bbaf0-1852-d830-f7dd-d909d58ff031@alvestrand.no>
On 05/23/2018 06:15 PM, Peter Thatcher wrote:
>     Q4:
>     While the WebRTC device may use different ICE agents for each
>     stream, the remote peer may not. Not sure how/if exactly that
>     would impact things, but it needs to be considered.
> That's already the case today if one side uses one PeerConnection and
> the other side uses multiple PeerConnections.  But given that almost
> all use of ICE is done with 1 components and one stream (because of
> BUNDLE), and it will probably continue to be thus, I think it's best
> to optimize for the overwhelming use case and not worry too much about
> bizarre scenarios people might setup.
Is there a successful example of one side using one PeerConnection and
the other side using multiple PeerConnections at the same time?
Offhand, I'd think that would be impossible in WebRTC 1.0, but if
there's running code out there, I guess I'm wrong.
Received on Wednesday, 23 May 2018 19:12:09 UTC

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