From 0cd5e806dd78446a7ace1a093cc333882514a37a Mon Sep 17 00:00:00 2001 From: Martin Thomson Date: Thu, 20 Apr 2017 15:29:43 +1000 Subject: [PATCH] Add STREAM_ID_NEEDED frame analogous to BLOCKED --- draft-ietf-quic-transport.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index cdb7d6fceb..4f9d56b3d6 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -791,6 +791,7 @@ explained in more detail as they are referenced later in the document. | 0x07 | PING | {{frame-ping}} | | 0x08 | BLOCKED | {{frame-blocked}} | | 0x09 | STREAM_BLOCKED | {{frame-stream-blocked}} | +| 0x0a | STREAM_ID_NEEDED | {{frame-stream-id-needed}} | | 0xa0 - 0x7f | ACK | {{frame-ack}} | | 0xc0 - 0xff | STREAM | {{frame-stream}} | {: #frame-types title="Frame Types"} @@ -1786,6 +1787,14 @@ Stream ID: : A 32-bit unsigned number indicating the stream which is flow control blocked. +## STREAM_ID_NEEDED Frame {#frame-stream-id-needed} + +A sender sends a STREAM_ID_NEEDED frame (type=0x0a) when it wishes to open a +stream, but is unable to due to the maximum stream ID limit. + +The STREAM_ID_NEEDED frame does not contain a payload. + + ## RST_STREAM Frame {#frame-rst-stream} An endpoint may use a RST_STREAM frame (type=0x01) to abruptly terminate a