From 0e216683cbc7cd8ffba8927158953d19081c7450 Mon Sep 17 00:00:00 2001 From: Mike Bishop Date: Fri, 16 Oct 2020 15:25:54 -0400 Subject: [PATCH 1/2] Clarify reserved frame streams --- draft-ietf-quic-http.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/draft-ietf-quic-http.md b/draft-ietf-quic-http.md index 56e5c490d7..64527ec81e 100644 --- a/draft-ietf-quic-http.md +++ b/draft-ietf-quic-http.md @@ -470,7 +470,8 @@ Header and trailer field sections are described in Sections 5.4 and 5.6 of Receipt of an invalid sequence of frames MUST be treated as a connection error of type H3_FRAME_UNEXPECTED ({{errors}}). In particular, a DATA frame before any HEADERS frame, or a HEADERS or DATA frame after the trailing HEADERS frame -is considered invalid. +is considered invalid. (Other frame types, especially unknown frame types, +might be permitted subject to their own rules; see {{extensions}}.) A server MAY send one or more PUSH_PROMISE frames ({{frame-push-promise}}) before, after, or interleaved with the frames of a response message. These @@ -1614,10 +1615,10 @@ a connection error of type H3_ID_ERROR. Frame types of the format `0x1f * N + 0x21` for non-negative integer values of N are reserved to exercise the requirement that unknown types be ignored -({{extensions}}). These frames have no semantics, and can be sent on any open -stream when application-layer padding is desired. They MAY also be sent on open -streams in connections where no data is currently being transferred. Endpoints -MUST NOT consider these frames to have any meaning upon receipt. +({{extensions}}). These frames have no semantics, and MAY be sent on any stream +where frames are allowed to be sent. This enables their use for +application-layer padding. Endpoints MUST NOT consider these frames to have any +meaning upon receipt. The payload and length of the frames are selected in any manner the implementation chooses. From cee2add1629d71b96928593d299bb13fbb16d025 Mon Sep 17 00:00:00 2001 From: Mike Bishop Date: Sun, 18 Oct 2020 22:35:39 -0400 Subject: [PATCH 2/2] Update draft-ietf-quic-http.md Co-authored-by: ianswett --- draft-ietf-quic-http.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/draft-ietf-quic-http.md b/draft-ietf-quic-http.md index 64527ec81e..a27f456fef 100644 --- a/draft-ietf-quic-http.md +++ b/draft-ietf-quic-http.md @@ -470,8 +470,8 @@ Header and trailer field sections are described in Sections 5.4 and 5.6 of Receipt of an invalid sequence of frames MUST be treated as a connection error of type H3_FRAME_UNEXPECTED ({{errors}}). In particular, a DATA frame before any HEADERS frame, or a HEADERS or DATA frame after the trailing HEADERS frame -is considered invalid. (Other frame types, especially unknown frame types, -might be permitted subject to their own rules; see {{extensions}}.) +is considered invalid. Other frame types, especially unknown frame types, +might be permitted subject to their own rules; see {{extensions}}. A server MAY send one or more PUSH_PROMISE frames ({{frame-push-promise}}) before, after, or interleaved with the frames of a response message. These