ICE (RFC 8445, RFC 8863, RFC 8838, RFC 7675, RFC 8839, mDNS candidates)

View Source

This page lists the ICE requirements tracked by the stack: the agent itself (RFC 8445, full and lite), the RFC 8863 failure timer, trickle ICE (RFC 8838), consent freshness (RFC 7675), the candidate semantics of RFC 8839 and mDNS host candidates (draft-ietf-mmusic-mdns-ice-candidates with RFC 6762). Read it to know what webrtc_ice_agent does before relying on a behavior. Tests named webrtc_ice_net_tests:* run two agents over the simulated network of test/webrtc_ice_net.erl (fake clock, seeded loss, NATs, test STUN and TURN servers); they are eunit tests, not tests over real sockets.

RFC 8445

IDSectionRequirementModuleTestStatus
ICE-15.1.1.1Host candidates from the owner's sockets, one socket per candidatewebrtc_ice_gatherwebrtc_ice_net_tests:host_host_testUnit tested
ICE-25.1.1.2Server-reflexive candidates from unauthenticated Binding requests, MAPPED-ADDRESS accepted, ALTERNATE-SERVER ignored, response must come from the serverwebrtc_ice_gatherwebrtc_ice_agent_tests:stun_srflx_test, webrtc_ice_net_tests:srflx_candidate_testUnit tested
ICE-35.1.1.2Relayed candidates from TURN Allocate, server-reflexive candidate from its XOR-MAPPED-ADDRESS, relay equal to a host candidate discardedwebrtc_ice_relaywebrtc_ice_net_tests:srflx_candidate_test, symmetric_needs_relay_testUnit tested
ICE-45.1.1.2Allocate rejected for resources (486, 508): fall back to a Binding request to the same serverwebrtc_ice_relaywebrtc_ice_net_tests:turn_quota_srflx_fallback_testUnit tested
ICE-55.1.1.2, 14.3One new gathering transaction per Ta, RTO = MAX(500 ms, Ta * number of jobs), retransmissions per RFC 8489webrtc_ice_gatherwebrtc_ice_agent_tests:stun_timeout_completes_gathering_testUnit tested
ICE-65.1.1.3Foundation equal iff type, base IP, server IP and transport are equalwebrtc_ice_candidatewebrtc_ice_candidate_tests:foundation_testUnit tested
ICE-75.1.1.4Server-reflexive bindings refreshed by Binding requests every 15 s until ICE completeswebrtc_ice_gatherImplemented, untested
ICE-85.1.2.1, 5.1.2.2Priority formula, type preferences 126 / 110 / 100 / 0, unique prioritieswebrtc_ice_candidatewebrtcice_candidate_tests:priority_test, prop_webrtc_ice:prop_type_preference_dominatesUnit tested
ICE-95.1.2.1, RFC 8421Unique local preferences, IPv6 head start then IPv4/IPv6 intermingled; unique per STUN/TURN serverwebrtc_ice_candidatewebrtc_ice_candidate_tests:local_preferences_test, prop_webrtc_ice:prop_local_preferences_unique, webrtc_ice_net_tests:dual_stack_testUnit tested
ICE-105.1.3Redundant candidates (same transport address and base) eliminatedwebrtc_ice_candidate, webrtc_ice_gatherwebrtc_ice_candidate_tests:redundant_test, webrtc_ice_agent_tests:stun_srflx_testUnit tested
ICE-115.2Lite agent uses host candidates onlywebrtc_ice_gatherwebrtc_ice_net_tests:full_lite_testUnit tested
ICE-125.3ufrag with at least 24 random bits and password with at least 128 random bitswebrtc_ice_candidatewebrtcice_candidate_tests:credentials_testUnit tested
ICE-136.1.1Lite agent is controlled against a full peer; a full agent is controlling against a lite peerwebrtc_ice_agentwebrtc_ice_net_tests:lite_forced_controlled_testUnit tested
ICE-146.1.2.2Pairs only within a component, address family and transport; IPv6 link-local only with link-localwebrtc_ice_candidate, webrtc_ice_checklistwebrtcice_candidate_tests:can_pair_test, webrtc_ice_agent_tests:remote_candidate_family_test, webrtc_ice_net_tests:dual_stack_testUnit tested
ICE-156.1.2.3Pair priority 2^32MIN(G,D) + 2MAX(G,D) + (G>D?1:0), same on both agentswebrtc_ice_candidatewebrtcice_candidate_tests:pair_priority_test, prop_webrtc_ice:prop_pair_priority_agrees, prop_pair_priority_orderUnit tested
ICE-166.1.2.4Reflexive local candidates replaced by their base, redundant pairs prunedwebrtc_ice_checklistwebrtc_ice_net_tests:full_cone_testUnit tested
ICE-176.1.2.5Pair limit (default 100, configurable) keeping the highest prioritieswebrtc_ice_checklistwebrtc_ice_agent_tests:max_pairs_testUnit tested
ICE-186.1.2.6Initial states: one Waiting pair per foundation, others Frozenwebrtc_ice_checklistwebrtc_ice_agent_tests:freezing_testUnit tested
ICE-196.1.4.2Every Ta: triggered queue first, else best Waiting pair, else unfreeze one pair per idle foundationwebrtc_ice_checklist, webrtc_ice_agentwebrtc_ice_agent_tests:pacing_test, prop_webrtc_ice:prop_checks_by_priorityUnit tested
ICE-207.1.1PRIORITY computed with the peer-reflexive type preferencewebrtc_ice_conncheckwebrtc_ice_agent_tests:valid_check_testUnit tested
ICE-217.1.2USE-CANDIDATE sent only by the controlling agent, ignored when received by itwebrtc_ice_conncheck, webrtc_ice_responderwebrtc_ice_agent_tests:use_candidate_ignored_when_controlling_testUnit tested
ICE-227.1.3ICE-CONTROLLING / ICE-CONTROLLED with a 64-bit tie-breakerwebrtc_ice_conncheckwebrtcice_agent_tests:valid_check_test, role_conflict_testUnit tested
ICE-237.2.1TURN permissions created for remote candidates before checks from a relayed candidatewebrtc_ice_relaywebrtc_ice_net_tests:symmetric_needs_relay_testUnit tested
ICE-247.2.2USERNAME "remote:local", MESSAGE-INTEGRITY keyed with the remote passwordwebrtc_ice_conncheckwebrtc_ice_agent_tests:valid_check_testUnit tested
ICE-257.2.4FINGERPRINT on every check, no RFC 3489 compatibilitywebrtc_ice_conncheckwebrtc_ice_agent_tests:valid_check_testUnit tested
ICE-267.2.5Responses matched by transaction id; without valid integrity or FINGERPRINT discarded and retransmissions go onwebrtc_ice_conncheckwebrtc_ice_agent_tests:forged_response_ignored_testUnit tested
ICE-277.2.5.1487: switch role, new tie-breaker, recompute priorities, pair re-queued as triggeredwebrtc_ice_conncheckwebrtc_ice_agent_tests:role_conflict_response_test, webrtc_ice_net_tests:both_controlling_test, both_controlled_testUnit tested
ICE-287.2.5.2.1Non-symmetric source or destination fails the pairwebrtc_ice_conncheckwebrtc_ice_agent_tests:spoofed_source_testUnit tested
ICE-297.2.5.2.2ICMP errors (optional)Not implemented: the owner has no way to report ICMP errors
ICE-307.2.5.2.3Transaction timeout fails the pairwebrtc_ice_conncheckwebrtc_ice_agent_tests:check_timeout_testUnit tested
ICE-317.2.5.2.4Unrecoverable error response fails the pairwebrtc_ice_conncheckwebrtc_ice_agent_tests:error_response_fails_pair_testUnit tested
ICE-327.2.5.3.1Unknown mapped address becomes a peer-reflexive local candidate (priority from the request, base from the pair), not signaledwebrtc_ice_conncheckwebrtc_ice_agent_tests:peer_reflexive_local_testUnit tested
ICE-337.2.5.3.2Valid pair built from the mapped address, possibly outside the checklistwebrtc_ice_conncheckwebrtc_ice_agent_tests:peer_reflexive_local_test, webrtc_ice_net_tests:symmetric_needs_relay_testUnit tested
ICE-347.2.5.3.3Pair and valid pair Succeeded; Frozen pairs of the foundation become Waitingwebrtc_ice_conncheck, webrtc_ice_checklistwebrtc_ice_agent_tests:trickle_states_testUnit tested
ICE-357.2.5.3.4Successful USE-CANDIDATE check nominates; a failed one removes the pair from the valid list and fails the checklistwebrtc_ice_conncheckwebrtc_ice_net_tests:host_host_test, webrtc_ice_agent_tests:nomination_failure_testUnit tested
ICE-367.2.5.4Checklist Failed when all pairs are done without a valid pair for each componentwebrtc_ice_sessionwebrtc_ice_net_tests:no_working_pair_fails_test, family_mismatch_fails_testUnit tested
ICE-377.3Requests authenticated with the short-term credential: 400 without USERNAME or MESSAGE-INTEGRITY, 401 for a wrong ufrag or integritywebrtc_ice_responderwebrtcice_agent_tests:reject_testUnit tested
ICE-387.3Requests before the remote credentials are answered at once and processed when the credentials arrivewebrtc_ice_responderwebrtc_ice_agent_tests:early_check_test, early_check_other_session_testUnit tested
ICE-397.3FINGERPRINT required, ALTERNATE-SERVER never usedwebrtc_ice_responderwebrtc_ice_agent_tests:no_fingerprint_dropped_testUnit tested
ICE-407.3, RFC 8489 6.3.1420 with UNKNOWN-ATTRIBUTES; 400 without PRIORITY or with zero or two role attributeswebrtc_ice_responderwebrtcice_agent_tests:reject_testUnit tested
ICE-417.3.1.1Role conflict repair on received requests (487 or role switch)webrtc_ice_responderwebrtcice_agent_tests:role_conflict_test, role_conflict_code_testUnit tested
ICE-427.3.1.2XOR-MAPPED-ADDRESS of a relayed request is the peer address seen by the TURN serverwebrtc_ice_relay, webrtc_ice_responderwebrtc_ice_net_tests:symmetric_needs_relay_testUnit tested
ICE-437.3.1.3Unknown source becomes a peer-reflexive remote candidate with the request PRIORITY, not pairedwebrtc_ice_responderwebrtc_ice_agent_tests:valid_check_testUnit tested
ICE-447.3.1.4Triggered checks: Succeeded unchanged, In-Progress cancelled and re-queued, others Waiting and queued, new pairs insertedwebrtc_ice_responderwebrtc_ice_agent_tests:valid_check_test, webrtc_ice_net_tests:late_candidates_testUnit tested
ICE-457.3.1.5Controlled agent: USE-CANDIDATE nominates a Succeeded pair's valid pair, or the pair once its triggered check succeedswebrtc_ice_responderwebrtc_ice_agent_tests:use_candidate_on_succeeded_pair_test, early_check_testUnit tested
ICE-467.3.2Lite agent: USE-CANDIDATE makes the pair valid and nominated; no checks sentwebrtc_ice_responderwebrtc_ice_agent_tests:lite_test, webrtc_ice_net_tests:full_lite_testUnit tested
ICE-478.1.1Regular nomination: the check that produced the chosen valid pair is repeated with USE-CANDIDATE, one nomination per session; policy best waits for better pending pairs or nomination_timeout, policy first does notwebrtc_ice_sessionwebrtc_ice_agent_tests:nomination_best_waits_test, nomination_first_testUnit tested
ICE-488.1.1Several nominations from an RFC 5245 peer: the highest priority nominated pair is selectedwebrtc_ice_conncheckImplemented, untested
ICE-498.1.2After nomination the other pairs of the component leave the checklist, in-progress checks cancelled, checklist and session Completedwebrtc_ice_conncheckwebrtc_ice_net_tests:host_host_test, host_host_stats_testUnit tested
ICE-508.2Lite agent Completed once nominatedwebrtc_ice_responderwebrtc_ice_net_tests:full_lite_testUnit tested
ICE-518.2Lite agent against a lite peer (lite agent controlling)Not implemented: both lite is not supported, a lite agent is always controlled
ICE-528.3Freeing unused candidates 3 s after completionNon-compliant / known limitation: candidates are kept and checks answered for the whole session (no protocol impact, uses resources)
ICE-539Restart: new ufrag and password, all state except the role flushed, previous selected pair kept usable until the new session selects onewebrtc_ice_sessionwebrtc_ice_net_tests:restart_test, restart_requires_new_credentials_testUnit tested
ICE-5410ice2 option announcedwebrtc_jsep_buildwebrtc_jsep_tests:ice_options_and_pacing_testUnit tested: offers and answers carry a=ice-options:trickle ice2. The agent never uses aggressive nomination
ICE-5511Keepalives: Binding indication with FINGERPRINT only, when nothing was sent for Tr = 15 s, on the selected pair, when consent freshness is off and for lite agentswebrtc_ice_consentwebrtc_ice_net_tests:consent_disabled_keepalive_testUnit tested
ICE-5612.1Data on any valid pair before nomination, on the selected pair afterwardswebrtc_ice_sessionwebrtc_ice_agent_tests:check_success_test, webrtc_ice_net_tests:host_host_testUnit tested
ICE-5712.2, RFC 8826 4.2Non-ICE traffic accepted only from validated addresses (is_valid_remote/3)webrtc_ice_sessionwebrtc_ice_agent_tests:valid_check_test, spoofed_source_test, webrtc_ice_net_tests:remove_host_testUnit tested
ICE-5814.2Ta default 50 mswebrtc_ice_agentwebrtc_ice_agent_tests:pacing_testUnit tested
ICE-5914.2Ta negotiation: a value other than 50 ms announced, both sides use the higher one, never below 5 mswebrtc_ice_agent, webrtc_jsep_build, webrtc_pcwebrtc_ice_agent_tests:pacing_remote_higher_test, pacing_local_higher_test, pacing_floor_test, webrtc_jsep_tests:ice_options_and_pacing_test, webrtc_pc_SUITE:ice_pacing_negotiatedUnit and e2e tested (ice_pacing option; set_remote_pacing/2)
ICE-6014.3Check RTO = MAX(500 ms, Ta N (Waiting + In-Progress)), never below 500 mswebrtc_ice_conncheckwebrtc_ice_agent_tests:check_rto_testUnit tested; the value is capped by max_check_rto (2500 ms by default), a local choice the section allows
ICE-6119.2Malformed, truncated or bit-flipped checks and responses never crash the agentwebrtc_ice_agentwebrtcice_agent_tests:malformed_check_test, malformed_response_test, garbage_testUnit tested
ICE-622.2Two agents conclude on the same pair under random loss below 50%webrtc_ice_agentprop_webrtc_ice:prop_lossy_network_connects, webrtc_ice_net_tests:lossy_checks_testUnit tested (the property uses Rc = 40 to make transaction failure negligible)
ICE-635.1.1.1, 17.1Host, server-reflexive, peer-reflexive and relayed paths through full cone, restricted, port-restricted and symmetric NATs, IPv4, IPv6 and dual stackwebrtc_ice_agentwebrtc_ice_net_tests:full_cone_test, restricted_test, port_restricted_test, symmetric_needs_relay_test, ipv6_only_test, dual_stack_testUnit tested
ICE-6519.5.1Per-peer state bounded: pairs (max_pairs), remote candidates including peer-reflexive ones (max_remote, 100), checks remembered before the remote credentials (64), consent transactions (30 s window); unauthenticated requests get a small unprotected error and create no statewebrtc_ice_checklist, webrtc_ice_responderwebrtcice_agent_tests:remote_candidate_cap_test, max_pairs_test, reject_testUnit tested
ICE-645.1.1.4, 8.1.1, 9Network change: removing a socket removes its candidates, pairs and transactions; a lost selected pair fails the ICE session; the application restarts ICE, or with ice_auto_restart the peer connection does it by itself (no second nomination within a session)webrtc_ice_gather, webrtc_pcwebrtc_ice_net_tests:remove_host_test, webrtc_pc_SUITE:ice_auto_restartE2E tested

RFC 8863

IDSectionRequirementModuleTestStatus
PAC-14PAC timer (39.5 s) started with the remote credentials; no checklist failure before it expireswebrtc_ice_sessionwebrtc_ice_net_tests:no_working_pair_fails_test, symmetric_without_turn_fails_test, family_mismatch_fails_testUnit tested
PAC-24Controlling agent waits before nominatingwebrtc_ice_sessionwebrtc_ice_agent_tests:nomination_best_waits_testUnit tested; the wait is nomination_timeout after the first valid pair, not the PAC timer
PAC-35With trickle ICE, failure also waits for end-of-candidates, with a timer (eoc_timeout, PAC by default) as fallbackwebrtc_ice_sessionwebrtc_ice_net_tests:no_eoc_waits_test, webrtc_ice_agent_tests:check_timeout_testUnit tested

RFC 6544 (ICE-TCP)

Enabled with the ice_tcp peer connection option. The agent stays sans-IO: the transport listens and accepts, opens the connections the agent asks for and frames packets with RFC 4571.

IDSectionRequirementModuleTestStatus
TCP-14.1, 4.5Passive host candidate on a TCP listener next to every UDP host address; active host candidate with port 9webrtc_ice_tcp, webrtc_transport_netwebrtc_ice_tcp_tests:candidates_testUnit tested
TCP-24.2Local preference 2^13 * direction preference (active 6, passive 4) + other preference, below UDP host candidateswebrtc_ice_candidatewebrtc_ice_tcp_tests:candidates_testUnit tested
TCP-36.2Active pairs with remote passive, passive with remote active, UDP with UDPwebrtc_ice_candidatewebrtc_ice_tcp_tests:connectivity_testUnit tested
TCP-47.1An active pair opens its connection before its check; a passive pair waits for the peer's connection and answers on it; a connection that cannot be opened fails its pairwebrtc_ice_tcpwebrtc_ice_tcp_tests:connectivity_test, refused_connection_testUnit tested
TCP-57.1Checks not retransmitted over TCP; a transaction fails after 39.5 swebrtc_ice_conncheckwebrtc_ice_tcp_tests:connectivity_testUnit tested
TCP-67.2A peer-reflexive candidate learned on a passive candidate is TCP active; the valid pair of an active candidate keeps it (its mapped port differs)webrtc_ice_responder, webrtc_ice_conncheckwebrtc_ice_tcp_tests:connectivity_testUnit tested
TCP-77.2, RFC 4571Packets on the connection framed with a 16-bit length; DTLS, SRTP and SCTP over it only from the validated connectionwebrtc_transport_net, webrtc_ice_sessionwebrtc_pc_SUITE:ice_tcp_only, webrtc_pc_interop_SUITE chromium_tcp, firefox_tcpInteroperability tested
TCP-8Inbound connections bounded (32); pairs of authenticated checks kept past the pair limit (up to twice max_pairs)webrtc_ice_tcp, webrtc_ice_checklistwebrtc_pc_interop_SUITE chromium_tcpInteroperability tested
TCP-94.1Simultaneous-open (so) candidatesNot implemented: browsers do not gather them

RFC 8838

IDSectionRequirementModuleTestStatus
TRK-17, 8Checklist Running while empty; candidates paired as they arrivewebrtc_ice_checklistwebrtc_ice_net_tests:late_candidates_testUnit tested
TRK-28Failure only after local gathering completed and remote end-of-candidateswebrtc_ice_sessionwebrtc_ice_agent_tests:check_timeout_test, webrtc_ice_net_tests:no_eoc_waits_testUnit tested
TRK-39New local candidates trickled as events; a redundant one ignored regardless of prioritywebrtc_ice_gatherwebrtc_ice_agent_tests:stun_srflx_test, webrtc_ice_net_tests:host_host_testUnit tested
TRK-410, 11New local or remote candidates paired with the known ones, reflexive locals replaced by their basewebrtc_ice_checklistwebrtc_ice_net_tests:late_candidates_testUnit tested
TRK-511A signaled candidate already known as peer-reflexive: it is then paired with every local base (the relayed one included, with its TURN permission), not only the one that received the checkwebrtc_ice_agentwebrtc_ice_net_tests:late_candidates_test, signaled_after_prflx_pairs_every_local_test, webrtc_turn_interop_SUITE:one_side_relayedInteroperability tested; the remote candidate takes the signaled type, priority and foundation in place and pair priorities are recomputed, instead of discarding and re-sorting pairs
TRK-610, 11Pair limit: Failed pairs dropped first, then lower priority oneswebrtc_ice_checklistwebrtc_ice_agent_tests:max_pairs_testUnit tested
TRK-712New pair Waiting when it tops its foundation or the foundation has a Succeeded pair, Frozen otherwisewebrtc_ice_checklistwebrtc_ice_agent_tests:trickle_states_testUnit tested
TRK-813End of local gathering reported ({gathering_state, complete}) for the owner to signal end-of-candidateswebrtc_ice_gatherwebrtc_ice_net_tests:host_host_testUnit tested
TRK-914Candidates received after end-of-candidates ignoredwebrtc_ice_agentwebrtc_ice_net_tests:candidates_after_eoc_ignored_testUnit tested
TRK-109, 15Candidates for another session (ufrag extension) ignoredwebrtc_ice_agentwebrtc_ice_net_tests:old_generation_candidate_ignored_testUnit tested
TRK-1116Half trickleNot implemented here: signaling layer

RFC 7675

IDSectionRequirementModuleTestStatus
CNS-15Consent obtained when a pair succeedswebrtc_ice_conncheckwebrtc_ice_agent_tests:check_success_testUnit tested
CNS-25.1No application data without consent (send/3,4 refuses)webrtc_ice_sessionwebrtc_ice_agent_tests:spoofed_source_test, webrtc_ice_net_tests:no_working_pair_fails_testUnit tested
CNS-35.1Consent request every 5 s randomized between 0.8 and 1.2, never under 4 s, on the selected pair or the best valid pair before nominationwebrtc_ice_consentwebrtc_ice_net_tests:consent_loss_testUnit tested
CNS-45.1New transaction id per request, sent once; a response may answer any outstanding requestwebrtc_ice_consentwebrtc_ice_net_tests:consent_loss_testUnit tested
CNS-55.1Only an authenticated success response from the remote address on the same path refreshes consentwebrtc_ice_consentwebrtc_ice_agent_tests:forged_consent_response_testUnit tested
CNS-65.1Consent expires 30 s after the last response: transmission stops, {consent_lost, L, R}webrtc_ice_consentwebrtc_ice_net_tests:consent_loss_testUnit tested
CNS-75.1Outstanding consent transactions dropped at expiry; no consent requests or data on the lost pair afterwards. By default nothing restarts by itself: as in browsers (W3C webrtc-pc, restartIce()), the application decides. With ice_auto_restart the peer connection restarts ICE after ice_restart_delay ms disconnected (disconnected) or at expiry (failed), the controlling side first, and the new session selects a working path. With signaling the peer connection makes and applies the restart offer and answer itself; on glare the controlled side rolls its offer back (RFC 9429 §4.1.8.2)webrtc_ice_consent, webrtc_pcwebrtc_ice_net_tests:consent_loss_test, webrtc_pc_SUITE:ice_auto_restart (IPv6 path dropped, IPv4 selected after the restart), ice_auto_restart_signaling, ice_auto_restart_glare, ice_auto_restart_off, ice_auto_restart_defaultE2E tested
CNS-85.1Consent kept on the previous pair during an ICE restartwebrtc_ice_consentwebrtc_ice_net_tests:restart_testUnit tested
CNS-95.1Response wait based on RTTNon-compliant / known limitation: responses are accepted until consent expires, there is no per-request window
CNS-105.2Authenticated 403 revokes consent at oncewebrtc_ice_consentwebrtc_ice_agent_tests:forbidden_revokes_consent_testUnit tested
CNS-114No Binding indication keepalives where consent requests runwebrtc_ice_consentwebrtc_ice_net_tests:consent_disabled_keepalive_testUnit tested
CNS-125.1Lite agent (sends no requests)webrtc_ice_consentwebrtc_ice_net_tests:lite_consent_expiry_testUnit tested; local policy: consent of a lite agent is refreshed by the peer's authenticated checks and expires 30 s after the last one
CNS-13disconnected state after disconnect_timeout (10 s) without a consent response, back to completed on the next onewebrtc_ice_sessionwebrtc_ice_net_tests:consent_loss_testUnit tested (local policy)

RFC 8839 candidate semantics

IDSectionRequirementModuleTestStatus
SDP-15.1candidate-attribute: foundation of 1 to 32 ice-chars, component 1 to 256, transport, priority 1 to 2^31-1, address, port, typ, raddr/rport, extension pairs keptwebrtc_ice_candidatewebrtcice_candidate_tests:sdp_roundtrip_test, sdpparse_test, prop_webrtc_ice:prop_sdp_roundtripUnit tested
SDP-25.1Related address of a server-reflexive candidate is its base, of a relayed candidate the mapped addresswebrtc_ice_gather, webrtc_ice_relaywebrtc_ice_net_tests:srflx_candidate_testUnit tested
SDP-35.1FQDN connection addresses: looked up AAAA then A, one address chosen (IPv6 when the transport has an IPv6 socket), the candidate ignored when nothing resolveswebrtc_mdns_client, webrtc_mdnswebrtc_mdns_client_tests:fqdn_family_choice_test, webrtc_mdns_SUITE:fqdn_candidatesE2E tested. The agent itself still takes IP literals only ({error, {fqdn, Name}}); the transport resolves names before handing candidates to it
SDP-45.1TCP candidates (tcptype)webrtc_ice_candidatewebrtcice_candidate_tests:sdp_roundtrip_test, webrtc_ice_tcp_testsUnit tested; used by ICE-TCP, see the RFC 6544 table
SDP-55.4ice-ufrag 4 to 256 and ice-pwd 22 to 256 ice-chars, checked on inputwebrtc_ice_candidate, webrtc_ice_agentwebrtcice_candidate_tests:credentials_test, webrtc_ice_net_tests:restart_requires_new_credentials_testUnit tested
SDP-65.5, 5.6a=ice-lite, a=ice-options, a=ice-pacingwebrtc_sdp_attr, webrtc_jsep_build, webrtc_pcwebrtc_sdp_tests:ice_pacing_test, webrtc_jsep_tests:ice_options_and_pacing_testUnit tested: the SDP layer parses and announces them; the agent takes lite, remote_lite, ta and set_remote_pacing/2

mDNS candidates (draft-ietf-mmusic-mdns-ice-candidates-03, RFC 6762)

Remote .local candidates are resolved by the transport with one-shot multicast DNS queries; our own host candidates can be hidden behind names with the mdns_host_candidates option (off by default: a server usually wants to expose its address).

IDSectionRequirementModuleTestStatus
MDNS-1draft 3.2.1A remote candidate whose address is a <uuid>.local name is resolved with mDNS and added with the resolved address, its other fields unchanged; a name that does not resolve drops that candidate onlywebrtc_mdns_client, webrtc_transportwebrtc_mdns_client_tests:mdns_resolved_and_marked_test, webrtc_mdns_SUITE:remote_mdns_candidates, webrtc_pc_interop_SUITE:chromium_mdnsInteroperability tested (Chromium)
MDNS-2draft 3.2.2Names that are not a version 4 UUID followed by .local are not resolved; a name with more than one address is ignoredwebrtc_mdns_clientwebrtc_mdns_client_tests:non_uuid_local_name_ignored_test, mdns_several_addresses_ignored_testUnit tested
MDNS-3draft 3.3.2Relayed local candidates are never paired with remote candidates resolved from an mDNS namewebrtc_ice_candidatewebrtcice_candidate_tests:can_pair_testUnit tested
MDNS-4RFC 8838 14End-of-candidates received while names resolve is applied once they are done, so late candidates are keptwebrtc_mdns_clientwebrtc_mdns_client_tests:unresolved_name_and_deferred_end_of_candidates_test, webrtc_mdns_SUITE:remote_mdns_candidatesE2E tested
MDNS-5Bounded: at most 32 candidates waiting for a name ({error, too_many_pending} beyond), 32 queries, 64 cached names, 8 DNS lookups; resolution never blocks the transport processwebrtc_mdns_client, webrtc_mdns, webrtc_mdns_resolverwebrtc_mdns_SUITE:pending_candidates_bounded, webrtc_mdns_resolver_tests:max_queries_test, cache_bounded_testE2E tested
MDNS-6RFC 6762 5.1, 5.4One-shot queries from an ephemeral port, one question per message (A, then AAAA), QU bit on the first query, QM on the retransmissions at 250 ms and 1.25 s, failure at 3.25 swebrtc_mdns_resolverwebrtc_mdns_resolver_tests:query_test, retransmit_then_timeout_testUnit tested
MDNS-7RFC 6762 6.7, 18.1Legacy unicast answers must echo the query ID and repeat the question; multicast answers (ID ignored) are received on a group socket shared through SO_REUSEPORTwebrtc_mdns_resolver, webrtc_mdnswebrtc_mdns_resolver_tests:legacy_answer_needs_id_and_question_test, multicast_answer_test, webrtc_mdns_testsUnit tested
MDNS-8RFC 6762 6, 11Only class IN A/AAAA records naming a pending question are used, from the answer and additional sections; unsolicited answers are ignored and never cached; packets from outside the local subnets are droppedwebrtc_mdns_resolver, webrtc_mdnswebrtc_mdns_resolver_tests:unsolicited_ignored_test, additional_section_testUnit tested
MDNS-9RFC 6762 10, 10.1Cache honors record TTLs (capped at one hour); goodbye records (TTL 0) are not usedwebrtc_mdns_resolverwebrtc_mdns_resolver_tests:legacy_unicast_answer_test, ttl_capped_test, invalid_responses_ignored_testUnit tested
MDNS-10RFC 1035 4.1.4, RFC 6762 18Codec: name compression with backward pointers only (no loops), at most 64 pointers and 255 octets per name, every count and length checked, never raiseswebrtc_mdns_msgwebrtc_mdns_msg_tests, prop_webrtc_parsers:prop_decoders_never_raise, prop_mdns_roundtripUnit tested
MDNS-11draft 3.1.1With mdns_host_candidates, each host address gets a random version 4 UUID .local name (same address, same name), announced without probingwebrtc_mdns_responder, webrtc_mdns_clientwebrtc_mdns_client_tests:hidden_local_candidates_test, webrtc_mdns_tests:responder_answers_queriesE2E tested (webrtc_mdns_SUITE:hidden_host_candidates)
MDNS-12draft 3.1.2.2The related address of our other candidates becomes 0.0.0.0 or ::, port 9webrtc_mdns_clientwebrtc_mdns_client_tests:hidden_local_candidates_testUnit tested
MDNS-13RFC 6762 5.4, 6, 6.7, 7.1, 10.1Responder: legacy queries answered by unicast with ID and question and TTL 10, QU by unicast, QM by multicast at most once per second per name, known answers suppressed, goodbye on stopwebrtc_mdns_responderwebrtcmdns_tests:responder*Unit tested
MDNS-14draft 3.1.2.2Each hidden host gets the usual STUN check: a mapped address equal to the host address shows it is public. The server-reflexive candidate is then not redundant with its hidden host and is kept (raddr 0.0.0.0 or ::, port 9). The finding is cached by the node for that set of STUN servers and dropped when the set changes; with mdns_expose_public (default true) later gatherings (ICE restarts, other peer connections) signal the address as it iswebrtc_ice_gather, webrtc_mdns_client, webrtc_mdns_publicwebrtc_ice_agent_tests:stun_srflx_hidden_host_test, webrtc_mdns_client_tests:public_address_test, private_address_test, webrtc_mdns_SUITE:public_host_addressE2E tested
MDNS-15RFC 6762 6.1Negative (NSEC) answers for the missing address family: the record's own name as next domain name and a one-window bitmap of the type it haswebrtc_mdns_responder, webrtc_mdns_msgwebrtc_mdns_tests:responder_nsec_test, responder_answers_ipv6Unit tested
MDNS-16RFC 6762 5, 6, 11, 20IPv6 multicast transport (ff02::fb): queries, announcements and answers sent on every IPv6 multicast interface (the interface as scope id), the group joined on each; IPv6 link-local and on-link sources acceptedwebrtc_mdnswebrtc_mdns_tests:ipv6_only_answer, responder_answers_ipv6, from_link_test, webrtc_pc_interop_SUITE chromium_mdns groupUnit tested; interop runs with both families on (Chromium answers over IPv4)

Notes

  • Specification status checked on 2026-11-14 at rfc-editor.org: RFC 8445 is updated only by RFC 8863; RFC 8838 is updated by RFC 8863; RFC 8489, RFC 8839, RFC 8863 and RFC 7675 have no update or obsoleting document. draft-ietf-mmusic-mdns-ice-candidates-03 (December 2021) is the latest revision and is expired; browsers implement it as written.

  • Chromium's responder answers only queries with a single QM question, by multicast. The first (QU) query therefore gets no answer from it; the first retransmission, 250 ms later, does.

  • Integration with TURN: the agent owns one webrtc_turn_client per (host socket, TURN server). See docs/compliance/turn.md.

  • Selection of the pair to keep after a network change is not automatic: the owner calls restart/2,3 and signals the new credentials and candidates.