Need clarification on 'apt' parameter #539

Closed
ibc opened this Issue May 11, 2016 · 1 comment

Projects

None yet

3 participants

@ibc
Contributor
ibc commented May 11, 2016

In http://ortc.org/wp-content/uploads/2016/05/ortc.html#rtx-codec-capability*:

apt    As defined in [RFC4588], the associated payload type of the original stream being retransmitted.

Would I retrieve as many RTX codecs as media codecs for which RTX can apply? would those RTX capability codec include an apt parameter?

@aboba
Contributor
aboba commented May 11, 2016 edited

In the current specification, there will be as an RTX codec for each media codec to which it applies, with its own apt parameter, yes. I think this is also true for WebRTC 1.0.

@aboba aboba added the 1.1 label May 11, 2016
@aboba aboba added a commit that referenced this issue May 11, 2016
@aboba aboba Clarification on 'apt' parameter
Fix for Issue #539
b27b015
@aboba aboba added the PR exists label May 11, 2016
@aboba aboba added a commit to w3c/webrtc-pc that referenced this issue May 11, 2016
@aboba aboba Clarification on 'apt' parameter
Fix for Issue w3c/ortc#539 (filed against ORTC, but also applies to WebRTC 1.0).
0351e35
@aboba aboba referenced this issue in w3c/webrtc-pc May 11, 2016
Closed

Clarification on 'apt' parameter #631

@aboba aboba added a commit to w3c/webrtc-pc that referenced this issue May 16, 2016
@aboba aboba Clarification on 'apt' parameter
Fix for Issue w3c/ortc#539 (filed against ORTC, but also applies to WebRTC 1.0).

Rebase of PR #631
d8fe5f1
@aboba aboba added a commit to w3c/webrtc-pc that referenced this issue Aug 5, 2016
@aboba aboba Clarification on RTX in Codec Capabilities/Parameters
Fix for Issue w3c/ortc#539 (filed against ORTC, but also applies to WebRTC 1.0).

Rebase of PR #631
82e105c
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment