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
8.3 RTP matching rules and "packet_receiver" (bad word) #344
Comments
packet_receiver denotes an attribute whose value is the Would rtp_receiver work better? |
LGTM Also, not sure now if the spec mentions "attribute" but if so I think that "key" would fit better (an object/map/hash has "key/value" pairs rather than "attribute/value"). |
Let me a question: this issue is fixed in master, should it remain open? |
Once we have a PR in master we mark it as "PR exists". Next step is to close it if there is positive feedback on the PR (or at least no objections for a while). |
The PR is merged, that's why I expect this issue to be closed now. |
Section 8.3 mentions packet_receiver several times but, in fact, it means
RTCRtpReceiver
and I consider it confusing for the reader. IMHO it should useRTCRtpReceiver
or RTP receiver rather than packet_receiver.The text was updated successfully, but these errors were encountered: