public-ortc@w3.org from February 2016 by author

aboba via GitHub

• [ortc] STUN/TURN error codes (Monday, 29 February)
• [ortc] Pull Request: Change log updates (Monday, 29 February)
• [ortc] Pull Request: Garbage collection clarifications (Monday, 29 February)
• [ortc] RTCRtpSender and RTCRtpReceiver state (Monday, 29 February)
• [ortc] Merged Pull Request: Change log fix for Generic NACK Issue (Monday, 29 February)
• [ortc] Pull Request: For Generic NACK, RTCRtcpFeedback.parameter is unset (Monday, 29 February)
• [ortc] Pull Request: Clarification for Generic NACK (Monday, 29 February)
• [ortc] Pull Request: Add FEC/RTX/RED support to "RTP matching rules" (Monday, 29 February)
• [ortc] Merged Pull Request: Reference fixes (Monday, 29 February)
• [ortc] Pull Request: Reference fixes (Monday, 29 February)
• [ortc] Closed Pull Request: Typo fix in respec.js (Monday, 29 February)
• [ortc] Pull Request: Typo fix in respec.js (Monday, 29 February)
• [ortc] Merged Pull Request: Revert "RFC 7675 updates (was CONSENT reference)" (Monday, 29 February)
• [ortc] Pull Request: Revert "RFC 7675 updates (was CONSENT reference)" (Monday, 29 February)
• [ortc] Merged Pull Request: Revert "Reference updates" (Monday, 29 February)
• [ortc] Pull Request: Revert "Reference updates" (Monday, 29 February)
• [ortc] Merged Pull Request: RFC 7675 updates (was CONSENT reference) (Monday, 29 February)
• [ortc] Pull Request: RFC 7675 updates (was CONSENT reference) (Monday, 29 February)
• [ortc] Merged Pull Request: Reference updates (Monday, 29 February)
• [ortc] Pull Request: Reference updates (Monday, 29 February)
• Closed: [ortc] RTCRtpReceiver.getParameters() needed (Monday, 29 February)
• Closed: [ortc] DTMF Support (Monday, 22 February)
• [ortc] Pull Request: Required DTMF Tone Support (Monday, 22 February)
• [ortc] DTMF Support (Monday, 22 February)
• Closed: [ortc] level-asymmetry-allowed and profile-level-id capabilities and settings (Sunday, 21 February)
• Closed: [ortc] RTCIceGathererEvent needs url member (Sunday, 21 February)
• Closed: [ortc] encodingId syntax (Sunday, 21 February)
• Closed: [ortc] RangeError for resolutionScale < 1.0 (Sunday, 21 February)
• [ortc] Pull Request: level-asymmetry-allowed (Sunday, 21 February)
• [ortc] level-asymmetry-allowed and profile-level-id capabilities and settings (Saturday, 20 February)
• [ortc] Pull Request: Fix change logs (Tuesday, 16 February)
• [ortc] Pull Request: RangeError for resolutionScale < 1.0 (Tuesday, 16 February)
• [ortc] RangeError for resolutionScale < 1.0 (Tuesday, 16 February)
• [ortc] Pull Request: encodingId syntax (Tuesday, 16 February)
• Closed: [ortc] Something is wrong with document anchor links (Tuesday, 16 February)
• Closed: [ortc] What does RTCRtpEncodingParameters.active=false in a RtpReceiver? (Tuesday, 16 February)
• Closed: [ortc] Certificate checking (Tuesday, 16 February)
• [ortc] Merged Pull Request: Certificate checking (Tuesday, 16 February)
• [ortc] Pull Request: RTCIceGathererEvent needs url member (Tuesday, 16 February)
• [ortc] encodingId syntax (Thursday, 11 February)
• [ortc] Pull Request: Certificate checking (Sunday, 7 February)
• [ortc] Certificate checking (Thursday, 4 February)
• Closed: [ortc] RTCRtpParameters: unclear requirements (Wednesday, 3 February)
• [ortc] Pull Request: WebRTC 1.0 as normative reference (Wednesday, 3 February)
• [ortc] Merged Pull Request: RTCRtpParameters: requirements (Monday, 1 February)
• [ortc] Name differences between ORTC and WebRTC 1.0 (Monday, 1 February)

Bernard Aboba

• Re: Need SDP to ORTC good example code (Monday, 29 February)

Iñaki Baz Castillo

• Re: Need SDP to ORTC good example code (Monday, 29 February)
• Re: Need SDP to ORTC good example code (Monday, 29 February)
• Re: Need SDP to ORTC good example code (Monday, 29 February)
• Need SDP to ORTC good example code (Monday, 29 February)
• Re: [ortc] [non rtcp-mux pain] Doesn't RTCRtpReceiver belong to RTCDtlsTransport? (Tuesday, 2 February)

Iñaki Baz Castillo via GitHub

• Closed: [ortc] N rtpSenders sharing SSRC on same transport (Monday, 29 February)
• [ortc] N rtpSenders sharing SSRC on same transport (Monday, 29 February)
• Closed: [ortc] No .kind in RTCRtpCodecParameters? (Monday, 29 February)
• [ortc] RTCRtcpFeedback.parameter should be optional (Monday, 29 February)
• [ortc] No .kind in RTCRtpCodecParameters? (Monday, 29 February)
• [ortc] RTX and ssrc indication (Monday, 29 February)
• Closed: [ortc] [non rtcp-mux pain] Doesn't RTCRtpReceiver belong to RTCDtlsTransport? (Tuesday, 2 February)
• [ortc] [non rtcp-mux pain] Doesn't RTCRtpReceiver belong to RTCDtlsTransport? (Monday, 1 February)

Lennart Grahl via GitHub

• Closed: [ortc] Which RTCWeb RFCs/drafts apply to ORTC? (Saturday, 6 February)
• [ortc] Which RTCWeb RFCs/drafts apply to ORTC? (Thursday, 4 February)

Peter Thatcher

• Re: [ortc] [non rtcp-mux pain] Doesn't RTCRtpReceiver belong to RTCDtlsTransport? (Monday, 1 February)

Philipp Hancke

• Re: Need SDP to ORTC good example code (Monday, 29 February)

Philipp Hancke via GitHub

• [ortc] RTCIceGathererEvent needs url member (Friday, 12 February)

Robin Raymond via GitHub

• [ortc] Merged Pull Request: Add FEC/RTX/RED support to "RTP matching rules" (Monday, 29 February)
• [ortc] Merged Pull Request: Required DTMF Tone Support (Monday, 22 February)
• [ortc] Merged Pull Request: level-asymmetry-allowed (Sunday, 21 February)
• [ortc] Merged Pull Request: Fix change logs (Sunday, 21 February)
• [ortc] Merged Pull Request: RangeError for resolutionScale < 1.0 (Sunday, 21 February)
• [ortc] Merged Pull Request: encodingId syntax (Sunday, 21 February)
• [ortc] Merged Pull Request: RTCIceGathererEvent needs url member (Sunday, 21 February)
• [ortc] Merged Pull Request: WebRTC 1.0 as normative reference (Sunday, 7 February)

Victor Pascual Avila

• Re: Need SDP to ORTC good example code (Monday, 29 February)

Last message date: Monday, 29 February 2016 23:41:47 UTC