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

Re: [webrtc-pc] No way to tell when SCTP association is closed

From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
Date: Mon, 02 Oct 2017 17:57:46 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-333613631-1506967052-sysbot+gh@w3.org>
I tried to summarize it in my previous comment; what part specifically needs more clarity?

Also, my reason for preferring an `RTCSctpTransport` state change as opposed to `negotiationneeded`:

> I'd prefer [an `RTCSctpTransport` state change event], because there also may be corner cases where the SCTP association is closed for some other reason [(besides this call forking scenario)], and renegotiating won't help. So better to let the application decide, given what it knows about the call topology. Plus, the state change event is already there in ORTC. 

And the `RTCDataChannel` events don't completely work, because they don't distinguish between an individual SCTP stream being closed and the whole association being closed.

-- 
GitHub Notification of comment by taylor-b
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1612#issuecomment-333613631 using your GitHub account
Received on Monday, 2 October 2017 17:57:36 UTC

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