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

[webrtc-pc] Data channel closing procedure

From: Lennart Grahl via GitHub <sysbot+gh@w3.org>
Date: Fri, 15 Dec 2017 15:32:48 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-282463148-1513351967-sysbot+gh@w3.org>
lgrahl has just created a new issue for https://github.com/w3c/webrtc-pc:

== Data channel closing procedure ==
The [data channel closing procedure](https://rawgit.com/w3c/webrtc-pc/master/webrtc.html#data-transport-closing-procedure) lacks information how implementations should gracefully close data channels. It only mentions:

> An RTCDataChannel object's underlying data transport may be torn down in a non-abrupt manner by running the closing procedure. When that happens the user agent must, unless the procedure was initiated by the close method, queue a task that sets the object's [[ReadyState]] slot to closing. This will eventually render the data transport closed.

As far as I can see, that is the whole closing procedure description the `close` method references, too.

We need to add a few detailed steps and should probably reference [draft-ietf-rtcweb-data-cannel, section 6.7](https://tools.ietf.org/html/draft-ietf-rtcweb-data-channel-13#section-6.7) which describes how a data channel can be closed gracefully.

Related bug in Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1413198

---

I'm also confused by the following statement of the closing procedure:

> [...] This will eventually render the data transport closed.

I don't believe that's actually true. Why would that be the case? Only the data channel will be closed, not the transport.

---

Mention: @taylor-b 

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1699 using your GitHub account
Received on Friday, 15 December 2017 15:32:55 UTC

This archive was generated by hypermail 2.3.1 : Friday, 15 December 2017 15:32:56 UTC