[quicwg/base-drafts] Streams start as "idle" (#778)

ekr <notifications@github.com> Mon, 18 September 2017 19:58 UTC

Date: Mon, 18 Sep 2017 12:58:36 -0700
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab5c0d9b91a95999756b73ae0e39e6be2ccca7766e92cf0000000115d7e76c92a169ce0f69f59b@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/778@github.com>
Subject: [quicwg/base-drafts] Streams start as "idle" (#778)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_59c0256c944da_7ca13fa5f870af3420144"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/FIE0t9-0MXWj2mJ_b5_n9DrCeCU>

There are two ways of thinking about streams:

1. All 2^32 streams exist but are in the IDLE state and transition to other states when messages are received/sent on them.
2. Streams are created when the aforementioned messages are received/sent.

The document is kind of agnostic on this, talking about them as being in IDLE (the state machine) but also talking about streams being created:

```
   A QUIC endpoint cannot reuse a Stream ID.  Streams MUST be created in
   sequential order.  Open streams can be used in any order.  Streams
```

I tend to think that it would be better to talk about streams being created and remove the IDLE state, but in any case it would be good if the draft were consistent.


-- 
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/778

[quicwg/base-drafts] Streams start as "idle" (#77… ekr
Re: [quicwg/base-drafts] Streams start as "idle" … ianswett
Re: [quicwg/base-drafts] Streams start as "idle" … Martin Thomson
Re: [quicwg/base-drafts] Streams start as "idle" … Martin Thomson