W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > January 2017

Re: [webrtc-pc] When is an RTCSctpTransport created and destroyed?

From: Peter Thatcher via GitHub <sysbot+gh@w3.org>
Date: Tue, 03 Jan 2017 17:47:16 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-270175594-1483465634-sysbot+gh@w3.org>
I agree that:

1.  The SctpTransport is created by setLocalDescription (like the 
other transports)

2.  Rejecting an m-line permanently stops an SctpTransport.

3.  A new port creates a new SCTP association and SctpTransport. 

4.  There is no reason to change a port of an existing SctpTransport.


As to the question of what happens when an m-line rejection closes an 
SctpTransport and then a second SctpTransport is created later, I 
don't see why the new SctpTransport can't have the same port.  Just 
like if you stopped an RtpTransceiver and created a new one with the 
same SSRCs.   As long as we don't have two SctpTransports at the same 
time with the same port, it shouldn't matter that the port is reused.

-- 
GitHub Notification of comment by pthatcherg
Please view or discuss this issue at 
https://github.com/w3c/webrtc-pc/issues/979#issuecomment-270175594 
using your GitHub account
Received on Tuesday, 3 January 2017 17:47:21 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 9 October 2019 15:14:51 UTC