RE: A proposal for solving non-muxed RTCP *and* ICE freezing

Peter said:

“But where does that number actually get used anywhere?”

[BA] The only place RTCIceComponent is currently used in the API is:

partial interface RTCIceTransport {
RTCIceTransport createAssociatedTransport (RTCIceComponent component);
}

However, since any component value other than “RTCP” is invalid, I am wondering if the component argument is really needed here.

Peter said:

“But the IceTransport already knows which component it is, so the it's unnecessary and even confusing.”

[BA] Indeed, the component of an RTCIceTransport object is determined by how it was constructed, and the application can keep track of this.  However, I did wonder if it would be useful to make this explicit via an attribute:

  partial interface RTCIceTransport {
       readonly attribute RTCIceComponent component;
   }

Peter said:

“​What would the RtpListener do with RTCP?”

[BA]  If the onunhandledrtp EventHandler is only called because of unhandled RTP packets, then nothing.  I guess there is no need to worry about receipt of RTCP Sender Reports from an unknown SSRC; these wouldn’t contain a Payload Type anyway.