RFC 7540, "Hypertext Transfer Protocol Version 2 (HTTP/2)", May 2015Source of RFC: httpbis (app)
Errata ID: 4535
Status: Held for Document Update
Publication Format(s) : TEXT
Reported By: Erik Schnell
Date Reported: 2015-11-17
Held for Document Update by: Barry Leiba
Date Held: 2015-11-19
Section 5.1 says:
(content of Figure 2)
It should say:
(see notes, below)
Section 5.1 Figure 2 is unclear about what stream is being depicted when PUSH_PROMISE is used. The figure shows a transition from /idle/ to /reserved (local)/ on a PUSH_PROMISE receive, but Section 6.6 only allows PUSH_PROMISE to be sent on a stream that is in /open/ or /half-closed (remote)/ state. But these are talking about different streams.
A note should be added to figure 2 in section 5.1 clarifying that where a PUSH_PROMISE is sent or received, the state diagram is for the promised stream, not the original stream.