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

[Lucas Pardue <[e-mail]>]

LPardue commented on this pull request.



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

Do we need to make this change? The requirement is that they MUST NOT appear in trailers

>  
-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
+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
 header fields, these MUST be concatenated into a single octet string using the

```suggestion
fields, these MUST be concatenated into a single octet string using the
```

> @@ -1193,8 +1194,8 @@ connection error ({{errors}}) of type H3_FRAME_UNEXPECTED.
 
 ### HEADERS {#frame-headers}
 
-The HEADERS frame (type=0x1) is used to carry a header block, compressed using
-QPACK. See [QPACK] for more details.
+The HEADERS frame (type=0x1) is used to carry a block of HTTP fields, compressed
+using QPACK. See [QPACK] for more details.
 
 ~~~~~~~~~~  drawing
  0                   1                   2                   3

the diagram still contains "Header Block"

> @@ -1387,7 +1388,7 @@ error of type H3_SETTINGS_ERROR.
 ### PUSH_PROMISE {#frame-push-promise}
 
 The PUSH_PROMISE frame (type=0x5) is used to carry a promised request header
-set from server to client on a request stream, as in HTTP/2.
+field set from server to client on a request stream, as in HTTP/2.
 
 ~~~~~~~~~~  drawing
  0                   1                   2                   3

the diagram still contains "Header Block"

-- 
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-373234297