… ¶ ▲ Table of Contents 1. Introduction The Real-time Transport Protocol (RTP) [ RFC3550 ] provides a framework for delivery of audio and video teleconferencing data and other real-time media applications. Previous work has defined the RTP protocol, along with numerous profiles, p…

… ¶ ▲ Table of Contents 1. Introduction The Real-time Transport Protocol (RTP) [ RFC3550 ] provides a framework for delivery of audio and video teleconferencing data and other real-time media applications. Previous work has defined the RTP protocol, along with numerous profiles, p…

…on The existing taxonomy of sources in the Real-time Transport Protocol (RTP) [ RFC3550 ] has previously been regarded as confusing and inconsistent. Consequently, a deep understanding of how the different terms relate to each other becomes a real challenge. Frequently cited exam…

…on The existing taxonomy of sources in the Real-time Transport Protocol (RTP) [ RFC3550 ] has previously been regarded as confusing and inconsistent. Consequently, a deep understanding of how the different terms relate to each other becomes a real challenge. Frequently cited exam…

… RFC 5506 Reduced-Size RTCP in RTP Profile April 2009 1 . Introduction In RTP [ RFC3550 ] it is currently mandatory to send RTP Control Protocol (RTCP) packets as compound packets containing at least a sender report (SR) or receiver report (RR), followed by a source description (…

… RFC 5506 Reduced-Size RTCP in RTP Profile April 2009 1 . Introduction In RTP [ RFC3550 ] it is currently mandatory to send RTP Control Protocol (RTCP) packets as compound packets containing at least a sender report (SR) or receiver report (RR), followed by a source description (…

… RFC 5506 Reduced-Size RTCP in RTP Profile April 2009 1 . Introduction In RTP [ RFC3550 ] it is currently mandatory to send RTP Control Protocol (RTCP) packets as compound packets containing at least a sender report (SR) or receiver report (RR), followed by a source description (…

…conferencing node or participant chooses to temporarily pause an incoming RTP [ RFC3550 stream and later resume it when needed. The receiver does not need to terminate or inactivate the RTP session and start all over again by negotiating the session parameters, for example, using…

…re for multi-party conferencing. Among others, the framework borrows from RTP [ RFC3550 ] and extends the concept of a mixer entity "responsible for combining the media streams that make up a conference, and generating one or more output streams that are delivered to recipients".…

…o be used in the Receiver Report "SSRC of packet sender" field as defined in [[!RFC3550]] Section 6.4.2. If unset, ssrc is chosen by the browser, and the chosen value is not reflected in RTCRtcpParameters.ssrc If the browser chooses the ssrc it may change it in event of a collisi…

…o be used in the Receiver Report "SSRC of packet sender" field as defined in [[!RFC3550]] Section 6.4.2. If unset, the SSRC is chosen by the browser. Note that the browser may change the SSRC in event of a collision, as described in [[!RFC3550]]. DOMString cname The Canonical Nam…

…o be used in the Receiver Report "SSRC of packet sender" field as defined in [[!RFC3550]] Section 6.4.2. If unset, ssrc is chosen by the browser, and the chosen value is not reflected in RTCRtcpParameters.ssrc If the browser chooses the ssrc it may change it in event of a collisi…

…ong ssrc The SSRC to be used in the "SSRC of packet sender" field defined in [[!RFC3550]] Section 6.4.2 (Receiver Report) and [[!RFC4585]] Section 6.1 (Feedback Messages), as well as the "SSRC" field defined in [[!RFC3611]] Section 2 (Extended Reports). This is only set for an RT…

…ong ssrc The SSRC to be used in the "SSRC of packet sender" field defined in [[!RFC3550]] Section 6.4.2 (Receiver Report) and [[!RFC4585]] Section 6.1 (Feedback Messages), as well as the "SSRC" field defined in [[!RFC3611]] Section 2 (Extended Reports). This is only set for an RT…

…ong ssrc The SSRC to be used in the "SSRC of packet sender" field defined in [[!RFC3550]] Section 6.4.2 (Receiver Report) and [[!RFC4585]] Section 6.1 (Feedback Messages), as well as the "SSRC" field defined in [[!RFC3611]] Section 2 (Extended Reports). This is only set for an RT…