Thursday, 31 March 2016
- [ortc] Reverse RTCRtpSender<->RTCDtmfSender composition
- [ortc] RTPReceiver encoding parameters are useless
- Re: Proposal: face meeting in Madrid
- Re: Proposal: face meeting in Madrid
- Re: Proposal: face meeting in Madrid
Tuesday, 29 March 2016
- [ortc] RTX APT capability?
- Closed: [ortc] directionality of rtp headerextensions?
- [ortc] Merged Pull Request: directionality of rtp headerextensions
- Closed: [ortc] Regarding queued candidate events
- Closed: [ortc] RTCIceGatherPolicy harmonization with WebRTC
Sunday, 27 March 2016
- [ortc] Pull Request: directionality of rtp headerextensions
- Closed: [ortc] Changing ICE servers on an RtcIceGatherer
Saturday, 26 March 2016
Friday, 25 March 2016
- [ortc] Merged Pull Request: Cleanup the RTX/RED/FEC example
- [ortc] Pull Request: Cleanup the RTX/RED/FEC example
Monday, 21 March 2016
- Re: Issue 439: RtpSender.send() should just allow a single codec
- Re: Issue 438: SSRC values should not be entered by the user
- [ortc] Split RTCRtpEncodingParameters in RTCRtpEncodingParameters and RTCRtpDecodingParameters
- [ortc] RtpSender.send() should just allow a single codec
- [ortc] SSRC values should not entered by the user
Sunday, 20 March 2016
Saturday, 19 March 2016
Friday, 18 March 2016
- Re: Proposal: face meeting in Madrid
- Proposal: face meeting in Madrid
- Closed: [ortc] RTX apt vs PayloadType within RTCRtpRtxParameters
- Closed: [ortc] Methods that can return empty lists (and nullable attributes)
- [ortc] Merged Pull Request: RTX "apt" as a codec param, not encoding param
- [ortc] Merged Pull Request: Remove "public" from RTCIceGatherPolicy
- [ortc] Merged Pull Request: Empty sequences
Thursday, 17 March 2016
- Re: RED and FEC and RTX (and related questions!)
- RE: RED and FEC and RTX (and related questions!)
- [ortc] Pull Request: RTX "apt" as a codec param, not encoding param
- [ortc] RTX apt vs PayloadType within RTCRtpRtxParameters
- [ortc] Pull Request: Remove "public" from RTCIceGatherPolicy
Wednesday, 16 March 2016
- [ortc] Pull Request: Empty sequences
- [ortc] Methods that can return null (and attributes that can be null)
- Re: Issue 227: RTCIceCandidateComplete dictionary
- Re: Suggestion for changes to IceGatherer to make it possible to signal IceParameters without gathering
- [ortc] Merged Pull Request: Add gather() method
- [ortc] Merged Pull Request: add transport-cc
- [ortc] Pull Request: Add gather() method
- [ortc] Pull Request: add transport-cc
- Re: Issue 227: RTCIceCandidateComplete dictionary
- Closed: [ortc] Section 8.3: Matching Rules Issue
- Closed: [ortc] [RtpParameters] clockRate is per stream, not per codec
- Closed: [ortc] Datachannel's label and protocol should be USVString
- [ortc] Merged Pull Request: Datachannel's label and protocol are USVString
- [ortc] Pull Request: Datachannel's label and protocol are USVString
- [ortc] Datachannel's label and protocol should be USVString
Tuesday, 15 March 2016
- Closed: [ortc] Certificate API: getAlgorithm method
- [ortc] Merged Pull Request: Certificate API: getAlgorithm method
- Closed: [ortc] Receiver "kind" not known until calling receiver.receive()
- Closed: [ortc] RTX and ssrc indication
- Closed: [ortc] SctpTransport has no state or state change event
- Closed: [ortc] Header extension official list review
- Closed: [ortc] Feedback mechanisms - review this list
- [ortc] Pull Request: Certificate API: getAlgorithm method
- [ortc] Certificate API: getAlgorithm method
- [ortc] Merged Pull Request: SctpTransport state and state change event
- [ortc] Merged Pull Request: Add REMB to feedback messages
- [ortc] Merged Pull Request: Add abs-send-time extension
- [ortc] Merged Pull Request: Add to reference list
- [ortc] Merged Pull Request: RTX/RED/FEC example
- [ortc] Merged Pull Request: Multiple encodings can share the same SSRC
- [ortc] Pull Request: Add REMB to feedback messages
- [ortc] Pull Request: Add abs-send-time extension
- [ortc] Pull Request: SctpTransport state and state change event
- Re: Need SDP to ORTC good example code
- RTX/RED/FEC examples (simulcast!)
- [ortc] Pull Request: RTX/RED/FEC example
Sunday, 13 March 2016
- Closed: [ortc] STUN/TURN error codes
- Closed: [ortc] [RtpParameters] Spec should state that `codec.payloadType` must be unique
- Closed: [ortc] RTCRtpSender.send(...) kind issue
- [ortc] Merged Pull Request: Markup fixes
- [ortc] Pull Request: Markup fixes
- [ortc] Merged Pull Request: STUN/TURN error codes
- [ortc] Merged Pull Request: Payload Type Uniqueness
- [ortc] Merged Pull Request: Change log
- [ortc] Merged Pull Request: Header extension list
- [ortc] Merged Pull Request: RTCRtpSender.send(...) kind issue
- [ortc] Pull Request: Multiple encodings can share the same SSRC
Saturday, 12 March 2016
- [ortc] Pull Request: STUN/TURN error codes
- [ortc] Pull Request: Payload Type Uniqueness
- [ortc] Pull Request: Change log
- [ortc] Pull Request: Header extension list
- [ortc] Pull Request: RTCRtpSender.send(...) kind issue
- [ortc] RTCRtpSender.send(...) kind issue
- [ortc] Merged Pull Request: Receiver "kind" not known until calling receiver.receive()
- [ortc] Pull Request: Receiver "kind" not known until calling receiver.receive()
Friday, 11 March 2016
- [ortc] RTCRtpCodecCapability options vs parameters
- [ortc] Receiver "kind" not known until calling receiver.receive()
- [ortc] Feedback mechanisms - review this list
- [ortc] Header extension official list review
- Closed: [ortc] RRID support
- Re: RED and FEC and RTX (and related questions!)
Wednesday, 9 March 2016
Monday, 7 March 2016
- RE: [ortc] Same payload for different codecs in same RtpSender/RtpReceiver
- [ortc] Same payload for different codecs in same RtpSender/RtpReceiver
- Will your Community Group meet during TPAC 2016?
Sunday, 6 March 2016
Friday, 4 March 2016
- Re: RED and FEC and RTX (and related questions!)
- Re: RED and FEC and RTX (and related questions!)
- Re: RED and FEC and RTX (and related questions!)
- RED and FEC and RTX (and related questions!)
- Re: Mapping RTX in SDP to ORTC RtpParameters
- Re: Mapping RTX in SDP to ORTC RtpParameters
- Re: Mapping RTX in SDP to ORTC RtpParameters
- Re: Mapping RTX in SDP to ORTC RtpParameters
- Re: Mapping RTX in SDP to ORTC RtpParameters
- Re: Mapping RTX in SDP to ORTC RtpParameters
- Re: Mapping RTX in SDP to ORTC RtpParameters
- [ortc] [RtpParameters] Spec should state that `codec.payloadType` must be unique
- Re: Mapping RTX in SDP to ORTC RtpParameters
- [ortc] [RtpParameters] clockRate is per stream, not per codec
- Re: Mapping RTX in SDP to ORTC RtpParameters
- RE: Mapping RTX in SDP to ORTC RtpParameters
Thursday, 3 March 2016
Tuesday, 1 March 2016
- Closed: [ortc] RTCRtcpFeedback.parameter should be optional
- [ortc] Merged Pull Request: Change log updates
- [ortc] Merged Pull Request: Garbage collection clarifications
- [ortc] SctpTransport has no state or state change event
- [ortc] Merged Pull Request: For Generic NACK, RTCRtcpFeedback.parameter is unset