Re: Some ideas on SVC support in WebRTC 1.0 (Take 2)

But ORTC.

El mié., 11 jul. 2018 19:00, Bernard Aboba <Bernard.Aboba@microsoft.com>
escribió:

> Harald said:
>
> "> The problem of having each SVC layer defined in a
> > RTCRtpEncodingParameters entry (within encodings array) is that all
> > those entries belonging to the same stream must share LOT of fields
> > (such as pt, ssrc, etc). Super error prune IMHO.
> >
>
> RTCRtpEncodingParameters doesn't contain either pt or ssrc. Perhaps it
> should have for the simulcast case (didn't we have an issue on that?),
> but at present it doesn't.
>
> These would be read-only, I think, so the only source of error is the
> browser, not the user's app."
>
> [BA] Right.
>
> We removed PT and SSRC from RTCRtpEncodingParameters as well as RTCRtpRtxParameters and RTCRtpFecParameters because we did not expect WebRTC 1.0 browser applications (as opposed to SDP-consuming servers) to use this (read-only) information.
>
> BTW, it does not appear necessary to reintroduce those parameters to support SVC, assuming we only support SRST codecs.
>
>
> "
>
>