- From: Tony Herre via GitHub <sysbot+gh@w3.org>
- Date: Mon, 13 May 2024 13:34:42 +0000
- To: public-webrtc-logs@w3.org
Feedback messages are at least somewhat aggregated, sent [every 50-250ms in libwebrtc](https://source.chromium.org/chromium/chromium/src/+/main:third_party/webrtc/modules/remote_bitrate_estimator/remote_estimator_proxy.cc;drc=41d53a863ef269e6d53fea38cc1d3feda6c3df78;l=35), recommended per frame or less often in the ietf draft. `onrtpsent` is my bigger concern, indeed. Is it enough to just get the actual sent timestamps in the `RtpAcks` message somewhere and not be notified on every send? Depends on whether it's the UA deciding that packets are lost and notifying up (akin to the [TransportPacketsFeedback](https://source.chromium.org/chromium/chromium/src/+/main:third_party/webrtc/api/transport/network_types.h;drc=cc92b6e1bd101f69517da7fa0c80eacf37b65621;l=171) struct in libwebrtc passed to the googcc impl) or the JS making its own decision based on being notified of a send but not of a remote feedback ack. -- GitHub Notification of comment by tonyherre Please view or discuss this issue at https://github.com/w3c/webrtc-rtptransport/issues/20#issuecomment-2107596964 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 13 May 2024 13:34:43 UTC