- From: docfaraday via GitHub <noreply@w3.org>
- Date: Thu, 26 Feb 2026 02:31:36 +0000
- To: public-webrtc-logs@w3.org
I'm going to put my two cents in here. Whatever we end up doing, we have to remember one of the cardinal rules of network protocol: Thou Shalt Not Ghost the Other Endpoint If you know you are done with some network protocol association (connection, stream, whatever), you must make an effort to notify the other end in a timely fashion. The entire internet relies on this general rule being followed. Imagine if TCP did not have FIN, or if FIN weren't used as a matter of course, and the only way TCP connections died was by timeout. Think of the poor routing equipment. In addition, I will point out that pretending you aren't done with the protocol association when you know full well you will never use it again, continuing to send and respond to heartbeats/keepalives/what-have-you, *is even worse than ghosting the other end*. That ends up wasting far more resources. -- GitHub Notification of comment by docfaraday Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/3090#issuecomment-3963593069 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 26 February 2026 02:31:37 UTC