RE: Getting rid of RTP from Bernard Aboba on 2018-03-05 (public-webrtc@w3.org from March 2018)

From: Bernard Aboba <Bernard.Aboba@microsoft.com>
Date: Mon, 5 Mar 2018 22:42:00 +0000
To: Iñaki Baz Castillo <ibc@aliax.net>
CC: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <CY1PR00MB013914998C970EA729AB88E6ECDA0@CY1PR00MB0139.namprd00.prod.outlook.com>

Inaki said: 

"I hope we can discuss about encoders/decoders without having to also mention QUIC."

[BA] Definitely. In ORTC, the RtpSender/RtpReceiver is distinct from the transport.  I think what is being suggested here is a more granular pipeline so as to be able to distinguish encoding from encapsulation and decoding from decapsulation.  Controlling transport(s) separately would remain. 

"ORTC can already handle forking, trickle ICE and TURN mobility."

[BA] Yes, but something like multi-path ICE would be trickier.  Not sure how we can guarantee that a design would be compatible with a version of ICE that doesn't yet exist though.

Received on Monday, 5 March 2018 22:42:25 UTC