Re: [quicwg/base-drafts] http-core and Friends (#3513)

[Mark Nottingham <[e-mail]>]

mnot requested changes on this pull request.

I've reviewed the diffs, not the changes in situ.

>  Because HPACK {{?HPACK=RFC7541}} relies on in-order transmission of compressed
-header blocks (a guarantee not provided by QUIC), HTTP/3 replaces HPACK with
+field blocks (a guarantee not provided by QUIC), HTTP/3 replaces HPACK with

"field sections" is the term of art - see https://httpwg.org/http-core/draft-ietf-httpbis-semantics-latest.html#header.fields
```suggestion
field sections (a guarantee not provided by QUIC), HTTP/3 replaces HPACK with
```

>  
 ## Discovering an HTTP/3 Endpoint {#discovery}
 
 An HTTP origin advertises the availability of an equivalent HTTP/3 endpoint via
-the Alt-Svc HTTP response header field or the HTTP/2 ALTSVC frame
+the Alt-Svc HTTP response field or the HTTP/2 ALTSVC frame

AIUI Alt-Svc is a header field, so this is fine either way.

>  
-Just as in previous versions of HTTP, header field names are strings of ASCII
+Just as in previous versions of HTTP, field names are strings of ASCII

Hm. It's not _all_ ASCII characters.

>  characters that are compared in a case-insensitive fashion.  Properties of HTTP
-header field names and values are discussed in more detail in Section 3.2 of
-{{!RFC7230}}, though the wire rendering in HTTP/3 differs.  As in HTTP/2, header
-field names MUST be converted to lowercase prior to their encoding.  A request
-or response containing uppercase header field names MUST be treated as
-malformed ({{malformed}}).
+field names and values are discussed in more detail in Section 4.3 of
+{{!SEMANTICS}}.  As in HTTP/2, field names MUST be converted to lowercase prior
+to their encoding.  A request or response containing uppercase field names MUST

```suggestion
to their encoding.  A request or response containing uppercase characters in field names MUST
```

>  QPACK [QPACK].  QPACK uses separate unidirectional streams to modify and track
-header table state, while header blocks refer to the state of the table without
+field table state, while field blocks refer to the state of the table without

```suggestion
field table state, while field sections refer to the state of the table without
```

>  
-Like HTTP/2, HTTP/3 does not use the Connection header field to indicate
-connection-specific header fields; in this protocol, connection-specific
-metadata is conveyed by other means.  An endpoint MUST NOT generate an HTTP/3
-message containing connection-specific header fields; any message containing
-connection-specific header fields MUST be treated as malformed ({{malformed}}).
+Like HTTP/2, HTTP/3 does not use the Connection field to indicate

Again, it's perfectly OK to call it a "header field" if it hasn't said it can be used in trailers.

>  
-Like HTTP/2, HTTP/3 does not use the Connection header field to indicate
-connection-specific header fields; in this protocol, connection-specific
-metadata is conveyed by other means.  An endpoint MUST NOT generate an HTTP/3
-message containing connection-specific header fields; any message containing
-connection-specific header fields MUST be treated as malformed ({{malformed}}).
+Like HTTP/2, HTTP/3 does not use the Connection field to indicate
+connection-specific fields; in this protocol, connection-specific metadata is
+conveyed by other means.  An endpoint MUST NOT generate an HTTP/3 message

```suggestion
conveyed by other means.  An endpoint MUST NOT generate an HTTP/3 field section
```

>  
-#### Pseudo-Header Fields
+#### Pseudo-Fields

There are not pseudo-trailer fields, and I fervently hope we won't be defining any. Let's just keep it as pseudo-header.

>  
-To allow for better compression efficiency, the cookie header field {{!RFC6265}}
-MAY be split into separate header fields, each with one or more cookie-pairs,
-before compression. If a decompressed header list contains multiple cookie
-header fields, these MUST be concatenated into a single octet string using the
-two-octet delimiter of 0x3B, 0x20 (the ASCII string "; ") before being passed
-into a context other than HTTP/2 or HTTP/3, such as an HTTP/1.1 connection, or a
+To allow for better compression efficiency, the "Cookie" field {{!RFC6265}} MAY
+be split into separate field lines, each with one or more cookie-pairs, before
+compression. If a decompressed field list contains multiple cookie field lines,

```suggestion
compression. If a decompressed field section contains multiple cookie field lines,
```

>  
 A request or response that includes a payload body can include a
-`content-length` header field.  A request or response is also malformed if the
-value of a content-length header field does not equal the sum of the DATA frame
-payload lengths that form the body.  A response that is defined to have no
-payload, as described in Section 3.3.2 of {{!RFC7230}} can have a non-zero
-content-length header field, even though no content is included in DATA frames.
+`content-length` field.  A request or response is also malformed if the value of

Again, C-L is very definitely a header field; it cannot appear in a trailer.

> @@ -809,7 +809,7 @@ using the same format described for responses in {{request-response}}.
 Due to reordering, push stream data can arrive before the corresponding
 PUSH_PROMISE frame.  When a client receives a new push stream with an
 as-yet-unknown Push ID, both the associated client request and the pushed
-request headers are unknown.  The client can buffer the stream data in
+request fields are unknown.  The client can buffer the stream data in

Can you push request trailers?

>  
 ~~~~~~~~~~  drawing
  0                   1                   2                   3
  0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                          Push ID (i)                        ...
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
-|                       Header Block (*)                      ...
+|                        Field Block (*)                      ...

See previous comments about Block v Section.

-- 
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/pull/3513#pullrequestreview-373968241