- From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
- Date: Thu, 28 Sep 2017 21:31:19 +0000
- To: public-webrtc-logs@w3.org
JSEP actually does call out this case of the answerer changing the SCTP port:
```
If an SCTP association exists, and the remote SCTP port has
changed, discard the existing SCTP association. This includes
the case when the PeerConnection state is "have-remote-
pranswer".
```
So maybe we should reconsider marking this as CR-blocking.
The issue occurs when the SCTP port and TLS ID are changing due to a call being transitioned to a new remote endpoint (which is why "pranswer" would be used). But there's a chance the new endpoint uses the same SCTP port number as the previous endpoint. In which case the WebRTC endpoint would just see its SCTP association close, and would need to do a re-offer to establish the new association.
--
GitHub Notification of comment by taylor-b
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1612#issuecomment-332969704 using your GitHub account
Received on Thursday, 28 September 2017 21:31:11 UTC