[webrtc-rtptransport] Survive going to sleep and coming back (#105)

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

== Survive going to sleep and coming back ==
If there isn't a Wake Lock and a laptop goes to sleep, and comes back, it's likely that a long time has passed and that NAT bindings have probably been released and the remote endpoint (client or server) may have given up on us.  

How quickly can a connection be restored?
- Can we use the same local ports?
- Can we use the same ICE ufrag/pwd?
- Do we automatically re-attempt STUN and TURN, or does the app need to do that?
- Do we automatically re-attempt ICE checks to the remote candidates, or does the app need to do that?
- Does a new crypto handshake need to be done?  How do we know?  

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


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

Received on Tuesday, 24 February 2026 09:15:23 UTC