[ortc] Pull Request: Update RTCWEB-VIDEO reference to RFC7742
[ortc] Pull Request: Identity checks and media stream constraints
Closed: [ortc] RTCRtpSender and RTCRtpReceiver state
[ortc] Pull Request: Unset encodings in send()
[ortc] Pull Request: send() / receive() behaviour when RtpParameters has empty sequence of…
[ortc] Pull Request: Change log update
[ortc] Pull Request: RTCDataChannelParameters Issues
[ortc] RTCDataChannelParameters issues
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()
[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] Pull Request: Remove "null if unset"
[ortc] Use "required" attribute in specification
[ortc] Check all dictionary defaults vs unsets
Closed: [ortc] What does minQuality do, exactly?
[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?
[ortc] RTCRtpHeaderExtensionParameters parameters
[ortc] H264 caps vs params
[ortc] RTCRtpCodecParameters clock rate nullable?
[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?
[ortc] Pull Request: RTCDataChannel on a dead transport
[ortc] RTCDataChannel on a dead transport?
[ortc] RTCDtmfSender confusion
[ortc] Pull Request: RTCIceGathererIceErrorEvent hostCandidate
Closed: [ortc] Aggressive ICE nomination
[ortc] Merged Pull Request: Cleanup of the Codec and Encoding Parameter Example
[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] Pull Request: Fix examples
[ortc] Pull Request: Add RFC 5245bis and Trickle-ICE references
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
[ortc] RTCIceTransport description is "lacking"
[ortc] RTCIceGatherer closed state
[ortc] ongathererstatechange vs onstatechange
[ortc] RTCIceGathererIceErrorEvent hostCandidate
[ortc] Add "RTP Sending Rules" section
Closed: [ortc] Which ICE state if consent fails or TCP is disconnected?
Closed: [ortc] Same payload for different codecs in same RtpSender/RtpReceiver
[ortc] Pull Request: Check for invalid encodings usage
Is sending multiple audio codecs on same RTCRtpSender supported?
- Re: Is sending multiple audio codecs on same RTCRtpSender supported?
- RE: 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
[ortc] RTCRtpSender not checking media track state or identity constraints
[ortc] RTCRtpSender.setTransport may raise a IncompatibleMediaStreamTrackError due to identity check
[ortc] Wrong usage of RTCIceCredentialType enum in examples
[ortc] Wrong usage of RTCDtlsParameters dictionaries on examples
[ortc] Wrong usage of RTCIceGatherOptions dictionaries on examples
RTCRtpSender corner cases clarification
[ortc] Promises resolution not defined
Re: Issue 444: RTX APT capability?
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
[ortc] receive() rtcp.ssrc advice for implementations
[ortc] send() / receive() behaviour when RtpParameters has empty sequence of encodings specified
[ortc] Pull Request: Clarification on setting rtcp.ssrc
[ortc] Pull Request: Further clarifications on ssrc conflicts
[ortc] Pull Request: Update references
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
- 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
- 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
- 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] Upgrade [GROUPING] reference to rfc7656
[ortc] Move degradationPreference from RTCRtpParameters to
[ortc] Pull Request: Clarification of onssrconflict
[ortc] Pull Request: Change log updates
[ortc] Pull Request: Table of RTCRtpEncodingParameters
[ortc] Pull Request: Addition of apt capability to RTX
[ortc] Pull Request: CNAME clarification for RTCRtcpParameters
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
- Closed: [ortc] Change onssrcconflict event in RTCRtpSender by exception
- Closed: [ortc] Change onssrcconflict event in RTCRtpSender by exception