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

Proposed updates to RTP processing #34

Merged
merged 1 commit into from Aug 31, 2017

Conversation

Projects
None yet
4 participants
@gloinul
Copy link
Contributor

gloinul left a comment

These changes works for me and provide improvements in clarity.

@fluffy
Copy link
Contributor

fluffy left a comment

Much of what is proposed here is written better than the existing text. However, given the extreme difficulty in getting to the current text, this would need very significant review with the many people that wrote the existing text before we change it.

SSRC, and the mapping will not be changed even if the same
SSRC is received with a different payload type. In other
Note that when using the payload type to associate RTP streams
with m= lines an RTP stream, identified by SSRC, will be mapped

This comment has been minimized.

@fluffy

fluffy Jul 20, 2017

Contributor

The confusion this causes is that implementers do not think m=lines are identified by SSRC. They point out there is no requirement for the SDP to have SSRC values in it at all.

This comment has been minimized.

@csperkins

csperkins Jul 20, 2017

Author Contributor

The RTP stream is identified by SSRC. That RTP stream is associated with an m= line.

The intent is to change "the SSRC is mapped to an m= line" to "the RTP stream identified by an SSRC is mapped to an m= line".

This comment has been minimized.

@cdh4u

cdh4u Jul 24, 2017

Owner

People have been informed about the PR. I am happy to give people some time to review the text, but then we need to move on. Also, Colin suggested the text on the list already back in April.

@cdh4u cdh4u merged commit 4d62eda into cdh4u:master Aug 31, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.