-
https://github.com/rtcweb-wg/jsep/issues/856 has some implications for webrtc-pc.
I think @henbos already identified the two places where this impacts things.
The spec says under set the associate…
fippo updated
5 years ago
-
There is a mismatch between how clients set up streams and how they communicate the created state. This is relevant to the case of Unified Plan and RIDs and is highlighted in the case of simulcast.
…
-
Just wondering if the simulcast video SDP m= section should signal the `CNAME` into it or not.
### Firefox
This is a video m= section with simulcast produced by Firefox:
```
m=video 5148…
-
In the RTCRTPSendParameters.encodings, the description is:
"A sequence containing parameters for RTP encodings of media"
In "getParameters", it says "encodings is populated based on the RIDs pre…
-
There is a long standing issue with large data channel messages in the existing API of RTCDataChannel. If I want to send a single message containing 1 GiB of data (for example a large file), I have to…
-
http://w3c.github.io/webrtc-pc/#dom-rtcdtlstransport
The attribute description is "The iceTransport attribute is the underlying transport that is used to send and receive packets. The underlying tr…
-
Planning on doing this Friday, Nov 9
-
Take this simplified SDP offer from a remote endpoint (in parts taken from [here](https://tools.ietf.org/html/draft-ietf-rtcweb-sdp-11#section-5.2.2.1):
```
v=0
o=- 20518 0 IN IP4 0.0.0.0
s=-
t=0…
fippo updated
5 years ago
-
The process for reusing an m-line is only referenced in the spec under addTrack:
http://w3c.github.io/webrtc-pc/#dom-rtcpeerconnection-addtrack
In particular, it's not referenced under addTransc…
-
[JSEP Section 5.2.1 and 5.2.2](https://tools.ietf.org/html/draft-ietf-rtcweb-jsep-24#section-5.2.1) says:
> - For each MediaStream that was associated with the transceiver when it was created via a…