Identifying streams more precisely

Two issues were raised about the use of the words "existing" and "current" to refer to streams.  These were a little squishy, so I tightened the language a little.  The text no longer uses either word to refer to streams, instead using stream states to describe where the relevant text applies and favouring "identified" as a fallback.
Dicey, apart from this little bit in [Section 8.2](http://http2.github.io/http2-spec/#PushResources):

> A client cannot push. Thus, servers MUST treat the receipt of a PUSH_PROMISE frame as a connection error (Section 5.4.1) of type PROTOCOL_ERROR. Clients MUST reject any attempt to change the SETTINGS_ENABLE_PUSH setting to a value other than 0 by treating the message as a connection error (Section 5.4.1) of type PROTOCOL_ERROR.