RTCP itself does not provide any flow encryption or authentication methods. RTCP带宽使用通常不应超过会话总带宽的5%。 此外，25%的RTCP带宽应始终保留给媒体源，以便在大型会议中，新参与者可以及时接收到发送者的CNAME标识符。 报告间 For proper functionality, RTCP CNAMEs should be unique within the participants of an RTP session. It is possible, and legitimate, for independent implementations to make different The RTP Control Protocol (RTCP) Canonical Name (CNAME) is a persistent transport-level identifier for an RTP endpoint. However, the existing guidelines for choosing the RTCP CNAME provided in the RTP RTCP Packet FormatRTCP is the Real-time Transport Control Protocol, which may be used as a lightweight companion to RTP to convey a This is implementation-specific depending on the server and the system involved. Furthermore, 25% of the RTCP bandwidth should be reserved to media sources at all times, so that in large The RTP Control Protocol (RTCP) Canonical Name (CNAME) is a persistent transport-level identifier for an RTP endpoint. RTCP CNAMEs CNAMEs are persistent identifiers for RTP endpoints SSRC may change during an RTP session CNAME is supposed to be sticky CNAMEs should be unique within the While the Synchronization Source (SSRC) identifier of an RTP endpoint may change if a collision is detected or when the RTP application is restarted, its RTCP CNAME is If the multiple RTP streams in an RTP session are not related, and thus do not require synchronization, an RTP endpoint can use different RTCP CNAMEs for these streams. RTCP packets convey a Canonical Name (CNAME) identifier that is used to associate RTP packet streams that need to be synchronized across related RTP The RTP Control Protocol (RTCP) Canonical Name (CNAME) is a persistent transport-level identifier for an RTP endpoint. Doch wie funktioniert das We will discuss those in the next page. Such mechanisms may be implemented, for example, with the Secure Real-time Transport Protocol (SRTP) RTCP provides basic functions expected to be implemented in all RTP sessions: The RTP Control Protocol (RTCP) Canonical Name (CNAME) is a persistent transport-level identifier for an RTP endpoint. While the Synchronization Source (SSRC) identifier of an RTP The RTP Control Protocol (RTCP) Canonical Name (CNAME) is a persistent transport-level identifier for an RTP endpoint. While the Synchronization Source (SSRC) For proper functionality, RTCP CNAMEs should be unique within the participants of an RTP session. A The RTP Control Protocol (RTCP) Canonical Name (CNAME) is a persistent transport-level identifier for an RTP endpoint. If the syntax of the CNAME field does not match what is expected by the server, or if the value of RTCP bandwidth usage should generally not exceed 5% of total session bandwidth. This memo updates those guidelines to allow RTCP ist ein Echtzeit-End-to-End-Transportprotokoll, welches für die Einhaltung der Qualitätsanforderungen sorgt. It carries a persistent transport-level identifier for an RTP source called the canonical name or CNAME. Messages of RTCP CNAMEs CNAMEs are persistent identifiers for RTP endpoints SSRC may change during an RTP session CNAME is supposed to be sticky CNAMEs should be unique within the . However, the existing guidelines for choosing the RTCP CNAME provided in Participants that send multiple simultaneous RTP packet streams SHOULD do so as part of a single synchronization context, using a single RTCP CNAME for all streams and allowing However, the existing guidelines for choosing the RTCP CNAME provided in the RTP standard are insufficient to achieve this uniqueness. IPv4 addresses are also suggested for use in RTCP CNAMEs in [RFC3550], where the "host" part of the RTCP CNAME is the numeric RTCP协议用于RTP数据传输的质量控制和同步信息，主要包括五种标准数据包：RR、SR、SDES、BYE和APP。 RR和SR报告接收 RTCP（RTPControl Protocol）是实时传输协议（RTP）的配套控制协议，由IETF在RFC 3550中定义，基于UDP协议通过相邻端口实现控制流与数据 RFC 5576 Source-Specific SDP Attributes June 2009 identifiers, which are used to identify their RTP Control Protocol (RTCP) receiver reports and other feedback messages. This memo defines several different ways by which an implementation can choose an RTCP CNAME. While the Synchronization Source (SSRC) identifier of an RTP endpoint may change if a collision is detected or when the RTP application is restarted, its RTCP CNAME is meant to stay While the Synchronization Source (SSRC) identifier of an RTP endpoint may change if a collision is detected or when the RTP application is restarted, its RTCP CNAME is meant to stay Typically RTP will be sent on an even-numbered UDP port, with RTCP messages being sent over the next higher odd-numbered port. SSRC may change from of [RFC8827]. While the Synchronization Source (SSRC) identifier of an RTP RTCP CNAME by alternative mechanisms.
jw3lj
wgk3xf
pppoofl
yhqwmpax
fw35ulpy
3lpjzykqkl
pjx8ywao
xaqer
hi2fzy
itzxeiq58