Editing RTP Control Protocol (section)

== Protocol functions ==
Typically RTP will be sent on an even-numbered [[User Datagram Protocol|UDP]] port, with RTCP messages being sent over the next higher odd-numbered port.{{Ref RFC|3605}}

RTCP itself does not provide any flow encryption or authentication methods. Such mechanisms may be implemented, for example, with the [[Secure Real-time Transport Protocol]] (SRTP){{Ref RFC|3711}}

RTCP provides basic functions expected to be implemented in all RTP sessions:
*The primary function of RTCP is to gather statistics on quality aspects of the media distribution during a session and transmit this data to the session media source and other session participants. Such information may be used by the source for adaptive media encoding ([[codec]]) and detection of transmission faults. If the session is carried over a multicast network, this permits non-intrusive session quality monitoring.
*RTCP provides canonical end-point identifiers (CNAME) to all session participants. Although a source identifier (SSRC) of an RTP stream is expected to be unique, the instantaneous binding of source identifiers to end-points may change during a session. The CNAME establishes unique identification of end-points across an application instance (multiple use of media tools) and for third-party monitoring.
*Provisioning of session control functions. RTCP is a convenient means to reach all session participants, whereas RTP itself is not. RTP is only transmitted by a media source.

RTCP reports are expected to be sent by all participants, even in a multicast session which may involve thousands of recipients. Such traffic will increase proportionally with the number of participants. Thus, to avoid network congestion, the protocol must include session bandwidth management. This is achieved by dynamically controlling the frequency of report transmissions. RTCP bandwidth usage should generally not exceed 5% of the total session bandwidth. Furthermore, 25% of the RTCP bandwidth should be reserved to media sources at all times, so that in large conferences new participants can receive the CNAME identifiers of the senders without excessive delay.

The RTCP reporting interval is randomized to prevent unintended synchronization of reporting. The recommended minimum RTCP report interval per station is 5 seconds. Stations should not transmit RTCP reports more often than once every 5 seconds.