- From: aboba via GitHub <sysbot+gh@w3.org>
- Date: Fri, 23 Dec 2016 18:15:31 +0000
- To: public-webrtc-logs@w3.org
@taylor-b I'd assume that the SctpTransport is created/destroyed at the same time that the DtlsTransport is created/destroyed. 1. My assumption has been that for both the Offerer and Answerer the local DtlsTransport/SctpTransport is created by calling setLocalDescription. 2. I'd assume that there was no SctpTransport created on the Answering side (since the section was rejected). On the Offering side, an SctpTransport was created. If it is permanently stopped by the rejection, then application of another offer would presumably create a new SctpTransport. Would the port also change in that situation? 3. I would also lean toward creating a new SCTP association in this case. 4. I don't think there's a need to change the port on an existing SctpTransport. -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/979#issuecomment-269027073 using your GitHub account
Received on Friday, 23 December 2016 18:15:32 UTC