…/AVP profile [ RFC3551 ] , the RTP profile for RTCP-based feedback (RTP/AVPF) [ RFC4585 ] , and the secure RTP profile (RTP/SAVP) [ RFC3711 ] . ¶ The RTCP-based feedback extensions [ RFC4585 ] are needed for the improved RTCP timer model. This allows more flexible transmission of…

…/AVP profile [ RFC3551 ] , the RTP profile for RTCP-based feedback (RTP/AVPF) [ RFC4585 ] , and the secure RTP profile (RTP/SAVP) [ RFC3711 ] . ¶ The RTCP-based feedback extensions [ RFC4585 ] are needed for the improved RTCP timer model. This allows more flexible transmission of…

…oes result in the minimal RTCP packets being quite large. The RTP/AVPF profile [RFC4585] specifies new RTCP packet types for feedback messages. Some of these feedback messages would benefit from being transmitted with minimal delay. AVPF provides some mechanisms to support this; …

…es result in the minimal RTCP packets being quite large. The RTP/AVPF profile [ RFC4585 ] specifies new RTCP packet types for feedback messages. Some of these feedback messages would benefit from being transmitted with minimal delay. AVPF provides some mechanisms to support this;…

…es result in the minimal RTCP packets being quite large. The RTP/AVPF profile [ RFC4585 ] specifies new RTCP packet types for feedback messages. Some of these feedback messages would benefit from being transmitted with minimal delay. AVPF provides some mechanisms to support this;…

…es result in the minimal RTCP packets being quite large. The RTP/AVPF profile [ RFC4585 ] specifies new RTCP packet types for feedback messages. Some of these feedback messages would benefit from being transmitted with minimal delay. AVPF provides some mechanisms to support this;…

…le for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)" [ RFC4585 ] appears appropriate. No currently existing RTCP feedback message explicitly supports pausing and resuming an incoming RTP stream. As this affects the generation of packets and may even allow…

…d whose U and V (chrominance) dimensions are 8x8 pixels. Two definitions from [ RFC4585 ] are also used in this document. RPSI: Reference picture selection index. A feedback message to let the encoder know that the decoder has correctly decoded a certain frame. SLI: Slice loss in…

…nsport-layer FB message) or PSFB (payload-specific FB message), as defined in [ RFC4585 ] , it will contain a media source SSRC, and this SSRC is used for routing certain subtypes of feedback messages. However, several subtypes of PSFB and RTPFB messages include a target SSRC(s) …

…. Capabilities rtcpFeedback Supported RTCP capabilities, such as "nack" from [[!RFC4585]]. dictionary RTCRtpCodec DOMString name="" The MIME media type, if set, empty string otherwise. unsigned int? hzRate=null Codec clock rate expressed in Hertz, null if unset. unsigned byte pre…

…d: * "RTP/AVP" (Defined in [RFC4566], Section 8.2.2 ) * "RTP/AVPF" (Defined in [RFC4585], Section 9 ) * "RTP/SAVP" (Defined in [RFC3711], Section 12 ) * "RTP/SAVPF" (Defined in [RFC5124], Section 6 ) * "TCP/DTLS/RTP/SAVP" (Defined in [RFC7850], Section 3.4 ) * "TCP/DTLS/RTP/SAVPF…

…ated in [[RFC4587]]. unsigned long pliCount Count of PLI packets, defined in [[!RFC4585]] Section 6.3.1. unsigned long nackCount Count of NACK packets, defined in [[!RFC4585]] Section 6.2.1. unsigned long sliCount Count of SLI packets, defined in [[!RFC4585]] Section 6.3.2. RTCIn…

…ated in [[RFC4587]]. unsigned long pliCount Count of PLI packets, defined in [[!RFC4585]] Section 6.3.1. unsigned long nackCount Count of NACK packets, defined in [[!RFC4585]] Section 6.2.1. unsigned long sliCount Count of SLI packets, defined in [[!RFC4585]] Section 6.3.2. RTCIn…

…15]] ("sli", "rpsi", etc.). For the Generic NACK feedback message defined in [[!RFC4585]] Section 6.2.1, the type attribute is set to "nack" and the parameter attribute is unset. For a type value of "ccm", valid values for parameter are the "Codec Control Messages" enumerated in …

…15]] ("sli", "rpsi", etc.). For the Generic NACK feedback message defined in [[!RFC4585]] Section 6.2.1, the type attribute is set to "nack" and the parameter attribute is unset. For a type of "ccm", valid values for parameter are the "Codec Control Messages" enumerated in [[!IAN…