HTTP/2 is not client-speaks-first

Over on the HTTP WG mailing list, Patrick McManus points out that HTTP/2 over TLS is actually not a client-speaks-first protocol. Both parties can speak (and usually do) speak concurrently, and they get around breaking HTTP/1.x clients by negotiating with the h2 ALPN token.

This suggests that maybe this document should be more narrowly scoped to demuxing HTTP/1.x and stream-based DNS, which would make it simpler and would avoid adding any further implications or constraints against future versions of HTTP.