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

Reference to draft-ietf-rtcweb-fec #217

Closed
aboba opened this Issue Jun 21, 2015 · 0 comments

Comments

Projects
None yet
1 participant
@aboba
Copy link
Contributor

aboba commented Jun 21, 2015

Currently Section 9.1.1 says the following:

"Currently [RTP-USAGE] makes no recommendations relating to FEC mechanisms."

Proposal is to replace this with the following:

"[FEC] summarizes requirements relating to FEC mechanisms."

And to add the following to the informative references:

[FEC]
J. Uberti. WebRTC Forward Error Correction Requirements. 05 March 2015. Internet Draft (work in progress). URL: https://tools.ietf.org/html/draft-ietf-rtcweb-fec

robin-raymond pushed a commit that referenced this issue Jun 22, 2015

Robin Raymond
Addressed Philipp Hancke's review comments, as noted in: Issue #198
Added the "failed" state to RTCIceTransportState, as noted in: Issue #199
Added text relating to handling of incoming media packets prior to remote fingerprint verification, as noted in: Issue #200
Added a complete attribute to the RTCIceCandidateComplete dictionary, as noted in: Issue #207
Updated the description of RTCIceGatherer.close() and the "closed" state, as noted in: Issue #208
Updated Statistics API error handling to reflect proposed changes to the WebRTC 1.0 API, as noted in: Issue #214
Updated Section 10 (RTCDtmfSender) to reflect changes in the WebRTC 1.0 API, as noted in: Issue #215
Clarified state transitions due to consent failure, as noted in: Issue #216
Added a reference to [FEC], as noted in: Issue #217

@aboba aboba closed this Jun 24, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment