signalapp/webrtc
signalapp/webrtc
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

abs-send-time: clarify "close to the metal" as "after pacing"

Browse Source 
in the past this was interpreted as "after encryption and in
the network process" but that did not make much difference.

Doing this after pacing is still a good idea

Bug: webrtc:487743907
Change-Id: I3b14225c29c210db0b12b54ca51814fe2836e1e8
No-Try: true
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/452960
Reviewed-by: Fredrik Solenberg <solenberg@webrtc.org>
Reviewed-by: Danil Chapovalov <danilchap@webrtc.org>
Commit-Queue: Philipp Hancke <philipp.hancke@googlemail.com>
Cr-Commit-Position: refs/heads/main@{#47081}
This commit is contained in:
Philipp Hancke 2026-03-02 12:14:17 +01:00 committed by WebRTC LUCI CQ
parent fda4e0da0c
commit 8223963924
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/native-code/rtp-hdrext/abs-send-time/README.md
View File

@ -26,6 +26,8 @@ Relation to NTP timestamps: abs_send_time_24 = (ntp_timestamp_64 >> 14) &
0x00ffffff ; NTP timestamp is 32 bits for whole seconds, 32 bits fraction of
second.
Notes: Packets are time stamped when going out, preferably close to metal.
Notes: Packets are time stamped as close as possible to the time the packet is
sent on the wire. The current implementation allocates space before pacing
and stamps them after pacing and before encryption.
Intermediate RTP relays (entities possibly altering the stream) should remove
the extension or set its own timestamp.