- From: RFC Errata System <rfc-editor@rfc-editor.org>
- Date: Thu, 11 Aug 2016 07:01:20 -0700 (PDT)
- To: kazu@iij.ad.jp, mike@belshe.com, fenix@google.com, martin.thomson@gmail.com
- Cc: aamelnikov@fastmail.fm, iesg@ietf.org, ietf-http-wg@w3.org, rfc-editor@rfc-editor.org
The following errata report has been held for document update 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=4720 -------------------------------------- Status: Held for Document Update Type: Editorial Reported by: Kazu Yamamoto <kazu@iij.ad.jp> Date Reported: 2016-06-27 Held by: Alexey Melnikov (IESG) Section: 8.2.1 Original Text ------------- Pushed responses are always associated with an explicit request from the client. The PUSH_PROMISE frames sent by the server are sent on that explicit request's stream. Corrected Text -------------- Promised requests are always associated with an explicit request from the client. The PUSH_PROMISE frames sent by the server are sent on that explicit request's stream. Notes ----- This section talks about promised requests, not pushed responses. Alexey: As per HTTPBIS WG discussion, this is correct in the original, but clearer in the proposed text. -------------------------------------- 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, 11 August 2016 14:01:50 UTC