I'm surprised nobody has brought up that this was originally called GOAWAY in the spec, and that it was only renamed from GOAWAY to GTFO five days ago. It's no

I'm surprised nobody has brought up that this was originally called GOAWAY in the spec, and that it was only renamed from GOAWAY to GTFO five days ago. It's not like it was always named GTFO or that people are remotely attached to it. In fact, people involved in the process (ie, the working group mailing list) only heard about it after it was renamed. (I realise that's because this isn't a protocol-related issue, only a documentation one, but my argument is that there's no real impact in the change back.)