…am maps into an RTP session. The RTP RFC [ RFC1889 ] (at present obsoleted by [ RFC3550 ]) used to define an RTP session as follows: "For each participant, the session is defined by a particular pair of destination transport addresses (one network address plus a port pair for RTP…

…t self-delimiting. Instead, it assumes that a lower layer (such as UDP or RTP [ RFC3550 ] or Ogg [ RFC3533 ] or Matroska [ MATROSKA-WEBSITE ]) will communicate the length, in bytes, of the packet, and it uses this information to reduce the framing overhead in the packet itself. A…

… RTCP BYE for each RTP stream that was being sent by sender , as specified in [ RFC3550 ]. Stop receiving media with receiver Set the readyState of receiver 's [[ReceiverTrack]] to "ended" Set transceiver 's [[Stopped]] slot to true Set the [[ReadyState]] slot of each of connecti…

…s share a RTCDtlsTransport , this implies that they also share a single SSRC [[!RFC3550]] and header extension [[!RFC5285]] numbering space. The restrictions arising from this are described in [[!BUNDLE]] Sections 10.1 and 10.1.1. ORTC routing tables Since ORTC does not utilize R…

…t self-delimiting. Instead, it assumes that a lower layer (such as UDP or RTP [ RFC3550 ] or Ogg [ RFC3533 ] or Matroska [ MATROSKA-WEBSITE ]) will communicate the length, in bytes, of the packet, and it uses this information to reduce the framing overhead in the packet itself. A…

…ize RTCP [ RFC5506 ] is configured (if true) or compound RTCP as specified in [ RFC3550 ] (if false). Read-only parameter . 5.2.7 RTCRtpHeaderExtensionParameters Dictionary WebIDL dictionary RTCRtpHeaderExtensionParameters { required DOMString uri ; required unsigned short id ; b…

…ize RTCP [ RFC5506 ] is configured (if true) or compound RTCP as specified in [ RFC3550 ] (if false). Read-only parameter . 5.2.7 RTCRtpHeaderExtensionParameters Dictionary WebIDL dictionary RTCRtpHeaderExtensionParameters { required DOMString uri ; required unsigned short id ; b…

… al. Standards Track [Page 56] RFC 8445 ICE July 2018 Section 8.2 of RFC 3550 [ RFC3550 ] describes an algorithm for detecting synchronization source (SSRC) collisions and loops. These algorithms are based, in part, on seeing different source transport addresses with the same SSR…

…eived for this SSRC . This includes retransmissions. Calculated as defined in [ RFC3550 ] section 6.4.1. firCount of type unsigned long MUST NOT exist for audio. Count the total number of Full Intra Request (FIR) packets, as defined in [ RFC5104 ] section 4.3.1, sent by this rece…

…ptation. For such codecs, it is RECOMMENDED that the sender set the marker bit [RFC3550] when an agent switches transmission of media from one candidate pair to another. 11.2. Receiving Media ICE implementations MUST be prepared to receive media on each component on any candidate…

…ize RTCP [ RFC5506 ] is configured (if true) or compound RTCP as specified in [ RFC3550 ] (if false). Read-only parameter . 5.2.8 RTCRtpHeaderExtensionParameters Dictionary WebIDL dictionary RTCRtpHeaderExtensionParameters { required DOMString uri ; required unsigned short id ; b…

…tation. For such codecs, it is RECOMMENDED that the sender set the marker bit [ RFC3550 ] when an agent switches transmission of media from one candidate pair to another. 11.2 . Receiving Media ICE implementations MUST be prepared to receive media on each component on any candida…

…ize RTCP [ RFC5506 ] is configured (if true) or compound RTCP as specified in [ RFC3550 ] (if false). Read-only parameter . 5.2.7 RTCRtpHeaderExtensionParameters Dictionary WebIDL dictionary RTCRtpHeaderExtensionParameters { required DOMString uri ; required unsigned short id ; b…

…ize RTCP [[RFC5506]] is configured (if true) or compound RTCP as specified in [[RFC3550]] (if false). Read-only parameter . RTCRtpCodec Dictionary dictionary RTCRtpCodec { required DOMString mimeType; required unsigned long clockRate; unsigned short channels; DOMString sdpFmtpLin…

…tation. For such codecs, it is RECOMMENDED that the sender set the marker bit [ RFC3550 ] when an agent switches transmission of media from one candidate pair to another. 11.2 . Receiving Media ICE implementations MUST be prepared to receive media on each component on any candida…