Friday, 29 April 2016
- [ortc] Merged Pull Request: Update RTCWEB-VIDEO reference to RFC7742
- [ortc] Pull Request: Update RTCWEB-VIDEO reference to RFC7742
- [ortc] Merged Pull Request: Identity checks and media stream constraints
- [ortc] Pull Request: Identity checks and media stream constraints
Thursday, 28 April 2016
- Re: ORTC CG vs WebRTC WG Issues
- Closed: [ortc] send() / receive() behaviour when RtpParameters has empty sequence of encodings specified
- Closed: [ortc] RTCRtpSender send should return a promise
- Closed: [ortc] Promises resolution not defined
- Closed: [ortc] RTCRtpSender and RTCRtpReceiver state
- Closed: [ortc] RTCDataChannelParameters issues
- [ortc] Merged Pull Request: Unset encodings in send()
- [ortc] Closed Pull Request: send() / receive() behaviour when RtpParameters has empty sequence of…
- [ortc] Pull Request: Unset encodings in send()
- [ortc] Merged Pull Request: Change log update
- [ortc] Merged Pull Request: RTCDataChannelParameters Issues
- [ortc] Merged Pull Request: Examples: async usage of send() and receive()
- [ortc] Merged Pull Request: Promise for send() and receive()
Wednesday, 27 April 2016
- Re: ORTC CG vs WebRTC WG Issues
- [ortc] Pull Request: send() / receive() behaviour when RtpParameters has empty sequence of…
- [ortc] Pull Request: Change log update
Tuesday, 26 April 2016
- Re: ORTC CG vs WebRTC WG Issues
- [ortc] Pull Request: RTCDataChannelParameters Issues
- [ortc] RTCDataChannelParameters issues
- Closed: [ortc] RTCRtpSender not checking media track state or identity constraints in constructor
- Closed: [ortc] RTCRtpSender.setTransport may raise a IncompatibleMediaStreamTrackError due to identity check
- Closed: [ortc] Split RTCRtpEncodingParameters in RTCRtpEncodingParameters and RTCRtpDecodingParameters
- Closed: [ortc] RTX APT capability?
- ORTC CG vs WebRTC WG Issues
- [ortc] Pull Request: Examples: async usage of send(), receive() and setTransport()
Monday, 25 April 2016
- [ortc] Pull Request: Promise for send(), receive() and setTransport()
- Closed: [ortc] Which RTCWeb RFCs/drafts apply to ORTC?
- Closed: [ortc] Behavior when encodings are not set
- Closed: [ortc] Ice gathering
- [ortc] Merged Pull Request: Change log update
- [ortc] Merged Pull Request: setTrack() operation different from replaceTrack() in WebRTC 1.0
- Closed: [ortc] RTCRtpReceiver.getCapabilities and feature codec "kind"
- [ortc] Merged Pull Request: getCapabilities and feature codec "kind"
- [ortc] Merged Pull Request: RTCRtpReceiver instance
- Closed: [ortc] RTCRtpCodecParameters clock rate nullable?
- [ortc] Merged Pull Request: RTCRtpCodecParameters clock rate nullable
- Closed: [ortc] H264 caps vs params
- Closed: [ortc] dictionary RTCDataChannelParameters id is null and other "null if unset"?
- [ortc] Merged Pull Request: Remove "null if unset"
- [ortc] Pull Request: Remove "null if unset"
- [ortc] Use "required" attribute in specification
- Closed: [ortc] RTCSctpTransport constructor nullable port?
- [ortc] Merged Pull Request: RTCSctpTransport constructor nullable port
- [ortc] Check all dictionary defaults vs unsets
- Closed: [ortc] RTCRtpEncodingParameters minQuality defaulted (and others)
- Closed: [ortc] What does minQuality do, exactly?
- [ortc] Merged Pull Request: Remove minQuality
- [ortc] Pull Request: Remove minQuality
- [ortc] Pull Request: setTrack() operation different from replaceTrack() in WebRTC 1.0
- [ortc] Pull Request: RTCDtlsTransport.onerror error.message
- [ortc] Pull Request: RTCRtpReceiver instance
- [ortc] Pull Request: getCapabilities and feature codec "kind"
- [ortc] Pull Request: RTCRtpCodecParameters clock rate nullable
- [ortc] Pull Request: Change log update
- [ortc] Pull Request: RTCSctpTransport constructor nullable port
- [ortc] RTCRtpEncodingParameters minQuality defaulted (and others)
- [ortc] RTCSctpTransport constructor nullable port?
- [ortc] dictionary RTCDataChannelParameters id is null?
Sunday, 24 April 2016
- [ortc] RTCRtpHeaderExtensionParameters parameters
- [ortc] H264 caps vs params
- [ortc] RTCRtpCodecParameters clock rate nullable?
Friday, 22 April 2016
- Closed: [ortc] RTCRtpContributingSource voiceActivityFlag
- [ortc] RTCRtpContributingSource voiceActivityFlag
- [ortc] RTCMediaStreamTrack.stop() from RTCRtpReceiver
- [ortc] RTCRtpReceiver.getCapabilities and feature codec "kind"
- [ortc] RTCRtpReceiver instance
- [ortc] RTCDtlsTransport.onerror error.message
- [ortc] RTCDtlsTransport.getRemoteParameters / DTCIceTransport.getRemoteParameters but not on sender / receiver?
- Closed: [ortc] RTCDataChannel on a dead transport?
- Closed: [ortc] RTCIceGathererIceErrorEvent hostCandidate
- [ortc] Merged Pull Request: RTCDataChannel on a dead transport
- [ortc] Merged Pull Request: RTCIceGathererIceErrorEvent hostCandidate
- [ortc] Pull Request: RTCDataChannel on a dead transport
Thursday, 21 April 2016
- [ortc] RTCDataChannel on a dead transport?
- [ortc] RTCDtmfSender confusion
- [ortc] Pull Request: RTCIceGathererIceErrorEvent hostCandidate
- Closed: [ortc] Aggressive ICE nomination
- Closed: [ortc] relatedPort on ICE candidate
- Closed: [ortc] ICE supper nitty - usernameFragment, etc
- [ortc] Merged Pull Request: Change log update
- [ortc] Merged Pull Request: Cleanup of the Codec and Encoding Parameter Example
- [ortc] Merged Pull Request: relatedPort on ICE candidate
- [ortc] Merged Pull Request: ICE nits
- [ortc] Pull Request: Change log update
- [ortc] Pull Request: relatedPort on ICE candidate
- [ortc] Pull Request: ICE nits
- [ortc] usernameFragment
- [ortc] relatedPort on ICE candidate
- [ortc] Merged Pull Request: Fix examples
Wednesday, 20 April 2016
- [ortc] Pull Request: Fix examples
- [ortc] Merged Pull Request: Add RFC 5245bis and Trickle-ICE references
- [ortc] Pull Request: Add RFC 5245bis and Trickle-ICE references
- Closed: [ortc] RTCIceTransport description is "lacking"
- [ortc] Merged Pull Request: Change log update
- [ortc] Merged Pull Request: RTCIceTransport description is "lacking"
- [ortc] Merged Pull Request: RTCIceGatherer closed state
- Closed: [ortc] RTCIceGatherer closed state
- Closed: [ortc] ongathererstatechange vs onstatechange
- [ortc] Merged Pull Request: ongathererstatechange vs onstatechange
- Closed: [ortc] Clarification on encodings codecPayloadType for RTCRtpSender
- Closed: [ortc] RtpSender.send() should just allow a single codec
- Closed: [ortc] SSRC values should not be entered by the user
- Closed: [ortc] RTCIceCandidateComplete dictionary
- Closed: [ortc] Name differences between ORTC and WebRTC 1.0
- [ortc] Pull Request: Change log update
- [ortc] Pull Request: RTCIceTransport description is "lacking"
- [ortc] Pull Request: ongathererstatechange vs onstatechange
- [ortc] Pull Request: RTCIceGatherer closed state
Tuesday, 19 April 2016
- [ortc] RTCIceTransport description is "lacking"
- [ortc] RTCIceGatherer closed state
- [ortc] ongathererstatechange vs onstatechange
- [ortc] RTCIceGathererIceErrorEvent hostCandidate
Monday, 18 April 2016
Saturday, 16 April 2016
- Re: Is sending multiple audio codecs on same RTCRtpSender supported?
- RE: Is sending multiple audio codecs on same RTCRtpSender supported?
- [ortc] Merged Pull Request: Check for invalid encodings usage
- Re: Is sending multiple audio codecs on same RTCRtpSender supported?
- Closed: [ortc] Which ICE state if consent fails or TCP is disconnected?
- Closed: [ortc] [Proposal] Add static RTCRtpParameters.factory() method
- Closed: [ortc] Same payload for different codecs in same RtpSender/RtpReceiver
Friday, 15 April 2016
- [ortc] Pull Request: Check for invalid encodings usage
- Is sending multiple audio codecs on same RTCRtpSender supported?
- [ortc] Clarification on behavior when codecPaloadType is unset on encoding
- [ortc] Clarification on encodings codecPayloadType for RTCRtpSender
- [ortc] RTCRtpSender send should return a promise
Thursday, 14 April 2016
Wednesday, 13 April 2016
- [ortc] RTCRtpSender not checking media track state or identity constraints
- [ortc] RTCRtpSender.setTransport may raise a IncompatibleMediaStreamTrackError due to identity check
- Re: Proposal: One media RTP packet stream (i.e. one SSRC) per RTCRtpSender/RTCRtpReceiver object
- Re: Proposal: One media RTP packet stream (i.e. one SSRC) per RTCRtpSender/RTCRtpReceiver object
- [ortc] Wrong usage of RTCIceCredentialType enum in examples
- [ortc] Wrong usage of RTCDtlsParameters dictionaries on examples
- [ortc] Wrong usage of RTCIceGatherOptions dictionaries on examples
- Re: Proposal: One media RTP packet stream (i.e. one SSRC) per RTCRtpSender/RTCRtpReceiver object
Tuesday, 12 April 2016
- Re: Proposal: One media RTP packet stream (i.e. one SSRC) per RTCRtpSender/RTCRtpReceiver object
- Re: Proposal: One media RTP packet stream (i.e. one SSRC) per RTCRtpSender/RTCRtpReceiver object
- Re: Proposal: One media RTP packet stream (i.e. one SSRC) per RTCRtpSender/RTCRtpReceiver object
- Re: Proposal: One media RTP packet stream (i.e. one SSRC) per RTCRtpSender/RTCRtpReceiver object
- Re: Proposal: One media RTP packet stream (i.e. one SSRC) per RTCRtpSender/RTCRtpReceiver object
- Re: Proposal: One media RTP packet stream (i.e. one SSRC) per RTCRtpSender/RTCRtpReceiver object
Monday, 11 April 2016
Friday, 8 April 2016
- Re: Proposal: One media RTP packet stream (i.e. one SSRC) per RTCRtpSender/RTCRtpReceiver object
- Re: Proposal: One media RTP packet stream (i.e. one SSRC) per RTCRtpSender/RTCRtpReceiver object
- Re: Issue 444: RTX APT capability?
- Re: Proposal: One media RTP packet stream (i.e. one SSRC) per RTCRtpSender/RTCRtpReceiver object
- Re: Issue 444: RTX APT capability?
Thursday, 7 April 2016
- Re: Issue 444: RTX APT capability?
- Re: Issue 444: RTX APT capability?
- Re: Proposal: One media RTP packet stream (i.e. one SSRC) per RTCRtpSender/RTCRtpReceiver object
- Re: Issue 456 (Move degradationPreference from RTCRtpParameters to RTCRtpEncodingParameters)
- Closed: [ortc] Unclear whether XxxTransport is really closed or not
- Closed: [ortc] RTPReceiver encoding parameters are useless
- Closed: [ortc] Change onssrcconflict event in RTCRtpSender by exception
- [ortc] Merged Pull Request: Further clarifications on ssrc conflicts
- [ortc] receive() rtcp.ssrc advice for implementations
- Closed: [ortc] Clarification on usage of ssrc value on RTCRtpReceiver
- [ortc] Merged Pull Request: Clarification on setting rtcp.ssrc
- [ortc] send() / receive() behaviour when RtpParameters has empty sequence of encodings specified
- Re: Proposal: One media RTP packet stream (i.e. one SSRC) per RTCRtpSender/RTCRtpReceiver object
- Re: Proposal: One media RTP packet stream (i.e. one SSRC) per RTCRtpSender/RTCRtpReceiver object
Wednesday, 6 April 2016
- [ortc] Pull Request: Clarification on setting rtcp.ssrc
- [ortc] Pull Request: Further clarifications on ssrc conflicts
- Closed: [ortc] Upgrade [GROUPING] reference to rfc7656
- [ortc] Merged Pull Request: Update references
- Closed: [ortc] Change onssrcconflict event in RTCRtpSender by exception
- Closed: [ortc] CNAME clarification for RTCRtcpParameters
- [ortc] Pull Request: Update references
Monday, 4 April 2016
- Proposal: One media RTP packet stream (i.e. one SSRC) per RTCRtpSender/RTCRtpReceiver object
- [ortc] Upgrade [GROUPING] reference to rfc7656
- [ortc] Move degradationPreference from RTCRtpParameters to
Friday, 1 April 2016
- [ortc] Merged Pull Request: Clarification of onssrconflict
- [ortc] Merged Pull Request: Change log updates
- [ortc] Merged Pull Request: Table of RTCRtpEncodingParameters
- [ortc] Pull Request: Clarification of onssrconflict
- [ortc] Pull Request: Change log updates
- [ortc] Pull Request: Table of RTCRtpEncodingParameters
- [ortc] Merged Pull Request: Addition of apt capability to RTX
- [ortc] Merged Pull Request: CNAME clarification for RTCRtcpParameters
- [ortc] Pull Request: Addition of apt capability to RTX
- [ortc] Pull Request: CNAME clarification for RTCRtcpParameters
- Re: Proposal: face meeting in Madrid
- Re: Proposal: face meeting in Madrid
- Re: Proposal: face meeting in Madrid
- Re: Proposal: face meeting in Madrid
- [ortc] CNAME clarification for RTCRtcpParameters
- [ortc] Clarification on usage of ssrc value on RTCRtpReceiver
- [ortc] Value of onssrcconflict event in RTCRtpSender
- [ortc] [Proposal] RtpSender setParameters(), getParameters() and send()