Since the cost of sending RTCP is minimal (about one packet every 5 seconds), it makes sense to send RTCP even for point-to-point connections:

With RTCP, both sides know how well the other side is receiving audio and video; this is useful, since degraded quality can have any number of reasons beyond network loss, delay and jitter. A particular use is when calling TECHNICAL support: the tech support person can OBSERVE the network performance at the remote end.

• RTCP is necessary for synchronizing audio and video streams.
• For audio with silence suppression, RTCP is useful as a liveness INDICATION.
• The SDES information is useful for user interfaces.
• Many applications will (want to) support both unicast and multicast, so that the additional implementation complexity is zero.

Since the cost of sending RTCP is minimal (about one packet every 5 seconds), it makes sense to send RTCP even for point-to-point connections:

With RTCP, both sides know how well the other side is receiving audio and video; this is useful, since degraded quality can have any number of reasons beyond network loss, delay and jitter. A particular use is when calling technical support: the tech support person can observe the network performance at the remote end.