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

[ortc] RTCQuicStreamState: Definitions and implications for Readable and Writeable

From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
Date: Mon, 23 Oct 2017 20:33:22 +0000
To: public-ortc@w3.org
Message-ID: <issues.opened-267807845-1508790801-sysbot+gh@w3.org>
aboba has just created a new issue for https://github.com/w3c/ortc:

== RTCQuicStreamState: Definitions and implications for Readable and Writeable ==
We have combined the half-closed-remote and half-closed-local states from the QUIC transport document into a single "closing" state.  Also, we have both finish and reset methods.  Some questions: 

1. Does receipt of a STREAM frame with the  FIN bit set automatically cause the RTCQuicStream object to send a STREAM frame with the FIN bit set in reply?  Or does this not happen until the local peer calls finish()?

2. Does receipt of a STREAM frame with the FIN bit set affect either the Readable or Writeable slots on the local peer? 

3. Does receipt of a RST_STREAM frame automatically cause the RTCQuicStream object to send a RST_STREAM frame in reply?

4. Does receipt of a RST_STREAM frame cause both the Readable and Writeable slots on the local peer to be set to false? 

5. Calling reset() causes both the Readable and Writeable slots to transition to false, correct?

6. Calling finish() causes the Writeable slot to transition to false, but does not affect the Readable slot on the local peer, correct? 

Please view or discuss this issue at https://github.com/w3c/ortc/issues/788 using your GitHub account
Received on Monday, 23 October 2017 20:33:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:40:01 UTC