- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Tue, 17 Nov 2015 09:20:40 -0800
- To: RFC Errata System <rfc-editor@rfc-editor.org>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>, erik@schnell-ahaus.de, mike@belshe.com, fenix@google.com, mnot@mnot.net, barryleiba@computer.org
- Message-ID: <CABkgnnVoWioeAXUPAtTtbE+MmW2KFenQF_K_Mm+zYwsz4Ubtdw@mail.gmail.com>
This appears to be a fairly common misunderstanding. PUSH_PROMISE is sent on one stream, but affects the state of the promised stream rather than the one it is sent on. On Nov 17, 2015 9:00 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=4535 > > -------------------------------------- > Type: Technical > Reported by: Erik Schnell <erik@schnell-ahaus.de> > > Section: GLOBAL > > Original Text > ------------- > > > Corrected Text > -------------- > > > Notes > ----- > Section 5.1 (fig. 2) and section 6.6 are contradictory. While the figure > in 5.1 shows a transition from \\"idle\\" to \\"reserved (local)\\" on a > PUSH_PROMISE receive, section 6.6 mentions: > \\"A sender MUST NOT send a PUSH_PROMISE on a stream unless that stream is > either \\"open\\" or \\"half-closed (remote)\\" > AND > \\"PUSH_PROMISE frames MUST only be sent on a peer-initiated stream that > is in either the \\"open\\" or \\"half-closed (remote)\\" state.\\" > > 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, 17 November 2015 17:21:10 UTC