Harald Alvestrand
Harald Alvestrand
Proposal seems good to me. (with the proviso that we should read it as "or any implementation that has the same result", but that's implicit).
For logical consistency, I think it's the SctpTransport that should have a strong reference to the data channels it carries, not the RTCPeerConnection. But the RTCPeerConnection should have a strong...
The needed modification is to modify PR #2390 to not remove the language that deals with non-origin-clean tracks.
If one end does max-bundle and the other does must-bundle, will they interoperate?
I'll vote :laughing: for obvious reasons :-) - no DTLS? Just Say No!
In practice, people use single-character RIDs, because anything bigger bloats the RTP header. (We also had an issue with the size of MID, which ended up recommending 16 bytes maximum,...
I am worried about 7. In particular, if the offer is 1,2,3 and the answer is 1,foo,2, exactly what is being removed? If we want to be lenient, I would...
the URL specified in https://datatracker.ietf.org/doc/html/rfc7065#section-3.1 explicitly does not allow a path component. I don't know if the URL spec parse algorithm has an argument to it that says "fail if...
Note: the browsers do have a parser for TURN URL parsing; for Chrome, it is https://source.chromium.org/chromium/chromium/src/+/main:third_party/webrtc/pc/ice_server_parsing.cc;drc=65c9257f1777731d6d0669598f6fe6fe65fa61d3;l=149?q=webrtc::ParseIceServers&ss=chromium
Note: the generated version seemed to have a number of respec errors. Those probably need to be hunted down during the merge process.