[webrtc-pc] Steps for RTCDtlsTransport state update are vague when handling RFC 8842 DTLS association re-establishment (#3111)

docfaraday has just created a new issue for https://github.com/w3c/webrtc-pc:

== Steps for RTCDtlsTransport state update are vague when handling RFC 8842 DTLS association re-establishment ==
In RFC 8842 DTLS association re-establishment (which might or might not be accompanied by an ICE restart), there is a switch-over period where both the old and new associations are being used (https://datatracker.ietf.org/doc/html/rfc8842#section-5.5-3.1). When does the RTCDtlsTransport.[[RemoteCertificates]] update happen? As soon as the new association is established, or when the old association stops being used? For my money, I think the former makes more sense. Deciding when to stop using the old association could be very situation/implementation dependent.

These steps also don't have a bail-out when there's no state change like other places in the spec, but one could argue that no-change updates aren't supposed to happen given the phrase "When the underlying DTLS transport needs to update the state". Maybe that's fine. Adding a bailout would probably require checking both [[DtlsTransportState]] and [[RemoteCertificates]] for changes.

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/3111 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 28 May 2026 13:18:29 UTC