Code change:
state (see HeaderBlock); similarly DATA frames MUST be counted toward the connection flow control window. <del> The GTFO frame does not define any flags. </del> <ins> The GOAWAY frame does not define any flags. </ins> <del> The GTFO frame applies to the connection, not a specific stream.  An endpoint MUST treat a </del> <ins> The GOAWAY frame applies to the connection, not a specific stream. An endpoint MUST treat a </ins> frame with a stream identifier other than 0x0 as a ConnectionErrorHandler of type . <del> The last stream identifier ("Last-Stream-ID") in the GTFO frame contains the highest numbered stream identifier for which the sender of the GTFO frame has received frames on and might have taken some action on.  All streams up to and including the identified stream might have been processed in some way.  The last stream identifier is set to 0 if no streams were processed. </del> <ins> The last stream identifier in the GOAWAY frame contains the highest numbered stream identifier for which the sender of the GOAWAY frame has received frames on and might have taken some action on.  All streams up to and including the identified stream might have been processed in some way.  The last stream identifier is set to 0 if no streams were processed. </ins> Note: In this case, "processed" means that some data from the stream was passed to some higher layer of software that might have taken some action as a result. <del> If a connection terminates without a GTFO frame, this value is </del> <ins> If a connection terminates without a GOAWAY frame, this value is </ins> effectively the highest stream identifier. On streams with lower or equal numbered identifiers that were not

Related discussion:
text: This is almost a straight revert of the various GOAWAY -> GTFO changes. It seems like this is the popular move as per the discussion on the httpbis mailing list. Arguments for the revert: GOAWAY is self-descriptive and serves it purpose well. Editorial changes that don't clearly improve the spec should be discouraged so we can reach a stable spec sooner (granted this change doesn't affect the wire at all, but documentation churn counts too). GTFO is crass and doesn't belong in internet standards. GTFO, if it really stands for "General Termination of Future Operations," has a surprising definition and may produce confusion. We should strive for absolute clarity above all else in editorial changes.
Boo! You guys are no fun.
goaway is just as bad as gtfo for the same reasons as the argument against gtfo... just called it disconnectclient or endcommunication if you're going to be a grumplestiltskin.
QUENCH may be a better, more descriptive word that has been used before in RFC's (for TCP Source Quench messages)
I think we should call it BIKESHED. , Sean McElroy EMAIL:
Here we go.. useless HN circle jerk.
:cat2:
How about STFU?
Boo!
:-1:
This commit should be reverted. It's time we stop behaving like oversensitive automatons and display the beautiful human quality that is a sense of humor every once in a while.
^ this
^ that
how about something like PLZSTOP? it's slightly humorous, but it actually reflects what is wanted (if I understood the spec correctly)
GOAWAY is clearer for non-native English speakers, easier to pronounce, and more professionally appropriate than the common connotational definition of GTFO. There are times and places for pushing the boundaries of professional speech, but the HTTP2 spec isn't one of them.
At least the pendulum didn't swing the other way NICETALKINGTOYOU
This revert is for the express purpose of stopping endless bikeshedding. We shouldn't encourage trivial changes to frame names. If the name is good enough, it should stay. I'm all for fun and games, but clarity and concision (as well as spec stability) come first.