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} |
||
|---|---|---|
| .. | ||
| abs-capture-time | ||
| abs-send-time | ||
| color-space | ||
| corruption-detection | ||
| inband-cn | ||
| playout-delay | ||
| transport-wide-cc-02 | ||
| video-content-type | ||
| video-frame-tracking-id | ||
| video-layers-allocation00 | ||
| video-timing | ||
| README.md | ||
Experimental RTP header extensions
The following subpages define experimental RTP header extensions: