title: RTP RFC (3550) interpretation question
body: <p>I'm doing <a href="http://github.com/brunodecarvalho/efflux" rel="nofollow noreferrer">a Java implementation</a> of <a href="https://www.rfc-editor.org/rfc/rfc3550" rel="nofollow noreferrer">RFC 3550 (RTP)</a> and I've ran into a little problem:</p>
  <p>In <a href="https://www.rfc-editor.org/rfc/rfc3550#section-11" rel="nofollow noreferrer">chapter 11</a>, paragraph 2, it states that:</p>
  <blockquote>
  <p>(...) A participant MUST NOT assume that the source port of the incoming RTP or RTCP packet can be used as the destination port for outgoing RTP or RTCP packets.  When RTP data packets are being sent in both directions, each participant's RTCP SR packets MUST be sent to the port that the other participant has specified for reception of RTCP. (...)</p>
  </blockquote>
  <p>RTP does not have any mechanism to inform of these addresses and ports (that's up to SDP or some other setup protocol), which would lead me to understand this paragraph as &quot;if you're receiving data from an unknown source, just discard it&quot;.</p>
  <p>But in <a href="https://www.rfc-editor.org/rfc/rfc3550#section-6.3.3" rel="nofollow noreferrer">section 6.3.3</a> it basically says that when an RTP or non-BYE RTCP packet is received with an unknown SSRC, a new participant should be added to the table.</p>
  <p>So to sum up:</p>
  <ol>
  <li>You should add a new participant when an unknown SSRC is received;</li>
  <li>You can't use the packet's source IP/port as the destination of packets for that participant;</li>
  <li>SDP doesn't define the SSRC that will be used by each of the RTP participants;</li>
  <li>You can manually add RTP participants (discovered in other ways) BUT you have no idea what the SSRC's will be.</li>
  </ol>
  <p>So the million dollar question is: just how is one supposed to handle unexpected SSRC's?</p>