- From: RFC Errata System <rfc-editor@rfc-editor.org>
- Date: Wed, 6 Jul 2022 13:33:31 -0700 (PDT)
- To: summerwind.jp@gmail.com, mt@lowentropy.net, cbenfield@apple.com
- Cc: rfc-ed@rfc-editor.org, iesg@ietf.org, ietf-http-wg@w3.org, iana@iana.org
The following errata report has been verified for RFC9113,
"HTTP/2".
--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7013
--------------------------------------
Status: Verified
Type: Editorial
Reported by: Moto Ishizawa <summerwind.jp@gmail.com>
Date Reported: 2022-07-06
Verified by: RFC Editor
Section: 6.1
Original Text
-------------
| Note: An endpoint that learns of stream closure after sending
| all data can close a stream by sending a STREAM frame with a
| zero-length Data field and the END_STREAM flag set. This is
| only possible if the endpoint does not send trailers, as the
| END_STREAM flag appears on a HEADERS frame in that case; see
| Section 8.1.
Corrected Text
--------------
| Note: An endpoint that learns of stream closure after sending
| all data can close a stream by sending a DATA frame with a
| zero-length Data field and the END_STREAM flag set. This is
| only possible if the endpoint does not send trailers, as the
| END_STREAM flag appears on a HEADERS frame in that case; see
| Section 8.1.
Notes
-----
Since STREAM frame is not defined in HTTP/2, I assume this is a DATA frame. This is probably a typo, possibly confused with the QUIC specification.
--------------------------------------
RFC9113 (draft-ietf-httpbis-http2bis-07)
--------------------------------------
Title : HTTP/2
Publication Date : June 2022
Author(s) : M. Thomson, Ed., C. Benfield, Ed.
Category : PROPOSED STANDARD
Source : HTTP
Area : Applications and Real-Time
Stream : IETF
Received on Wednesday, 6 July 2022 20:33:45 UTC