Add capture/receive/RTP timestamps definitions for RTCRtpReceiver frames #233
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…rmative as things should be observable.
guidou
changed the title
henbos
reviewed
Mar 20, 2025
| as specified in [[?RFC3550]] Section 6.4.1, or by other alternative means if use by RTCP SR | ||
| isn't feasible. | ||
| The capture time of an incoming frame is available if its constituent RTP packets contain the | ||
| [=RTP Header Extension for Absolute Capture Time=]. |
There was a problem hiding this comment.
When the relevant information is available (RTCP SR or header extension) then I think the UA "MUST" provide an estimate, and if not it MUST NOT provde an estimate
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Preview | Diff