-
Make sure that 4672-update says
At least one of the "a=fingerprint" lines for each certificate MUST have use the digest algorithm used in the certificate signature.
-
Hello,
there is an opened discussion in discuss-webrtc [1] in relation to which values should be used in "a=setup" attribute.
The main problem came from:
1. the text in RFC 5763 section-5 (Estab…
-
From Magnus Westerlund in IETF LC:
1. Section 8.1:
[I-D.martinsen-mmusic-ice-dualstack-fairness]
Martinsen, P., Reddy, T., and P. Patil, "ICE IPv4/IPv6
Dual Stack Fair…
-
The Trickle ICE draft has still an informative reference to a draft that has expired long ago and will not go forward since it became part of ICE-bis. Seems safe to remove.
https://mailarchive.ietf.or…
-
In WebRTC section 5.1, addTransceiver(), it says
'When setRemoteDescription is called with a corresponding remote description that is able to receive multiple RTP encodings as defined in [JSEP], the …
-
There are a number of questions that occur to me:
- Are changes to the parameters signaled to the other side? If so, which ones, and does onnegotiationneeded fire?
- How does content know when its pre…
-
When the SDP changes, including new trickle ICE candates, the sess-version needs to go up. Need to decide how to do this and add text to support.
See http://tools.ietf.org/html/rfc4566#section-5.1
-
In section 5.1 addTransceiver() it says
'When setRemoteDescription is called with a corresponding remote description that is able to receive multiple RTP encodings as defined in [JSEP], the RTCRtpSen…
-
I have reviewed this document in preparation for IETF last call. It is in good shape and I have requested the last call.
While the last call is ongoing, I would like to double-check that this documen…
-
According to BUNDLE draft, if the same payload value appears more than twice in m= lines belonging to the same BUNDLE group, then those codecs MUST be the very same.
Not yet completely clear what wou…