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

[Editorial Errata Reported] RFC7540 (4647)

From: RFC Errata System <rfc-editor@rfc-editor.org>
Date: Tue, 29 Mar 2016 01:19:58 -0700 (PDT)
To: mike@belshe.com, fenix@google.com, martin.thomson@gmail.com, barryleiba@computer.org, mnot@mnot.net
Cc: jingzl@microsoft.com, ietf-http-wg@w3.org, rfc-editor@rfc-editor.org
Message-Id: <20160329081958.27C7F180004@rfc-editor.org>
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=4647

--------------------------------------
Type: Editorial
Reported by: Jessie Liu <jingzl@microsoft.com>

Section: Global

Original Text
-------------
 open:
      A stream in the "open" state may be used by both peers to send
      frames of any type.  In this state, sending peers observe
      advertised stream-level flow-control limits (Section 5.2).

-----------------------------------

   The entries in the following table are registered by this document.

   +---------------+------+--------------+
   | Frame Type    | Code | Section      |
   +---------------+------+--------------+
   | DATA          | 0x0  | Section 6.1  |
   | HEADERS       | 0x1  | Section 6.2  |
   | PRIORITY      | 0x2  | Section 6.3  |
   | RST_STREAM    | 0x3  | Section 6.4  |
   | SETTINGS      | 0x4  | Section 6.5  |
   | PUSH_PROMISE  | 0x5  | Section 6.6  |
   | PING          | 0x6  | Section 6.7  |
   | GOAWAY        | 0x7  | Section 6.8  |
   | WINDOW_UPDATE | 0x8  | Section 6.9  |
   | CONTINUATION  | 0x9  | Section 6.10 |
   +---------------+------+--------------+

Corrected Text
--------------
 open:
      A stream in the "open" state MAY be used by both peers to send
      frames of any type.  In this state, sending peers observe
      advertised stream-level flow-control limits (Section 5.2).

-----------------------------------

   The entries in the following table are registered by this document.

   +---------------+------+----------------+
   | Frame Type    | Code | Specification |
   +---------------+------+----------------+
   | DATA          | 0x0  | Section 6.1  |
   | HEADERS       | 0x1  | Section 6.2  |
   | PRIORITY      | 0x2  | Section 6.3  |
   | RST_STREAM    | 0x3  | Section 6.4  |
   | SETTINGS      | 0x4  | Section 6.5  |
   | PUSH_PROMISE  | 0x5  | Section 6.6  |
   | PING          | 0x6  | Section 6.7  |
   | GOAWAY        | 0x7  | Section 6.8  |
   | WINDOW_UPDATE | 0x8  | Section 6.9  |
   | CONTINUATION  | 0x9  | Section 6.10 |
   +---------------+------+--------------+

Notes
-----
2 editorial issues in section 5.1 and section 11.2.

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 Tuesday, 29 March 2016 08:20:56 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 29 March 2016 08:21:00 UTC