dcsctp: Resend SHUTDOWN ACK if receiving SHUTDOWN According to RFC 9260 Section 9.2, once an endpoint has reached the SHUTDOWN-RECEIVED state, it MUST continue responding to SHUTDOWN chunks from its peer. Previously, HandleShutdown would explicitly return without action if the state was SHUTDOWN-ACK-SENT. This caused the socket to ignore the peer's retransmitted SHUTDOWN chunks (sent if our first SHUTDOWN ACK was lost), leading to a delay until the socket's own timer expired to resend SHUTDOWN ACK. This CL fixes this by calling SendShutdownAck() when a SHUTDOWN chunk is received in the SHUTDOWN-ACK-SENT state, which resends the ACK and restarts the T2-shutdown timer. Bug: webrtc:500087337 Change-Id: I4d35156b02aad529bcd68906d9d0c8898b53eb6a Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/462001 Commit-Queue: Victor Boivie <boivie@webrtc.org> Reviewed-by: Danil Chapovalov <danilchap@webrtc.org> Cr-Commit-Position: refs/heads/main@{#47368}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
See here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.