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

Support for RRID #727

Closed
aboba opened this issue Jul 19, 2017 · 3 comments
Closed

Support for RRID #727

aboba opened this issue Jul 19, 2017 · 3 comments
Labels

Comments

@aboba
Copy link
Contributor

aboba commented Jul 19, 2017

As noted in the following message, the RRID is necessary in order to support robustness (RTX/FEC) with simulcast:
https://www.ietf.org/mail-archive/web/mmusic/current/msg18035.html

How is the RRID set in an RtpSender/RtpReceiver?

@aboba
Copy link
Contributor Author

aboba commented Jul 26, 2017

The text suggests that for simulcast the RRID is mandatory-to-use, and that the RRID is set to the value of encodings[].rid. If we can assume that ORTC implementations support RRID according to the specification, there may not be a need to set the RRID in an RtpSender/RtpReceiver.

@aboba aboba added the question label Jul 26, 2017
@aboba
Copy link
Contributor Author

aboba commented Jul 26, 2017

Currently the rtpunhandled event provides the RID, but not the RRID:

dictionary RTCRtpUnhandledEventInit : EventInit {
DOMString muxId;
DOMString rid;
payloadtype payloadType;
unsigned long ssrc;
};

What if an unhandled FEC/RTX packet containing the RRID was received?

@aboba
Copy link
Contributor Author

aboba commented Aug 22, 2017

This is a corner case unlikely to be encountered within existing or planned implementations.

@aboba aboba closed this as completed Aug 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant