RE: Issue 223: Asymmetry between RTP and RTCP within the API

1. Currently the API draft does not state that RTP and RTCP IceGatherers need to have the same ufrag/password. Within SDP, this is a requirement since RTP/RTCP share the same m-line.  From the JSEP draft:

Each m= section MUST include the following attribute lines:

o "a=ice-ufrag" and "a=ice-pwd" lines, as specified in [RFC5245], Section 15.4.

So a proposal is to require that RTP and RTCP IceGatherers share the same RTCIceParameters and RTCIceGatherOptions?

Here is some proposed text for to Section 2.3.2:

"Create an associated RTCIceGatherer for RTCP, with the same RTCIceParameters and RTCIceGatherOptions as for the RTP RTCIceGatherer."

2. If createAssociatedGatherer() is called before createAssociatedTransport, then the RTCP IceTransport can be associated with the RTCP IceGatherer. Otherwise, the RTCP IceTransport and RTCP IceGatherer are not associated until rtcpIceTransport.start() is called and pruning of an RTCP IceGatherer cannot occur until rtpIceTransport.start() is called.  Not sure if this rises to the level of an exception (no harm done, just loss of optimization).

Received on Tuesday, 30 June 2015 17:55:04 UTC