W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2016

Re: [Technical Errata Reported] RFC7540 (4636)

From: Barry Leiba <barryleiba@computer.org>
Date: Thu, 10 Mar 2016 06:56:55 +0000
Message-ID: <CALaySJJ_8hiGA6htqCZTsSNgAVfmyuz1Z6sM133OfN_nMUMphQ@mail.gmail.com>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: Mike Belshe <mike@belshe.com>, Roberto Peon <fenix@google.com>, Martin Thomson <martin.thomson@gmail.com>, Mark Nottingham <mnot@mnot.net>, melon198502@gmail.com, HTTP Working Group <ietf-http-wg@w3.org>
RFC Editor,
The submitter has sent a separate note saying that this is not an
error, but his misunderstanding, and he understands it on re-reading.
Will you please remove this errata report?

Thanks,
Barry


On Thu, Mar 10, 2016 at 2:46 AM, RFC Errata System
<rfc-editor@rfc-editor.org> wrote:
> The following errata report has been submitted for RFC7540,
> "Hypertext Transfer Protocol Version 2 (HTTP/2)".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=7540&eid=4636
>
> --------------------------------------
> Type: Technical
> Reported by: hongbo li <melon198502@gmail.com>
>
> Section: 5.1
>
> Original Text
> -------------
>
>
> Corrected Text
> --------------
>
>
> Notes
> -----
> The explanation about "reserved (remote)" stream state in section 5.1 makes me confused, I don't know whether sending a WINDOW_UPDATE frame in this state should be treated as PROTOCOL_ERROR or not.
>
> Maybe "Receiving any type of frame other than HEADERS, RST_STREAM, or PRIORITY on a stream in this state MUST be treated as a connection error (Section 5.4.1) of type PROTOCOL_ERROR" should be:
> Receiving any type of frame other than HEADERS,WINDOW_UPDATE, RST_STREAM, or PRIORITY on a stream in this state MUST be treated as a connection error (Section 5.4.1) of type PROTOCOL_ERROR.
>
> 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 (IESG)
> can log in to change the status and edit the report, if necessary.
>
> --------------------------------------
> RFC7540 (draft-ietf-httpbis-http2-17)
> --------------------------------------
> Title               : Hypertext Transfer Protocol Version 2 (HTTP/2)
> Publication Date    : May 2015
> Author(s)           : M. Belshe, R. Peon, M. Thomson, Ed.
> Category            : PROPOSED STANDARD
> Source              : Hypertext Transfer Protocol Bis APP
> Area                : Applications
> Stream              : IETF
> Verifying Party     : IESG
>
Received on Thursday, 10 March 2016 06:57:29 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 22 March 2016 12:47:11 UTC