… parameters are defined for "h264", as noted in [[RFC6184]] Section 8.1, and [[!RFC7742]] Section 6.2. Property Name Values Receiver/Sender Notes profileLevelId unsigned long Receiver/Sender This parameter describes the maximum capability of the decoder (for an RTCRtpReceiver ) o…

… parameters are defined for "h264", as noted in [[RFC6184]] Section 8.1, and [[!RFC7742]] Section 6.2. Property Name Values Receiver/Sender Notes profileLevelId unsigned long Receiver/Sender This parameter describes the maximum capability of the decoder (for an RTCRtpReceiver ) o…

… parameters are defined for "h264", as noted in [[RFC6184]] Section 8.1, and [[!RFC7742]] Section 6.2. Property Name Values Receiver/Sender Notes profileLevelId DOMString Receiver/Sender This parameter is encoded as a string representation of 6 upper case hexadecimal digits, repr…

…ment video codecs and RTP payload formats for WebRTC endpoints are defined in [ RFC7742 ] . WebRTC endpoints MAY additionally implement any other codec for which an RTP payload format and associated signaling has been defined. ¶ WebRTC endpoints cannot assume that the other parti…

…ment video codecs and RTP payload formats for WebRTC endpoints are defined in [ RFC7742 ] . WebRTC endpoints MAY additionally implement any other codec for which an RTP payload format and associated signaling has been defined. ¶ WebRTC endpoints cannot assume that the other parti…

…de the mandatory audio/video codecs as specified in [RFC7874], Section 3 , and [RFC7742], Section 5 . The m= line MUST be followed immediately by a "c=" line, as specified in [RFC4566], Section 5.7 . Again, as no candidates are available yet, the "c=" line must contain the "dummy…

… parameters are defined for "h264", as noted in [[RFC6184]] Section 8.1, and [[!RFC7742]] Section 6.2. Property Name Values Receiver/Sender Notes profile-level-id DOMString Receiver/Sender This parameter is encoded as a string representation of 6 upper case hexadecimal digits, re…