RTCDtlsTransport: Effect of calling start() after start()? #146
Calling IceTransport.start does a restart. We could do the same for
On Thu, Aug 21, 2014 at 10:03 AM, aboba firstname.lastname@example.org wrote:
The issue is with calling RTCDtlsTransport.start(newRemoteParameters).- a situation in which a new negotiation would be required (since the remote parameters have changed). For that case, returning without actually restarting negotiation with the requested remote parameters is probably not a good idea.
…3c#146 Address questions about RTCRtpCodecCapability.preferredPayloadType, as noted in: Issue w3c#147 Address questions about RTCRtpSender.setTrack() error handling, as noted in: Issue w3c#148 Partially address 'automatic' use of scalable video coding (in RTCRtpReceiver.receive()) as noted in: Issue w3c#149 Renamed RTCIceListener to RTCIceGatherer as noted in: Issue w3c#150 Added text on multiplexing of STUN, TURN, DTLS and RTP/RTCP, as noted in: Issue w3c#151 Address issue with queueing of candidate events within the RTCIceGatherer, as noted in: Issue w3c#152 Clarify behavior of RTCRtpReceiver.getCapabilities(kind), as noted in: Issue w3c#153