Remove UC1's custom seq num & document this in handled by the UA #22
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
…remove the custom sequence number Init field
|
The seqno should not need to be provided when constructing an |
aboba
approved these changes
Apr 15, 2024
pthatcher
approved these changes
Apr 16, 2024
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.
Be explicit that Use Case 1 doesn't require apps to control sequence numbers, as we'd expect the UA to do sequencing (and pacing etc). Remove the custom sequence number Init field as a result.
Maybe we should add another section with more discussion on what we expect the UA to take care of?
Similar work is definitely needed in UC2.
@pthatcher @Philipel-WebRTC et al