[quicwg/base-drafts] GOAWAY with StreamID == 0 (#1717)

Luca Niccolini <notifications@github.com> Thu, 30 August 2018 02:05 UTC

Date: Wed, 29 Aug 2018 19:05:43 -0700
From: Luca Niccolini <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abe6b9f48dc838b3e544b7726ac0f9b2753051a3a892cf00000001179f12f792a169ce152ee999@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1717@github.com>
Subject: [quicwg/base-drafts] GOAWAY with StreamID == 0 (#1717)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b8750f76de0d_acf3fccfbad45b4599bc"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/DnADv_iuXDSTdBbSxhnwCF0RqD8>

The current text says about the StreamID in the GOAWAY frame definition:

> This identifier ... MAY be zero if no requests were processed.


With the latest transport changes, stream 0 is now a valid bidirectional stream, so GOAWAY(0) actually means that stream 0 is accepted/could be opened.
This opens up a case where an endpoint cannot know for sure whether the remote endpoint has accepted stream 0 or not.

If you agree this is an issue, I see two options to fix this: 
one is to add a flag to the GOAWAY frame that identify this particular case; 
another one is to slightly change the GOAWAY semantics to say that StreamID is the id of the last client-initiated stream plus one, i.e. the endpoint agree that any stream with ID >= StreamID was not accepted.

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

[quicwg/base-drafts] GOAWAY with StreamID == 0 (#… Luca Niccolini
Re: [quicwg/base-drafts] GOAWAY with StreamID == … Martin Thomson
Re: [quicwg/base-drafts] GOAWAY with StreamID == … Mike Bishop