- From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
- Date: Tue, 21 Oct 2014 20:42:57 +0200
- To: Peter Thatcher <pthatcher@google.com>
- CC: "public-ortc@w3.org" <public-ortc@w3.org>
Received on Tuesday, 21 October 2014 18:43:24 UTC
On 21/10/2014 19:51, Peter Thatcher wrote: > > > On Tue, Oct 21, 2014 at 1:15 AM, Sergio Garcia Murillo > <sergio.garcia.murillo@gmail.com > <mailto:sergio.garcia.murillo@gmail.com>> wrote: > > Hi Peter, > > Re. Session-Multiplexing support on ORTC. I am perfeclty fine, and > I think that makes sense, but on RTP-USAGE draft it says : > > Receivers are REQUIRED to implement support for RTP retransmission > packets [RFC4588 <https://tools.ietf.org/html/rfc4588>]. > > > So either we ask webrtc to narrow that requirement to support > ssrc-mutliplexing only, or we should explicitly state in the ORTC > draft that we doesn't support session multiplexing. > > > Does that phrase mean there must be a way to send RTX, or there must > be all possible ways to send RTX? It seems a bit ambiguous to me. By > the way, I'm pretty sure none of the current WebRTC implementations > support session-multiplexing RTX right now (I'm sure Chrome doesn't > support it). > For me it reads that a receiver shall implement both session and ssrc multiplexing. I agree that session multiplexing RTX is useless in our context, so we should try to remove it from the spec. Best regards Sergio
Received on Tuesday, 21 October 2014 18:43:24 UTC