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.

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

Use an Unified Plan SDP instead of Plan B #5

Open
antonroman opened this issue Jul 26, 2018 · 2 comments
Open

Use an Unified Plan SDP instead of Plan B #5

antonroman opened this issue Jul 26, 2018 · 2 comments

Comments

@antonroman
Copy link
Contributor

The original SDP used for the post was generated by Chrome browser some years ago so it follows the Plan B specification. Maybe it could be good to use a new Unified version SDP as it is the only official one and Chrome/Chromium are adding support to it and will be the only one supported in the future.

@fippo
Copy link
Member

fippo commented Jul 26, 2018

well, the unified plan that ships in Chrome is actually a bastard thing as it has a=ssrc:12345 msid:something lines in addition to the standard a=msid.
We should/could update the example to explain that line though!

Also both Chrome and Firefox still have a=ssrc lines even though everyone said "lets not signal ssrcs" -- that turned out to be not very realistic :-)

@antonroman
Copy link
Contributor Author

:-) yes, you are right. Maybe a good option could be to use a reference SDP from draft-ietf-rtcweb-jsep. It would also be helpful to add the bastard lines Chrome and FF use (in different colors) letting the readers know that they are non-compliant with the draft in the explanation.
PS. very interesting your last Simulcast post by the way :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants