We currently have multiple RTP/RTCP related issues with Pion. I would like to agree on a design that addresses all the issues. I worry if we address them all independently we might make a decision that makes things worse. I would like to achieve the following for each issue.
- Fix the issues
- Not break existing users
- Fix on by default. SettingEngine only benefits power users.
- Ensure design works for all features in the list
- Not break or add APIs (if possible). A new release is extremely expensive.
Issues
A RTX doesn't stop Pion from sending NACKs
pion/webrtc#3063
#317
RTX isn't enabled by default (users registering codecs, and not dedicated RTX)
pion/webrtc#3095
Congestion Controllers are hard to associate with a a PeerConnection
Congestion Controllers improvements
Add interceptor to aggregate CCFB reports
#300
GCC refactoring
#306
More? We have so many Interceptor related issues right now I am losing track :)
We currently have multiple RTP/RTCP related issues with Pion. I would like to agree on a design that addresses all the issues. I worry if we address them all independently we might make a decision that makes things worse. I would like to achieve the following for each issue.
Issues
A RTX doesn't stop Pion from sending NACKs
pion/webrtc#3063
#317
RTX isn't enabled by default (users registering codecs, and not dedicated RTX)
pion/webrtc#3095
Congestion Controllers are hard to associate with a a PeerConnection
Congestion Controllers improvements
Add interceptor to aggregate CCFB reports
#300
GCC refactoring
#306
More? We have so many Interceptor related issues right now I am losing track :)