This describes the list of problems with the current farsight 2 API in git.
- Should we declare the stream to be in connecting state if the RTP component is connected, but RTCP is still connecting, what if one of the components gets disconnected?
- No way to reset the remote candidates while keeping the same local ones (for ICE restarts, example case is SIP forking where the same offer to sent to multiple recipients, but only one is accepted) (done in nice branch.. well by doing set_remote_candidates(,NULL,))
- Possible race: One has a session with one stream... one creates a new stream.. then packet in the new stream come in (with the new stream's cname) before the "src-pad-added" signal is connected... ie doesn't link... failure ensues..