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

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

From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
Date: Tue, 24 Jan 2017 23:59:11 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-274978492-1485302350-sysbot+gh@w3.org>
@taylor-b In looking into the operation of the SctpTransport, it is 
helpful to understand things in a bit more detail.  Does the following
 make sense?

a. When an SctpTransport is created by setLocalDescription, the local 
port is allocated and can be determined from the SDP provided to 
setLocalDescription.  In ORTC this means that SctpTransport.port is 
non-null. 
b. If setRemoteDescription has been called prior to 
setLocalDescription, then when the SctpTransport is created, the 
remote port is known, and can be determined from the SDP provided to 
setRemoteDescription.  Therefore, the SctpTransport starts negotiating
 an SCTP association.  In ORTC, this implies that 
start(SctpCapabilities, remote.port) is called, and 
SctpTransport.state transitions from new to connecting and eventually,
 connected.
c. If setRemoteDescription has not been called prior to 
setLocalDescription, then when the SctpTransport is created the remote
 port is not known, and so when the SctpTransport is created it cannot
 begin to negotiate an SCTP association until setRemoteDescription is 
called. In ORTC this implies that SctpTransport.start is new.

-- 
GitHub Notification of comment by aboba
Please view or discuss this issue at 
https://github.com/w3c/webrtc-pc/issues/979#issuecomment-274978492 
using your GitHub account
Received on Tuesday, 24 January 2017 23:59:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 4 June 2019 15:32:41 UTC