Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Consider RTP matching rules of JSEP #36

Closed
ibc opened this issue Oct 6, 2016 · 3 comments
Closed

Consider RTP matching rules of JSEP #36

ibc opened this issue Oct 6, 2016 · 3 comments
Labels
enhancement

Comments

@ibc
Copy link
Member

ibc commented Oct 6, 2016 •
edited
Loading

Discussed in:
@ibc ibc added the enhancement label Oct 6, 2016
@ibc
Copy link
Member Author

ibc commented Jan 9, 2017

Note: things are being modified in the ORTC spec regarding this subject.

@ibc
Copy link
Member Author

ibc commented Feb 14, 2017

Also, we must check the current rules for filling the RtpListener's tables.

For example, I don't like the idea of allowing incoming packets with an unknown SSRC if an SSRC value was given for all the encodings in all the RtpReceivers sharing the same Transport. It makes difficult to find out browser bugs such as this one in Firefox Nightly 54.

@ibc
Copy link
Member Author

ibc commented Mar 27, 2017

Will eventually check JSEP stuff regarding "RTP matching rules", but no need to keep an issue open for it. Closing.

@ibc ibc closed this as completed Mar 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ibc