Friday, 27 June 2014
- Issue 116: Retrieving RTCRtpParameters
- Re: Issue 101: Section 3: ICE Transport
- Re: Issue 101: Section 3: ICE Transport
- Re: Issue 102: Section 4: ICE Transport Controller
- Re: Issue 115: Restart method needed for the ICE Listener?
- Re: Issue 100: Section 2: DTLS Transport Issues
- Re: Issue 113: Section 9.7: RTCRtpCodecParameters
- Re: Issue 115: Restart method needed for the ICE Listener?
- Re: Issue #112: Does BUNDLE work in ORTC API?
Thursday, 26 June 2014
- Re: Issue 110: Temporal Scalability
- Re: Issue 115: Restart method needed for the ICE Listener?
- Issue 115: Restart method needed for the ICE Listener?
Wednesday, 25 June 2014
- Issue 114: Identity Assertions and RTCDtlsTransport objects
- Issue 113: Section 9.7: RTCRtpCodecParameters
- Issue 112: BUNDLE: Does it work in ORTC?
- Issue 100: Section 2: DTLS Transport Issues
- Issue 101: Section 3: ICE Transport
- Issue 102: Section 4: ICE Transport Controller
- Issue 103: RTCRtpSender and RTCRtpReceiver
- Issue 104: Section 9.8: RTCRtpEncodingParameters
- Issue 105: Section 1: ICE Transport Controller not in Big Picture
- Issue 106: RTCRtpParameter defaults?
- Issue 107: Section 4: Behavior of RTCIceTransportController.addTransport
- Issue 108: Section 9.4: multiStreamSupport
- Issue 108: Section 9.4: multiStreamSupport
- Issue 109: Sections 9.4 & 9.8: Quality-related parameters
- Issue 110: Temporal Scalability
- Issue 111: Section 11.3: RTCDataChannel: Promise send
Tuesday, 24 June 2014
Monday, 23 June 2014
Friday, 20 June 2014
- Re: CNAME use
- RE: Issue #78: IdP
- Re: CNAME use
- Issue #104: Section 9.8: RTCRtpEncodingParameters
- Issue #103: RTCRtpSender and RTCRtpReceiver
- Issue #102: Section 4, ICE Transport Controller
- Issue 101: ICE Transport Issues
- Issue #100: DTLS Transport Issues
- Issue 98: NITs
- RE: RTCRtpParameter defaults?
Wednesday, 18 June 2014
Tuesday, 17 June 2014
- RTCP parameters, per-codec header extension parameters, and max layer capibilities
- Re: Proposed Resolution: Removal of the createParameter and filterParameter functions
Monday, 16 June 2014
- Re: Proposed Resolution: Removal of the createParameter and filterParameter functions
- Re: Proposed Resolution: Removal of the createParameter and filterParameter functions
- Re: RTCRtpParameter defaults?
- Re: RTCRtpParameter defaults?
- Re: Proposed Resolution to Issue #84: Capabilities and Settings
- Re: Proposed Resolution: Removal of the createParameter and filterParameter functions
- Re: Latest editor's draft + last call
Sunday, 15 June 2014
Friday, 13 June 2014
- RTCRtpParameter defaults?
- Support for non-multiplexed RTP and RTCP
- Proposed Resolution to Issue #84: Capabilities and Settings
- Proposed Resolution: Removal of the createParameter and filterParameter functions
Tuesday, 10 June 2014
- Re: ORTC CG Meeting - June 26
- Re: Issue 80: filterParameters
- Re: Issue 80: filterParameters
- Re: ORTC CG Meeting - June 26
- Re: Issue 80: filterParameters
- Re: Issue 80: filterParameters
- Re: ORTC CG Meeting - June 26
Monday, 9 June 2014
- Re: ORTC CG Meeting - June 26
- Re: ORTC CG Meeting - June 26
- Re: ORTC CG Meeting - June 26
- Re: ORTC CG Meeting - June 26
- Re: ORTC CG Meeting - June 26
Friday, 6 June 2014
Thursday, 5 June 2014
Wednesday, 4 June 2014
- Re: A proposal for solving non-muxed RTCP *and* ICE freezing
- Re: ORTC CG Meeting - June 26
- Examples without filterParameters and createParameters
- Issue 95: onerror eventhandlers
- Issue 95: onerror eventhandlers
- Re: A proposal for solving non-muxed RTCP *and* ICE freezing
- Re: A proposal for solving non-muxed RTCP *and* ICE freezing