- From: Cory Benfield <cory@lukasa.co.uk>
- Date: Wed, 6 Jul 2022 13:41:00 +0100
- To: RFC Errata System <rfc-editor@rfc-editor.org>
- Cc: summerwind.jp@gmail.com, Martin Thomson <mt@lowentropy.net>, Cory Benfield <cbenfield@apple.com>, HTTP Working Group <ietf-http-wg@w3.org>
This looks correct to me: I propose verifying this one. On Wed, 6 Jul 2022 at 12:09, RFC Errata System <rfc-editor@rfc-editor.org> wrote: > > The following errata report has been submitted for RFC9113, > "HTTP/2". > > -------------------------------------- > You may review the report below and at: > https://www.rfc-editor.org/errata/eid7013 > > -------------------------------------- > Type: Editorial > Reported by: Moto Ishizawa <summerwind.jp@gmail.com> > > 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. > > Instructions: > ------------- > This erratum is currently posted as "Reported". If necessary, please > use "Reply All" to discuss whether it should be verified or > rejected. When a decision is reached, the verifying party > can log in to change the status and edit the report, if necessary. > > -------------------------------------- > 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 > Verifying Party : IESG >
Received on Wednesday, 6 July 2022 12:47:33 UTC