Re: FW: [rtcweb] How to signal RTX SSRCs with simulcast

Bo Burman <[email protected]>
Newsgroups gmane.ietf.mmusic
Message-ID <AM5PR0701MB257767A071B4BAE79A9DFE878D250@AM5PR0701MB2577.eurprd07.prod.outlook.com>
> -----Original Message-----
> From: Iñaki Baz Castillo [mailto:[email protected]]
> Sent: den 13 mars 2017 12:50
> 
> 2017-03-13 12:41 GMT+01:00 Bo Burman <[email protected]>:
> > Could you elaborate a bit to help me understand why that would be needed for FLEX-FEC when using
> RepairedRtpStreamId?
> 
> I just meant that, in case of option A above, FLEX-FEC would require the same as RTX (when RID is in use and ssrcs are
> therefore not signaled).
[BoB] OK

> 
> 
> > I guess that use of RtpStreamId or RepairedRtpStreamId on RTP level (in the RTP and RTCP packets) should not matter
> much, neither for FLEX-FEC nor RTX, as long as it is clearly defined what it means?
> 
> I'm not against it. It's just that this requires a new draft about RID and "complementary streams" (or include it into
> existing ones).
[BoB] Usage of RepairedRtpStreamId and RtpStreamId are already defined on RTP level by -avtext-rid. If we have preferences on how to best use them with redundancy RTP streams in general, I suggest we add text to -mmusic-rid about it. This would be regardless if we go for option A or B, but decided once and for all, thus applicable to RFC 4588 rtx and FLEX-FEC alike.

/Bo
(as individual)

> 
> 
> --
> Iñaki Baz Castillo
> <[email protected]>
_______________________________________________
mmusic mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/mmusic
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.