Subject: Re: [quicwg/base-drafts] Avoid sending FINs on empty streams (#240)

From: MikkelFJ <[email-masked]>
Date: Wed, 26 Apr 2017 11:57:02 -0700

I have hinted at this elsewhere, but it is perhaps relevant to summarize in the this topic:

This can be handled by stating that a stream is initiated by one end-point and accepted by the other end point. A stream can be initiated as read-only or read/write, and a stream can be accepted as write-only or read/write. In read/write mode both directions must be FIN or RST_STREAM terminated. QUIC can then tear down a connection early and fail if assumptions are broken by when receiving data where none are expected. The application level protocol defines when a stream is initiated and accepted in either mode.

However, it would be simpler with uni-directional streams.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/240#issuecomment-297508194