Transport, multiplexing and cross-layer requirements (RFC 7983, RFC 9443, RFC 8835, RFC 8837, RFC 8842, RFC 8261)

View Source
IDSpecRequirementModuleTestStatus
TR-17983 §7, 9443 §3Demultiplex by first byte: STUN 0-3, DTLS 20-63, TURN ChannelData 64-79, RTP/RTCP 128-191, others droppedwebrtc_demuxwebrtc_demux_testsUnit tested
TR-28835 §3.4STUN, DTLS, SRTP and SCTP share one UDP 5-tuple per BUNDLE groupwebrtc_transportwebrtc_pc_SUITE, webrtc_pc_interop_SUITEInteroperability tested
TR-38445 §12.2, 8826 §4.2Media and DTLS only accepted from validated candidate pairs, direct or relayed through TURNwebrtc_transportwebrtc_security_SUITE:spoofed_traffic_dropped, webrtc_turn_interop_SUITE:relayed_spoofing_droppedInteroperability tested
TR-47675No data sent without fresh consentwebrtc_ice_agent, webrtc_transportwebrtc_ice_net_tests (consent loss)Unit tested
TR-58842 §4DTLS association kept across ICE restartswebrtc_transport, webrtc_pcwebrtc_pc_SUITE:ice_restartE2E tested
TR-68842 §5DTLS role from a=setup, client starts the handshake once ICE has a pair, early DTLS datagrams buffered (bounded)webrtc_transportwebrtc_pc_SUITE, interop suitesInteroperability tested
TR-75764 §4.2SRTP keys exported from DTLS for the negotiated profile and rolewebrtc_transport, webrtc_srtpwebrtc_pc_SUITE:audio_video_rtp, webrtc_pc_interop_SUITE media casesInteroperability tested
TR-88261 §5SCTP packets fit in one DTLS record within a 1200 byte datagramwebrtc_transportwebrtc_impairment_SUITE:path_mtu_1200E2E tested
TR-98261 §6.1SCTP started over DTLS application data once DTLS is connectedwebrtc_transportwebrtc_pc_SUITEInteroperability tested
TR-10Bounded reception: active-N sockets, bounded early buffers, bounded SCTP bufferswebrtc_transportwebrtc_security_SUITE:garbage_flood, unauthenticated_stun_floodE2E tested
TR-11Independent peer connections, no shared state on the packet pathwebrtc_pc_sup, webrtc_transportwebrtc_pc_SUITE:concurrent_peer_connectionsE2E tested
TR-128835 §3.2ICE-TCP and TURN over TCP/TLSwebrtc_transport_net, webrtc_ice_tcp, webrtc_ice_relaysee the RFC 6544 table of ice.md and TURN-32Interoperability tested
TR-138835 §3.5HTTP proxy traversalNot implemented
TR-148421Multihomed and dual stack host candidateswebrtc_transport, webrtc_ice_candidatewebrtc_ice_net_testsUnit tested
TR-15A transport never outlives its peer connection: it monitors it, and close kills a transport that does not stop within 5 s (sockets, timers and TURN state released)webrtc_pc, webrtc_transportwebrtc_security_SUITE:stuck_transport_killed_on_closeE2E tested
TR-165246 §7.2.1, 7675After DTLS close or failure the transport is finished: SRTP keys and SCTP dropped, ICE closed (no consent checks, TURN deleted), media and data calls return {error, closed}webrtc_transportwebrtc_security_SUITE:nothing_sent_after_peer_closeE2E tested
TR-17The API keeps no state in the calling process: transports are found in the webrtc_transports table owned by the application supervisor, rows removed when a transport stops; calls on a closed connection return {error, closed}webrtc, webrtc_pc, webrtc_supwebrtc_security_SUITE:no_state_in_callerE2E tested
TR-188445 §12.1DTLS starts on the first valid pair instead of waiting for nomination; the connection is up about one checklist interval sooner (direct) or one nomination timeout sooner (when higher priority pairs never answer)webrtc_transportwebrtc_turn_interop_SUITE:one_side_relayed, webrtc_pc_SUITEInteroperability tested
TR-196347 §4.2.4, 9147 §5.8A DTLS datagram produced before ICE can send it (the peer's check validated the path for incoming data first) is kept, at most 16, and sent once a pair is valid: a server never retransmits on its own, so a dropped reply would wait for the client's next retransmissionwebrtc_transportwebrtc_turn_interop_SUITE:one_side_relayedInteroperability tested
TR-208835 §4.2, 8837 §5Packets marked by flow type and application priority (Table 1): audio LE/DF/EF, interactive video LE/DF/AF42-43/AF41-42, data LE/DF/AF11/AF21; priority per transceiver and per simulcast encoding, DF at the default lowwebrtc_dscp, webrtc_media_outwebrtcdscp_tests:table_test, webrtc_pc_SUITE:dscp_markingE2E tested
TR-218837 §5Within a cell, the lower drop precedence for the more important packets: those of a key frame; FEC, padding and the rest of the flow the higherwebrtc_media_outwebrtc_pc_SUITE:dscp_marking (AF41 on the key frame, AF42 after)E2E tested
TR-228837 §5AF3x only for video known not to be interactive (MAY for non-browsers; browsers MUST NOT)webrtc_dscp, webrtc_jseptabletestUnit tested (interactive => false on the transceiver)
TR-238835 §4.2, 8837 §5One DSCP for every packet of the SCTP association, that of its highest priority channelwebrtc_dcep, webrtc_transport_securewebrtc_dcep_tests:priority_class_test, webrtc_pc_SUITE:dscp_markingE2E tested (it only rises while channels are open)
TR-248837 §5SCTP congestion control restarted when the association's DSCP changeswebrtc_sctp_assocwebrtc_sctp_assoc_tests:reset_congestion_testUnit tested (initial cwnd and ssthresh; RTT and MTU kept)
TR-258837 §5One DSCP per TCP connection, the highest of the flows it carrieswebrtc_transport_netwebrtc_pc_SUITE:dscp_tcp_connectionE2E tested: the tos option of each ICE-TCP connection, read back from the operating system, is EF for high priority audio beside an AF21 data channel
TR-268835 §4.2Connectivity checks unmarked; once a pair is selected, each consent request also sent with each DSCP in use; a DSCP missed three times in a row while consent holds is dropped for its flowswebrtc_ice_marks, webrtc_transport_securewebrtc_ice_net_tests:dscp_blocked_test, dscp_unmarked_test, webrtc_pc_SUITE:dscp_markingUnit tested: the owner gets {dscp_disabled, Dscp}; other flows keep their marks
TR-278835 §4.2No marking where the platform has nonewebrtc_transport_netwebrtcdscp_tests:wire_testUnit tested on IPv4 and IPv6: the TOS byte reaches the receiver; a send refused with it turns marking off and goes unmarked
TR-283168 §5ECN bits kept beside the DSCPwebrtc_dscp, webrtc_transport_netwiretest (DSCP 34 with ECT(0))Unit tested