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

Re: WebRTC NV Use Cases

From: Bernard Aboba <Bernard.Aboba@microsoft.com>
Date: Mon, 14 May 2018 23:16:03 +0000
To: Peter Thatcher <pthatcher@google.com>
CC: Roman Shpount <roman@telurix.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <B93643D7-EC2E-485A-B5B4-0276829FE466@microsoft.com> 
On May 14, 2018, at 6:19 PM, Peter Thatcher <pthatcher@google.com<mailto:pthatcher@google.com>> wrote:

2. Redundant data path

Client maintains two data paths to the remote party, one direct p2p and another with lower bandwidth through a different network path like a TURN server. If p2p connection fails or experiences packet loss, media is recovered using packets received over the alternative media path.


You're talking about two different things:

- graceful switching
- multipath

One is harder than the other.  Which one do you want more?  Or do you just want both?

[BA] Graceful switching can be provided via TURN mobility [RFC8016]. AFAIK this does not require any API changes (it is supported already in ORTC lib and its WebRTC 1.0 shim).
Received on Monday, 14 May 2018 23:16:32 UTC

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